From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: nick <xerofoify@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Bug gives no stack trace on segfault
Date: Sun, 17 Mar 2019 10:50:00 -0000 [thread overview]
Message-ID: <CAH6eHdSAUAZUHr=3gp_crkN1jH0CX2pvKOFL4UjEmdoVT=DjKw@mail.gmail.com> (raw)
In-Reply-To: <d0fb1400-0321-d8e3-9f7e-afcb4b14c31a@gmail.com>
On Sun, 17 Mar 2019, 00:21 nick, <xerofoify@gmail.com> wrote:
> Greetings,
>
> I've been busy so this probably has been fixed in since I last worked on
> it:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88395
>
> I was using these instructions to try and get a trace:
> https://www.gnu.org/software/gcc/bugs/segfault.html
>
> But nothing seems to be outputted and don't known if that's normal. Here
> is what I'm
> running the program with and I've enabled --enable-checking:
>
> gdb --args ./bin/g++ -v -da -Q -fconcepts test.cpp
>
That is not what the instructions you linked to tell you to do.
You need to run that command to find out how the g++ driver invokes the
cc1plus compiler, and then debug cc1plus, not g++.
next prev parent reply other threads:[~2019-03-17 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 0:21 nick
2019-03-17 10:50 ` Jonathan Wakely [this message]
2019-03-17 14:51 ` nick
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='CAH6eHdSAUAZUHr=3gp_crkN1jH0CX2pvKOFL4UjEmdoVT=DjKw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=xerofoify@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).