public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113612] [13/14 Regression] ICE: SIGSEGV in get_template_info (pt.cc:378) or tree_check (tree.h:3611)
Date: Tue, 06 Feb 2024 15:40:48 +0000	[thread overview]
Message-ID: <bug-113612-4-ZiCJ67tr9i@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113612-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113612

--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(gdb) up
#1  0x0000000001120e27 in get_partial_spec_bindings (tmpl=<template_decl
0x7ffff7fc2080 t>, 
    spec_tmpl=<template_decl 0x7ffff7fc2180 t>, args=<tree_vec 0x7fffea3a7d20>)
    at /home/mpolacek/src/gcc/gcc/cp/pt.cc:25888
25888       = TI_ARGS (get_template_info (DECL_TEMPLATE_RESULT (spec_tmpl)));
(gdb) p spec_tmpl
$1 = <template_decl 0x7ffff7fc2180 t>
(gdb) p DECL_TEMPLATE_RESULT (spec_tmpl)
$2 = <ggc_freed 0x7fffea210e10>

  parent reply	other threads:[~2024-02-06 15:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26  6:02 [Bug c++/113612] New: ICE: SIGSEGV in get_template_info (pt.cc:378) or tree_check (tree.h:3611) with invalid -fpreprocessed zsojka at seznam dot cz
2024-01-26  6:48 ` [Bug c++/113612] [13/14 Regression] " pinskia at gcc dot gnu.org
2024-01-26  6:49 ` pinskia at gcc dot gnu.org
2024-01-26  8:37 ` rguenth at gcc dot gnu.org
2024-02-06 15:40 ` mpolacek at gcc dot gnu.org
2024-02-06 15:40 ` mpolacek at gcc dot gnu.org [this message]
2024-02-06 15:46 ` [Bug c++/113612] [13/14 Regression] ICE: SIGSEGV in get_template_info (pt.cc:378) or tree_check (tree.h:3611) mpolacek at gcc dot gnu.org
2024-02-13  2:00 ` jason at gcc dot gnu.org
2024-02-13 16:15 ` cvs-commit at gcc dot gnu.org
2024-02-13 16:16 ` cvs-commit at gcc dot gnu.org
2024-02-13 16:19 ` jason at gcc dot gnu.org

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-113612-4-ZiCJ67tr9i@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).