public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ja11sop at yahoo dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53490] Segmentation Fault when accessing std::set
Date: Fri, 25 May 2012 22:51:00 -0000 [thread overview]
Message-ID: <bug-53490-4-2ku0cruySG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53490-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53490
--- Comment #5 from Jamie Allsop <ja11sop at yahoo dot co.uk> 2012-05-25 22:16:41 UTC ---
(In reply to comment #2)
> I only tried briefly but couldn't reproduce a crash with boost 1.47, will try
> later with boost 1.49
For clarity I should say I just tried with a vanilla build of 1.47 and get
essentially the same backtrace here.
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7933427 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) bt
#0 0x00007ffff7933427 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1 0x0000000000464233 in std::_Rb_tree_iterator<std::string>::operator--
(this=0x7fffffffdc60)
at /usr/include/c++/4.7/bits/stl_tree.h:203
#2 0x0000000000462db0 in std::_Rb_tree<std::string, std::string,
std::_Identity<std::string>, std::less<std::string>,
std::allocator<std::string> >::_M_insert_unique<std::string const&>
(this=0x6a4540, __v=...)
at /usr/include/c++/4.7/bits/stl_tree.h:1295
#3 0x0000000000461c2b in std::set<std::string, std::less<std::string>,
std::allocator<std::string> >::insert (
this=0x6a4540, __x=...) at /usr/include/c++/4.7/bits/stl_set.h:415
#4 0x000000000047afb5 in boost::program_options::store (options=..., xm=...,
utf8=false)
at libs/program_options/src/variables_map.cpp:98
#5 0x0000000000460480 in store_properties (argc=2, argv=0x7fffffffe0b0) at
program_options_test.cpp:31
#6 0x00000000004607db in main (argc=1, argv=0x7fffffffe1c8) at
program_options_test.cpp:64
(gdb)
next prev parent reply other threads:[~2012-05-25 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 18:13 [Bug c++/53490] New: " ja11sop at yahoo dot co.uk
2012-05-25 18:22 ` [Bug c++/53490] " redi at gcc dot gnu.org
2012-05-25 18:24 ` redi at gcc dot gnu.org
2012-05-25 20:42 ` daniel.kruegler at googlemail dot com
2012-05-25 22:16 ` ja11sop at yahoo dot co.uk
2012-05-25 22:51 ` ja11sop at yahoo dot co.uk [this message]
2012-05-26 0:14 ` redi at gcc dot gnu.org
2012-05-26 13:26 ` ja11sop at yahoo dot co.uk
2012-05-28 9:32 ` ja11sop at yahoo dot co.uk
2012-05-28 9:40 ` redi at gcc dot gnu.org
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-53490-4-2ku0cruySG@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).