TweetFollow Us on Twitter

Debugging Tips
Volume Number:10
Issue Number:5
Column Tag:PowerPC Series

Related Info: Memory Manager Dialog Manager

Debugging Tips for Mixed Mode

So that’s what I’m looking at when I crash!

By Dave Falkenburg, Apple Computer, Inc.

Note: Source code files accompanying article are located on MacTech CD-ROM or source code disks.

About the author

For having such short legs, Dave runs well - he’s part of the team which just shipped Power Macintosh in record time. As keeper of the secrets of the Process Manager, he’s something of a nexus for the myriad parts of the Macintosh which all seem to come together in that cauldron of code, a veritable witch’s brew of bat wings and furless pets. Among other accomplishments, he’s the guy who gave Ron Avitzur his first PowerPC 601 book.

When writing for Power Macs...

You’ll need several tools. The obvious ones are a Power Macintosh and a development environment. Also handy, and not so obvious, are some bits and pieces. develop Issue #17 contains the dis dcmd. ETO #13 and recent developer CDs have MacsBug 6.5d6 (or later), and it has support for the new Power Macintosh Memory Manager.

When developing native applications for the Power Macintosh family, it’s pretty likely that you will stumble upon bugs which get introduced due to misuse of Mixed Mode Universal Procedure Pointers (UPPs).

Both the calling conventions and instruction set of any function are encoded within a data structure when that function has been “wrapped” by a UPP - two essential details which Mixed Mode needs in order to make your applications and plug-in modules work without knowing the sordid details of the emulator.

In the 68K Macintosh world, parameters to functions generally go on the stack or in registers, or sometimes both. PowerPC code generally puts all parameters in registers. On 68K, Pascal and C also have different calling conventions- each language passes parameters in the reverse order of it’s peer, and Pascal also insists on the callee cleaning up parameters. PowerPC has a single calling convention, which Mixed Mode will happily deal with.

Another important point is that PowerPC ProcPtrs aren’t pointers to code, but in fact, point at a data structure called a transition vector. This essentially makes them “ProcHandles”. We can take advantage of that when we diagnose crashes.

Another essential thing we rely on is the fact that the PowerPC and 680x0 instruction sets aren’t very similar - if you are looking at some sort of code in MacsBug, il <address> or dis <address> will probably tell you what kind of code you are looking at. For example, if we look at 680x0 code with dis, we will see something like the following.

dis 00142028
 00142028
 00142028 **undefined**   | 4e754e56
 0014202c **undefined**   | fffc48e7
 00142030 twi TO_LT|TO_GT,23622098,0x2a2e    | 0f082a2e
 00142034 **undefined**   | 000c286e
 00142038 **undefined**   | 0010382e
 0014203c **undefined**   | 0014200d
 00142040 subfic  r16,r21,0x2a78   | 22152a78
 00142044 **undefined**   | 0b7c2a81
 

The same code as viewed with il looks more familiar:

il 0014202A
 +15DA  0014202A LINKA6,#$FFFC| 4E56 FFFC
 +15DE  0014202E MOVEM.L  D4-D7/A4,-(A7)     | 48E7 0F08
 +15E2  00142032 MOVE.L   $000C(A6),D5 | 2A2E 000C
 +15E6  00142036 MOVEA.L  $0010(A6),A4 | 286E 0010
 +15EA  0014203A MOVE.W   $0014(A6),D4 | 382E 0014
 +15EE  0014203E MOVE.L   A5,D0    | 200D

If you aren’t already familiar with the Mixed Mode Manager or the PowerPC Runtime Architecture, you’ll might want to read more about it in Inside Macintosh: RISC System Software before reading on.

UPP Basics

Emulated code can always call UPPs “blindly”, that is, without needing to use CallUniversalProc.

This was a necessary design principle for the emulator, because older applications, and large portions of the Macintosh Toolbox have no idea they are running on a PowerPC 601 microprocessor most of the time. JSR-ing through a UPP essentially executes a trap instruction which transfers control to Mixed Mode. Mixed Mode converts parameters, calls the PowerPC subroutine, and the returns to the emulated caller after translating the result code.

