Bug 243292
Summary: | Program that works otherwise segfaults when enabling libstdc++ debug defines | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Albert Strasheim <13640887> |
Component: | gcc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 6 | CC: | bkoz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-06-12 20:48:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Albert Strasheim
2007-06-08 12:24:29 UTC
From looking at the stack trace, I think this is probably an issue with debug mode's thread safety. There have been improvements to support for threads in debug mode, and it looks like gcc-4_1-branch is lagging mainline and gcc-4_2-branch. The relevant file is gcc/libstdc++-v3/src/debug.cc. See the added mutexes. I would ask the reporter to do one of the following things: 1) try to use the FSF gcc-4.2.0 compiler (which has these mt fixes), instead of gcc-4.1.x, and see if you still have this issue. If it goes away, we'll try to backport the fixes to 4.1.x. 2) try to come up with a single file that we can use to reproduce your issue, and attach it to this bug report. Then, we can tell you if this is indeed the issue. best, benjamin I suspect this is a false alarm. The stack trace contains a hint as to what I did wrong: link "normal" CppUnit against my debug code. This causes the CppUnit::Message destructor segfault when it tries to deallocate a debug string, thinking it's a normal string. It would be really handy if there were a way to make mixing of debug and normal code cause a link error or something. Anyway, this bug can be resolved as invalid. |