Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Lev Assinovsky <LAssinovsky@algorithm.aelita.com>,
	gdb@sources.redhat.com
Subject: Re: gdb 5.3 bug
Date: Fri, 28 Feb 2003 17:18:00 -0000	[thread overview]
Message-ID: <20030228171845.GB24839@nevyn.them.org> (raw)
In-Reply-To: <20030227190930.GC9375@nevyn.them.org>

On Thu, Feb 27, 2003 at 02:09:30PM -0500, Daniel Jacobowitz wrote:
> On Thu, Feb 27, 2003 at 09:11:14PM +0300, Lev Assinovsky wrote:
> > GNU gdb 5.3
> > Copyright 2002 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General Public License, and you are
> > welcome to change it and/or distribute copies of it under certain conditions.
> > Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB.  Type "show warranty" for details.
> > This GDB was configured as "i386-pc-solaris2.8"...
> > (gdb) l
> > 
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x08136671 in finish_block (symbol=0x6e5f5f3a, listhead=0x82241f4, old_blocks=0x3a787863, start=1634562671, 
> >     end=1634562720, objfile=0x8263fe0) at buildsym.c:304
> > 304           struct type *ftype = SYMBOL_TYPE (symbol);
> > (gdb) 
> > 
> > 
> > Any clue what might be the reason of gdb crash?
> 
> OK, the value of "symbol" is obviously wrong.  Could you privately send
> me the binary?  If that's not possible, at least a backtrace would be
> useful...


Lev,

You're in luck, this has already been fixed.  It appears to be a bug in
the Sun compilers - it outputs end-of-function markers without a
corresponding beginning-of-function marker.  If you get a GDB snapshot
from CVS (http://sources.redhat.com/gdb/) it should handle your program
gracefully.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-28 17:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 18:11 Lev Assinovsky
2003-02-27 19:09 ` Daniel Jacobowitz
2003-02-28 17:18   ` Daniel Jacobowitz [this message]
2003-03-01 15:59 Lev Assinovsky
2003-03-01 16:05 ` Daniel Jacobowitz
2003-03-01 16:13 Lev Assinovsky
2003-03-01 17:40 Lev Assinovsky
2003-03-05 14:27 Lev Assinovsky
2003-03-05 15:57 ` Daniel Jacobowitz
2003-03-05 16:06 Lev Assinovsky
2003-03-05 16:12 ` Daniel Jacobowitz
2003-03-05 16:54 Lev Assinovsky
2003-03-05 17:12 Lev Assinovsky
2003-03-05 17:23 ` Daniel Jacobowitz
2003-03-05 17:32 Lev Assinovsky
2003-03-05 17:52 ` Kevin Buettner
2003-03-07 11:05 Lev Assinovsky
2003-03-07 14:26 ` Daniel Jacobowitz
2003-03-07 14:35 Lev Assinovsky

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=20030228171845.GB24839@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=LAssinovsky@algorithm.aelita.com \
    --cc=gdb@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