From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [obv] linux-nat.c: Move variable new_lp
Date: Sun, 18 Jul 2010 21:23:00 -0000 [thread overview]
Message-ID: <20100718212256.GA31054@host1.dyn.jankratochvil.net> (raw)
Hi,
checked-in as obvious.
Thanks,
Jan
http://sourceware.org/ml/gdb-cvs/2010-07/msg00103.html
--- src/gdb/ChangeLog 2010/07/16 23:19:37 1.11996
+++ src/gdb/ChangeLog 2010/07/18 21:21:52 1.11997
@@ -1,3 +1,8 @@
+2010-07-18 Jan Kratochvil <jan.kratochvil@redhat.com>
+
+ * linux-nat.c (linux_handle_extended_wait): Move variable new_lp into
+ a more inner block. Remove its unused declaration initializer.
+
2010-07-16 Thiago Jung Bauermann <bauerman@br.ibm.com>
* NEWS: Mention support for the new ptrace interface and hardware
--- src/gdb/linux-nat.c 2010/07/07 12:28:32 1.173
+++ src/gdb/linux-nat.c 2010/07/18 21:21:53 1.174
@@ -2149,7 +2149,6 @@
{
int pid = GET_LWP (lp->ptid);
struct target_waitstatus *ourstatus = &lp->waitstatus;
- struct lwp_info *new_lp = NULL;
int event = status >> 16;
if (event == PTRACE_EVENT_FORK || event == PTRACE_EVENT_VFORK
@@ -2213,7 +2212,10 @@
ourstatus->kind = TARGET_WAITKIND_VFORKED;
else
{
+ struct lwp_info *new_lp;
+
ourstatus->kind = TARGET_WAITKIND_IGNORE;
+
new_lp = add_lwp (BUILD_LWP (new_pid, GET_PID (lp->ptid)));
new_lp->cloned = 1;
new_lp->stopped = 1;
reply other threads:[~2010-07-18 21:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100718212256.GA31054@host1.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).