This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Bug gives no stack trace on segfault
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: nick <xerofoify at gmail dot com>
- Cc: GCC Development <gcc at gcc dot gnu dot org>
- Date: Sun, 17 Mar 2019 10:50:10 +0000
- Subject: Re: Bug gives no stack trace on segfault
- References: <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++.