From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29936 invoked by alias); 23 Oct 2005 22:13:29 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 29922 invoked by uid 48); 23 Oct 2005 22:13:27 -0000 Date: Sun, 23 Oct 2005 22:13:00 -0000 Message-ID: <20051023221327.29921.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug debug/24490] [4.1 Regression] gcc / gdb backtrace problem In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "kev dot gilbert at cdu dot edu dot au" X-SW-Source: 2005-10/txt/msg03054.txt.bz2 List-Id: ------- Comment #3 from kev dot gilbert at cdu dot edu dot au 2005-10-23 22:13 ------- Just for the record, I've pasted the incorrect gdb output for the second backtrace. It is as follows: #0 0x00240402 in __kernel_vsyscall () #1 0x00726118 in raise () from /lib/libc.so.6 #2 0x00727888 in abort () from /lib/libc.so.6 #3 0x0804839d in main (argc=1, argv=0xbfa69a14) at office/test.c:4 Sorry. And, yes, I should have added the OS & hardware platform. Noted for future reference. -- kev dot gilbert at cdu dot edu dot au changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kev dot gilbert at cdu dot | |edu dot au http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24490