public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug exp/27265] gdbtypes.c:3429: internal-error: type* init_complex_type(const char*, type*): Assertion `target_type->code () == TYPE_CODE_INT || target_type->code () == TYPE_CODE_FLT' failed. Date: Thu, 28 Jan 2021 11:05:43 +0000 [thread overview] Message-ID: <bug-27265-4717-ku8hsNn3Sp@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27265-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27265 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot org --- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> --- Bisects to: ... commit c34e87146628a14cf662dca46aac893d06502f52 Author: Tom Tromey <tom@tromey.com> Date: Wed Apr 1 14:09:52 2020 -0600 Implement complex arithmetic ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-01-28 11:05 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-28 8:48 [Bug exp/27265] New: " vries at gcc dot gnu.org 2021-01-28 8:54 ` [Bug exp/27265] " vries at gcc dot gnu.org 2021-01-28 10:04 ` vries at gcc dot gnu.org 2021-01-28 11:05 ` vries at gcc dot gnu.org [this message] 2021-01-28 11:09 ` vries at gcc dot gnu.org 2021-01-28 11:26 ` vries at gcc dot gnu.org 2021-01-28 11:28 ` vries at gcc dot gnu.org 2021-01-28 12:50 ` vries at gcc dot gnu.org 2021-01-28 13:07 ` vries at gcc dot gnu.org 2021-02-05 9:56 ` cvs-commit at gcc dot gnu.org 2021-02-05 9:58 ` vries 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-27265-4717-ku8hsNn3Sp@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: linkBe 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).