This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Debugging GDB and breaking?


Hello

I'm debugging the GDB with the GDB - Not to catch a bug, but to investigate 
what's going on. In that case I wan't to step through everything the GDB does 
when just working with it manualy. Where I am now, I've loaded a file into the 
GDB being debugged, and I want the other GDB to take over, so I can see what 
happens, when the GDB actually sets a breakpoint in this small testprogram. 
But when I type e.g. "break main", the control never goes back to the other 
GDB, so I can't see what's going on.
Isn't there a command to issue a breakpoint at the next line of code instead 
of a obsolute position (name, address)?

Or could someone tell me where to look in the source code for the functions 
which places a breakpoint?.

Best Regards
James
						


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]