Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Paul_Woegerer@mentor.com (Woegerer, Paul)
Subject: [lttng-dev] Broken patch for a wrapping libdl
Date: Tue, 5 Nov 2013 09:27:40 +0100	[thread overview]
Message-ID: <5278ABFC.6050303@mentor.com> (raw)
In-Reply-To: <5277D16E.4080603@ericsson.com>

Hi Matthew,

I have a working solution for that (also based on LD_PRELOADing) as part
of my base address tracing stuff.
I'm going submit the whole patch series next week (hopefully).

Best,
Paul

On 11/04/2013 05:55 PM, Matthew Khouzam wrote:
> Hello tracing arch-wizards,
>
> I was working a bit on a trace with the cyg_profile stuff, and an issue
> that would arise is when you dynamically lync a library, you don't have
> it's name in the symbol tables of the executable, so you cannot nm it to
> have something human readable in the callstack.
>
> The easy solution is to wrap libdl, that way you get the handle of the
> lib i dlopen, and from that you get the function name in dlsym, it also
> handles seamlessly if a lib is closed, and another would replace the
> addresses used.
>
> The only problem is, it doesn't work and I don't have time to get it
> working (in the short term).
>
> I am posting this beginning idea to see if it generates any
> interest/solutions.
>
> Hope this works out,
>
> Matthew
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev


-- 
Paul Woegerer, SW Development Engineer
Sourcery Analyzer <http://go.mentor.com/sourceryanalyzer>
Mentor Graphics, Embedded Software Division




      reply	other threads:[~2013-11-05  8:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 16:55 Matthew Khouzam
2013-11-05  8:27 ` Woegerer, Paul [this message]

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=5278ABFC.6050303@mentor.com \
    --to=paul_woegerer@mentor.com \
    /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