Debug build to analyze core dumps ?
How do I build with debug symbols (i.e. -g) so that I can inspect core dumps when you get a traceback like this ?Do you always recompile with pypy ../../rpython/bin/rpython --opt=jit ? RPython traceback: File "implement_11.c", line 5310, in fastfunc_enable_1 File "rpython_rlib_rvtune.c", line 1761, in VTune_enable File "rpython_rlib_rvtune.c", line 2205, in gather_all_code_objs_1 File "rpython_rlib_rvtune.c", line 534, in VTune__write_code_registrationFatal RPython error: AssertionErrorAborted (core dumped)
Though I'm still curious about how to get debug builds so far the core dumps I've experienced are prettyeasy to root-cause. Attaching gdb seems overkill. On Thursday, December 29, 2016 9:14 AM, Shubha Ramani <shubharamani@yahoo.com> wrote: How do I build with debug symbols (i.e. -g) so that I can inspect core dumps when you get a traceback like this ?Do you always recompile with pypy ../../rpython/bin/rpython --opt=jit ? RPython traceback: File "implement_11.c", line 5310, in fastfunc_enable_1 File "rpython_rlib_rvtune.c", line 1761, in VTune_enable File "rpython_rlib_rvtune.c", line 2205, in gather_all_code_objs_1 File "rpython_rlib_rvtune.c", line 534, in VTune__write_code_registrationFatal RPython error: AssertionErrorAborted (core dumped)
Hi Shubha, On 29 December 2016 at 22:42, Shubha Ramani via pypy-dev <pypy-dev@python.org> wrote:
How do I build with debug symbols (i.e. -g) so that I can inspect core dumps when you get a traceback like this ?
Run "make clean; make lldebug" in the directory containing the generated C sources (.../usession-xyz/testing_1). A bientôt, Armin.
participants (2)
-
Armin Rigo -
Shubha Ramani