: critical
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: eyenseo at gmail dot com
Target Milestone: ---
Created attachment 37264
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37264&action=edit
Precompiled
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
eyenseo at gmail dot com changed:
What|Removed |Added
Attachment #37264|0 |1
is obsolete
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #3 from eyenseo at gmail dot com ---
This bug does not appear in 5.3.0 - using Arch Linux.
I would like to know what a critical or major bug would be if a segfault is
not? I think that a segfault is quite devastating, especially when
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #4 from eyenseo at gmail dot com ---
The ubuntu system I used is "normal" no testing / unstable.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #5 from eyenseo at gmail dot com ---
(In reply to Jonathan Wakely from comment #2)
> I can't reproduce this, it might be specific to Ubuntu, maybe caused by
> mixing gcc 4.9 with the lisbtdc++ from gcc 5 (which would mean
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #7 from eyenseo at gmail dot com ---
(In reply to Jonathan Wakely from comment #6)
Thanks for letting me know of the "importance-ignoring" one two less clicks
next time ;)
I didn't include the segfault in the precom
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #9 from eyenseo at gmail dot com ---
(In reply to Jonathan Wakely from comment #8)
> That only shows how your gcc compiler was built. If I understand correctly
> the Ubuntu packages that provide libstdc++.so.6 come from a dif
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #11 from eyenseo at gmail dot com ---
(In reply to Jonathan Wakely from comment #10)
> Use ldd to see which library is used at runtime. See what file that symlink
> points to. Compare with the version numbers of the releases.
&g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #12 from eyenseo at gmail dot com ---
(In reply to Jonathan Wakely from comment #10)
> Use ldd to see which library is used at runtime. See what file that symlink
> points to. Compare with the version numbers of the releases.
&g
