Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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: Fri, 26 Dec 2008 12:54:00 -0000	[thread overview]
Message-ID: <20081226125329.GA12783@caradoc.them.org> (raw)
In-Reply-To: <74fef6df0812260239o1f21e833t6464c9d41bedcdd1@mail.gmail.com>

On Fri, Dec 26, 2008 at 11:39:59AM +0100, Mathieu Lacage wrote:
> 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 ?

Does it work any better with ld.so?  I doubt it - GDB doesn't do
this well, and I don't have any clear idea on how to improve it.
Sorry.  There's probably a way that I haven't thought of.

Modifying the on-stack auxv copy won't make a difference; GDB uses the
read-only copy in the kernel (since locating the stack copy is
unreliable, and it is prone to corruption).

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-12-26 12:54 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
2008-12-26 12:54         ` Daniel Jacobowitz [this message]
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=20081226125329.GA12783@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