This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Ping: unconditionally print detaching message
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 7 Dec 2010 08:56:26 +0100
- Subject: Re: Ping: unconditionally print detaching message
- References: <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