Charles, thanks for the reply, I would prefer not to ;<) But I don't see how this would help. What I need is a way to record all lines of code executed between two breakpoints. Is this possible?
Thanks, Paul Charles Manning-2 wrote: > > On Saturday 16 October 2010 02:28:45 ppmoore wrote: >> Hello, >> >> I'm trying to track down a strange bug that has all of us stumped. >> >> I set a breakpoint at a point in the code, and start the program. >> The breakpoint is reached and the program stops. >> When I try step over the breakpoint to the next line of code, GDB >> immediately indicates that the program executed normally, the intervening >> lines of code are not executed. > > Have you considered using assembler instruction level stepping? >> >> To track it down, I would like to do record lines of code executed. >> Something like the following: >> - set the breakpoint as mentioned above, and start the program >> - the breakpoint is reached >> - set a breakpoint at exit(), and then somehow record all lines of code >> executed up to the point where the program exits >> - when the exit() breakpoint is reached, examine the recorded trace of >> the >> program execution, line by line. AFAIK, the trace command can't do this. >> >> Is this possible? >> >> Many thanks, >> Paul > > > > > -- View this message in context: http://old.nabble.com/Possible-to-record-program-execution-tp29971548p29989599.html Sent from the Gnu - gdb - General mailing list archive at Nabble.com.