From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Kevin Pouget <kevin.pouget@gmail.com>, gdb@sourceware.org
Subject: Re: GDB and LD_PRELOAD library-call interception
Date: Thu, 31 Mar 2011 15:07:00 -0000 [thread overview]
Message-ID: <m3k4ffmiq4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110331121617.GA32739@host1.jankratochvil.net> (Jan Kratochvil's message of "Thu, 31 Mar 2011 14:16:17 +0200")
Kevin> but it it possible to follow easily (two) forks?
Jan> Yes, `set detach-on-fork off', so-called multi-inferior mode, it has some
Jan> issues on native GNU/Linux system.
If you do try this, and run into bugs, please file them in bugzilla.
Tom
next prev parent reply other threads:[~2011-03-31 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 8:25 Kevin Pouget
2011-03-31 8:47 ` Jan Kratochvil
2011-03-31 9:47 ` Kevin Pouget
2011-03-31 12:16 ` Jan Kratochvil
2011-03-31 15:07 ` Tom Tromey [this message]
2011-04-03 16:54 ` Xavier de Gaye
[not found] ` <BANLkTi=j6+-85R4B+N1Nd5kb9bkEZfsT9A@mail.gmail.com>
2011-04-04 13:35 ` Kevin Pouget
2011-03-31 15:06 ` Tom Tromey
2011-03-31 15:55 ` Kevin Pouget
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=m3k4ffmiq4.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=kevin.pouget@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