Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: crasher in dwarf2loc.c
Date: Wed, 23 Apr 2003 00:50:00 -0000	[thread overview]
Message-ID: <3EA5E370.F069D062@redhat.com> (raw)

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

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.


             reply	other threads:[~2003-04-23  0:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23  0:50 Michael Snyder [this message]
2003-04-23  9:37 ` Daniel Jacobowitz
2003-04-25  1:47   ` Michael Snyder
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=3EA5E370.F069D062@redhat.com \
    --to=msnyder@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