public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/27156] New: SIGSEGV in operator delete() / wrong-code?
Date: Fri, 14 Apr 2006 09:35:00 -0000 [thread overview]
Message-ID: <bug-27156-7667@http.gcc.gnu.org/bugzilla/> (raw)
$ i486-gnu-linux-g++ -v
Using built-in specs.
Target: i486-gnu-linux
Configured with: ../configure --target=i486-gnu-linux
--prefix=/local/devel/toolchain41/i486-gnu-linux
--libdir=/local/devel/toolchain41/i486-gnu-linux/lib
--libexecdir=/local/devel/toolchain41/i486-gnu-linux/lib
--with-slibdir=/local/devel/toolchain41/i486-gnu-linux/lib
--with-sysroot=/local/devel/toolchain41/i486-gnu-linux
--disable-multilib --disable-nls --disable-libmudflap
--disable-libssp --disable-libstdcxx-pch --enable-shared
--enable-threads=posix --enable-__cxa_atexit --enable-languages=c,c++
--enable-symvers=gnu
Thread model: posix
gcc version 4.1.1 20060405 (prerelease) (PLD-Linux)
$ i486-gnu-linux-g++ \
-I/local/devel/buildenv41/i486-gnu-linux/STLport/include/stlport \
-L/local/devel/buildenv41/i486-gnu-linux/STLport/lib \
testDrv.cpp -o testDrv --save-temps -pthread \
-Wl,-rpath,/local/devel/buildenv41/i486-gnu-linux/STLport/lib \
-lstlport -nodefaultlibs -lc -O2
Program received signal SIGSEGV, Segmentation fault.
0x55674c91 in free () from /lib/tls/libc.so.6
(gdb) bt
#0 0x55674c91 in free () from /lib/tls/libc.so.6
#1 0x555ded2b in operator delete ()
from /local/devel/buildenv41/i486-gnu-linux/
STLport/lib/libstlport.so.5.0
#2 0x08048d19 in main ()
testcase works with 3.3.6, 3.4.x and 4.1.x(-fno-strict-aliasing).
4.0.x and 4.2.x not tested. 4.1.x(-fstrict-aliasing) causing segv
in the testcase. -Wall -Wstrict-aliasing=2 says nothing :(
--
Summary: SIGSEGV in operator delete() / wrong-code?
Product: gcc
Version: 4.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: pluto at agmk dot net
GCC build triplet: i486-linux
GCC host triplet: i486-linux
GCC target triplet: i486-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27156
next reply other threads:[~2006-04-14 9:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 9:35 pluto at agmk dot net [this message]
2006-04-14 9:36 ` [Bug other/27156] " pluto at agmk dot net
2006-04-19 0:36 ` pinskia at gcc dot gnu dot org
2006-04-19 0:39 ` pinskia at gcc dot gnu dot org
2006-04-19 8:13 ` pluto at agmk dot net
2006-04-19 8:33 ` pluto at agmk dot net
2006-04-19 8:38 ` pluto at agmk dot net
2006-04-30 8:02 ` pinskia at gcc dot gnu dot org
2006-05-03 9:02 ` pluto at agmk dot net
2006-05-03 9:05 ` pluto at agmk dot net
2006-05-03 9:19 ` pluto at agmk dot net
2006-05-03 9:22 ` pluto at agmk dot net
2006-05-10 22:37 ` pluto at agmk dot net
2006-08-10 9:58 ` pluto at agmk dot net
2006-08-10 9:58 ` pluto at agmk dot net
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=bug-27156-7667@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: link
Be 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).