Created attachment 10580 [details] gdb.log generated when running the test I've been meaning to file this bug for a while now. Unfortunately gdb.base/dtrace-probe.exp is not working anymore. I cannot really say when was the last time it worked, but I remember seeing reports of compilation failures for quite some time on BuildBot. I am attaching the gdb.log generated when I run "make check-gdb TESTS=gdb.base/dtrace-probe.exp" on my x86_64 Fedora 26 machine. I also took the liberty to add Jose Marchesi to the Cc list, since he is the original author of the test infrastructure for DTrace probes.
I have a patch for this.
(In reply to Sergio Durigan Junior from comment #1) > I have a patch for this. Well, it turns out the patch doesn't work... I was passing extra options to the 'strip' program in order to prevent the removal of 'main' and '.eh_frame' symbols. ${STRIP} -R .eh_frame -K main ... This "works" in the sense that the compilation succeeds, but there is clearly something else that needs to be done because I now see a regression that constantly happens: 133 print $_probe_arg0 134 $2 = 0x0 135 (gdb) FAIL: gdb.base/dtrace-probe.exp: print $_probe_arg0 for probe progress-counter As was discussed in PR 22557, this impacts the testing ability of the DTrace probe support on GDB.