public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "sven dot anderson at snom dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/11648] New: gdb crashes with segmentation fault when printing larger objects Date: Mon, 31 May 2010 10:26:00 -0000 [thread overview] Message-ID: <20100531102611.11648.sven.anderson@snom.com> (raw) System: Linux anderssv-lx-01 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686 GNU/Linux Glibc: 2.11.1-0ubuntu7.1 g++: 4.4.3-4ubuntu5 The following happens only with gdb 7.1 and latest snapshot, 7.0.1 works fine. Since my last system update to Ubuntu 10.4 I was unable to use the debugger for our software project in eclipse. I noticed that gdb has been updated to 7.1 and found out that I can reproduce a segmentation fault with a few steps by just setting a breakpoint in main and from there printing a string object three times (own implementation, not std::string) and quitting it with q each time. I will attach a session log with glibc debugging informations and backtrace. In eclipse it even crashes when I step through the code, but I don't know if there are also prints involved while stepping in eclipse. If you need any further information I will try to provide it. -- Summary: gdb crashes with segmentation fault when printing larger objects Product: gdb Version: 7.1 Status: UNCONFIRMED Severity: critical Priority: P2 Component: c++ AssignedTo: unassigned at sourceware dot org ReportedBy: sven dot anderson at snom dot com CC: gdb-prs at sourceware dot org,sven dot anderson at snom dot com http://sourceware.org/bugzilla/show_bug.cgi?id=11648 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-05-31 10:26 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-31 10:26 sven dot anderson at snom dot com [this message] 2010-05-31 11:44 ` [Bug c++/11648] " sven dot anderson at snom dot com 2010-05-31 11:45 ` sven dot anderson at snom dot com 2010-05-31 11:50 ` sven dot anderson at snom dot com 2010-06-03 15:52 ` tromey at redhat dot com 2010-06-17 7:23 ` steffenschmidt dot ext at siemens dot com 2010-06-17 17:06 ` tromey at redhat dot com 2010-09-03 10:33 ` steffenschmidt dot ext at siemens dot com 2010-09-03 10:37 ` steffen-schmidt at siemens dot com 2010-09-21 13:56 ` sven dot anderson at snom dot com 2010-09-21 14:02 ` sven dot anderson at snom dot com 2010-09-21 14:04 ` sven dot anderson at snom dot com 2010-09-27 17:49 ` tromey at redhat dot com 2010-09-28 9:09 ` sven dot anderson at snom dot com 2010-09-28 12:03 ` sven dot anderson at snom dot com 2010-09-28 12:13 ` sven dot anderson at snom dot com 2010-09-28 12:29 ` sven dot anderson at snom dot com 2010-09-28 12:35 ` sven dot anderson at snom 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=20100531102611.11648.sven.anderson@snom.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).