From: Tom Tromey <tromey@redhat.com>
To: "Giovanni Visciano" <giovannivisciano@virgilio.it>
Cc: gcc@sources.redhat.com
Subject: Re: gcj segmentation fault
Date: Wed, 22 Oct 2003 18:31:00 -0000 [thread overview]
Message-ID: <87he21npym.fsf@fleche.redhat.com> (raw)
In-Reply-To: <3F8C9C450000FF06@ims1d.cp.tin.it>
>>>>> "Giovanni" == Giovanni Visciano <giovannivisciano@virgilio.it> writes:
Giovanni> (gdb) run
Giovanni> Starting program: /home/gio/Desktop/a.out
Giovanni> [New Thread 1024 (LWP 488)]
Giovanni> Program received signal SIGSEGV, Segmentation fault.
Giovanni> [Switching to Thread 1024 (LWP 488)]
Giovanni> 0x79730065 in ?? ()
Try "bt". That should tell us something.
I suspect that you have the wrong version of binutils. We've seen
crashes in exception handling when ld is too old. That's just a guess
though.
Tom
next prev parent reply other threads:[~2003-10-22 17:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 22:18 Giovanni Visciano
2003-10-21 22:45 ` Jeff Sturm
2003-10-22 17:21 ` Giovanni Visciano
2003-10-22 18:31 ` Tom Tromey [this message]
2003-10-22 18:49 ` Giovanni Visciano
2003-10-22 18:56 ` Andrew Pinski
2003-10-22 19:23 ` Jeff Sturm
2003-10-22 20:04 ` Andrew Haley
2003-10-22 21:46 Giovanni Visciano
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=87he21npym.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gcc@sources.redhat.com \
--cc=giovannivisciano@virgilio.it \
/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).