Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com, cagney@redhat.com
Subject: Re: crasher in dwarf2loc.c
Date: Fri, 25 Apr 2003 01:47:00 -0000	[thread overview]
Message-ID: <3EA87EDF.4A0826F8@redhat.com> (raw)
In-Reply-To: <20030423021617.GB13849@nevyn.them.org>

Daniel Jacobowitz wrote:
> 
> On Tue, Apr 22, 2003 at 05:50:56PM -0700, Michael Snyder wrote:
> > Hey Daniel,
> >
> > I've got a core dump coming from dwarf_expr_frame_base.
> > First you call get_frame_function, and then you immediately
> > use its return value.  But get_frame_function can return zero,
> > so I think you need to check for zero before using it.
> >
> > Michael
> 
> Just to avoid the crash, you're probably right.
> 
> > PS: more details:  get_frame_block returns zero, because
> > frame_address_in_block returns a pc that is not in any block.
> >
> > The crash occurs while running recurse.exp, when we have a
> > watchpoint on a local variable in an inner frame, and we
> > continue -- so I don't know the exact context; but I'm
> > willing to bet that it is trying to evaluate the local
> > variable after the stack frame has been destroyed.
> 
> Huh - we should not even be reaching this code.  I don't quite
> understand your explanation; what target does this happen?  Can it be
> reproduced on a simulator, or something of that ilk?

mumble, mumble...

[...]

mumble, mumble, mumble...

OK, yes.

But first you have to back out this change: then run recurse.exp.
If it doesn't crash in your target of choice, try h8300-elf (sim).

2003-04-21  Andrew Cagney  <cagney@redhat.com>

	* frame.c (frame_id_eq): Fail when the code_addr's do not match.

*************** frame_id_eq (struct frame_id l, struct f
*** 295,304 ****
      /* The .stack and .code are identical, the ID's are identical.  */
      eq = 1;
    else
!     /* FIXME: cagney/2003-04-06: This should be zero.  Can't yet do
!        this because most frame ID's are not being initialized
!        correctly.  */
!     eq = 1;
    if (frame_debug)
      {
        fprintf_unfiltered (gdb_stdlog, "{ frame_id_eq (l=");
--- 295,302 ----
      /* The .stack and .code are identical, the ID's are identical.  */
      eq = 1;
    else
!     /* No luck.  */
!     eq = 0;
    if (frame_debug)
      {
        fprintf_unfiltered (gdb_stdlog, "{ frame_id_eq (l=");


  reply	other threads:[~2003-04-25  0:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23  0:50 Michael Snyder
2003-04-23  9:37 ` Daniel Jacobowitz
2003-04-25  1:47   ` Michael Snyder [this message]
2003-06-21 17:27     ` Daniel Jacobowitz

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=3EA87EDF.4A0826F8@redhat.com \
    --to=msnyder@redhat.com \
    --cc=cagney@redhat.com \
    --cc=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