This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug testsuite/22420] gdb.base/dtrace-probe.exp not working (as in "not able to run")
- From: "sergiodj at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 11 Dec 2017 20:59:58 +0000
- Subject: [Bug testsuite/22420] gdb.base/dtrace-probe.exp not working (as in "not able to run")
- Auto-submitted: auto-generated
- References: <bug-22420-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22420
--- Comment #2 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
(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.
--
You are receiving this mail because:
You are on the CC list for the bug.