* info shar vs. /proc/*/maps
@ 2005-03-17 2:13 Michael L. Artz
2005-03-17 3:47 ` Daniel Jacobowitz
0 siblings, 1 reply; 2+ messages in thread
From: Michael L. Artz @ 2005-03-17 2:13 UTC (permalink / raw)
To: gdb
Why is the data returned by an 'info shar' different from /proc/*/maps?
I like to use /proc/*/maps to calculate the breakpoint address in my
shared library, which I can do by adding the offset within the file to
the library base load address.
I'm using all the default packages from Fedora Core 3, but I don't think
that matters, as I've seen the same behavior on several x86 Linux machines.
-Mike
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: info shar vs. /proc/*/maps
2005-03-17 2:13 info shar vs. /proc/*/maps Michael L. Artz
@ 2005-03-17 3:47 ` Daniel Jacobowitz
0 siblings, 0 replies; 2+ messages in thread
From: Daniel Jacobowitz @ 2005-03-17 3:47 UTC (permalink / raw)
To: slyph; +Cc: gdb
On Wed, Mar 16, 2005 at 09:12:03PM -0500, Michael L. Artz wrote:
> Why is the data returned by an 'info shar' different from /proc/*/maps?
> I like to use /proc/*/maps to calculate the breakpoint address in my
> shared library, which I can do by adding the offset within the file to
> the library base load address.
>
> I'm using all the default packages from Fedora Core 3, but I don't think
> that matters, as I've seen the same behavior on several x86 Linux machines.
GDB is reporting the load address of the .text section, not the
read-execute segment.
--
Daniel Jacobowitz
CodeSourcery, LLC
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-03-17 3:47 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-03-17 2:13 info shar vs. /proc/*/maps Michael L. Artz
2005-03-17 3:47 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox