From: Mark Wielaard <mjw@redhat.com>
To: systemtap@sourceware.org
Subject: Re: Making the transport layer more robust
Date: Wed, 20 Jul 2011 14:13:00 -0000 [thread overview]
Message-ID: <1311171165.5022.2.camel@springer.wildebeest.org> (raw)
In-Reply-To: <1311065908.9144.27.camel@springer.wildebeest.org>
On Tue, 2011-07-19 at 10:58 +0200, Mark Wielaard wrote:
> I am still investigating the test results on
> rhel5, they don't look that good (in particular exelib.exp fails a lot
> of tests because it is unable to find process.mark probe points)
Finally tracked this down to an old binutils bug... sigh. When I finally
knew what it was, the fix was was easy. With this all the 188 exelib.exp
tests PASS also on rhel5 based systems.
Cheers,
Mark
commit 1189063f8adaa13e2da16b51ab665663497ac102
Author: Mark Wielaard <mjw@redhat.com>
Date: Wed Jul 20 16:05:31 2011 +0200
Always look for .note.stapsdt sections in the main elf file.
In dwflpp::iterate_over_notes we really want the actual elf file,
not the dwarf .debug file. Older binutils had a bug where they
mangled the SHT_NOTE type during --keep-debug.
diff --git a/dwflpp.cxx b/dwflpp.cxx
index fcc142b..2ab8772 100644
--- a/dwflpp.cxx
+++ b/dwflpp.cxx
@@ -1007,8 +1007,10 @@ int
dwflpp::iterate_over_notes (void *object, void (*callback)(void *object, int type, const char *data, size_t len))
{
Dwarf_Addr bias;
- Elf* elf = (dwarf_getelf (dwfl_module_getdwarf (module, &bias))
- ?: dwfl_module_getelf (module, &bias));
+ // Note we really want the actual elf file, not the dwarf .debug file.
+ // Older binutils had a bug where they mangled the SHT_NOTE type during
+ // --keep-debug.
+ Elf* elf = dwfl_module_getelf (module, &bias);
size_t shstrndx;
if (elf_getshdrstrndx (elf, &shstrndx))
return elf_errno();
next prev parent reply other threads:[~2011-07-20 14:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 8:59 Mark Wielaard
2011-07-19 11:42 ` Mark Wielaard
2011-07-19 15:03 ` Mark Wielaard
2011-07-20 8:29 ` Mark Wielaard
2011-07-19 15:05 ` William Cohen
2011-07-20 14:13 ` Mark Wielaard [this message]
2011-07-21 17:18 ` David Smith
2011-08-12 17:43 ` Mark Wielaard
2011-08-15 8:24 ` Mark Wielaard
2011-08-15 18:30 ` Josh Stone
2011-08-16 13:23 ` Mark Wielaard
2011-08-25 12:12 ` Turgis, Frederic
2011-08-26 15:45 ` Turgis, Frederic
2011-08-26 18:45 ` Frank Ch. Eigler
2011-08-29 8:32 ` Turgis, Frederic
2011-08-29 11:21 ` Frank Ch. Eigler
2011-08-29 14:46 ` Frank Ch. Eigler
2011-08-30 13:20 ` Turgis, Frederic
2011-09-05 11:27 ` Mark Wielaard
2011-09-05 14:32 ` Turgis, Frederic
[not found] ` <13872098A06B02418CF379A158C0F1460163182604@dnce02.ent.ti.com>
2011-09-06 10:12 ` Mark Wielaard
2011-09-06 14:30 ` Turgis, Frederic
2011-09-06 14:37 ` David Smith
2011-09-06 15:37 ` David Smith
2011-09-06 16:25 ` Turgis, Frederic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1311171165.5022.2.camel@springer.wildebeest.org \
--to=mjw@redhat.com \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).