From: Joel Brobecker <brobecker@ACT-Europe.FR>
To: henri delebecque <henri.delebecque@supelec.fr>
Cc: gdb@sources.redhat.com, delebecq@supelec.fr
Subject: Re: gdb on Alpha/Tru64 Unix ??
Date: Thu, 21 Mar 2002 10:33:00 -0000 [thread overview]
Message-ID: <20020321193337.D3351@act-europe.fr> (raw)
In-Reply-To: <p04330108b8bfc275e4d5@[160.228.100.5]>; from henri.delebecque@supelec.fr on Thu, Mar 21, 2002 at 06:10:18PM +0100
[-- Attachment #1: Type: text/plain, Size: 485 bytes --]
> mdebugread.c:2448:gdb-internal-error:Scetion index is unintialized.
You may want to try the following patch. I have intended to discuss this
matter with the rest of the GDB community, but haven't had time yet.
Anyway, this is not what will be the final fix (a bit too... brutal...),
but it should allow you to get past this internal error (note that the
error in itself is non-fatal, so you can just answer continue->yes and
dump_core->no, and everything should be fine).
--
Joel
[-- Attachment #2: mdebugread.c.diff --]
[-- Type: text/plain, Size: 2379 bytes --]
Index: mdebugread.c
===================================================================
RCS file: /nile.c/cvs/Dev/gdb/gdb-5/gdb/mdebugread.c,v
retrieving revision 1.1.1.1
diff -c -3 -p -r1.1.1.1 mdebugread.c
*** mdebugread.c 2 Sep 2000 21:56:11 -0000 1.1.1.1
--- mdebugread.c 21 Mar 2002 18:29:44 -0000
*************** parse_partial_symbols (struct objfile *o
*** 2438,2455 ****
--- 2453,2500 ----
break;
case stLabel:
/* Label */
+
+ /* On certain plateforms, some extra label symbols can be
+ generated by the linker. One possible usage for this kind
+ of symbols is to represent the address of the begining of a
+ given section. For instance, on Tru64 5.1, the address of
+ the _ftext label is the start address of the .text section.
+
+ The storage class of these symbols is usually directly
+ related to the section to which the symbol refers. For
+ instance, on Tru64 5.1, the storage class for the _fdata
+ label is scData, refering to the .data section.
+
+ It is actually possible that the section associated to the
+ storage class of the label does not exist. On True64 5.1
+ for instance, the libm.so shared library does not contain
+ any .data section, although it contains a _fpdata label
+ which storage class is scData... Since these symbols are
+ usually useless for the debugger user anyway, we just
+ discard these symbols.
+ */
+
if (SC_IS_TEXT (ext_in->asym.sc))
{
+ if (objfile->sect_index_text == -1)
+ continue;
+
ms_type = mst_file_text;
svalue += ANOFFSET (objfile->section_offsets, SECT_OFF_TEXT (objfile));
}
else if (SC_IS_DATA (ext_in->asym.sc))
{
+ if (objfile->sect_index_data == -1)
+ continue;
+
ms_type = mst_file_data;
svalue += ANOFFSET (objfile->section_offsets, SECT_OFF_DATA (objfile));
}
else if (SC_IS_BSS (ext_in->asym.sc))
{
+ if (objfile->sect_index_bss == -1)
+ continue;
+
ms_type = mst_file_bss;
svalue += ANOFFSET (objfile->section_offsets, SECT_OFF_BSS (objfile));
}
prev parent reply other threads:[~2002-03-21 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 9:11 henri delebecque
2002-03-21 10:33 ` Joel Brobecker [this message]
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=20020321193337.D3351@act-europe.fr \
--to=brobecker@act-europe.fr \
--cc=delebecq@supelec.fr \
--cc=gdb@sources.redhat.com \
--cc=henri.delebecque@supelec.fr \
/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