public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb@sources.redhat.com, carlton@kealia.com, tromey@redhat.com,
	kettenis@chello.nl
Subject: Re: java crash from tom tromey
Date: Wed, 06 Aug 2003 17:03:00 -0000	[thread overview]
Message-ID: <20030806170247.GA19616@nevyn.them.org> (raw)
In-Reply-To: <200308061650.h76Gooib012449@duracef.shout.net>

On Wed, Aug 06, 2003 at 12:50:50PM -0400, Michael Elizabeth Chastain wrote:
> Here is a brain dump.
> 
> Tom T sent me a reproducible test case and I can reproduce it.
> 
> The problem happens with these commands:
> 
>   break 't::main TAB'
>   run
>   next next next step fini
>   step step step step step
>   print str
>   run yes
>   next
> 
> I have appended a backtrace.
> 
> My guess at the etiology is:
> 
>   gdb creates an objfile with name "<<anonymous objfile>>"
>   and sect_index_test of -1.  I suspect that happens somewhere
>   around the "print str" command but I don't really know enough
>   about Java to say.
> 
>   It's essential to re-run the executable in order to blow away
>   some sort of frame cache (another guess on my part).
> 
>   In the second run, gdb builds frames again.  It is in the middle
>   of frame building when it calls dwarf2_frame_find_fde
>   (frame #6 on the stack trace).
> 
>   dwarf2_frame_find_fde, gdb does this:
> 
>     ALL_OBJFILES (objfile)
>       {
> 	...
> 	offset = ANOFFSET (objfile->section_offsets, SECT_OFF_TEXT(objfile));
> 	...
>       }
> 
>   objfile has name "<<anonymous objfile>>" and sect_index_text of -1,
>   which triggers the internal error inside the SECT_OFF_TEXT macro.

The correct fix is:
  - a patch, posted by Mark Kettenis:
Date: Sun, 13 Jul 2003 19:17:04 +0200 (CEST)
From: Mark Kettenis <kettenis@chello.nl>
Subject: [RFC/RFA] Per-objfile data mechanism    
  - Then, after that patch, move the check for FDEs in this objfile
before the check for section offsets.

The patch was approved but never checked in.  I'm guessing that Mark
has been too busy (or gotten caught up in the FSF's email troubles)
since we haven't heard from him in a few weeks.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  parent reply	other threads:[~2003-08-06 17:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06 16:50 Michael Elizabeth Chastain
2003-08-06 17:00 ` David Carlton
2003-08-06 17:17   ` Tom Tromey
2003-08-06 17:03 ` Daniel Jacobowitz [this message]
2003-08-06 17:12 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=20030806170247.GA19616@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carlton@kealia.com \
    --cc=gdb@sources.redhat.com \
    --cc=kettenis@chello.nl \
    --cc=mec@shout.net \
    --cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).