This may seem like magic, but is actually more mundane than mysterious. A UPP data structure starts with a trap (0xAAFE, a.k.a. _MixedModeMagic). When you’re executing 68K code, and it JSRs through a UPP, the trap gets handled by Mixed Mode. Mixed Mode checks the rest of the data structure to figure out whether it’s 68K code, PowerPC code, or both. Mixed Mode then transfers control to the destination code, moving parameters from one mode to the other. So it might move 68K registers and/or stack arguments into PowerPC registers, or vice versa. What gets moved depends on the contents of the procInfo, a data structure which describes where parameters live, and where they should go.

PowerPC code must always use CallUniversalProc to call code which was passed as a ProcPtr of unknown type. All code which doesn’t look like a UPP is assumed to be 68K code. This allows a PowerPC-based Dialog Manager to automatically call a ModalFilterProc regardless of whether or not the application is 68K code or PowerPC code.

Mixed Mode relies on the procInfo field in order to convert parameters and function result.

The biggest opportunity for making a mistake is in the creation of procInfo values. Much of the work has been done for you by Apple engineers in the Universal Headers. They defined constants and CallXXXProc macros for most of the Toolbox and OS routines which accept a ProcPtr, and it’s far more trouble-free to use them than to create your own.

UPP Symptoms

We’ll discuss the problems you can stumble across by breaking down the three major cases that Mixed Mode must deal with:
68K -> PowerPC, PowerPC -> 68K, and PowerPC -> PowerPC.

In almost all cases, a bad procInfo value is usually fatal, and very difficult to debug. Your program’s stack can be completely munged beyond all repair. It’s far easier to check your procInfos up front than to debug a bad one at run time! Always use the uppXXX, NewXXXProc, and CallXXXProc macros in the Universal Headers to keep you from screwing this up.

Bad procInfo values usually show up as either a crash with the PC pointing two bytes into the RoutineDescriptor data structure, or as mysterious crashes which have unexplained side effects. Remember those Macintosh 128K crashes when you accidentally slammed into the sound/disk pages? You won’t have any easier of a time figuring out how you got there, and you don’t even get to see the technicolor snowcrash or hear the machine-gun sounds.

Here are a variety of situations where something can go wrong. I’ll treat each one separately.

Calling from 68K to PowerPC

Problem: Calling a PowerPC ProcPtr that hasn’t been wrapped in a UPP.

You will see a 68K illegal instruction, and the PC will be somewhere in code where every third longword is a zero.

What’s happening is that Mixed Mode never got the chance to switch modes for you, so you’re still trying to execute this code with the 68K emulator. That’s eventually going to generate an error, because the PowerPC instruction set is so different from the 68K instruction set. You can tell if this is what happened by doing a dis PC^ in MacsBug. You’ll need the dis dcmd that came with develop Issue #17, or future developer CDs. If you see something like “mflr r0” then this is probably what happened.

Problem: Calling a UPP with a bad procInfo

Check your procInfos, because bad ones will almost always get you. I’ve told you this already, and Imay repeat it a time or two. Check out Inside Macintosh: RISC System Software, or <MixedMode.h> for information about creating procInfo values.

Calling from PowerPC to 68K

Problem: Calling 68K code as PowerPC code (i.e. you forgot to use CallUniversalProc)

This will manifest itself as a “spurious interrupt” or “bus error” in older versions of MacsBug. This usually turns up as a random jump into space. Remember that PowerPC ProcPtrs are really ProcHandles and the caller will actually dereference your “LINK #-xx,A6” and try to use it as a pointer.

Take a look at your PC. Are you executing in the 0x4E560000 to 0x4E56FFFF range? If you are, odds are good that you did a jump into what turns out to have been a LINK instruction which was incorrectly treated as an address. LINK’s opcode is 0x4E56.

Problem: Calling a UPP with a bad procInfo

Check your procInfos. An incorrectly-formed procInfo will get you. It is OK to call 68K code directly with CallUniversalProc. That’s because anything that doesn’t begin with the MixedMode trap instruction is assumed to be 68K code, and that particular instruction was carefully chosen to not be a likely value to hit by accident.

Calling from PowerPC to PowerPC

I bet you didn’t think of this case. It arises when a PowerPC-based manager must support both emulated callers, and PowerPC callers.

Problem: Calling a UPP without CallUniversalProc from PowerPC Code

