From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Fix Java PR gdb/1322 (was Re: [rfa/doc] Document pr gdb/1322 in PROBLEMS)
Date: Sun, 24 Aug 2003 16:56:00 -0000 [thread overview]
Message-ID: <20030824165607.GC17841@nevyn.them.org> (raw)
In-Reply-To: <200308181832.h7IIWKUx004464@duracef.shout.net>
On Mon, Aug 18, 2003 at 02:32:20PM -0400, Michael Elizabeth Chastain wrote:
> +
> + gdb/1322: "internal-error: sect_index_text not initialized" after printing a java type
> +
> + When gdb debugs a Java program which uses shared libraries, it can
> + generate this internal error.
> +
> + If you get this error when debugging Java, you can try working around
> + the problem by relinking your program with no shared libraries at all
> + (even the standard C library). With the GNU linker, use the "-static"
> + argument to do this.
> +
> + You can also try this patch for gdb:
> +
> + http://sources.redhat.com/ml/gdb-prs/2003-q3/msg00190.html
How about we fix it instead? This patch depends on Mark K's
per-objfile-data patch, but only because it touches the same area, I
think.
Dwarf maintainers, is this OK? Could someone test that it fixes the
Java problems on HEAD?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
2003-08-24 Daniel Jacobowitz <drow@mvista.com>
PR gdb/1322
* dwarf2-frame.c (dwarf2_frame_find_fde): Check whether any FDEs are
available before calling SECT_OFF_TEXT.
Index: dwarf2-frame.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2-frame.c,v
retrieving revision 1.11
diff -u -p -r1.11 dwarf2-frame.c
--- dwarf2-frame.c 21 Aug 2003 22:35:33 -0000 1.11
+++ dwarf2-frame.c 24 Aug 2003 16:52:24 -0000
@@ -1024,9 +1024,12 @@ dwarf2_frame_find_fde (CORE_ADDR *pc)
struct dwarf2_fde *fde;
CORE_ADDR offset;
- offset = ANOFFSET (objfile->section_offsets, SECT_OFF_TEXT (objfile));
-
fde = objfile_data (objfile, dwarf2_frame_data);
+ if (fde == NULL)
+ continue;
+
+ offset = ANOFFSET (objfile->section_offsets, SECT_OFF_TEXT (objfile));
+
while (fde)
{
if (*pc >= fde->initial_location + offset
next prev parent reply other threads:[~2003-08-24 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 18:32 [rfa/doc] Document pr gdb/1322 in PROBLEMS Michael Elizabeth Chastain
2003-08-24 16:56 ` Daniel Jacobowitz [this message]
2003-08-24 19:42 ` Fix Java PR gdb/1322 (was Re: [rfa/doc] Document pr gdb/1322 in PROBLEMS) Mark Kettenis
2003-08-26 3:09 ` Daniel Jacobowitz
2003-08-25 15:56 ` [rfa/doc] Document pr gdb/1322 in PROBLEMS Andrew Cagney
2003-08-24 19:48 Fix Java PR gdb/1322 (was Re: [rfa/doc] Document pr gdb/1322 in PROBLEMS) Michael Elizabeth Chastain
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=20030824165607.GC17841@nevyn.them.org \
--to=drow@mvista.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