public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mannu7410 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/42033] libstdc++ seems to miss std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*>(char*, char*, std::allocator<char> const&) Date: Tue, 28 Apr 2015 05:23:00 -0000 [thread overview] Message-ID: <bug-42033-4-P2q9TpaROI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-42033-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42033 Manoj <mannu7410 at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mannu7410 at gmail dot com --- Comment #12 from Manoj <mannu7410 at gmail dot com> --- Hi, I am facing a similar issue. Following is the error that I am facing at run time: 0x00007ffff6a69e3e in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x00007ffff6a69e3e in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff704c842 in std::string::_Rep::_M_clone(std::allocator<char> const&, unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x00007ffff704c8e0 in std::string::reserve(unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #3 0x00007ffff704cc10 in std::string::append(char const*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x0000000000414577 in std::basic_string<char, std::char_traits<char>, std::allocator<char> > std::operator+<char, std::char_traits<char>, std::allocator<char> >(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char const*) () #5 0x000000000040bb78 in ?? () #6 0x00000000004273ef in ?? () #7 0x0000000000427adc in ?? () #8 0x000000000040e01d in ?? () #9 0x00000000004273ef in ?? () #10 0x0000000000427adc in ?? () #11 0x000000000040beec in ?? () #12 0x00000000004273ef in ?? () #13 0x0000000000427adc in ?? () #14 0x000000000040beec in ?? () #15 0x00000000004273ef in ?? () #16 0x0000000000427adc in ?? () ---Type <return> to continue, or q <return> to quit--- #17 0x000000000040c38c in ?? () #18 0x00000000004273ef in ?? () #19 0x00000000004219ea in ?? () #20 0x000000000041c9c0 in ?? () #21 0x00007ffff69f2ec5 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #22 0x0000000000408cb9 in ?? () (gdb) fr #0 0x00007ffff6a69e3e in ?? () from /lib/x86_64-linux-gnu/libc.so.6 This is very random and I am not sure if this is some memory related issue or what. Any help will be great. Thanks
next prev parent reply other threads:[~2015-04-28 5:23 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-42033-4@http.gcc.gnu.org/bugzilla/> 2010-09-29 13:31 ` manu at gcc dot gnu.org 2010-12-12 20:48 ` hubicka at gcc dot gnu.org 2015-04-28 5:23 ` mannu7410 at gmail dot com [this message] 2015-04-28 9:24 ` redi at gcc dot gnu.org 2009-11-13 19:25 [Bug c++/42033] New: " hubicka at gcc dot gnu dot org 2009-11-13 20:09 ` [Bug c++/42033] " jason at gcc dot gnu dot org 2009-11-13 20:37 ` paolo dot carlini at oracle dot com 2009-11-13 21:02 ` hubicka at ucw dot cz 2009-11-13 21:11 ` paolo dot carlini at oracle dot com 2009-11-13 21:16 ` hubicka at ucw dot cz 2009-11-13 21:59 ` rguenth at gcc dot gnu dot org 2009-11-13 21:59 ` rguenth at gcc dot gnu dot org 2009-11-13 23:18 ` jason at redhat dot com 2010-09-13 15:23 ` paolo dot carlini at oracle dot com
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-42033-4-P2q9TpaROI@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: linkBe 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).