All routine descriptors start with 0xAAFE, which is not only a trap, but also an illegal instruction for the PowerPC microprocessor.

This will manifest itself as either a PowerPC Illegal Instruction (a.k.a. spurious interrupt, for you MacsBug fans) or bus error depending on what is going on inside Mixed Mode at the time. This is similar to the Calling 68K code as PowerPC code above. If you get an illegal instruction, you can try doing a dm PC-2 and see if you find an 0xAAFE hanging around.

Problem: Calling a PowerPC procPtr as if it were a UPP

This case is pretty easy to spot - you will die in MacsBug with a 68K illegal instruction error. If you do a dis PC (using those wonderful PowerPC dcmds), you can see that the emulator is running, but for some reason the PC is pointing at “mflr r0” and something like “lwz r3,10(r1)”, two things a 680x0 emulator doesn’t know how to do!

Problem: Calling a routine descriptor with a bad procInfo

Check your procInfos. Got the idea?

More tips and tricks

When developing native applications for Power Macintosh, try to do the following things to avoid getting into the trouble described above.

• Source level debugging and single stepping are your friends - become familiar with one of the PowerPC-capable debuggers: CodeWarrior, Macintosh Debugger for PowerPC, or Jasik’s Debugger. Keep your eyes open for others, as well.

• Try to understand everywhere you use ProcPtrs in your code. This is where all those seemingly useless naming conventions we all use really pay off, like naming call function pointers XXXProcPtr, or all global variables gXXX.

• Use the macros provided by in the Universal Headers to avoid botching procInfos. You can also make your code “universal” by using these macros. That means that you can compile for 68K or PowerPC without any further modification of your source code.

Remember, you don’t need to use UPPs internally within your application if the code type is always known - UPPs are only needed when code can be called from either side of the mixed mode boundary. Supporting both emulated and PowerPC plug in modules is a good example of when to use a UPP.

Happy debugging!

For more information on items mentioned above:

CodeWarrior - a development environment from Metrowerks for both 68K and PowerPC, and it runs native on either platform. Available from the Mail Order Store. See page 89 for details, or call 310/575-4343.

Macintosh Debugger for PowerPC - a two-machine debugger from Apple. Requires one Power Macintosh (to debug) and any other Macintosh to do the driving.

Jasik’s Debugger - a two-headed debugger from Steve Jasik, famous for his personal support. Available from the Mail Order Store. See page 89 for details, or call 310/575-4343. Jasik Designs may be reached at 415/322-1386.

dis dcmd - develop Issue #17, available from Apple.

Debugging On PowerPC, by Dave Falkenburg and Brian Topping - develop Issue #17, available from Apple.

MacsBug 6.5d6 - ETO #13 and recent developer CDs.

 

Community Search:
MacTech Search:

Software Updates via MacUpdate

Latest Forum Discussions

See All

Six fantastic ways to spend National Vid...
As if anyone needed an excuse to play games today, I am about to give you one: it is National Video Games Day. A day for us to play games, like we no doubt do every day. Let’s not look a gift horse in the mouth. Instead, feast your eyes on this... | Read more »
Old School RuneScape players turn out in...
The sheer leap in technological advancements in our lifetime has been mind-blowing. We went from Commodore 64s to VR glasses in what feels like a heartbeat, but more importantly, the internet. It can be a dark mess, but it also brought hundreds of... | Read more »
Today's Best Mobile Game Discounts...
Every day, we pick out a curated list of the best mobile discounts on the App Store and post them here. This list won't be comprehensive, but it every game on it is recommended. Feel free to check out the coverage we did on them in the links below... | Read more »
Nintendo and The Pokémon Company's...
Unless you have been living under a rock, you know that Nintendo has been locked in an epic battle with Pocketpair, creator of the obvious Pokémon rip-off Palworld. Nintendo often resorts to legal retaliation at the drop of a hat, but it seems this... | Read more »
Apple exclusive mobile games don’t make...
If you are a gamer on phones, no doubt you have been as distressed as I am on one huge sticking point: exclusivity. For years, Xbox and PlayStation have done battle, and before this was the Sega Genesis and the Nintendo NES. On console, it makes... | Read more »
Regionally exclusive events make no sens...
Last week, over on our sister site AppSpy, I babbled excitedly about the Pokémon GO Safari Days event. You can get nine Eevees with an explorer hat per day. Or, can you? Specifically, you, reader. Do you have the time or funds to possibly fly for... | Read more »
As Jon Bellamy defends his choice to can...
Back in March, Jagex announced the appointment of a new CEO, Jon Bellamy. Mr Bellamy then decided to almost immediately paint a huge target on his back by cancelling the Runescapes Pride event. This led to widespread condemnation about his perceived... | Read more »
Marvel Contest of Champions adds two mor...
When I saw the latest two Marvel Contest of Champions characters, I scoffed. Mr Knight and Silver Samurai, thought I, they are running out of good choices. Then I realised no, I was being far too cynical. This is one of the things that games do best... | Read more »
Grass is green, and water is wet: Pokémo...
It must be a day that ends in Y, because Pokémon Trading Card Game Pocket has kicked off its Zoroark Drop Event. Here you can get a promo version of another card, and look forward to the next Wonder Pick Event and the next Mass Outbreak that will be... | Read more »
Enter the Gungeon review
It took me a minute to get around to reviewing this game for a couple of very good reasons. The first is that Enter the Gungeon's style of roguelike bullet-hell action is teetering on the edge of being straight-up malicious, which made getting... | Read more »

