Re: [Valgrind-developers] Segmentation fault when debugging Valgrind under GDB

[Jefferson C. <jef...@gm...>]

Wow, thanks for the quick reply! :)

On 10/5/2019 3:43 AM, John Reiser wrote:
> On which hardware architecture and operating system?

x86_64, linux

> With which compiler?

gcc (Gentoo 8.3.0-r1 p1.1) 8.3.0

> 
> The *runtime* auto-configuration code (detect which CPU variant
> and its hardware properties) might generate several signals including 
> SIGSEGV.
> 
> Figure out why gdb is not showing symbols in the backtrace,
> then get beyond the runtime configuration before complaining.

The reason the backtrace is truncated is because of some of the 
vgPlain_disp_run_translations code - the pushq instructions 
progressively garble the backtrace that gdb is able to report.  However 
the segfault is certainly at dispatch-amd64-linux.S:111.  I'll try to 
figure out why this jump doesn't work.