From: Erik Leunissen <e.leunissen@hccnet.nl>
Cc: gdb@sourceware.org
Subject: Re: segfault
Date: Sun, 12 Nov 2006 21:40:00 -0000 [thread overview]
Message-ID: <455794DB.2080503@hccnet.nl> (raw)
In-Reply-To: <4557902A.9020504@hccnet.nl>
Erik Leunissen wrote:
> Daniel Jacobowitz wrote:
>>
>> Is s->filename NULL?
>>
>
> It appears that segfaults occur in more programs/libraries on my system
> since a week or so. These programs have in common that they were
> compiled with a home-compiled upgrade of gcc-4.1.1. Gdb-6.4 was one of
> the programs compiled with the upgraded compiler.
>
> I am now recompiling with the system supplied compiler (gcc-3.1.1).
> Whether the segfault persists, I will report later.
>
> Erik Leunissen
> =============
>
>
The segfault does not occur anymore with gdb-6.4 compiled by the system
supplied compiler. Therefore, I attribute the observed segfault to a
broken gcc-4.1.1 and not to gdb-6.4
Sorry for the noise.
Erik.
prev parent reply other threads:[~2006-11-12 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 10:22 segfault Erik Leunissen
2006-11-06 10:28 ` segfault Erik Leunissen
2006-11-06 13:36 ` segfault Daniel Jacobowitz
2006-11-07 18:43 ` segfault Erik Leunissen
2006-11-12 21:20 ` segfault Erik Leunissen
2006-11-12 21:40 ` Erik Leunissen [this message]
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=455794DB.2080503@hccnet.nl \
--to=e.leunissen@hccnet.nl \
--cc=gdb@sourceware.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