From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb@sourceware.org
Subject: Re: Debugging through exec() (Linux MAY_FOLLOW_EXEC)
Date: Mon, 14 Aug 2006 21:39:00 -0000 [thread overview]
Message-ID: <20060814213849.GA1433@nevyn.them.org> (raw)
In-Reply-To: <u7j1b581f.fsf@gnu.org>
On Tue, Aug 15, 2006 at 12:20:12AM +0300, Eli Zaretskii wrote:
> > Date: Mon, 14 Aug 2006 17:06:28 +0200
> > From: Jan Kratochvil <jan.kratochvil@redhat.com>
> > Cc: Daniel Jacobowitz <drow@false.org>
> >
> > please review the proposed functionality to be able to debug though exec().
>
> Thanks. Please wait for others to comment; what's below are
> relatively minor comments.
Eli, have you got an opinion on the broader question, by chance?
This is really an issue of use cases and interface; the technical
changes I'm ok to handle by myself, but there are broader questions
about how this would work (did work, on HP/UX, at some point in the
past) and should work.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-14 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060614142552.GA15021@nevyn.them.org>
[not found] ` <20060615203519.GA9603@host0.dyn.jankratochvil.net>
[not found] ` <20060721181556.GA9150@lace.redhat.com>
[not found] ` <20060721184421.GA22820@nevyn.them.org>
[not found] ` <20060722123102.GA1936@lace.redhat.com>
[not found] ` <20060724190332.GA13612@nevyn.them.org>
[not found] ` <20060729185317.GA16200@host0.dyn.jankratochvil.net>
[not found] ` <200607312038.k6VKchKj018729@elgar.sibelius.xs4all.nl>
[not found] ` <20060805164144.GA23819@host0.dyn.jankratochvil.net>
[not found] ` <20060808160113.GC21032@nevyn.them.org>
2006-08-14 15:07 ` Jan Kratochvil
2006-08-14 21:20 ` Eli Zaretskii
2006-08-14 21:39 ` Daniel Jacobowitz [this message]
2006-08-15 3:22 ` Eli Zaretskii
2006-08-15 14:28 ` Jan Kratochvil
2006-08-18 12:27 ` Eli Zaretskii
2006-09-04 17:59 ` Jan Kratochvil
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=20060814213849.GA1433@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.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