Price Scanner via MacPrices.net

Take $150 off every Apple 11-inch M3 iPad Air
Amazon is offering a $150 discount on 11-inch M3 WiFi iPad Airs right now. Shipping is free: – 11″ 128GB M3 WiFi iPad Air: $449, $150 off – 11″ 256GB M3 WiFi iPad Air: $549, $150 off – 11″ 512GB M3... Read more
Apple iPad minis back on sale for $100 off MS...
Amazon is offering $100 discounts (up to 20% off) on Apple’s newest 2024 WiFi iPad minis, each with free shipping. These are the lowest prices available for new minis among the Apple retailers we... Read more
Apple’s 16-inch M4 Max MacBook Pros are on sa...
Amazon has 16-inch M4 Max MacBook Pros (Silver and Black colors) on sale for up to $410 off Apple’s MSRP right now. Shipping is free. Be sure to select Amazon as the seller, rather than a third-party... Read more
Red Pocket Mobile is offering a $150 rebate o...
Red Pocket Mobile has new Apple iPhone 17’s on sale for $150 off MSRP when you switch and open up a new line of service. Red Pocket Mobile is a nationwide MVNO using all the major wireless carrier... Read more
Switch to Verizon, and get any iPhone 16 for...
With yesterday’s introduction of the new iPhone 17 models, Verizon responded by running “on us” promos across much of the iPhone 16 lineup: iPhone 16 and 16 Plus show as $0/mo for 36 months with bill... Read more
Here is a summary of the new features in Appl...
Apple’s September 2025 event introduced major updates across its most popular product lines, focusing on health, performance, and design breakthroughs. The AirPods Pro 3 now feature best-in-class... Read more
Apple’s Smartphone Lineup Could Use A Touch o...
COMMENTARY – Whatever happened to the old adage, “less is more”? Apple’s smartphone lineup. — which is due for its annual refresh either this month or next (possibly at an Apple Event on September 9... Read more
Take $50 off every 11th-generation A16 WiFi i...
Amazon has Apple’s 11th-generation A16 WiFi iPads in stock on sale for $50 off MSRP right now. Shipping is free: – 11″ 11th-generation 128GB WiFi iPads: $299 $50 off MSRP – 11″ 11th-generation 256GB... Read more
Sunday Sale: 14-inch M4 MacBook Pros for up t...
Don’t pay full price! Amazon has Apple’s 14-inch M4 MacBook Pros (Silver and Black colors) on sale for up to $220 off MSRP right now. Shipping is free. Be sure to select Amazon as the seller, rather... Read more
Mac mini with M4 Pro CPU back on sale for $12...
B&H Photo has Apple’s Mac mini with the M4 Pro CPU back on sale for $1259, $140 off MSRP. B&H offers free 1-2 day shipping to most US addresses: – Mac mini M4 Pro CPU (24GB/512GB): $1259, $... Read more

Jobs Board

All contents are Copyright 1984-2011 by Xplain Corporation. All rights reserved. Theme designed by Icreon.