From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12423 invoked by alias); 31 May 2010 10:26:12 -0000 Received: (qmail 12399 invoked by uid 48); 31 May 2010 10:26:12 -0000 Date: Mon, 31 May 2010 10:26:00 -0000 From: "sven dot anderson at snom dot com" To: gdb-prs@sourceware.org Message-ID: <20100531102611.11648.sven.anderson@snom.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug c++/11648] New: gdb crashes with segmentation fault when printing larger objects X-Bugzilla-Reason: CC Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2010-q2/txt/msg00332.txt.bz2 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.