From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [commit] fix syntax errors in hpread.c
Date: Thu, 04 Jan 2007 07:21:00 -0000 [thread overview]
Message-ID: <20070104072205.GS3434@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
Hello,
The gods of automated nightly builds whispered to me in my sleep that
hpread.c failed to build last night. There are indeed a couple of
syntax errors that slipped through the the last commit. Fixed thusly.
I can't test this myself because it looks like this code handles C++
objects. I don't have a C++ compiler available to me on HP/UX. The
change looks reasonably obvious, so hopefully it is fine.
2007-01-04 Joel Brobecker <brobecker@adacore.com>
* hpread.c (hpread_type_lookup): Fix compilation failure.
Checked in.
--
Joel
[-- Attachment #2: hpread.c.diff --]
[-- Type: text/plain, Size: 780 bytes --]
Index: hpread.c
===================================================================
RCS file: /cvs/src/src/gdb/hpread.c,v
retrieving revision 1.59
diff -u -p -r1.59 hpread.c
--- hpread.c 3 Jan 2007 18:05:43 -0000 1.59
+++ hpread.c 4 Jan 2007 07:12:11 -0000
@@ -4871,10 +4871,9 @@ hpread_type_lookup (dnttpointer hp_type,
struct type *ptrmemtype;
struct type *class_type;
struct type *memtype;
- memtype = hpread_type_lookup (dn_bufp->dptrmem.memtype,
- objfile),
- class_type = hpread_type_lookup (dn_bufp->dptrmem.pointsto,
- objfile),
+
+ memtype = hpread_type_lookup (dn_bufp->dptrmem.memtype, objfile);
+ class_type = hpread_type_lookup (dn_bufp->dptrmem.pointsto, objfile);
return lookup_memberptr_type (memtype, class_type);
}
break;
next reply other threads:[~2007-01-04 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 7:21 Joel Brobecker [this message]
2007-01-04 14:11 ` Daniel Jacobowitz
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=20070104072205.GS3434@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