From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] Kill last SECT_OFF_MAX (somread.c)
Date: Wed, 09 Jul 2003 17:25:00 -0000 [thread overview]
Message-ID: <20030709172458.GC985@gnat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
This is a patch I forgot to submit. It fixes a compilation error on
HP/UX and finally kills the last instance of SECT_OFF_MAX.
2003-07-09 Joel Brobecker <brobecker@gnat.com>
* somread.c (som_symfile_offsets): Fix compilation error.
Ok to apply mainline and branch?
Thanks,
--
Joel
[-- Attachment #2: somread.c.diff --]
[-- Type: text/plain, Size: 1029 bytes --]
Index: somread.c
===================================================================
RCS file: /cvs/src/src/gdb/somread.c,v
retrieving revision 1.19
diff -c -3 -p -r1.19 somread.c
*** somread.c 6 Jun 2003 23:32:59 -0000 1.19
--- somread.c 9 Jul 2003 17:17:44 -0000
*************** som_symfile_offsets (struct objfile *obj
*** 453,459 ****
/* Note: Here is OK to compare with ".text" because this is the
name that gdb itself gives to that section, not the SOM
name. */
! for (i = 0; i < SECT_OFF_MAX && addrs->other[i].name; i++)
if (strcmp (addrs->other[i].name, ".text") == 0)
break;
text_addr = addrs->other[i].addr;
--- 453,459 ----
/* Note: Here is OK to compare with ".text" because this is the
name that gdb itself gives to that section, not the SOM
name. */
! for (i = 0; i < objfile->num_sections && addrs->other[i].name; i++)
if (strcmp (addrs->other[i].name, ".text") == 0)
break;
text_addr = addrs->other[i].addr;
next reply other threads:[~2003-07-09 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 17:25 Joel Brobecker [this message]
2003-07-09 17:56 ` Elena Zannoni
2003-07-09 18:52 ` 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=20030709172458.GC985@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