wait for debugger problem

[earlevel]

I've built a LabView application on a Mac G5 system and want to test it another system with just the LabView runtime. The other system is an intel-based MacBook Pro, so I strip the universal part (using make PowerPC Only.vi), because at this point I don't want to install the entire LabView system. The app runs on the MacBook Pro and displays the application window and graphics fine, but quits a few seconds, during initialization. That's not surprising--I'm it calls some custom libraries, and those haven't been debugger for x86 yet. At this point, I'd only like to have an idea of where it is failing and quitting (quietly--no message of any kind).

So, it looks like I can debug it remotely from my other Mac. I build the with debugging and "wait for debugger on launch". It seems to heed these requests, as the application is considerably larger than when built without.

However, when I launch the application on the MacBook Pro, it does not wait--it goes ahead and starts running, and quits in the same place. I never have a chance to attach the debugger to it.

Am I misunderstanding the process?

[Amanda_H]

Hi,

Here are some things we can try:
1. Build the executable on MacBook Pro, or
2. Remove the debugging functionality.

Since the MacBook Pro has an Intel-based chipset and the Mac G5 is PowerPC-based, the debugging functions are implemented differently.

I am researching this further and will let you know if I find any more information.

[earlevel]

>1. Build the executable on MacBook Pro, or

Ultimately, of course, I will do that. In this case though, I wanted to work with only the runtime install on a virgin system. We had a show starting (AES) and I was attempting to confirm that I was giving the folks at the show the files required to get their machine (G5) up and running in NY. (As it turned out, the package I supplied didn't run, but I suspected right off that ni-visa was not working, and quickly figured out that a separate ni-visa installer was needed, got that to them and they were in business.) The only reason I was using an Intel machine here, at this point, was that it was my only other Mac to try the runtime install on.