public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mahek2k1 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/26094] Segmentation fault in  Linux 7.1 GCC 3.1 Kernel 2.4.9-45lxset34smp
Date: Mon, 06 Feb 2006 21:05:00 -0000	[thread overview]
Message-ID: <20060206210503.26697.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26094-12131@http.gcc.gnu.org/bugzilla/>



------- 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 <vtable for std::num_put<char, 
std::ostreambuf_iterator<char, std::char_traits<char> > >+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


  parent reply	other threads:[~2006-02-06 21:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03 23:23 [Bug libstdc++/26094] New: " mahek2k1 at yahoo dot com
2006-02-04 18:49 ` [Bug libstdc++/26094] " pinskia at gcc dot gnu dot org
2006-02-04 20:51 ` rguenth at gcc dot gnu dot org
2006-02-05 15:41 ` pinskia at gcc dot gnu dot org
2006-02-06 21:05 ` mahek2k1 at yahoo dot com [this message]
2006-02-08 16:34 ` bkoz at gcc dot gnu dot org

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=20060206210503.26697.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).