From: Craig Rodrigues <rodrigc@attbi.com>
To: gdb@sources.redhat.com
Subject: gdb 5.1.92-1 crash on C++ program
Date: Thu, 02 May 2002 14:00:00 -0000 [thread overview]
Message-ID: <20020502170018.A31253@attbi.com> (raw)
Hi,
I downloaded the Source rpm for gdb 5.1.92-1 from rawhide.redhat.com.
I compiled a C++ program with:
2.96 20000731 (Red Hat Linux 7.1 2.96-85)
When I tried to debug my program, gdb coredumped:
==================================================================================
% gdb server
GNU gdb Red Hat Linux (5.1.92-1)
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-redhat-linux"...
(gdb) b 93
Breakpoint 1 at 0x80512b7: file server.cpp, line 93.
(gdb) run -o server.ior
Starting program: /home/crodrigu/Big_Twoways/server -o server.ior
[New Thread 1024 (LWP 2348)]
[Switching to Thread 1024 (LWP 2348)]
Breakpoint 1, main (argc=3, argv=0xbffff5b4) at server.cpp:96
96 coordinator_impl->_this (ACE_ENV_SINGLE_ARG_PARAMETER);
(gdb) p coordinator_impl
$1 = (class Coordinator *) 0x80bf0a8
(gdb) p *coordinator_impl
Segmentation fault (core dumped)
==================================================================================
The static trace for gdb looked like:
#0 0x080a77bd in fill_in_vptr_fieldno ()
#1 0x080a77f2 in fill_in_vptr_fieldno ()
#2 0x080a77f2 in fill_in_vptr_fieldno ()
#3 0x080a77f2 in fill_in_vptr_fieldno ()
#4 0x080a77f2 in fill_in_vptr_fieldno ()
#5 0x080a77f2 in fill_in_vptr_fieldno ()
#6 0x080a77f2 in fill_in_vptr_fieldno ()
#7 0x080a77f2 in fill_in_vptr_fieldno ()
#8 0x080a77f2 in fill_in_vptr_fieldno ()
#9 0x080a77f2 in fill_in_vptr_fieldno ()
#10 0x080a77f2 in fill_in_vptr_fieldno ()
#11 0x080a77f2 in fill_in_vptr_fieldno ()
#12 0x080a77f2 in fill_in_vptr_fieldno ()
#13 0x080a77f2 in fill_in_vptr_fieldno ()
#14 0x080a77f2 in fill_in_vptr_fieldno ()
#15 0x080a77f2 in fill_in_vptr_fieldno ()
#16 0x080a77f2 in fill_in_vptr_fieldno ()
#17 0x080a77f2 in fill_in_vptr_fieldno ()
#18 0x080a77f2 in fill_in_vptr_fieldno ()
#19 0x080a77f2 in fill_in_vptr_fieldno ()
#20 0x080a77f2 in fill_in_vptr_fieldno ()
[ etc. ]
Just for fun, I tried compiling the same program with gcc 3.1 (prerelease)
and I got the same coredump in gdb.
Does anyone have any ideas as to what the problem could be?
Thanks.
--
Craig Rodrigues
http://www.gis.net/~craigr
rodrigc@attbi.com
next reply other threads:[~2002-05-02 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 14:00 Craig Rodrigues [this message]
2002-05-02 14:11 ` 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=20020502170018.A31253@attbi.com \
--to=rodrigc@attbi.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