From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1370 invoked by alias); 21 May 2015 17:26:23 -0000 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 Received: (qmail 685 invoked by uid 55); 21 May 2015 17:26:22 -0000 From: "stanton at haas dot berkeley.edu" To: gdb-prs@sourceware.org Subject: [Bug gdb/18436] Can't print dynamically allocated global array Date: Thu, 21 May 2015 17:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.9 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: stanton at haas dot berkeley.edu X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-q2/txt/msg00304.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18436 --- Comment #10 from stanton at haas dot berkeley.edu --- Final follow-up (for now): gdb works fine if you add a -g flag to both the compilation and the linking step. Not sure why, but at least it=E2=80=99s working now. > gcc -g -c -o main.o main.c > gcc -g -o main main.o=20 > On May 20, 2015, at 1:15 PM, Richard Stanton = wrote: >=20 > I just noticed something odd. Using gcc 5.1 and gdb 7.7.1 (both MacPorts)= , I can inspect v[0] fine if I compile like this: >=20 > gcc -g main.c -o main >=20 > It fails if I compile the same program (same gcc, some gdb) like this: >=20 > gcc -g -c -o main.o main.c > gcc -o main main.o=20 >=20 > Any idea why this should be different?=20 >=20 >=20 >> On May 20, 2015, at 11:17 AM, Richard Stanton wrote: >>=20 >> Unfortunately, the workaround below doesn=E2=80=99t work on my system: >>=20 >> (gdb) print vec[0] >> cannot subscript something of type `' >> (gdb) print ((double*)vec)[0] >> Cannot access memory at address 0x200000 >>=20 >> I just installed MacPorts gcc 5.1.0, and also hand-compiled gdb 7.9.1. I= t didn=E2=80=99t help. >>=20 >>=20 > --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-18112-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 21 17:39:52 2015 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 61389 invoked by alias); 21 May 2015 17:39:52 -0000 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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 61342 invoked by uid 48); 21 May 2015 17:39:50 -0000 From: "dje at google dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/17976] ptype (anonymous namespace) doesn't work Date: Thu, 21 May 2015 17:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dje at google dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-q2/txt/msg00306.txt.bz2 Content-length: 474 https://sourceware.org/bugzilla/show_bug.cgi?id=17976 dje at google dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from dje at google dot com --- patch committed -- You are receiving this mail because: You are on the CC list for the bug.