From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC 1/2] Remove linux-waitpid.c debugging code
Date: Wed, 05 Jun 2019 09:32:00 -0000 [thread overview]
Message-ID: <bd3f675c-0228-3b13-948e-0931220e4607@redhat.com> (raw)
In-Reply-To: <87blzeocix.fsf@tromey.com>
On 6/3/19 5:32 PM, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
>
>>> My first thought was that this code is not extremely useful, so this
>>> patch removes this code. (However, if it is actually useful to
>>> someone, we could make it work by introducing a new abstraction.)
>
> Simon> Pedro probably has a stronger opinion about this (as he is probably the one who
> Simon> has spent the most time staring at those logs), but I would think that this
> Simon> logging is useful when debugging interactions with the kernel.
>
> I should have mentioned that the reason I figured it wasn't that useful
> is that it's not available in gdb proper, only gdbserver.
A bit of history here:
IIRC, the original reason my_waitpid in gdbserver printed the result, is
that I found that useful when I made my_waitpid emulate __WALL:
https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=gdb/gdbserver/linux-low.c;h=ba1d7b46bb96e4cec83ea698e40511d284f16532;hb=bd99dc858385792aad304d42f4a47791fd8d3272#l2110
Over the years, the function moved to gdb/nat/, gdb started using it too,
and then the __WALL emulation disappeared, making my_waitpid a simple
EINTR wrapper again.
Since the emulation is gone, and, both gdb and gdbserver print the result
of waitpid in the most interesting waitpid call spot:
if (debug_threads)
debug_printf ("LWFE: waitpid(-1, ...) returned %d, %s\n",
ret, errno ? strerror (errno) : "ERRNO-OK");
if (debug_linux_nat)
fprintf_unfiltered (gdb_stdlog,
"LNW: waitpid(-1, ...) returned %d, %s\n",
lwpid, errno ? safe_strerror (errno) : "ERRNO-OK");
... I guess I won't terribly miss it.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-06-05 9:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 21:30 [RFC 0/2] Let's discuss moving gdbserver to top-level Tom Tromey
2019-05-30 21:30 ` [RFC 1/2] Remove linux-waitpid.c debugging code Tom Tromey
2019-06-03 14:57 ` Simon Marchi
2019-06-03 16:32 ` Tom Tromey
2019-06-05 9:32 ` Pedro Alves [this message]
2019-05-30 21:30 ` [RFC 2/2] Move gdb's xmalloc and friends to new file Tom Tromey
2019-06-03 15:03 ` Simon Marchi
2019-06-03 16:33 ` Tom Tromey
2019-06-05 9:40 ` Pedro Alves
2019-06-05 22:33 ` Tom Tromey
2019-06-17 15:45 ` Alan Hayward
2019-06-17 17:43 ` Tom Tromey
2019-06-17 18:37 ` Pedro Alves
2019-06-18 9:31 ` Alan Hayward
2019-07-03 16:18 ` Alan Hayward
2019-07-13 16:04 ` Tom Tromey
2019-07-16 19:47 ` Pedro Alves
2019-06-03 10:24 ` [RFC 0/2] Let's discuss moving gdbserver to top-level Alan Hayward
2019-06-03 14:27 ` Simon Marchi
2019-06-03 16:30 ` Tom Tromey
2019-06-05 9:16 ` Pedro Alves
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=bd3f675c-0228-3b13-948e-0931220e4607@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tom@tromey.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