This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: gdb/1801: Linux g++ C++ assert
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 30 Oct 2004 02:18:01 -0000
- Subject: Re: gdb/1801: Linux g++ C++ assert
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR gdb/1801; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: xavier.warin@der.edfgdf.fr
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/1801: Linux g++ C++ assert
Date: Fri, 29 Oct 2004 22:14:17 -0400
On Fri, Oct 29, 2004 at 09:15:49AM -0000, xavier.warin@der.edfgdf.fr wrote:
> Problem with g++3.3.4 When using an assert in C/C++, if the assert
> fails, it is impossible to see where the failure is .
>
> g++ --version
> g++ (GCC) 3.3.4 (Debian 1:3.3.4-13)
>
> g++ -o test2 -g test2.cpp
>
> clr34bj:~> gdb test2
> GNU gdb 6.2.1
You are using Debian; I recommend you try using both the Debian package
of GDB, and installing the libc6-dbg package. I get this backtrace
from your test case:
Program received signal SIGABRT, Aborted.
0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x40144e23 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0x4014671c in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0x4013e3cb in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#4 0x080483fd in main () at test2.cpp:11
--
Daniel Jacobowitz