public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "hellmund at fzi dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18406] GDB crashes after segmentation fault in program
Date: Thu, 21 May 2015 22:05:00 -0000 [thread overview]
Message-ID: <bug-18406-4717-lfJQHzBMCh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18406-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18406
--- Comment #2 from Andi Hellmund <hellmund at fzi dot de> ---
Hi,
sorry for the delay in my response.
> I assume you're using GDB 7.9,
Yes, I was using GDB 7.9, built from the vanilla sources from the GNU
web page.
GNU gdb (GDB) 7.9
This GDB was configured as "x86_64-unknown-linux-gnu".
> but it would be nice to know if you have
> distro-specific patches on it.
No, no distro packages included in the sources.
> What is your distro?
My distribution is Ubuntu 14.04, 64-bit.
> Also, what is the version
> of your g++ compiler?
The compiler is a self-built gcc 4.9.2, again from the vanilla GNU
sources. We used -std=c++14 as language standard option.
> Are you just doing a './gdb binary' and then 'run', or
> something else? Thanks.
Mhhh, I was trying again to reproduce the bug, but no I fail as well
which is strange. I have no real explanation for this, other than that
Ubuntu is bogus or - which is obviously less likely - that I did
something fundamentally wrong :-)
I will try a bit further to reproduce this (we had a second system at
work that was crashing) and will let you know if find out how to
reproduce this.
Sorry for this and thanks,
Andi
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-05-21 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 7:56 [Bug gdb/18406] New: " hellmund at fzi dot de
2015-05-15 22:20 ` [Bug gdb/18406] " sergiodj at redhat dot com
2015-05-21 22:05 ` hellmund at fzi dot de [this message]
2015-05-21 22:12 ` hellmund at fzi dot de
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=bug-18406-4717-lfJQHzBMCh@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).