Article View: gnu.g++.bug
Article #1008Getting fatal signal 6 from cc1plus
From: patc
Date: Thu, 01 Oct 1992 16:48
Date: Thu, 01 Oct 1992 16:48
21 lines
1418 bytes
1418 bytes
Hi, sorry to bother you, but I'm getting SIGIOT from cc1plus when debugging is enabled. I'm trying to make libg++-2.2 with gcc-2.2.2 running on an i386-sysv4 (and used that argument with configure). This occurs with stage 1 and stage 2 compilers. There were no compare errors with stage 3. I've made no modifications, everything's straight "out of the box," directories and all. The file it crashes on is libg++/src/LogNorm.cc. According to Gdb 4.5's backtrace of the coredump, the last two items on the stack were var_labelno, which turns out to be a variable (with a value of 48). The third item is an actual function, output_mem_loc_descriptor (rtl=0x8194e84), directly after the line that goes case PLUS: output_mem_loc_descriptor (XEXP (rtl, 0)); The backtrace is huge. If you want a coredump or the backtrace or whatever, let me know. Not being able to debug this file is no big deal to me, I just thought I'd let you know. Let me know if I can do anything to help.
Technical Details
Message-ID:
<9210020048.AA23492@relay2.UU.NET>Path:
arc1-ca.pugleaf.net!sparky!uunet!convex!darwin.sura.net!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!cmcoa.UUCP!patcShow Full Headers
Complete Article Headers
Newsgroups: gnu.g++.bug Path: arc1-ca.pugleaf.net!sparky!uunet!convex!darwin.sura.net!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!cmcoa.UUCP!patc From: patc@cmcoa.UUCP Subject: Getting fatal signal 6 from cc1plus Message-ID: <9210020048.AA23492@relay2.UU.NET> Sender: gnulists@ai.mit.edu Organization: GNUs Not Usenet Distribution: gnu Date: Thu, 1 Oct 1992 16:48:02 GMT Approved: bug-g++@prep.ai.mit.edu Lines: 22