> I strongly suggest to only build Python with -O0 when using gdb. -Og > enables too many optimizations which makes gdb less usable.
Thanks, Victor. It never made sense to me that you would want any optimizations enabled when truly debugging code (as opposed to wanting debug symbols and a sane traceback in production code). I'm getting more convinced that the problem I'm seeing is a GCC/GDB thing, particularly because I can move the erroneous stopping point by changing the GCC optimization level. I'll probably open a bugzilla report just so it's on that team's radar screen. In the meantime, to get going again I wrote a crude script which maps the file:function:label form to file:linenumber form. That way I can save/restore breakpoints across GDB sessions and still avoid problems when the offsets to specific instructions change. Skip Skip _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/AOKKJHCRLEYU64V425AJHMM46CCYW55M/ Code of Conduct: http://python.org/psf/codeofconduct/
