public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: gabriel@dit.upm.es To: gcc-gnats@gcc.gnu.org Subject: c++/9706: Internal error: segmentation fault Date: Fri, 14 Feb 2003 14:36:00 -0000 [thread overview] Message-ID: <20030214142814.19476.qmail@sources.redhat.com> (raw) >Number: 9706 >Category: c++ >Synopsis: Internal error: segmentation fault >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Feb 14 14:36:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Gabriel Huecas >Release: 3.2 >Organization: >Environment: SuSE 8.1, PC arch P4 >Description: Hello, I have got an internal error, asking me to report the bug. The code is tricky, but should not crash compiler. Thank you very much. --- output of "g++ file.cc" -- THIS LINE NOT INCLUDED--- file.cc:23: internal error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. >How-To-Repeat: g++ file.cc >Fix: change the name of the type or static variable in class "item_t" >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="file.ii" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="file.ii" IyAxICJmaWxlLmNjIgojIDEgIjxidWlsdC1pbj4iCiMgMSAiPGNvbW1hbmQgbGluZT4iCiMgMSAi ZmlsZS5jYyIKCmNsYXNzIGl0ZW1fdAp7CiAgICBlbnVtIGRlYnVnTGV2ZWwgewogICAgICAgIGtf cGFyYW5vaWM9NjY2CiAgICB9OwoKICAgIHN0YXRpYyBpbnQgZGVidWdMZXZlbDsKfTsKCgp0ZW1w bGF0ZSA8Y2xhc3MgSywgY2xhc3MgVD4gY2xhc3MgZGljdGlvbmFyeV90CjogcHVibGljIHZpcnR1 YWwgaXRlbV90CnsKfTsKCmNsYXNzIGljZlN0cmluZ190CnsKfTsKCnRlbXBsYXRlIDxjbGFzcyBU PiBjbGFzcyBzdHJpbmdrZXlEaWN0aW9uYXJ5X3Q6CiAgICBwdWJsaWMgZGljdGlvbmFyeV90PGlj ZlN0cmluZ190LCBUPgp7Cn07Cg==
next reply other threads:[~2003-02-14 14:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-14 14:36 gabriel [this message] 2003-02-14 21:40 bangerth 2003-02-16 18:04 lerdsuwa 2003-02-17 15:06 Gabriel Huecas Fernandez-Toribio 2003-02-18 15:16 Kriang Lerdsuwanakij 2003-02-18 16:16 Gabriel Huecas Fernandez-Toribio
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=20030214142814.19476.qmail@sources.redhat.com \ --to=gabriel@dit.upm.es \ --cc=gcc-gnats@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: 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).