Thanks for the reply, Layne, but as far as I can tell, the built-in GDB commands don't solve this problem. GDB has a "commands" command which allows you to automate what happens after a breakpoint is reached. However, when an app compiled with "-g" is launched, there is no breakpoint. Instead, GDB receives a SIGSTOP signal from the simulator. I am unaware of any GDB commands to automate the response to a SIGSTOP. If anyone knows of a way to do this, or to allow GDB to "break in" to a running simulator, please let me know.
Thanks... Dave "Layne Lund" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > I am a very new gdb user. However, I know you can automate some of the debugging tasks. For one thing, you can create commands that execute when a breakpoint is reached and then have it print out information, such as data values, and then it can continue. I don't have my reference books handy, so I apologize for being unable to give you any more details. I suspect that if you use this technique, you can find the exact values of input that cause the crash so you can run through them manually instead of waiting for a gremlin to do it instead. > > HTH > > Layne > > ----- Original Message ----- > From: "David M. Lasker" <[EMAIL PROTECTED]> > Date: Monday, September 22, 2003 4:10 pm > Subject: Need advice on how to debug simulator crash when running gremlins > > > My application causes PalmSim to crash when running gremlins. Yes, I > > know the bug is in my app, not in PalmSim. > > > > When I stop gremlins at the event just before the crash, I can see > > thatmy app is all screwed up. I am pulling out my hair trying to > > debug this. > > Unfortunately the problem does not occur with POSE, only with PalmSim. > > > > I am using prc-tools w/gdb. > > > > Here are some more details: > > > > 1) If I exit and restart my app to get gdb to stop at PilotMain, the > > problem goes away. > > > > 2) If I attach GDB prior to running gremlins, I get a bezillion stops > > entering PilotMain as gremlins repeatedly runs the find command. Note > > that my bug involves use of the find command, so I can't turn it off. > > > > Question: is there any way to stop gdb from breaking at PilotMain and > > still be able to use it to debug the app? Maybe by turning off the > > gdbSfeature after my app's initial startup??? > > > > 3) I'm willing to debug with PalmDebugger, but I can't figure out > > how to > > attach it to PalmSim. PalmDebugger works fine with POSE, but when > > I try > > to attach it to PalmSim I get error "CmdGetRemoteState: error in > > SlkReceivePacket = Serial Link timeout." Connection is set to > > "Emulator". > > > > Question: Is there a way to use PalmDebugger with PalmSim??? > > > > Any ideas on how to attack this would be appreciated. > > > > Thanks... > > > > Dave > > > > > > -- > > For information on using the Palm Developer Forums, or to > > unsubscribe, please see http://www.palmos.com/dev/support/forums/ > > > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
