From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-198508-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 99261 invoked by alias); 17 Mar 2019 10:50:25 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 99244 invoked by uid 89); 17 Mar 2019 10:50:25 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=HCc:U*gcc, driver, H*f:sk:d0fb140, H*i:sk:d0fb140
X-HELO: mail-wm1-f54.google.com
Received: from mail-wm1-f54.google.com (HELO mail-wm1-f54.google.com) (209.85.128.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 17 Mar 2019 10:50:23 +0000
Received: by mail-wm1-f54.google.com with SMTP id v14so1345682wmf.2        for <gcc@gcc.gnu.org>; Sun, 17 Mar 2019 03:50:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to         :cc;        bh=oSKvJiSpNPu0aeINNwNHILwEB1DZrCkCSOuy9xWBSEE=;        b=dxSc8rzWYJz4jQaQP9YhKtfWG+7LLWpW8HEYQys+YpXpHB682Tlh0I9tQdsBJM4ddv         PcD0DtpYSsotE2FxQ6YQuuQMXLtK/J2uIhsRepCTev5PEuAieCz66hBw4NxPCYcUevmL         8NVBkGX4sYqxGDsxIDurXkE2BMXMJuY6MEOw86G9jM6xe071sWPVFZDCbYKSD8UcSQ0S         yAgusDby+UDOo7T4xnv3wcCnMaVplklvBhK23wW4ZdNN0fJ2oXiCkw+8s9EznJqnWmtL         OSX3Tt2vgZsJv93fsQOkDrTSaHrRS9WwV+s9lfLOG+y/vU1IeO0fz4zESoq4nBDBDoWq         2oxg==
MIME-Version: 1.0
References: <d0fb1400-0321-d8e3-9f7e-afcb4b14c31a@gmail.com>
In-Reply-To: <d0fb1400-0321-d8e3-9f7e-afcb4b14c31a@gmail.com>
From: Jonathan Wakely <jwakely.gcc@gmail.com>
Date: Sun, 17 Mar 2019 10:50:00 -0000
Message-ID: <CAH6eHdSAUAZUHr=3gp_crkN1jH0CX2pvKOFL4UjEmdoVT=DjKw@mail.gmail.com>
Subject: Re: Bug gives no stack trace on segfault
To: nick <xerofoify@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
X-SW-Source: 2019-03/txt/msg00122.txt.bz2

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++.