This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: operation and limitations of dladdr()?

From: Mike Frysinger <vapier at gentoo dot org>
To: britton dot kerin at gmail dot com
Cc: libc-help at sourceware dot org
Date: Sat, 9 Apr 2016 22:48:25 -0400
Subject: Re: operation and limitations of dladdr()?
Authentication-results: sourceware.org; auth=none
References: <CAC4O8c_Xudck=j4svT_2qAQJYJf3YMF2ksM5_Vg9GC8BJ5zhZw at mail dot gmail dot com> <CAE2sS1go9qMC_q_d=Lq9-zPe8hFn5wDNDWbdSLnTcttJO2Nm8A at mail dot gmail dot com>

On 30 Mar 2016 09:22, Carlos O'Donell wrote:
> On Tue, Mar 29, 2016 at 4:27 PM, Britton Kerin wrote:
> > I'm trying to learn as much as possible about dladdr() before
> > unleashing a small lib that uses it on the world.  Two questions:
> >
> > Does the fact that dladdr() reports the symbol with the nearest
> > address lower than the given
> > one mean that that might be the correct function?
> 
> I don't quite follow exactly what you're trying to ask.
> 
> So let me clarify a few things.
> 
> (a) The input argument to dladdr can be any address. There is no
> restriction placed on the void *.

one scenario where this is useful is when you have addresses in the
middle of a function.  consider a signal coming in and you want to
know where.
-mike

Attachment: signature.asc
Description: Digital signature

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]