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
