From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26711 invoked by alias); 6 Feb 2006 21:05:05 -0000 Received: (qmail 26698 invoked by uid 48); 6 Feb 2006 21:05:03 -0000 Date: Mon, 06 Feb 2006 21:05:00 -0000 Message-ID: <20060206210503.26697.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/26094] Segmentation fault in Linux 7.1 GCC 3.1 Kernel 2.4.9-45lxset34smp In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "mahek2k1 at yahoo dot com" 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 X-SW-Source: 2006-02/txt/msg00565.txt.bz2 List-Id: ------- Comment #3 from mahek2k1 at yahoo dot com 2006-02-06 21:05 ------- (In reply to comment #2) > Please try with Linux and gcc that are still supported. Thanks for the inputs, sorry for making it confusing, the linux is Redhat 7.1 Additional info GDB Stack trace is following: (gdb) run Starting program: tryrdstategrid.2 Error opening 'test.txt' Program received signal SIGSEGV, Segmentation fault. 0x00000000 in ?? () (gdb) backtrace #0 0x00000000 in ?? () #1 0x4011e6f0 in __libc_start_main ( main=0x400ad648 > >+8>, argc=0, ubp_av=0x400ad1e8, init=0, fini=0, rtld_fini=0, stack_end=0x0) at ../sysdeps/generic/libc-start.c:129 Previous frame inner to this frame (corrupt stack?) (gdb) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26094