Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Ping: unconditionally print detaching message
Date: Tue, 07 Dec 2010 07:56:00 -0000	[thread overview]
Message-ID: <20101207075626.GB1257@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3bp5l9dtl.fsf@fleche.redhat.com>

On Fri, 19 Nov 2010 22:57:26 +0100, Tom Tromey wrote:
> We've had this message on in Fedora for quite a while.  I find it mildly
> useful in that it can occasionally remind me that I am debugging the
> wrong process.

I wrote the patch because the user did not notice any new process there and so
that should be some solution for it.

But TBH I just got used to the message in Fedora, it is being printed zillions
times during debugging sessions and I even have no clue why.

$ ./gdb -q -nx -ex r --args ./gdb -nx -q
Reading symbols from .../gdb/gdb...done.
Starting program: .../gdb/gdb -nx -q
[Thread debugging using libthread_db enabled]
Detaching after fork from child process 4015.
(gdb) _

BTW I have found out now this one message is due to `iconv -l'.

So if it should be printed there should be IMO printed even the command
+ arguments.

But the right way would be rather to use `set detach-on-fork off' by default
when it would be working transparently enough.  Therefore this message is no
longer the right solution but just a temporary GDB deficiency workaround now.

So I am fine with dropping it (incl. Fedora) rather than trying to figure out
some new message format/options.


Thanks,
Jan


  parent reply	other threads:[~2010-12-07  7:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 21:57 Tom Tromey
2010-11-19 22:16 ` Joel Brobecker
2010-12-06 21:56   ` Tom Tromey
2010-12-07  7:56 ` Jan Kratochvil [this message]
2010-12-07 18:14   ` Tom Tromey

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=20101207075626.GB1257@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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