From: "Mathieu Lacage" <mathieu.lacage@gmail.com>
To: "Mathieu Lacage" <mathieu.lacage@gmail.com>, gdb@sourceware.org
Subject: Re: how to make gdb happy with my linkmap
Date: Fri, 26 Dec 2008 10:40:00 -0000 [thread overview]
Message-ID: <74fef6df0812260239o1f21e833t6464c9d41bedcdd1@mail.gmail.com> (raw)
In-Reply-To: <20081218221005.GA9012@caradoc.them.org>
On Thu, Dec 18, 2008 at 11:10 PM, Daniel Jacobowitz <drow@false.org> wrote:
> 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.
Ok, it appears that this is, indeed, sufficient to get good debugging
when running the executable from a PT_INTERP. However, as you
mentioned above, running the executable from the command-line without
an associated PT_INTERP entry seems to confuse gdb quite a bit: it
seems unable to place or handle breakpoints. Is there something I
could do to help alleviate this problem (I would be happy to do
whatever is needed in gdb proper) ? Maybe I could go and hack the
on-stack aux vectors to help gdb ?
regards,
Mathieu
--
Mathieu Lacage <mathieu.lacage@gmail.com>
next prev parent reply other threads:[~2008-12-26 10:40 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
2008-12-26 10:40 ` Mathieu Lacage [this message]
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=74fef6df0812260239o1f21e833t6464c9d41bedcdd1@mail.gmail.com \
--to=mathieu.lacage@gmail.com \
--cc=gdb@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