Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/i386newframe] Add asssertion to CFI frame unwinder
Date: Mon, 23 Jun 2003 22:35:00 -0000	[thread overview]
Message-ID: <16119.32928.499250.823983@localhost.redhat.com> (raw)
In-Reply-To: <200305291602.h4TG2HVr031955@elgar.kettenis.dyndns.org>

Mark Kettenis writes:
 > This assertion can unfortunately be triggered.  Don't know how to fix
 > the bug yet, but this makes clear there is a bug.
 > 
 > Mark
 > 
 > Index: ChangeLog
 > from  Mark Kettenis  <kettenis@gnu.org>
 >  
 > 	* dwarf-frame.c (dwarf2_frame_cache): Assert that we have a FDE.
 > 
 > Index: dwarf-frame.c
 > ===================================================================
 > RCS file: /cvs/src/src/gdb/Attic/dwarf-frame.c,v
 > retrieving revision 1.1.2.6
 > diff -u -p -r1.1.2.6 dwarf-frame.c
 > --- dwarf-frame.c 23 May 2003 20:18:32 -0000 1.1.2.6
 > +++ dwarf-frame.c 29 May 2003 15:47:12 -0000
 > @@ -483,6 +483,7 @@ dwarf2_frame_cache (struct frame_info *n
 >  
 >    /* Find the correct FDE.  */
 >    fde = dwarf2_frame_find_fde (&fs->pc);
 > +  gdb_assert (fde != NULL);
 >  
 >    /* Extract any interesting information from the CIE.  */
 >    fs->data_align = fde->cie->data_alignment_factor;


I am running into this in several cases running the testsuite on x86.
For instance for me callfuncs.exp just doesn't do anything, because
the assertion is triggered at startup.
what exactly is happening? 

thanks
elena


  reply	other threads:[~2003-06-23 22:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29 16:02 Mark Kettenis
2003-06-23 22:35 ` Elena Zannoni [this message]
2003-06-24 22:42   ` Elena Zannoni

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=16119.32928.499250.823983@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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