no feedback, closing the report
** Changed in: gcc-4.3 (Ubuntu)
Status: Incomplete = Invalid
--
cc1plus crashed with SIGSEGV
https://bugs.launchpad.net/bugs/343220
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
is this reproducible with gcc-4.4 or gcc-snapshot from karmic?
** Changed in: gcc-4.3 (Ubuntu)
Status: Triaged = Incomplete
--
cc1plus crashed with SIGSEGV
https://bugs.launchpad.net/bugs/343220
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Visibility changed to: Public
--
cc1plus crashed with SIGSEGV
https://bugs.launchpad.net/bugs/343220
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Another valuable thing I should mention is that this system has a
dmraid-based (i.e. software) RAID0 on two disks and it uses ext4 as
filesystem.
In fact, the corruption maybe due to something failing in these layers
(dmraid/ext4); but as I said GCC shouldn't crash, no matter what garbage
you
StacktraceTop:linemap_lookup (set=0x5675d00, line=84) at
../../src/libcpp/line-map.c:277
expand_location (loc=84)
diagnostic_build_prefix (diagnostic=0x7fffb6e76010)
cp_diagnostic_starter (context=0xe550a0,
diagnostic_report_diagnostic (context=0xe550a0,
** Attachment removed: CoreDump.gz
If you attach the pch file, then please compress it using lzma -9. I
doubt somebody will look at this report knowing that this is a corrupted
file; it's likely that we will close this report as won't fix. Make your
you attach an uncorrupted and the corrupted file (or put these files
somewhere on
