From: Daniel Jacobowitz <drow@false.org>
To: Mathieu Lacage <mathieu.lacage@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: how to make gdb happy with my linkmap
Date: Thu, 18 Dec 2008 22:10:00 -0000 [thread overview]
Message-ID: <20081218221005.GA9012@caradoc.them.org> (raw)
In-Reply-To: <74fef6df0812181402n1debced5xbe3f402a3a34ecf2@mail.gmail.com>
On Thu, Dec 18, 2008 at 11:02:22PM +0100, Mathieu Lacage wrote:
> > On SVR4 systems, basically, you can't. There is some information you
> > won't be able to update because it lives in the kernel (auxilliary
> > vector). This is one of the reasons I recently implemented "set
>
> erm, I might be totally naive, but, how does the libc loader achieve
> this then ? The only thing I am trying to do is be sufficiently
> compatible with the libc loader to make gdb happy with my loader. Did
> I mention that I am trying to replace the libc loader rather than try
> to make two loaders co-exist in the same process image (which would
> create another set of challenging problems from a compatibility
> perspective).
Oh! Sorry. Then I was off on a tangent. The salient difference is
whether your loader is started by the kernel based on a PT_INTERP
entry in the executable, or from the command line. If it's started
by PT_INTERP, things are much easier to handle.
The only things I can think of are having the main application first,
and having the debug function be named _dl_debug_state (because we set
a breakpoint before _r_debug is initialized). There's not much more
to it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-12-18 22:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 21:42 Mathieu Lacage
2008-12-18 21:49 ` Daniel Jacobowitz
2008-12-18 22:03 ` Mathieu Lacage
2008-12-18 22:10 ` Daniel Jacobowitz [this message]
2008-12-26 10:40 ` Mathieu Lacage
2008-12-26 12:54 ` Daniel Jacobowitz
2009-01-05 14:58 ` Mathieu Lacage
2009-01-05 17:13 ` Daniel Jacobowitz
2009-01-07 16:46 ` Doug Evans
2009-01-12 15:08 ` Mathieu Lacage
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=20081218221005.GA9012@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mathieu.lacage@gmail.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