From: Andrew Cagney <ac131313@cygnus.com>
To: Ralf Narozny <RNarozny@t-online.de>
Cc: gdb@sourceware.cygnus.com
Subject: Re: gdb crashes with seg fault
Date: Wed, 10 Oct 2001 15:05:00 -0000 [thread overview]
Message-ID: <3BC4C5FC.90603@cygnus.com> (raw)
In-Reply-To: <3BC4BBF8.9050207@web.de>
> Hello all!
>
> I got a strange problem. gdb is crashing with a segmentation fault while checking a 120MB large binary with each core that this binary produces.
>
> I hope I'm just too dumb to do the right things. But the problem occurred first after using gcc 3.0.1 to compile the binary. All was ok before that.
>
> Ok, here is some data you might need.
>
> Machine: Athlon 1.3GHz, 512M RAM
> Linux version 2.4.4-4GB (root@Pentium.suse.de) (gcc version 2.95.3 20010315 (SuSE))
> GDB: Version 5.0 (one self compiled one out of SuSE Linux distribution)
> GCC: Version 3.0.1 (self compiled)
FYI, the first thing to do is download a current snapshot and try that.
There are likely differences between SuSE's GDB and the official FSF GDB.
Andrew
http://sources.redhat.com/gdb/download/
next prev parent reply other threads:[~2001-10-10 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 14:22 Ralf Narozny
2001-10-10 15:05 ` Andrew Cagney [this message]
2001-10-10 15:30 ` Ralf Narozny
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=3BC4C5FC.90603@cygnus.com \
--to=ac131313@cygnus.com \
--cc=RNarozny@t-online.de \
--cc=gdb@sourceware.cygnus.com \
/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