From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix a compilation failure in rs6000-nat.c
Date: Tue, 01 Jul 2003 00:40:00 -0000 [thread overview]
Message-ID: <20030701004039.GT26149@gnat.com> (raw)
In-Reply-To: <20030701003728.GR26149@gnat.com>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
[sigh, resending with the patch this time...]
A leftover of the SIZEOF_SECTION_OFFSETS removal saga... Not sure how
I missed it the last time I tryed building GDB on AiX, but I lack the
time to investigate further...
2003-06-30 Joel Brobecker <brobecker@gnat.com>
* rs6000-nat.c (vmap_symtab): Fix compilation error.
tested on ppc-aix 4.3.2.0.
Ok to apply?
I think the gdb6 branch has the same problem :-(. I will double-check.
If I get the approval for this patch, and it turns out that we need it
on gdb6, can I apply it there too?
Thanks,
--
Joel
[-- Attachment #2: rs6000-nat.c.diff --]
[-- Type: text/plain, Size: 764 bytes --]
Index: rs6000-nat.c
===================================================================
RCS file: /cvs/src/src/gdb/rs6000-nat.c,v
retrieving revision 1.31
diff -u -p -r1.31 rs6000-nat.c
--- rs6000-nat.c 10 Jun 2003 20:34:09 -0000 1.31
+++ rs6000-nat.c 1 Jul 2003 00:31:09 -0000
@@ -664,7 +664,9 @@ vmap_symtab (struct vmap *vp)
/* If symbols are not yet loaded, offsets are not yet valid. */
return;
- new_offsets = (struct section_offsets *) alloca (SIZEOF_SECTION_OFFSETS);
+ new_offsets =
+ (struct section_offsets *) alloca (objfile->num_sections *
+ sizeof (struct section_offsets));
for (i = 0; i < objfile->num_sections; ++i)
new_offsets->offsets[i] = ANOFFSET (objfile->section_offsets, i);
next prev parent reply other threads:[~2003-07-01 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 0:37 Joel Brobecker
2003-07-01 0:40 ` Joel Brobecker [this message]
2003-07-02 18:02 ` Kevin Buettner
2003-07-04 16:49 ` Joel Brobecker
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=20030701004039.GT26149@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb-patches@sources.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