Yes, I had compiled with the '-g' option Another possibility I discovered is to use the "record" option for reverse debugging, described here: http://sourceforge.net/projects/record/ http://sourceforge.net/projects/record/ http://sourceware.org/gdb/wiki/ProcessRecord/Tutorial http://sourceware.org/gdb/wiki/ProcessRecord/Tutorial I tried it out, but it didn't work. I have the impression that it is still in its early development stages.
>> Did you compile with -g? >> I think that is the most common reason for this behavior. >> It is possible, though not readily, depending on what you want to trace. >> The simplest thing is: >> while 1 >> step >> end -- View this message in context: http://old.nabble.com/Possible-to-record-program-execution-tp29971548p30036863.html Sent from the Gnu - gdb - General mailing list archive at Nabble.com.
