the gdb, as said before hangs, i.e, no input prompt apears. the gdb porxy output is EXACT as shown above. and, the debug session is successful if it is debugged step-by-step, i.e. debug information in image is ok.
2007/6/16, Christian Böhme <[email protected]>:
matthias fend wrote: > sometimes i can step trough some lines of code without having > problems and sometimes gdb proxy starts with the -1 steps output - (yes > - it's the same code). > > if gdb proxy has started with this behaviour it will loop there forever. Again, what's the _exact_ output when you interrupt it while looping/ spinning ? If GDB knows where it's at then it's certainly in your program. If, OTOH, GDB lost its mind on where in the execution sequence it was interrupted, the GDB-Proxy combo is to blame for it (provided you're producing debug object files). Christian ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
-- _____________ Oleg V. Kobrin
