From: Mark Kettenis <kettenis@chello.nl>
To: kevinb@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] Propagate signals to non-clone PID on GNU/Linux
Date: Sun, 31 Mar 2002 07:36:00 -0000 [thread overview]
Message-ID: <200203311536.g2VFabb32137@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <1020328075921.ZM25566@localhost.localdomain> (message from Kevin Buettner on Thu, 28 Mar 2002 00:59:21 -0700)
Hi Kevin,
Hmm, there are a couple of things that make me doubt that this is the
right solution.
Please realize that lin-lwp.c:child_wait() is used for all Linux
processes, not only multi-threaded programs. Therefore I'm not very
enthousiastic about adding too much overhead to this function,
including setting up and manipulating GDB's internal LWP bookkeeping.
Actually, I think the patch in its current incarnation introduces a
memory leak: when debugging normal programs, GDB will keep adding
LWP's to its internal bookkeeping and never remove them.
Unfortunately I can't think of another way to fix the bug with the
"cloned" flag being set incorrectly for the LWP that GDB initially
attached to. Perhaps the use of a static global variable is justified
in this case?
I'm a bit confused by the name you've chosen for
set_up_clone_as_overall_process_id(), since it should never be called
for a "cloned" process isn't it. Can you find a better name?
I was also confused why you removed the code that "handles the overall
process being stopped in another layer" in lin_lwp_attach_lwp(), but
of course that is related to what you did to child_wait(). If we
agree that using a global variable in child_wait() is the right
approach, this bit is where the "cloned" flag should be set based on
the setting of that global variable.
Mark
prev parent reply other threads:[~2002-03-31 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 23:59 Kevin Buettner
2002-03-31 7:36 ` Mark Kettenis [this message]
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=200203311536.g2VFabb32137@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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