From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [commit] build failure in inf-ptrace.c (pa-hpux)
Date: Wed, 30 Dec 2009 19:47:00 -0000 [thread overview]
Message-ID: <20091230194628.GH5942@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
Hello,
inf-ptrace no longer builds on pa-hpux. Looks like a small thinko
while updating gazillions of files the same way. I hope I fixed it
right (notice the [...]->pspace = [...]->aspace on the second line
I changed ;-). I didn't see I first fixed the name of the variable...
2009-12-30 Joel Brobecker <brobecker@adacore.com>
Fix build failure in inf-ptrace.c.
* inf-ptrace.c (inf_ptrace_follow_fork): Fix typo.
Checked in.
--
Joel
[-- Attachment #2: inf-ptrace.diff --]
[-- Type: text/x-diff, Size: 879 bytes --]
commit 1a2d71c8b05b915da66a162b794eada3d85126ca
Author: brobecke <brobecke@f8352e7e-cb20-0410-8ce7-b5d9e71c585c>
Date: Wed Dec 30 19:34:08 2009 +0000
Fix build failure in inf-ptrace.c.
* inf-ptrace.c (inf_ptrace_follow_fork): Fix typo.
diff --git a/gdb/inf-ptrace.c b/gdb/inf-ptrace.c
index a138701..d2df3b1 100644
--- a/gdb/inf-ptrace.c
+++ b/gdb/inf-ptrace.c
@@ -67,8 +67,8 @@ inf_ptrace_follow_fork (struct target_ops *ops, int follow_child)
child_inf = add_inferior (fpid);
child_inf->attach_flag = parent_inf->attach_flag;
copy_terminal_info (child_inf, parent_inf);
- inf->pspace = parent_inf->pspace;
- inf->pspace = parent_inf->aspace;
+ child_inf->pspace = parent_inf->pspace;
+ child_inf->aspace = parent_inf->aspace;
/* Before detaching from the parent, remove all breakpoints from
it. */
next reply other threads:[~2009-12-30 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 19:47 Joel Brobecker [this message]
2009-12-30 20:10 ` Mark Kettenis
2009-12-31 8:50 ` 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=20091230194628.GH5942@adacore.com \
--to=brobecker@adacore.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