public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Lev Assinovsky" <LAssinovsky@algorithm.aelita.com>
To: <gdb@sources.redhat.com>
Subject: gdb 5.3 bug
Date: Thu, 27 Feb 2003 18:11:00 -0000	[thread overview]
Message-ID: <3F6F4712B759A34ABD453A8B39C10D6229DB66@bagman.edm.com> (raw)

Hi All!
I have executable "client" complied  by gcc 3.2 (with gnu as and gnu ld)
I use gdb 5.3 for debugging and get it's crash for very simple case:

lev@dog comm_test$ gdb bin/i386-sun-solaris/debug/client
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
Segmentation Fault (core dumped)
lev@dog comm_test$

Then I started to debug gdb:

lev@dog comm_test$ gdb /usr/local/bin/gdb
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) r bin/i386-sun-solaris/debug/client
Starting program: /export/home/local/bin/gdb bin/i386-sun-solaris/debug/client
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
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?
Thank you!
(gdb 5.2 has been crashed also)
----
Lev Assinovsky
Aelita Software Corporation
O&S Core Division, Programmer
ICQ# 165072909

             reply	other threads:[~2003-02-27 18:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 18:11 Lev Assinovsky [this message]
2003-02-27 19:09 ` Daniel Jacobowitz
2003-02-28 17:18   ` Daniel Jacobowitz
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=3F6F4712B759A34ABD453A8B39C10D6229DB66@bagman.edm.com \
    --to=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).