This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: userspace probe breakage with gcc 4.8 due to inablility to locate semaphore variable
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Mayuresh Kulkarni <mkulkarni at kcg dot com>
- Cc: "'systemtap at sourceware dot org'" <systemtap at sourceware dot org>
- Date: Mon, 20 Apr 2015 16:06:40 -0400
- Subject: Re: userspace probe breakage with gcc 4.8 due to inablility to locate semaphore variable
- Authentication-results: sourceware.org; auth=none
- References: <6ffd4403306349259c75f458f6941a53 at CMKWSCTSMAIL02 dot kcg dot com> <fe9fee0f48a741a2badfe5c436c0aef7 at CMKWSCTSMAIL02 dot kcg dot com> <y0m618wtadx dot fsf at fche dot csb> <c6f64d1c02c743129e3948e7338660d5 at CMKWSCTSMAIL02 dot kcg dot com>
mkulkarni wrote:
>
[...]
> Meanwhile, in my setup, I have found out that the runtime box has
> native gcc 4.4 And the regression is because the build uses gcc 4.8
> (which uses dwarf4 by default)
Why do you think so? stap works fine here on that version of gcc, and
older, and newer. Can you forward your full gcc/stap/elfutils/kernel
versions, and perhaps a binary (compiled with your gcc 4.8) that was
giving stap a hard time?
- FChE