From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] Support exec tracing on GNU/Linux and HP-UX
Date: Mon, 22 Oct 2007 06:01:00 -0000 [thread overview]
Message-ID: <20071022043831.GD764@adacore.com> (raw)
In-Reply-To: <20071019175920.GA548@caradoc.them.org>
> The user interface is the same as it was when this was originally
> added on HP-UX long ago. When GDB sees an exec event, it
> automatically loads the new executable as the main symbol file.
> This is a little disconcerting if you try to use "run" again
> later, but otherwise seems pretty convenient.
>
> Any comments? Mark (or someone else), could you offer to test this
> on HP-UX? I suspect the tests will fail for cosmetic reasons due to
> the changed messages but I hope exec tracing will generally work.
I have tested this patch, and it unfortunately creates some issues:
(gdb) run
Starting program: /[...]/p
Executing new program: /usr/local/bin/zsh
(no debugging symbols found)
Unable to find __dld_flags symbol in object file.
What seems to happen is that we're enabling exec-following during
the startup sequence, and that causes us to do the follow-exec routine
on it. Eventually, this fails because the shell binary that I use
apparently does not have any symbols, thus causing the solib-som hook
to error out.
Do we do the same on Linux? (exec-follow during the startup)
--
Joel
next prev parent reply other threads:[~2007-10-22 4:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 19:49 Daniel Jacobowitz
2007-10-22 6:01 ` Joel Brobecker [this message]
2007-10-22 12:09 ` Daniel Jacobowitz
2007-10-22 18:56 ` Joel Brobecker
2007-10-22 19:30 ` Joel Brobecker
2007-10-22 20:01 ` Daniel Jacobowitz
2007-12-21 16:04 ` Joel Brobecker
2007-12-21 16:13 ` Joel Brobecker
2008-01-29 17:09 ` Daniel Jacobowitz
2008-01-29 21:26 ` Joel Brobecker
2008-01-29 21:48 ` Daniel Jacobowitz
2008-01-29 21:48 ` Joel Brobecker
2008-01-29 22:17 ` Daniel Jacobowitz
2008-01-29 22:54 ` Daniel Jacobowitz
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=20071022043831.GD764@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@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