Thanks for the suggestion Luc, I looked at the disassembly around the break point address and it was all straight line code. I could not see a way that the breakpoint should not be triggered.
Regarding optimisation I ran configure with the --compile-type=debug flag, I will have to check what opt level that uses, but I don't think that is what is causing the problem. Roger > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Luc Gallant > Sent: 13 October 2005 01:10 > To: [email protected] > Subject: [mythtv] Dumb slightly off topic question > > One thing you have to watch out for with the debugger, and I found this > out the > hard way. If the code is optimized (O1, O2, O3), the debugger will not > follow > exactly. Try compiling without optimizations. Another thing you can try is > to > put fprintf statements around the lines you want (put like 3 statements > before > and 3 after) and it will occasionally cause the code not to compile > optimized > there, sometimes allowing you to use the debugger better. > > Try that, let us know. > > Luc Gallant > > > > ---------------------------------------- > This mail sent through www.mywaterloo.ca > _______________________________________________ > mythtv-dev mailing list > [email protected] > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
_______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
