From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 124567 invoked by alias); 3 Jan 2017 21:32:31 -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 124424 invoked by uid 48); 3 Jan 2017 21:32:29 -0000 From: "spencerbaugh at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/15468] crash breakpoint.c:5940: internal-error: print_one_breakpoint_location Date: Tue, 03 Jan 2017 21:32: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: 7.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: spencerbaugh at gmail dot com 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: cc 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: 2017-q1/txt/msg00000.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15468 Spencer Baugh changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |spencerbaugh at gmail dot = com --- Comment #5 from Spencer Baugh --- This can also be triggered through normal usage of multiple inferior debugg= ing. With any typical C++ program (such as hello.cc at the end of this comment) = the following sequence of commands... (gdb) catch throw=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 (gdb) add-inferior -copies 2 -exec hello=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 (gdb) infe 2=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 (gdb) break main=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 (gdb) run=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 (gdb) infe 3=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 (gdb) run=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 (gdb) info break=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 ...will trigger this error: breakpoint.c:6384: internal-error: print_one_breakpoint_location: Assertion `b->loc =3D=3D NULL || b->loc->next =3D=3D NULL' failed. It's key that the catchpoint is set before the inferiors are created. Whene= ver the catchpoint is pending before multiple C++ inferiors come into existence, this error will happen.=20 hello.cc: #include int main() { std::cout << "Hello World!" << std::endl; } --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20849-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 04 14:50:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 121306 invoked by alias); 4 Jan 2017 14:50:43 -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 121178 invoked by uid 48); 4 Jan 2017 14:50:42 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/15468] crash breakpoint.c:5940: internal-error: print_one_breakpoint_location Date: Wed, 04 Jan 2017 14:50: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: 7.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: cc 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: 2017-q1/txt/msg00001.txt.bz2 Content-length: 411 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15468 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.marchi at ericsson d= ot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20850-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 04 14:51:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 123086 invoked by alias); 4 Jan 2017 14:51:04 -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 122954 invoked by uid 48); 4 Jan 2017 14:51:01 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/15468] crash breakpoint.c:5940: internal-error: print_one_breakpoint_location Date: Wed, 04 Jan 2017 14:51: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: simon.marchi at ericsson dot com 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: version 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: 2017-q1/txt/msg00002.txt.bz2 Content-length: 381 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15468 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- Version|7.6 |HEAD --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20851-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 04 17:25:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122728 invoked by alias); 4 Jan 2017 17:25:04 -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 122704 invoked by uid 48); 4 Jan 2017 17:25:03 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tdep/18161] -mfloat-abi=hard causes some GDB tests fail Date: Wed, 04 Jan 2017 17:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WONTFIX X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00003.txt.bz2 Content-length: 676 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18161 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Yao Qi --- These fails are caused by arm linux kernel ptrace bug, instead of a gdb bug. These fails have been work around in gdb testsuite 27aba0477a4818fd760accd5b29a210d0ade2f42, so close this one. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20852-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 05 17:32:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 50514 invoked by alias); 5 Jan 2017 17:32:32 -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 50467 invoked by uid 48); 5 Jan 2017 17:32:31 -0000 From: "dje at google dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/21027] New: gdb takes too long looking up enum classes Date: Thu, 05 Jan 2017 17:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dje at google dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00004.txt.bz2 Content-length: 645 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21027 Bug ID: 21027 Summary: gdb takes too long looking up enum classes Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: dje at google dot com Target Milestone: --- This bug is to log the bug filed here: https://bugs.chromium.org/p/chromium/issues/detail?id=3D655961# I'll try to come up with a smaller repro. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20854-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 05 20:06:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 108010 invoked by alias); 5 Jan 2017 20:06:22 -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 107982 invoked by uid 48); 5 Jan 2017 20:06:22 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/20899] "dwarf2_string_attr" does not check for "DW_FORM_GNU_str_index" Date: Thu, 05 Jan 2017 20:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lgustavo at codesourcery dot com X-Bugzilla-Status: WAITING 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: bug_status cf_reconfirmed_on cc everconfirmed 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: 2017-q1/txt/msg00006.txt.bz2 Content-length: 579 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20899 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2017-01-05 CC| |lgustavo at codesourcery d= ot com Ever confirmed|0 |1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20855-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 05 20:06:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 108413 invoked by alias); 5 Jan 2017 20:06:44 -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 108384 invoked by uid 48); 5 Jan 2017 20:06:43 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/20899] "dwarf2_string_attr" does not check for "DW_FORM_GNU_str_index" Date: Thu, 05 Jan 2017 20:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lgustavo at codesourcery dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_status everconfirmed 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: 2017-q1/txt/msg00007.txt.bz2 Content-length: 439 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20899 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |UNCONFIRMED Ever confirmed|1 |0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20853-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 05 20:06:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107610 invoked by alias); 5 Jan 2017 20:06:07 -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 107571 invoked by uid 48); 5 Jan 2017 20:06:06 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/20926] gdb misses breakpoint and stops one line after Date: Thu, 05 Jan 2017 20:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: lgustavo at codesourcery dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00005.txt.bz2 Content-length: 773 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20926 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lgustavo at codesourcery d= ot com --- Comment #1 from Luis Machado --- I think you want "b *_start" if you want to stop at the first instruction of the function. Otherwise "b _start" will cause gdb to attempt to skip what it thinks is the prologue of the function, which is probably causing the breakpoint to be moved to line 6. This doesn't look like a bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20856-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 05 20:07:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 108864 invoked by alias); 5 Jan 2017 20:07:20 -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 108838 invoked by uid 48); 5 Jan 2017 20:07:20 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/20926] gdb misses breakpoint and stops one line after Date: Thu, 05 Jan 2017 20:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: lgustavo at codesourcery dot com X-Bugzilla-Status: WAITING 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: bug_status cf_reconfirmed_on everconfirmed 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: 2017-q1/txt/msg00008.txt.bz2 Content-length: 495 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20926 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2017-01-05 Ever confirmed|0 |1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20857-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 05 20:08:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109745 invoked by alias); 5 Jan 2017 20:08:15 -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 109720 invoked by uid 48); 5 Jan 2017 20:08:14 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/20926] gdb misses breakpoint and stops one line after Date: Thu, 05 Jan 2017 20:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: lgustavo at codesourcery dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: lgustavo at codesourcery dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: 2017-q1/txt/msg00009.txt.bz2 Content-length: 418 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20926 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |lgustavo at codesou= rcery dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20858-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 09 19:27:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 70926 invoked by alias); 9 Jan 2017 19:27:02 -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 70896 invoked by uid 48); 9 Jan 2017 19:27:01 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug corefiles/18964] [mips] 7.10.1 regression: internal-error: mips-tdep.c:1098: bad register size Date: Mon, 09 Jan 2017 19:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.10 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lgustavo at codesourcery dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: lgustavo at codesourcery dot com 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: 2017-q1/txt/msg00010.txt.bz2 Content-length: 252 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18964 --- Comment #10 from Luis Machado --- I just confirmed this is still happening. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20859-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 10 17:19:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 95052 invoked by alias); 10 Jan 2017 17:19:42 -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 95020 invoked by uid 48); 10 Jan 2017 17:19:42 -0000 From: "behzaterte at yandex dot com" To: gdb-prs@sourceware.org Subject: [Bug server/13984] gdb stops controlling a thread after "Remote 'g' packet reply is too long: ..." error message Date: Tue, 10 Jan 2017 17:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: behzaterte at yandex dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00011.txt.bz2 Content-length: 396 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13984 berte changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |behzaterte at yandex dot c= om --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20860-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 10 18:26:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89514 invoked by alias); 10 Jan 2017 18:26:29 -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 89483 invoked by uid 48); 10 Jan 2017 18:26:28 -0000 From: "behzaterte at yandex dot com" To: gdb-prs@sourceware.org Subject: [Bug server/13984] gdb stops controlling a thread after "Remote 'g' packet reply is too long: ..." error message Date: Tue, 10 Jan 2017 18:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: behzaterte at yandex dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00012.txt.bz2 Content-length: 704 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13984 --- Comment #14 from berte --- Hi all,=20 I've same issue with gdb 7.12. Also I found kinda workaround. If you remove -S paremeter passing to Qemu, = gdb works as expected but you cannot catch boot phase breakpoints. ### Env Info gdb -v GNU gdb (Gentoo 7.12 vanilla) 7.12 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later qemu-system-x86_64 --version QEMU emulator version 2.8.0 Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20861-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 12 02:37:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 90303 invoked by alias); 12 Jan 2017 02:37:54 -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 90237 invoked by uid 48); 12 Jan 2017 02:37:53 -0000 From: "sandra at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug sim/21042] New: arm-none-eabi-run no longer recognizes -m option Date: Thu, 12 Jan 2017 02:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sandra at codesourcery dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: 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: 2017-q1/txt/msg00013.txt.bz2 Content-length: 1195 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21042 Bug ID: 21042 Summary: arm-none-eabi-run no longer recognizes -m option Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: sim Assignee: unassigned at sourceware dot org Reporter: sandra at codesourcery dot com CC: vapier at gentoo dot org Target Milestone: --- We have a fairly ancient Dejagnu board file that causes the GDB simulator t= o be invoked like: % arm-none-eabi-run -m 100663296 a.out arm-none-eabi-run: unrecognized option '-m' Use --help for a complete list of options. The list of options printed by --help has basically nothing to do with the = ones documented in run.1, which seems to be the only documentation for the simulator. The former doesn't list -m while the latter does. I guess --memory-size is the replacement for -m, but why was backward compatibility broken? At the very least the documentation ought to be upda= ted to reflect the currently-supported options. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20862-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 12 09:02:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 40430 invoked by alias); 12 Jan 2017 09:02:47 -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 40345 invoked by uid 48); 12 Jan 2017 09:02:46 -0000 From: "hlfqdhj at 163 dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21044] New: Text or color mark on current line in code listing Date: Thu, 12 Jan 2017 09:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: hlfqdhj at 163 dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00014.txt.bz2 Content-length: 712 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21044 Bug ID: 21044 Summary: Text or color mark on current line in code listing Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: hlfqdhj at 163 dot com Target Milestone: --- Would you please add a textual mark or colorize the current line in `list` command? For example: 102 printf(...) 103 -> int a =3D 1; // arrow? 104 return 0; 105 } Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20863-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 12 11:27:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 76755 invoked by alias); 12 Jan 2017 11:27:17 -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 76628 invoked by uid 48); 12 Jan 2017 11:27:16 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/21044] Text or color mark on current line in code listing Date: Thu, 12 Jan 2017 11:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc component 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: 2017-q1/txt/msg00015.txt.bz2 Content-length: 1410 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21044 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com Component|tui |cli --- Comment #1 from Pedro Alves --- In the TUI (try "tui enable"), we already highlight the current line. For "list", I agree that'd be really nice. (I've wanted it for a long whil= e.) lldb does that, and puts the arrow before the line numbers, which I think is more visible: 102 printf(...) -> 103 int a =3D 1; // arrow? 104 return 0; 105 } This shouldn't be hard to implement if someone wants to take a stab at it. Note we already print the current instruction in the output of the "disassemble" command: 0x00000000004009d3 <+12>: mov %rsi,-0x30(%rbp) =3D> 0x00000000004009d7 <+16>: mov $0x400c62,%edi 0x00000000004009dc <+21>: callq 0x400760 0x00000000004009e1 <+26>: mov %rax,%rbx In the TUI, you'll notice that we also indicate which lines have breakpoints, with "b+". That's something that I've wanted for "list" and "disassemble" too. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20864-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 12 19:43:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20862 invoked by alias); 12 Jan 2017 19:43:34 -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 20740 invoked by uid 48); 12 Jan 2017 19:43:33 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug sim/21042] arm-none-eabi-run no longer recognizes -m option Date: Thu, 12 Jan 2017 19:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lgustavo at codesourcery dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00016.txt.bz2 Content-length: 1066 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21042 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lgustavo at codesourcery d= ot com --- Comment #1 from Luis Machado --- It was removed in this commit: commit 0fe84f3fbe9a740c38a8dbaa0150b8e4c25c69dd Author: Mike Frysinger Date: Tue Mar 31 01:13:12 2015 -0400 sim: run: punt! Now that all targets have been converted to nrun, we can finally punt this old inconsistent interface. A few stray references to the old run were sprinkled about; clean them up in the process. We leave behind the run(1) man page mostly so that we get it updated for the new nrun interface. It sounds like this option won't be coming back unless it is deemed appropriate? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20865-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 12 19:48:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53933 invoked by alias); 12 Jan 2017 19:48:24 -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 53884 invoked by uid 48); 12 Jan 2017 19:48:19 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/11606] GDB does not properly implement the default copy constructor Date: Thu, 12 Jan 2017 19:48: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: 7.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lgustavo at codesourcery 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: 7.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution 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: 2017-q1/txt/msg00017.txt.bz2 Content-length: 654 https://sourceware.org/bugzilla/show_bug.cgi?id=3D11606 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |lgustavo at codesourcery d= ot com Resolution|--- |FIXED --- Comment #7 from Luis Machado --- I've checked this against GDB 7.12.50 and it works fine. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20866-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 12 19:48:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 54149 invoked by alias); 12 Jan 2017 19:48:32 -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 54077 invoked by uid 48); 12 Jan 2017 19:48:30 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/16106] C++ expression parsing meta-bug Date: Thu, 12 Jan 2017 19:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: dep_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: lgustavo at codesourcery dot com 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: bug_status resolution 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: 2017-q1/txt/msg00018.txt.bz2 Content-length: 574 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16106 Bug 16106 depends on bug 11606, which changed state. Bug 11606 Summary: GDB does not properly implement the default copy constru= ctor https://sourceware.org/bugzilla/show_bug.cgi?id=3D11606 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20867-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 12 20:15:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 106359 invoked by alias); 12 Jan 2017 20:15:45 -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 106313 invoked by uid 48); 12 Jan 2017 20:15:44 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug record/21005] Process record does not support instruction GDB 7.12 (rdrand %eax) Date: Thu, 12 Jan 2017 20:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lgustavo at codesourcery dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00019.txt.bz2 Content-length: 792 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21005 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lgustavo at codesourcery d= ot com --- Comment #1 from Luis Machado --- I hit a different unsupported instruction with this testcase. 0x7ffff7dee6e7 <_dl_runtime_resolve_avx+71>: vmovdqa %ymm0,(%rsp) The current mechanism for supporting these instructions is really inefficie= nt. Everytime we find a new unsupported instruction we need to hardcode the knowledge inside gdb. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20868-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 13 08:10:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27722 invoked by alias); 13 Jan 2017 08:10:12 -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 27646 invoked by uid 48); 13 Jan 2017 08:10:11 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21048] New: backtrace is broken on i686 Date: Fri, 13 Jan 2017 08:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00020.txt.bz2 Content-length: 3597 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21048 Bug ID: 21048 Summary: backtrace is broken on i686 Product: gdb Version: 7.12 Status: NEW Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Target Milestone: --- https://bugzilla.redhat.com/show_bug.cgi?id=3D1411094 Hironobu Ishii 2017-01-08 11:58:16 CET Description of problem: On i686 (or 32-bit machine), bt does not work. Applying following upstream commit solved this bug in my environment. Fix some error-handling bugs in python frame filters =20 http://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommit;h=3D30= a7bb833cbd848b1814f18b91dfdafba4e86839 Version-Release number of selected component (if applicable): gdb-7.12-29.fc25 How reproducible: Always, but it seems to depend on core complexity or something. Steps to Reproduce: 1. Run firefox and gcore firefox. 2. gdb /usr/lib/firefox/firefox core.XXX 3. bt in gdb Actual results: (gdb) bt Python Exception retur= ned a result with an error set:=20 Python Exception retur= ned a result with an error set:=20 Python Exception retur= ned a result with an error set:=20 Python Exception retur= ned a result with an error set:=20 #0 0xffffffff in #1 0xffffffff in=20 Python Exception retur= ned a result with an error set:=20 Python Exception retur= ned a result with an error set:=20 Python Exception retur= ned a result with an error set:=20 Python Exception retur= ned a result with an error set:=20 Python Exception retur= ned a result with an error set:=20 Expected results: This log was collected after applying the upstream patch. (gdb) bt #0 0xb7730d05 in __kernel_vsyscall () #1 0xb73f655f in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0xb6123f4c in poll (__timeout=3D-1, __nfds=3D5, __fds=3D0xa2930100) at /usr/include/bits/poll2.h:46 #3 0xb6123f4c in g_poll (fds=3D0xa2930100, nfds=3D5, timeout=3D-1) at gpol= l.c:124 #4 0xb2cb07ba in PollWrapper(GPollFD*, guint, gint) (ufds=3Dufds@entry=3D0xa2930100, nfsd=3Dnfsd@entry=3D5, timeout_=3Dtimeout_= @entry=3D-1) at /usr/src/debug/firefox-50.1.0/firefox-50.1.0/widget/gtk/nsAppShell.cpp:42 #5 0xb61136e8 in g_main_context_poll (priority=3D, n_fds=3D= 5, fds=3D0xa2930100, timeout=3D, context=3D0xb712da90) at gmain= .c:4228 #6 0xb61136e8 in g_main_context_iterate (context=3Dcontext@entry=3D0xb712d= a90, block=3Dblock@entry=3D1, dispatch=3Ddispatch@entry=3D1, self=3D) at gmain.c:3924 #7 0xb6113837 in g_main_context_iteration (context=3D0xb712da90, may_block= =3D1) at gmain.c:3990 #8 0xb2cb0847 in nsAppShell::ProcessNextNativeEvent(bool) (this=3D0xa9749b= 50, mayWait=3Dtrue) at /usr/src/debug/firefox-50.1.0/firefox-50.1.0/widge/gtk/nsAppShell.cpp:270 Additional info: This bug is also repoted in debian. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D814558 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20869-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 13 08:14:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 33624 invoked by alias); 13 Jan 2017 08:14:21 -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 33597 invoked by uid 48); 13 Jan 2017 08:14:20 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21048] backtrace is broken on i686 Date: Fri, 13 Jan 2017 08:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat 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: 7.12.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution target_milestone 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: 2017-q1/txt/msg00021.txt.bz2 Content-length: 1227 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21048 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jan.kratochvil at redhat d= ot com Resolution|--- |FIXED Target Milestone|--- |7.12.1 --- Comment #1 from Jan Kratochvil --- Backported: commit 30a7bb833cbd848b1814f18b91dfdafba4e86839 Author: Tom Tromey Date: Mon Oct 31 11:10:35 2016 -0600 Fix some error-handling bugs in python frame filters [RFA 1/2] Fix some error-handling bugs in python frame filters https://sourceware.org/ml/gdb-patches/2016-10/msg00870.html https://sourceware.org/ml/gdb-patches/2016-11/msg00076.html into 7.12 as: commit df1fe27b672d7aa054eaad8b51f86302f7e46c65 Author: Tom Tromey Date: Mon Oct 31 11:10:35 2016 -0600 Fix some error-handling bugs in python frame filters --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20870-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 13 08:25:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 6566 invoked by alias); 13 Jan 2017 08:25:41 -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 6493 invoked by uid 48); 13 Jan 2017 08:25:39 -0000 From: "raphael.kubo.da.costa at intel dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/20899] "dwarf2_string_attr" does not check for "DW_FORM_GNU_str_index" Date: Fri, 13 Jan 2017 08:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: raphael.kubo.da.costa at intel dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00022.txt.bz2 Content-length: 1154 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20899 Raphael Kubo da Costa changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |raphael.kubo.da.costa@intel | |.com --- Comment #1 from Raphael Kubo da Costa --- Additional information: this is a regression caused by http://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommitdiff;h= =3D7d45c7c3f692d93c3a33a043c347f1386681deb4 (dwarf2read.c: Check type of string valued attributes prior to decoding) and has been present since 7.11. It makes GDB print the wrong namespace names for all code built with clang = and -gsplit-dwarf, there's additional information here: https://bugs.chromium.org/p/chromium/issues/detail?id=3D680654 Lech: I'm not sure your patch can be accepted as-is, see gdb/CONTRIBUTE and= the "Submitting Patches" section. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20871-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 13 08:36:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 42133 invoked by alias); 13 Jan 2017 08:36:01 -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 42098 invoked by uid 48); 13 Jan 2017 08:36:00 -0000 From: "raphael.kubo.da.costa at intel dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/20899] "dwarf2_string_attr" does not check for "DW_FORM_GNU_str_index" Date: Fri, 13 Jan 2017 08:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: raphael.kubo.da.costa at intel dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00023.txt.bz2 Content-length: 416 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20899 Raphael Kubo da Costa changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kevinb at redhat dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20872-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 13 09:01:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31020 invoked by alias); 13 Jan 2017 09:01:29 -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 30982 invoked by uid 48); 13 Jan 2017 09:01:29 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug record/21005] Process record does not support instruction GDB 7.12 (rdrand %eax) Date: Fri, 13 Jan 2017 09:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lgustavo at codesourcery dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: lgustavo at codesourcery dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed 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: 2017-q1/txt/msg00024.txt.bz2 Content-length: 762 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21005 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-01-13 Assignee|unassigned at sourceware dot org |lgustavo at codesou= rcery dot com Ever confirmed|0 |1 --- Comment #2 from Luis Machado --- Patch sent to support rdrand and rdseed. https://sourceware.org/ml/gdb-patches/2017-01/msg00262.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20873-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 14 23:43:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 98433 invoked by alias); 14 Jan 2017 23:43:18 -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 98404 invoked by uid 48); 14 Jan 2017 23:43:17 -0000 From: "ian at iankelling dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21051] New: nat/x86-linux-dregs.c:146: internal-error: void x86_linux_update_debug_registers(lwp_info*): Assertion `lwp_is_stopped (lwp)' failed. Date: Sat, 14 Jan 2017 23:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ian at iankelling dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00025.txt.bz2 Content-length: 8200 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21051 Bug ID: 21051 Summary: nat/x86-linux-dregs.c:146: internal-error: void x86_linux_update_debug_registers(lwp_info*): Assertion `lwp_is_stopped (lwp)' failed. Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: ian at iankelling dot org Target Milestone: --- I'm on debian testing, updated as of about 1-6-2017. Tested on gdb 7.12-4, and also 7.12.50.20170114-git. Error occurs when debugging emacs. I'm using emacs from commit e27203276 (J= an 7 2017), I assume it would happen with other versions of emacs, the bug proba= bly has nothing to do with emacs. $ uname -a Linux treetowl 4.8.0-2-amd64 #1 SMP Debian 4.8.11-1 (2016-12-02) x86_64 GNU/Linux $ gcc -v Using built-in specs. COLLECT_GCC=3Dgcc COLLECT_LTO_WRAPPER=3D/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion=3D'Debian 6.2.1-5' --with-bugurl=3Dfile:///usr/share/doc/gcc-6/README.Bugs --enable-languages=3Dc,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=3D/u= sr --program-suffix=3D-6 --program-prefix=3Dx86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=3D/usr/lib --without-included-gettext --enable-threads=3Dposix --libdir=3D/usr/lib --enable-nls --with-sysroot=3D/ --enable-clocale=3Dgnu --enable-libstdcxx-debug --enable-libstdcxx-time=3Dy= es --with-default-libstdcxx-abi=3Dnew --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --disable-browser-plugin --enable-java-awt=3Dgtk --enable-gtk-cairo --with-java-home=3D/usr/lib/jvm/java-1.5.0-gcj-6-amd64/j= re --enable-java-home --with-jvm-root-dir=3D/usr/lib/jvm/java-1.5.0-gcj-6-amd64 --with-jvm-jar-dir=3D/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 --with-arch-directory=3Damd64 --with-ecj-jar=3D/usr/share/java/eclipse-ecj.= jar --enable-objc-gc=3Dauto --enable-multiarch --with-arch-32=3Di686 --with-abi= =3Dm64 --with-multilib-list=3Dm32,m64,mx32 --enable-multilib --with-tune=3Dgeneric --enable-checking=3Drelease --build=3Dx86_64-linux-gnu --host=3Dx86_64-linu= x-gnu --target=3Dx86_64-linux-gnu Thread model: posix gcc version 6.2.1 20161124 (Debian 6.2.1-5) bash-4.4$ ./gdb/gdb -data-directory=3D./gdb/data-directory -ex=3D"set follow-fork-mode child" -ex=3Dr -ex=3Dquit --args emacsclient -nc GNU gdb (GDB) 7.12.50.20170114-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from emacsclient...done. Starting program: /usr/local/bin/emacsclient -nc /usr/local/bin/emacsclient: can't find socket; have you started the server? To start the server in Emacs, type "M-x server-start". [New process 15874] process 15874 is executing new program: /usr/local/bin/emacs-26.0.50 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Warning: due to a long standing Gtk+ bug http://bugzilla.gnome.org/show_bug.cgi?id=3D85715 Emacs might crash when run in daemon mode and the X11 connection is unexpectedly lost. Using an Emacs configured with --with-x-toolkit=3Dlucid does not have this problem. [New process 15877] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe7346700 (LWP 15878)] [New process 15879] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". nat/x86-linux-dregs.c:146: internal-error: void x86_linux_update_debug_registers(lwp_info*): Assertion `lwp_is_stopped (lwp= )' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y This is a bug, please report it. For instructions, see: . nat/x86-linux-dregs.c:146: internal-error: void x86_linux_update_debug_registers(lwp_info*): Assertion `lwp_is_stopped (lwp= )' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) y Aborted (core dumped) bash-4.4$ Error: server did not start correctly Error: Could not start the Emacs daemon Trace from the core file (too big to attach according to 10M limit stated on this form). (gdb) bt #0 0x00007f2bee6ddfdf in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f2bee6df40a in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x000055c2652f0496 in dump_core () at utils.c:479 #3 0x000055c2652f293a in internal_vproblem(internal_problem *, const char = *, int, const char *, typedef __va_list_tag __va_list_tag *) ( problem=3Dproblem@entry=3D0x55c265989540 , file=3D, line=3D, fmt=3D,=20 ap=3Dap@entry=3D0x7ffe284193a8) at utils.c:690 #4 0x000055c2652f2a0b in internal_verror (file=3D, line=3D, fmt=3D, ap=3Dap@entry=3D0x7ffe284193= a8) at utils.c:716 #5 0x000055c2652077b2 in internal_error (file=3Dfile@entry=3D0x55c265495878 "nat/x86-linux-dregs.c", line=3Dline@entry=3D146, fmt=3D) at common/errors.c:55 #6 0x000055c2650d23e0 in x86_linux_update_debug_registers (lwp=3D0x55c2677= ddaa0) at nat/x86-linux-dregs.c:146 #7 0x000055c2650c3085 in detach_one_lwp (lp=3Dlp@entry=3D0x55c2677ddaa0, signo_p=3Dsigno_p@entry=3D0x0) at linux-nat.c:1439 #8 0x000055c2650c336f in detach_callback (lp=3D0x55c2677ddaa0, data=3D) at linux-nat.c:1497 #9 0x000055c2650c5989 in iterate_over_lwps (filter=3D..., callback=3Dcallback@entry=3D0x55c2650c3330 , data=3Ddata@entry=3D0x0) at linux-nat.c:992 #10 0x000055c2650c5ed9 in linux_nat_detach (ops=3D0x55c265bf83c0, args=3D0x= 0, from_tty=3D0) at linux-nat.c:1519 #11 0x000055c2650cbf0f in thread_db_detach (ops=3D, args=3D0= x0, from_tty=3D0) at linux-thread-db.c:1100 #12 0x000055c26524eaa0 in handle_vfork_child_exec_or_exit (exec=3Dexec@entr= y=3D1) at infrun.c:976 #13 0x000055c26524f7af in handle_inferior_event_1 (ecs=3D0x7ffe28419820) at infrun.c:5321 #14 handle_inferior_event (ecs=3Decs@entry=3D0x7ffe28419820) at infrun.c:54= 11 #15 0x000055c265251608 in fetch_inferior_event (client_data=3D) at infrun.c:3959 #16 0x000055c26520e63d in gdb_wait_for_event (block=3Dblock@entry=3D0) at event-loop.c:859 #17 0x000055c26520e777 in gdb_do_one_event () at event-loop.c:322 #18 0x000055c26520e8c6 in gdb_do_one_event () at event-loop.c:353 #19 0x000055c2652e9d4c in wait_sync_command_done () at top.c:570 #20 0x000055c2652e9fb6 in maybe_wait_sync_command_done (was_sync=3D0) at top.c:587 #21 execute_command (p=3D, p@entry=3D0x7ffe2841aad1 "r", from_tty=3Dfrom_tty@entry=3D1) at top.c:676 #22 0x000055c265264b28 in catch_command_errors (command=3D0x55c2652e9d90 , arg=3D0x7ffe2841aad1 "r", from_tty=3D1) at main.c:376 #23 0x000055c265265722 in captured_main_1 (context=3D) at main.c:1119 #24 captured_main (data=3D) at main.c:1140 #25 gdb_main (args=3D) at main.c:1158 #26 0x000055c265078ae8 in main (argc=3D, argv=3D) at gdb.c:32 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20874-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 14 23:46:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 100518 invoked by alias); 14 Jan 2017 23:46:07 -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 100496 invoked by uid 48); 14 Jan 2017 23:46:06 -0000 From: "ian at iankelling dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21051] nat/x86-linux-dregs.c:146: internal-error: void x86_linux_update_debug_registers(lwp_info*): Assertion `lwp_is_stopped (lwp)' failed. Date: Sat, 14 Jan 2017 23:46: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ian at iankelling dot org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00026.txt.bz2 Content-length: 394 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21051 Ian Kelling changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ian at iankelling dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20875-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jan 15 05:39:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 28041 invoked by alias); 15 Jan 2017 05:38:54 -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 27970 invoked by uid 48); 15 Jan 2017 05:38:46 -0000 From: "hlfqdhj at 163 dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/21044] Text or color mark on current line in code listing Date: Sun, 15 Jan 2017 05:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: hlfqdhj at 163 dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00027.txt.bz2 Content-length: 1485 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21044 --- Comment #2 from Yifei Zheng --- (In reply to Pedro Alves from comment #1) > In the TUI (try "tui enable"), we already highlight the current line. >=20 > For "list", I agree that'd be really nice. (I've wanted it for a long > while.) >=20 > lldb does that, and puts the arrow before the line numbers, which I think= is > more visible: >=20 > 102 printf(...) > -> 103 int a =3D 1; // arrow? > 104 return 0; > 105 } >=20 > This shouldn't be hard to implement if someone wants to take a stab at it. >=20 > Note we already print the current instruction in the output of the > "disassemble" command: >=20 > 0x00000000004009d3 <+12>: mov %rsi,-0x30(%rbp) > =3D> 0x00000000004009d7 <+16>: mov $0x400c62,%edi > 0x00000000004009dc <+21>: callq 0x400760 > 0x00000000004009e1 <+26>: mov %rax,%rbx >=20 > In the TUI, you'll notice that we also indicate which lines have > breakpoints, with "b+". That's something that I've wanted for "list" and > "disassemble" too. Really fast reply... Thanks for your tips. I've never used "tui" before. I tried it just now and discovered it's quite similar to "layout" command (or are they the same?) And I totally agree with your idea putting arrow before line count. Anyway thanks for viewing the bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20876-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 16 15:30:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20474 invoked by alias); 16 Jan 2017 15:30:32 -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 19817 invoked by uid 48); 16 Jan 2017 15:30:31 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20939] GDB aborts if there is an error in disassembly Date: Mon, 16 Jan 2017 15:30: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.12.1 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: 2017-q1/txt/msg00028.txt.bz2 Content-length: 449 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20939 --- Comment #3 from Yao Qi --- It is a regression. GDB 7.11.1 works well (with --enable-build-with-cxx and without --enable-build-with-cxx) on aarch64-linux. (gdb) disassemble 0x0,+4 Dump of assembler code from 0x0 to 0x4: 0x0000000000000000: Cannot access memory at address 0x0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20877-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 16 16:18:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 43216 invoked by alias); 16 Jan 2017 16:18:10 -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 43193 invoked by uid 48); 16 Jan 2017 16:18:10 -0000 From: "vleschuk at accesssoftek dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20757] gdb: DWARF-5 support Date: Mon, 16 Jan 2017 16:18: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: vleschuk at accesssoftek dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan.kratochvil at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q1/txt/msg00029.txt.bz2 Content-length: 413 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20757 Victor Leschuk changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vleschuk at accesssoftek d= ot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20878-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 16 20:51:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 32269 invoked by alias); 16 Jan 2017 20:51:09 -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 31438 invoked by uid 48); 16 Jan 2017 20:51:09 -0000 From: "karlp at tweak dot net.au" To: gdb-prs@sourceware.org Subject: [Bug macros/21055] New: docs use -gdwarf-2 to avoid unavailable dwarf1 Date: Mon, 16 Jan 2017 20:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: macros X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: karlp at tweak dot net.au X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00030.txt.bz2 Content-length: 1756 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21055 Bug ID: 21055 Summary: docs use -gdwarf-2 to avoid unavailable dwarf1 Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: macros Assignee: unassigned at sourceware dot org Reporter: karlp at tweak dot net.au Target Milestone: --- The docs available at https://sourceware.org/gdb/onlinedocs/gdb/Macros.html#fn-1, contain the following lines: ``` Now, we compile the program using the gnu C compiler, gcc. We pass the -gdwarf-2[footnote] and -g3 flags to ensure the compiler includes informati= on about preprocessor macros in the debugging information. $ gcc -gdwarf-2 -g3 sample.c -o sample $ ``` While this advice to use -gdwarf2 to avoid dwarf1 was appropriate in 2002 w= hen it seems this documentation was written, it's redundant and unhelpful in 20= 17.=20 The footnote _does_ indicate that it only needs to be _at least_ dwarf2, wh= ich is helpful, if anyone actually reads the footnotes. Note that current gcc doesn't even have an option for building dwarf1, let alone is it the default. (It was deprecated back in gcc 3.3, and removed = in 3.4) I recommend that the documentation simply be: ``` Now, we compile the program using the gnu C compiler, gcc. We pass the -g3 flags to ensure the compiler includes information about preprocessor macros= in the debugging information. $ gcc -g3 sample.c -o sample $ ``` I don't believe even a footnote on minimum required dwarf versions is appropriate in current version gdb documentation. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20879-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 17 16:39:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 61860 invoked by alias); 17 Jan 2017 16:39:20 -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 61770 invoked by uid 48); 17 Jan 2017 16:39:19 -0000 From: "hjl.tools at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21057] GDB build failure with flex 2.6.3 Date: Tue, 17 Jan 2017 16:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hjl.tools at gmail dot com 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: component version product 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: 2017-q1/txt/msg00031.txt.bz2 Content-length: 477 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21057 H.J. Lu changed: What |Removed |Added ---------------------------------------------------------------------------- Component|binutils |build Version|2.29 (HEAD) |8.0 Product|binutils |gdb --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20880-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 19 17:38:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 13882 invoked by alias); 19 Jan 2017 17:38:12 -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 13846 invoked by uid 48); 19 Jan 2017 17:38:11 -0000 From: "pradeepkumar.chinnusamy at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21067] New: Trying to run gdb on the core file, but fails with coredump Date: Thu, 19 Jan 2017 17:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new 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: pradeepkumar.chinnusamy at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00032.txt.bz2 Content-length: 1649 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21067 Bug ID: 21067 Summary: Trying to run gdb on the core file, but fails with coredump Product: gdb Version: 7.9 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: pradeepkumar.chinnusamy at gmail dot com Target Milestone: --- i have installed GDB ( 7.9.1 ) in AIX 7100-02-03-1334 operating system.=20 root:#gdb /usr/openv/netbackup/bin/bptm /core.11993334.18202542 GNU gdb (GDB) 7.9.1 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "powerpc64-ibm-aix6.1.2.0". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/openv/netbackup/bin/bptm...(no debugging symbols found)...done. warning: core file may not match specified executable file. [New Thread 1] Segmentation fault(coredump) Can you let me know how to fix this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20881-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 19 22:12:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 2298 invoked by alias); 19 Jan 2017 22:12:56 -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 2273 invoked by uid 48); 19 Jan 2017 22:12:56 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21068] New: Python interactive prompt crashes GDB when using Python 3.6 Date: Thu, 19 Jan 2017 22:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00033.txt.bz2 Content-length: 1978 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21068 Bug ID: 21068 Summary: Python interactive prompt crashes GDB when using Python 3.6 Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: simon.marchi at ericsson dot com Target Milestone: --- When building GDB against Python 3.6, trying to enter anything in the Python interactive prompt crashes the process: GNU gdb (GDB) 7.12.50.20170119-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) python hello Traceback (most recent call last): File "", line 1, in NameError: name 'hello' is not defined Error while executing Python code. (gdb) pi >>> foo Fatal Python error: Python memory allocator called without holding the GIL Current thread 0x00007f28a32d7780 (most recent call first): [1] 31729 abort ./gdb The issue is that we're calling PyMem_Malloc instead of PyMem_RawMalloc in gdbpy_readline_wrapper. We need to change this only for Python >=3D 3.4. Ref: https://docs.python.org/3.4/c-api/veryhigh.html#c.PyOS_ReadlineFunctionPoin= ter --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20882-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 20 04:55:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 43120 invoked by alias); 20 Jan 2017 04:55:32 -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 42993 invoked by uid 48); 20 Jan 2017 04:55:24 -0000 From: "stilor at att dot net" To: gdb-prs@sourceware.org Subject: [Bug build/21070] New: GDB fails to build for mips-*-linux-musl Date: Fri, 20 Jan 2017 04:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: stilor at att dot net X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q1/txt/msg00034.txt.bz2 Content-length: 1419 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21070 Bug ID: 21070 Summary: GDB fails to build for mips-*-linux-musl Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: stilor at att dot net Target Milestone: --- Created attachment 9766 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9766&action=3Dedit PATCH Quote from the original patch description: [[[[ Build fix for MIPS with musl libc The MIPS specific header is provided by glibc and uclibc but not by musl. Regardless of the libc, the kernel headers provide which provides the same definitions, so use that instead. Upstream-Status: Pending Signed-off-by: Andre McCurdy Signed-off-by: Khem Raj ]]]] Despite the "Upstream-Status" line, I wasn't able to find this issue in the GDB's bugzilla - so submitting it. This has been reported as an issue in crosstool-ng: https://github.com/crosstool-ng/crosstool-ng/pull/517 The patch was originally provided for OpenEmbedded: http://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/gd= b/gdb/0007-use-asm-sgidefs.h.patch --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20883-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 20 13:04:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41479 invoked by alias); 20 Jan 2017 13:04:04 -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 41446 invoked by uid 55); 20 Jan 2017 13:04:03 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20939] GDB aborts if there is an error in disassembly Date: Fri, 20 Jan 2017 13:04: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.12.1 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: 2017-q1/txt/msg00035.txt.bz2 Content-length: 3047 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20939 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The gdb-7.12-branch branch has been updated by Yao Qi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3De2285602341f= ff057a9b4687b465a9d9cde1303f commit e2285602341fff057a9b4687b465a9d9cde1303f Author: Yao Qi Date: Fri Jan 20 13:00:52 2017 +0000 Throw SJ/LJ exception on error in disassembly PR 20939 reports that GDB will abort on memory error in disassembly, (gdb) disassemble 0x0,+4 Dump of assembler code from 0x0 to 0x4: terminate called after throwing an instance of 'gdb_exception_RETURN_MASK_ERROR' 0x0000000000000000: Aborted (gdb) guile (print (arch-disassemble arch 0 #:size 4))^M terminate called after throwing an instance of 'gdb_exception_RETURN_MASK_ERROR'^M ERROR: Process no longer exists This patch fixes PR 20939 by catching C++ exception, throwing SJ/LJ exception in the call back passed to C functions of opcodes, and catching SJ/LJ exception in gdb, and throw exception. The patch follows this commit 89525768cd086a0798a504c81fdf7ebcd4c904e1 Propagate GDB/C++ exceptions across readline using sj/lj-based TRY/CAT= CH rather than "backport" the fix to this PR I posted for mainline https://sourceware.org/ml/gdb-patches/2017-01/msg00288.html because the fix for mainline includes 1) some changes to opcodes, 2) some refactors in C++. All of them are risky to backport to 7.12 branch. With this patch applied to 7.12 branch, GDB doesn't abort on memory err= or in disassembly. It fixes some test failures in gdb.guile/scm-disasm.exp and gdb.python/py-arch.exp on aarch64-linux. -ERROR: Process no longer exists -UNRESOLVED: gdb.guile/scm-disasm.exp: test bad memory access +PASS: gdb.guile/scm-disasm.exp: test bad memory access -ERROR: Process no longer exists -UNRESOLVED: gdb.python/py-arch.exp: test bad memory access +PASS: gdb.python/py-arch.exp: test bad memory access I'll add the scm-disasm test to master later. gdb: 2017-01-20 Yao Qi PR gdb/20939 * disasm.c (dis_asm_memory_error): Catch the error and rethrow it as a SJ/LJ exception. Add GDB_NOEXCEPT. (disasm_print_insn_noexcept): New function. (disasm_print_insn): New function. (gdb_pretty_print_insn): Call disasm_print_insn instead of gdbarch_print_insn. (gdb_print_insn): Likewise. (gdb_buffered_insn_length): Likewise. * event-top.c (GDB_NOEXCEPT): Move it to ... * exceptions.h (GDB_NOEXCEPT): ... here. * guile/scm-disasm.c (gdbscm_disasm_memory_error): Remove. (gdbscm_print_insn_from_port): Don't set di.memory_errro_func. Call disasm_print_insn rather than gdbarch_print_insn. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20884-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 21 06:33:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3740 invoked by alias); 21 Jan 2017 06:33:18 -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 3703 invoked by uid 48); 21 Jan 2017 06:33:16 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21068] Python interactive prompt crashes GDB when using Python 3.6 Date: Sat, 21 Jan 2017 06:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00036.txt.bz2 Content-length: 629 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21068 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Simon Marchi --- Fixed by https://sourceware.org/git/?p=3Dbinutils-gdb.git;a=3Dcommit;h=3D6f8b04077b0= c3dc697b1c2bb042c69413d9813b8 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20885-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 21 13:52:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3538 invoked by alias); 21 Jan 2017 13:52:51 -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 3506 invoked by uid 48); 21 Jan 2017 13:52:50 -0000 From: "HBBroeker@T-Online.de" To: gdb-prs@sourceware.org Subject: [Bug build/21057] GDB build failure with flex 2.6.3 Date: Sat, 21 Jan 2017 13:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: HBBroeker@T-Online.de 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: cc 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: 2017-q1/txt/msg00037.txt.bz2 Content-length: 1063 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21057 HBBroeker@T-Online.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |HBBroeker@T-Online.de --- Comment #3 from HBBroeker@T-Online.de --- (In reply to Peter Foley from comment #0) > Building gdb at commit f964e51d90 with flex 2.6.3 and bison 3.0.4 fails w= ith > the below error. > I've attached a patch that allows the compile to succeed, although I'm > unclear whether the compatibility code it removes is still necessary. That patch relies on $(YACC) being bison, for otherwise the %name-prefix op= tion would not be available. I fear a more generally applicable solution will be needed (maybe use the -p command-line option instead, which is required by POSIX). The same issue could apply to the lex file change, but the gdb so= urce already insists on using flex, anyway. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20886-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 21 13:54:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 10073 invoked by alias); 21 Jan 2017 13:54:51 -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 10040 invoked by uid 48); 21 Jan 2017 13:54:49 -0000 From: "HBBroeker@T-Online.de" To: gdb-prs@sourceware.org Subject: [Bug build/20993] gdb does not link, when flex v2.6.2-19-g6bea32e is used Date: Sat, 21 Jan 2017 13:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: HBBroeker@T-Online.de X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00038.txt.bz2 Content-length: 465 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20993 HBBroeker@T-Online.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |HBBroeker@T-Online.de --- Comment #1 from HBBroeker@T-Online.de --- This is essentially a duplicate of bug 21057. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20887-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 23 09:35:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 84188 invoked by alias); 23 Jan 2017 09:35:11 -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 84155 invoked by uid 48); 23 Jan 2017 09:35:10 -0000 From: "kevin.brodsky at arm dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20939] GDB aborts if there is an error in disassembly Date: Mon, 23 Jan 2017 09:35: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kevin.brodsky at arm dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.12.1 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: 2017-q1/txt/msg00039.txt.bz2 Content-length: 228 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20939 --- Comment #5 from Kevin Brodsky --- Great, thank you Yao! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20888-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 24 00:07:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49829 invoked by alias); 24 Jan 2017 00:07:47 -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 49803 invoked by uid 48); 24 Jan 2017 00:07:46 -0000 From: "sayaghmohammed at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug record/21077] New: Record is not working for apache and php-interpreter Date: Tue, 24 Jan 2017 00:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sayaghmohammed at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q1/txt/msg00040.txt.bz2 Content-length: 1153 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21077 Bug ID: 21077 Summary: Record is not working for apache and php-interpreter Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: record Assignee: unassigned at sourceware dot org Reporter: sayaghmohammed at gmail dot com Target Milestone: --- Created attachment 9769 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9769&action=3Dedit A problem internal to GDB has been detected - I compiled and installed gdb, apache httpd, and php-interpreter. And I wa= nt to debug php, but record is not working.=20 - I executed then the command: sudo gdb /wwwroot/bin/httpd=20 --data-directory=3D/usr/src/gdb-7.11.1/gdb/data-directory - Then I set the following break point: b main/php_variables.c:274 - Once I execute the application, and the app stops at the breakpoint, I executed the record command record - Then continue command. But I got the enclosed error --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20889-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 24 07:15:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 33500 invoked by alias); 24 Jan 2017 07:15:04 -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 33386 invoked by uid 48); 24 Jan 2017 07:15:01 -0000 From: "tuben at lysator dot liu.se" To: gdb-prs@sourceware.org Subject: [Bug python/20624] gdb.Value doesn't support Python floordiv operator, // Date: Tue, 24 Jan 2017 07:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tuben at lysator dot liu.se X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00041.txt.bz2 Content-length: 1267 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20624 Johan Tufvesson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tuben at lysator dot liu.se --- Comment #3 from Johan Tufvesson --- I am running a pre-built version for ARM (from https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads), and = have problem with this. I don't know if that distribution has added any patch for this behavior but this works with their 7.10.1 release (part of their gcc "5.4-2016q3" toolchain): (gdb) py print gdb.Value(1)//1 1 but does not work for their 7.12.0 (part of their gcc "6.2-2016q4" toolchai= n): (gdb) py print gdb.Value(1)//1 Traceback (most recent call last): File "", line 1, in TypeError: unsupported operand type(s) for //: 'gdb.Value' and 'int' Error while executing Python code. I don't blame the GDB project if the ARM people have added (and later remov= ed) a patch for this behavior, but I think the behavior of not allowing // is wrong. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20890-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 24 09:22:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 331 invoked by alias); 24 Jan 2017 09:22:13 -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 301 invoked by uid 48); 24 Jan 2017 09:22:13 -0000 From: "jwakely.gcc at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/20624] gdb.Value doesn't support Python floordiv operator, // Date: Tue, 24 Jan 2017 09:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jwakely.gcc at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00042.txt.bz2 Content-length: 757 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20624 --- Comment #4 from Jonathan Wakely --- (In reply to Johan Tufvesson from comment #3) > but does not work for their 7.12.0 (part of their gcc "6.2-2016q4" > toolchain): It's possible their 7.10.1 is built against Python 2 and 7.12.0 is built against Python 3 or something like that. > I don't blame the GDB project if the ARM people have added (and later > removed) a patch for this behavior, but I think the behavior of not allow= ing > // is wrong. It's not explicitly disallowed, it just needs extra code to make it work. I will resume work on my patch for this when I get a chance. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20891-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 24 09:42:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 106873 invoked by alias); 24 Jan 2017 09:42:01 -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 106501 invoked by uid 48); 24 Jan 2017 09:41:52 -0000 From: "tuben at lysator dot liu.se" To: gdb-prs@sourceware.org Subject: [Bug python/20624] gdb.Value doesn't support Python floordiv operator, // Date: Tue, 24 Jan 2017 09:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tuben at lysator dot liu.se X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00043.txt.bz2 Content-length: 342 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20624 --- Comment #5 from Johan Tufvesson --- No, they both use the Python version that I have installed, which happens t= o be Python 2.7. A solution would be greatly appreciated. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20892-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 24 16:12:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 130670 invoked by alias); 24 Jan 2017 16:12:01 -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 130646 invoked by uid 48); 24 Jan 2017 16:12:00 -0000 From: "david at engster dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21078] New: gdb compiled with mingw32 crashes on Windows7 when entering any invalid command Date: Tue, 24 Jan 2017 16:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: david at engster dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q1/txt/msg00044.txt.bz2 Content-length: 1809 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21078 Bug ID: 21078 Summary: gdb compiled with mingw32 crashes on Windows7 when entering any invalid command Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: david at engster dot org Target Milestone: --- Created attachment 9770 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9770&action=3Dedit config.log file from configure run I have built the latest gdb (7.12.1) with i686-w64-mingw32 (gcc v6.3.0, MSY= S2) on a Windows 7 64bit system, simply using ./configure --prefix=3D/opt/gdb (I attached the config.log to this report.) When I start gdb and enter any invalid command that would normally lead to = an error message (like "help foobar"), the process just aborts (like from an unhandled exception): (gdb) help foobar This application has requested the Runtime to terminate it in an unusual = way. Please contact the application's support team for more information. Version 7.12 has the same problem, but 7.11 works fine, so this must be triggered by something since 7.11. I also tried building with the old mingw= gcc from mingw.org, but it has the same problem. Unfortunately, I cannot seem t= o be able to obtain any backtrace when running this inside another gdb. I also tried other gdb v7.12 binary builds, and some have the same problem, for instance the gdb in the latest Linaro toolchain for Arm, or the 'gdb' t= hat can be installed in MSYS2. However, the build from Eli Zaretskii (ezwinport= s) works fine. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20893-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 24 17:27:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3306 invoked by alias); 24 Jan 2017 17:27: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 3233 invoked by uid 48); 24 Jan 2017 17:27:52 -0000 From: "orlandoarias at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21079] New: [gdb-python] Error in handling MPX registers when using Python 3 Date: Tue, 24 Jan 2017 17:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: orlandoarias at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00045.txt.bz2 Content-length: 1543 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21079 Bug ID: 21079 Summary: [gdb-python] Error in handling MPX registers when using Python 3 Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: orlandoarias at gmail dot com Target Milestone: --- Greetings, When GDB is compiled with Python 3 support, dumping MPX registers in IA32 a= nd AMD64 results in the following error: (gdb) info reg bnd0 Python Exception name 'long' is not defined: Python Exception name 'long' is not defined: bnd0 This is because 'long' and 'int' were merged in Python 3. This issue has be= en brought up before [1] but I did not see anything in the bug tracker. There = was talk of submitting patches [2] but these appear to have never made it into = GDB. The patch alone seems to be insufficient, since I get duplicate output when printing MPX registers: (gdb) info reg bnd0 bnd0 {lbound =3D 0x0, ubound =3D 0xffffffffffffffff} : size =3D -1 {lbound = =3D 0x0, ubound =3D 0xffffffffffffffff} : size =3D -1 Thank you for looking into this. Cheers, Orlando. [1] https://lists.gnu.org/archive/html/bug-gnu-emacs/2016-02/msg00824.html [2] https://lists.gnu.org/archive/html/bug-gnu-emacs/2016-02/msg00849.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20894-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 24 17:28:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4264 invoked by alias); 24 Jan 2017 17:28:10 -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 4227 invoked by uid 48); 24 Jan 2017 17:28:09 -0000 From: "orlandoarias at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21079] [gdb-python] Error in handling MPX registers when using Python 3 Date: Tue, 24 Jan 2017 17:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: orlandoarias at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00046.txt.bz2 Content-length: 406 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21079 Orlando Arias changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |orlandoarias at gmail dot = com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20895-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 25 09:59:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3937 invoked by alias); 25 Jan 2017 09:59:05 -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 3908 invoked by uid 48); 25 Jan 2017 09:59:04 -0000 From: "lists at svrinformatica dot it" To: gdb-prs@sourceware.org Subject: [Bug win32/14527] warning: section .gnu_debuglink not found in MODULENAME.debug Date: Wed, 25 Jan 2017 09:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: win32 X-Bugzilla-Version: 7.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: lists at svrinformatica dot it 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: cc 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: 2017-q1/txt/msg00047.txt.bz2 Content-length: 695 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14527 Nicola changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lists at svrinformatica do= t it --- Comment #5 from Nicola --- still happen with gdb 7.12 and objcopy from binutils 2.27 tested in a cross build environment (https://www.archlinux.org/packages/?q=3Dmingw) the suggested fix does not work for dll anyway gdb is able to use the debug symbols --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20896-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 25 16:21:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66743 invoked by alias); 25 Jan 2017 16:21:03 -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 66700 invoked by uid 48); 25 Jan 2017 16:21:00 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21087] New: Configuring gdb with --enable-maintainer-mode fails with autoconf version error Date: Wed, 25 Jan 2017 16:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lgustavo at codesourcery dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00048.txt.bz2 Content-length: 1853 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21087 Bug ID: 21087 Summary: Configuring gdb with --enable-maintainer-mode fails with autoconf version error Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: lgustavo at codesourcery dot com Target Milestone: --- Reported on IRC. Attempting to configure master binutils-gdb with --enable-maintainer-mode fails due to an autoconf version check from src/in= tl: make[2]: Entering directory '/fsf/build-binutils-gdb-maintainer/intl' cd ../../binutils-gdb/intl && aclocal -I ../config configure.ac:2: error: Please use exactly Autoconf 2.64 instead of 2.69. ../config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from... configure.ac:2: the top level autom4te: m4 failed with exit status: 1 aclocal: error: echo failed with exit status: 1 Makefile:236: recipe for target '../../binutils-gdb/intl/aclocal.m4' failed make[2]: *** [../../binutils-gdb/intl/aclocal.m4] Error 1 make[2]: Leaving directory '/fsf/build-binutils-gdb-maintainer/intl' Makefile:6567: recipe for target 'all-intl' failed make[1]: *** [all-intl] Error 2 make[1]: Leaving directory '/fsf/build-binutils-gdb-maintainer' Makefile:849: recipe for target 'all' failed make: *** [all] Error 2 It has also been reported that switching to Autoconf 2.64 will then cause gnulib to complain about Autoconf being too old a version: make[4]: Entering directory `build/binutils-gdb/gdb/build-gnulib' cd /binutils-gdb/gdb/gnulib && aclocal -I import/m4 -I ../../config configure.ac:38: error: Autoconf version 2.65 or higher is required --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20897-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 25 16:27:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 130032 invoked by alias); 25 Jan 2017 16:27:34 -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 130004 invoked by uid 48); 25 Jan 2017 16:27:33 -0000 From: "bergner at vnet dot ibm.com" To: gdb-prs@sourceware.org Subject: [Bug build/21087] Configuring gdb with --enable-maintainer-mode fails with autoconf version error Date: Wed, 25 Jan 2017 16:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bergner at vnet dot ibm.com 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: cc 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: 2017-q1/txt/msg00049.txt.bz2 Content-length: 400 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21087 Peter Bergner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bergner at vnet dot ibm.com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20898-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 25 23:40:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 110819 invoked by alias); 25 Jan 2017 23:40:03 -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 110794 invoked by uid 48); 25 Jan 2017 23:40:02 -0000 From: "pbotfullerton at cock dot li" To: gdb-prs@sourceware.org Subject: [Bug tui/21089] New: GDB hangs if a syntax error is found when quitting Date: Wed, 25 Jan 2017 23:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: pbotfullerton at cock dot li X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00050.txt.bz2 Content-length: 1584 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21089 Bug ID: 21089 Summary: GDB hangs if a syntax error is found when quitting Product: gdb Version: 7.12 Status: UNCONFIRMED Severity: minor Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: pbotfullerton at cock dot li Target Milestone: --- If a syntax error is found after the "quit" keyword (eg, by typing in "quit= ;"), GDB hangs indefinitely and has to be killed. While in this hung state, it responds to Ctrl-C by printing out "Quit", a newline, and prompt but does do anything else. Example session: GNU gdb (Debian 7.12-4) 7.12 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) quit; Invalid character ';' in expression. (gdb)=20 [hanged process results] --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20899-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 26 14:38:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127908 invoked by alias); 26 Jan 2017 14:38:24 -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 127432 invoked by uid 55); 26 Jan 2017 14:38:22 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20939] GDB aborts if there is an error in disassembly Date: Thu, 26 Jan 2017 14:38: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.12.1 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: 2017-q1/txt/msg00051.txt.bz2 Content-length: 2753 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20939 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Yao Qi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dd8b49cf0c891= d09dd58de05ad5cfe396b612cf3b commit d8b49cf0c891d09dd58de05ad5cfe396b612cf3b Author: Yao Qi Date: Thu Jan 26 14:29:20 2017 +0000 Don't throw exception in dis_asm_memory_error Hi, GDB calls some APIs from opcodes to do disassembly and provide some call backs. This model makes troubles on C++ exception unwinding, because GDB is a C++ program, and opcodes is still compiled as C. As we can see, frame #10 and #12 are C++, while #frame 11 is C, #10 0x0000000000544228 in memory_error (err=3DTARGET_XFER_E_IO, memaddr=3D) at ../../binutils-gdb/gdb/corefile.c:237 #11 0x00000000006b0a54 in print_insn_aarch64 (pc=3D0, info=3D0xfffffff= feeb0) at ../../binutils-gdb/opcodes/aarch64-dis.c:3185 #12 0x0000000000553590 in gdb_pretty_print_insn (gdbarch=3Dgdbarch@entry=3D0xbbceb0, uiout=3Duiout@entry=3D0xbc73d0, di=3Ddi@entry=3D0xffffffffeeb0, insn=3D0xffffffffed40, insn@entry=3D0xffffffffed90, flags=3Dflags@e= ntry=3D0, C++ exception unwinder can't go across frame #11 unless it has unwind table. However, C program on many architectures doesn't have it in default. As a result, GDB aborts, which is described in PR 20939. This is not the first time we see this kind of problem. We've had a commit 89525768cd086a0798a504c81fdf7ebcd4c904e1 "Propagate GDB/C++ exceptions across readline using sj/lj-based TRY/CAT= CH". We can fix the disassembly bug in a similar way, this is the option one. Since opcodes is built with gdb, we fix this problem in a different way as we did for the same issue with readline. Instead of throwing exception in dis_asm_memory_error, we record the failed memory address, and throw exception when GDB returns from opcodes disassembler= s. gdb: 2017-01-26 Yao Qi Pedro Alves PR gdb/20939 * disasm.c (gdb_disassembler::dis_asm_memory_error): Don't call memory_error, save memaddr instead. (gdb_disassembler::print_insn): If gdbarch_print_insn returns negative, cal memory_error. * disasm.h (gdb_disassembler) : New field. gdb/testsuite: 2017-01-26 Yao Qi * gdb.base/all-architectures.exp.in (do_arch_tests): Test disassemble on address 0. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20900-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 26 15:47:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 9735 invoked by alias); 26 Jan 2017 15:47:20 -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 9702 invoked by uid 48); 26 Jan 2017 15:47:20 -0000 From: "dblaikie at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/15502] DW_AT_decl_line ignored in DW_TAG_imported_declaration Date: Thu, 26 Jan 2017 15:47: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: 7.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dblaikie at gmail dot com 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: 2017-q1/txt/msg00052.txt.bz2 Content-length: 208 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15502 --- Comment #1 from David Blaikie --- Ping --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20901-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 26 15:48:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 34120 invoked by alias); 26 Jan 2017 15:48:21 -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 33655 invoked by uid 48); 26 Jan 2017 15:48:21 -0000 From: "dblaikie at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/16841] virtual inheritance via typedef cannot find base Date: Thu, 26 Jan 2017 15:48: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dblaikie at gmail dot com 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: 2017-q1/txt/msg00053.txt.bz2 Content-length: 208 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16841 --- Comment #4 from David Blaikie --- ping --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20902-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 26 15:51:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 69085 invoked by alias); 26 Jan 2017 15:51:07 -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 69054 invoked by uid 48); 26 Jan 2017 15:51:07 -0000 From: "dblaikie at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/16843] GDB relies on the mangled name of a subprogram to be a prefix of the enclosing class name Date: Thu, 26 Jan 2017 15:51: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dblaikie at gmail dot com 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: 2017-q1/txt/msg00054.txt.bz2 Content-length: 208 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16843 --- Comment #4 from David Blaikie --- ping --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20903-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 26 15:52:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 71313 invoked by alias); 26 Jan 2017 15:52:22 -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 71275 invoked by uid 48); 26 Jan 2017 15:52:21 -0000 From: "dblaikie at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/17315] 'until' behavion in watchpoint.c (for loops) incompatible with loop condition instructions at the top of the loop Date: Thu, 26 Jan 2017 15:52: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: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dblaikie at gmail dot com 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: 2017-q1/txt/msg00055.txt.bz2 Content-length: 208 https://sourceware.org/bugzilla/show_bug.cgi?id=3D17315 --- Comment #1 from David Blaikie --- ping --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20904-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 26 15:55:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 96992 invoked by alias); 26 Jan 2017 15:55:39 -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 96237 invoked by uid 48); 26 Jan 2017 15:55:37 -0000 From: "dblaikie at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/17701] gdb.base/consecutive.exp fails when the line table includes column information Date: Thu, 26 Jan 2017 15:55: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: dblaikie at gmail dot com 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: 2017-q1/txt/msg00056.txt.bz2 Content-length: 208 https://sourceware.org/bugzilla/show_bug.cgi?id=3D17701 --- Comment #3 from David Blaikie --- ping --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20905-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 26 19:41:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 113908 invoked by alias); 26 Jan 2017 19:41:38 -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 113882 invoked by uid 48); 26 Jan 2017 19:41:38 -0000 From: "yyc1992 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20633] JIT code debugging doesn't work with dynamically linked LLVM Date: Thu, 26 Jan 2017 19:41: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.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: yyc1992 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00057.txt.bz2 Content-length: 266 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20633 --- Comment #2 from Yichao Yu --- Ping. Could someone comment on the correct way to fix this please? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20906-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 26 20:05:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 32973 invoked by alias); 26 Jan 2017 20:05:12 -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 32911 invoked by uid 48); 26 Jan 2017 20:05:11 -0000 From: "yyc1992 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20633] JIT code debugging doesn't work with dynamically linked LLVM Date: Thu, 26 Jan 2017 20:05: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.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: yyc1992 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00058.txt.bz2 Content-length: 302 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20633 --- Comment #3 from Yichao Yu --- Maybe reversing the lookup order can fix this? The global variable (descrip= tor) won't have PLT issue. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20907-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 26 22:22:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 51388 invoked by alias); 26 Jan 2017 22:22:03 -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 51364 invoked by uid 48); 26 Jan 2017 22:22:03 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20939] GDB aborts if there is an error in disassembly Date: Thu, 26 Jan 2017 22:22: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.12.1 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00059.txt.bz2 Content-length: 512 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20939 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Yao Qi --- It is fixed in master too. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20908-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 30 15:53:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94917 invoked by alias); 30 Jan 2017 15:53:13 -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 94875 invoked by uid 48); 30 Jan 2017 15:53:13 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug python/16798] gdb.Value does not accept values which fit in unsigned long on python3 Date: Mon, 30 Jan 2017 15:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution target_milestone 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: 2017-q1/txt/msg00060.txt.bz2 Content-length: 666 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16798 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tromey at sourceware dot o= rg Resolution|--- |FIXED Target Milestone|--- |8.0 --- Comment #1 from Tom Tromey --- This works for me with git gdb. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20909-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 30 16:03:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 8314 invoked by alias); 30 Jan 2017 16:03:40 -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 8272 invoked by uid 48); 30 Jan 2017 16:03:40 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug tui/21089] GDB hangs if a syntax error is found when quitting Date: Mon, 30 Jan 2017 16:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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 cc resolution 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: 2017-q1/txt/msg00061.txt.bz2 Content-length: 662 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21089 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |tromey at sourceware dot o= rg Resolution|--- |DUPLICATE --- Comment #1 from Tom Tromey --- Already fixed. *** This bug has been marked as a duplicate of bug 20604 *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20910-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 30 16:03:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 8449 invoked by alias); 30 Jan 2017 16:03:42 -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 8328 invoked by uid 48); 30 Jan 2017 16:03:41 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20604] Using quit() causes a infinity loop which and can not exit gdb Date: Mon, 30 Jan 2017 16:03: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.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q1/txt/msg00062.txt.bz2 Content-length: 530 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20604 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pbotfullerton at cock dot = li --- Comment #4 from Tom Tromey --- *** Bug 21089 has been marked as a duplicate of this bug. *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20911-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 30 21:58:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 44498 invoked by alias); 30 Jan 2017 21:58: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 44459 invoked by uid 48); 30 Jan 2017 21:58:22 -0000 From: "atotic at chromium dot org" To: gdb-prs@sourceware.org Subject: [Bug symtab/21095] New: gdb_index generated by gold causes "Couldn't find method" Date: Mon, 30 Jan 2017 21:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: atotic at chromium dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00063.txt.bz2 Content-length: 3120 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21095 Bug ID: 21095 Summary: gdb_index generated by gold causes "Couldn't find method" Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: atotic at chromium dot org Target Milestone: --- gdb version: GNU gdb (GDB) 7.9-gg19 gold version: GNU gold (GNU Binutils 2.26.20160125) 1.11 TL;DR Trying to eval a method results in "Couldn't find method" when debugging libraries linked with gold's gdb_index option. Details: I debug Chromium with gdb. I use gold linker's gdb_index option to speed up my gdb startup time. Chromium has lots of shared libraries, and they all get their own gdb_index. Everything works fine when I do not use gold to generate gdb_index. For example: 1) not using gdb_index at all works 2) generating gdb_index using gdb save gdb-index && objcopy works. The gold setup worked fine for a few months, but recently I've started running into problems where gdb can't evaluate methods because it can't find them in superclass chain. An example: Running Chromium, gold gdb_index =3D true The program is stopped in a method blink::NGBlockNode::Layout() 'this' is NGBlockNode* this->layout_box_ is LayoutBox* LayoutBox inheriths method debugName() from superclass LayoutObject. (gdb) p this->layout_box_->debugName() Couldn't find method blink::LayoutBox::debugName (gdb) p *this->layout_box_ $3 =3D I've discovered a workaround: If I set breakpoints in constructors of LayoutBox superclass chain, the methods become reachable. (gdb) br blink::LayoutBox::LayoutBox Breakpoint 2 at 0x7f2e1e7b8870 (2 locations) (gdb) p *this->layout_box_ $5 =3D { =3D {}, members of blink::LayoutBox: m_frameRect =3D {....... (gdb) br blink::LayoutObject::LayoutObject Breakpoint 4 at 0x7f2e1e7ba8b0 (2 locations) (gdb) p this->layout_box_->debugName() $6 =3D "LayoutBlockFlow HTML" Investigation: I've tried to compare gdb_index generated by gdb, and by gold. I dump the indexes with: > objdump --dwarf=3Dgdb_index They look very different. gdb_index produced by gold is 1.7MB, filled with lines that look suspicions such as: [3115] SafeReadBits: 2828 [no symbol information] [3117] axisAttributeGetter: 2261 [no symbol information] [3119] returnValueAttributeSetterCallback: 2158 [no symbol information] 2164 [no symbol information] 2213 [no symbol information] gdb_index generated by gdb is 7MB, and looks reasonable: [155610] blink::EventTypeNames::cached: 113 [global variable] [155612] blink::Member::Member: 287 [global function] [155613] blink::installV8HTMLDataListElementTemplate: 2211 [static function] [155618] blink::GarbageCollected::operator new: 1103 [global function] I'd be happy to help work on this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20912-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 31 21:20:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 129553 invoked by alias); 31 Jan 2017 21:20:46 -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 129523 invoked by uid 48); 31 Jan 2017 21:20:44 -0000 From: "binarycrusader at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21097] New: can't disambiguate between enum and other types for rust Date: Tue, 31 Jan 2017 21:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: binarycrusader at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00064.txt.bz2 Content-length: 1687 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21097 Bug ID: 21097 Summary: can't disambiguate between enum and other types for rust Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: binarycrusader at gmail dot com Target Milestone: --- I'm working on a port of rust to another platform and I'm trying to debug a crash in one of the internal functions. I built a copy of gdb 7.12.1 and was trying to figure out the syntax for specifying types when printing values. This seems to work for the most part: (gdb) ptype syntax::ast::Ident type =3D struct syntax::ast::Ident { name: syntax::symbol::Symbol, ctxt: syntax::ext::hygiene::SyntaxContext, } However, some cases produce unexpected results: (gdb) ptype syntax::ast::Mod=20=20 type =3D struct syntax::ast::Mod { RUST$ENUM$DISR: syntax::ast::ItemKind, __0: syntax::ast::Mod, } Does not match what I expect from src/libsyntax/ast.rs: pub struct Mod { /// A span from the first token past `{` to the last token until `}`. /// For `mod foo;`, the inner span ranges from the first token /// to the last token in the external file. pub inner: Span, pub items: Vec>, } Is this expected? What are the caveats when attempting to debug the rust compiler itself? The rust compiler was built with debug info and without optimizations enabled for debugging purposes. Bug 20168 seems related. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20913-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 31 21:21:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 485 invoked by alias); 31 Jan 2017 21:21:27 -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 450 invoked by uid 48); 31 Jan 2017 21:21:27 -0000 From: "binarycrusader at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21097] can't disambiguate between enum and other types for rust Date: Tue, 31 Jan 2017 21:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: binarycrusader at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00065.txt.bz2 Content-length: 412 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21097 Shawn Walker-Salas changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20914-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 31 21:35:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 102930 invoked by alias); 31 Jan 2017 21:35:16 -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 102878 invoked by uid 48); 31 Jan 2017 21:35:16 -0000 From: "binarycrusader at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21097] can't disambiguate between enum and other types for rust Date: Tue, 31 Jan 2017 21:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: binarycrusader at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00066.txt.bz2 Content-length: 394 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21097 --- Comment #1 from Shawn Walker-Salas --- Another respondent to where I originally posted this query pointed out that "Your ptype is showing the enum variant ItemKind::Mod and not the type Mod, both are from syntax::ast." --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20915-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 01 06:05:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 99125 invoked by alias); 1 Feb 2017 06:05:05 -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 99079 invoked by uid 48); 1 Feb 2017 06:05:05 -0000 From: "danek.duvall at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21097] can't disambiguate between enum and other types for rust Date: Wed, 01 Feb 2017 06:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: danek.duvall at oracle dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00067.txt.bz2 Content-length: 407 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21097 Danek Duvall changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |danek.duvall at oracle dot= com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20916-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 01 17:28:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68033 invoked by alias); 1 Feb 2017 17:28:16 -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 68003 invoked by uid 48); 1 Feb 2017 17:28:15 -0000 From: "ks132 at yandex dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/21100] New: clang follow-fork-mode child internal-error Date: Wed, 01 Feb 2017 17:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ks132 at yandex dot ru X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00068.txt.bz2 Content-length: 4813 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21100 Bug ID: 21100 Summary: clang follow-fork-mode child internal-error Product: gdb Version: 7.12 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: ks132 at yandex dot ru Target Milestone: --- [ tmp]$ cat test.cpp int main(int argc, char *argv[]) {} [ tmp]$ gdb -n --args /usr/bin/clang-3.8 -v test.cpp -o test.out GNU gdb (GDB) Fedora 7.12-29.fc25 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/clang-3.8...Reading symbols from /usr/bin/clang-3.8...(no debugging symbols found)...done. (no debugging symbols found)...done. Missing separate debuginfos, use: dnf debuginfo-install clang-3.8.0-2.fc25.x86_64 (gdb) set follow-fork-mode child=20 (gdb) r Starting program: /usr/bin/clang-3.8 -v test.cpp -o test.out [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". clang version 3.8.0 (tags/RELEASE_380/final) Target: x86_64-unknown-linux-gnu Thread model: posix InstalledDir: /usr/bin Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-redhat-linux/6= .2.1 Found candidate GCC installation: /usr/lib/gcc/x86_64-redhat-linux/6.2.1 Selected GCC installation: /usr/bin/../lib/gcc/x86_64-redhat-linux/6.2.1 Candidate multilib: .;@m64 Candidate multilib: 32;@m32 Selected multilib: .;@m64 "/usr/bin/clang-3.8" -cc1 -triple x86_64-unknown-linux-gnu -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -main-file-name test.cpp -mrelocation-model static -mthread-model posix -mdisable-fp-elim -fmath-err= no -masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array -target-cpu x86-64 -v -dwarf-column-info -debugger-tuning=3Dgdb -resource-d= ir /usr/bin/../lib64/clang/3.8.0 -internal-isystem /usr/bin/../lib/gcc/x86_64-redhat-linux/6.2.1/../../../../include/c++/6.2.1 -internal-isystem /usr/bin/../lib/gcc/x86_64-redhat-linux/6.2.1/../../../../include/c++/6.2.1= /x86_64-redhat-linux -internal-isystem /usr/bin/../lib/gcc/x86_64-redhat-linux/6.2.1/../../../../include/c++/6.2.1= /backward -internal-isystem /usr/local/include -internal-isystem /usr/bin/../lib64/clang/3.8.0/include -internal-externc-isystem /include -internal-externc-isystem /usr/include -fdeprecated-macro -fdebug-compilation-dir /tmp -ferror-limit 19 -fmessage-length 203 -fobjc-runtime=3Dgcc -fcxx-exceptions -fexceptions -fdiagnostics-show-optio= n -o /tmp/test-580659.o -x c++ test.cpp [New process 21394] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". process 21394 is executing new program: /usr/bin/clang-3.8 ../../gdb/breakpoint.c:13853: internal-error: void delete_breakpoint(breakpoint*): Assertion `bpt !=3D NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y This is a bug, please report it. For instructions, see: . ../../gdb/breakpoint.c:13853: internal-error: void delete_breakpoint(breakpoint*): Assertion `bpt !=3D NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) n clang-3.8: error: unable to execute command: Killed clang-3.8: error: clang frontend command failed due to signal (use -v to see invocation) clang version 3.8.0 (tags/RELEASE_380/final) Target: x86_64-unknown-linux-gnu Thread model: posix InstalledDir: /usr/bin clang-3.8: note: diagnostic msg: PLEASE submit a bug report to and include= the crash backtrace, preprocessed source, and associated run script. ******************** PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: clang-3.8: note: diagnostic msg: /tmp/test-e36013.cpp clang-3.8: note: diagnostic msg: /tmp/test-e36013.sh clang-3.8: note: diagnostic msg:=20 ******************** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20917-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 01 23:24:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 126093 invoked by alias); 1 Feb 2017 23:24:33 -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 126030 invoked by uid 48); 1 Feb 2017 23:24:28 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21097] can't disambiguate between enum and other types for rust Date: Wed, 01 Feb 2017 23:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_status cf_reconfirmed_on everconfirmed 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: 2017-q1/txt/msg00069.txt.bz2 Content-length: 603 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21097 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-02-01 Ever confirmed|0 |1 --- Comment #2 from Tom Tromey --- Confirmed even with my relatively old rustc build. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20918-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 01 23:31:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3202 invoked by alias); 1 Feb 2017 23:31:44 -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 3167 invoked by uid 48); 1 Feb 2017 23:31:43 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21097] can't disambiguate between enum and other types for rust Date: Wed, 01 Feb 2017 23:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q1/txt/msg00070.txt.bz2 Content-length: 1625 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21097 --- Comment #3 from Tom Tromey --- I see two definitions of Mod at the same level in the debuginfo. I didn't investigate further but this is in keeping with comment#1. I think there's a rustc bug open about this already, I will dig it up later. <3><196df>: Abbrev Number: 29 (DW_TAG_structure_type) <196e0> DW_AT_name : (indirect string, offset: 0x1c7f5f): Mod <196e4> DW_AT_byte_size : 48 <4><196e5>: Abbrev Number: 26 (DW_TAG_member) <196e6> DW_AT_name : (indirect string, offset: 0x154): RUST$ENUM$DISR <196ea> DW_AT_type : <0x16dc0> <196ee> DW_AT_data_member_location: 0 <4><196ef>: Abbrev Number: 26 (DW_TAG_member) <196f0> DW_AT_name : (indirect string, offset: 0xe8): __0 <196f4> DW_AT_type : <0x196fa> <196f8> DW_AT_data_member_location: 8 <4><196f9>: Abbrev Number: 0 <3><196fa>: Abbrev Number: 29 (DW_TAG_structure_type) <196fb> DW_AT_name : (indirect string, offset: 0x1c7f5f): Mod <196ff> DW_AT_byte_size : 40 <4><19700>: Abbrev Number: 26 (DW_TAG_member) <19701> DW_AT_name : (indirect string, offset: 0x4c0f): inner <19705> DW_AT_type : <0x1fad05> <19709> DW_AT_data_member_location: 0 <4><1970a>: Abbrev Number: 26 (DW_TAG_member) <1970b> DW_AT_name : (indirect string, offset: 0x33cd): items <1970f> DW_AT_type : <0x1c25bd> <19713> DW_AT_data_member_location: 16 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20919-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 02 04:26:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 9609 invoked by alias); 2 Feb 2017 04:26:56 -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 9577 invoked by uid 48); 2 Feb 2017 04:26:56 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21097] can't disambiguate between enum and other types for rust Date: Thu, 02 Feb 2017 04:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q1/txt/msg00071.txt.bz2 Content-length: 327 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21097 --- Comment #4 from Tom Tromey --- Maybe it is https://github.com/rust-lang/rust/issues/32924 That seems related, though the example there is a bit different. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20920-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 02 16:02:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 24769 invoked by alias); 2 Feb 2017 16:02:13 -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 24738 invoked by uid 48); 2 Feb 2017 16:02:12 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21097] can't disambiguate between enum and other types for rust Date: Thu, 02 Feb 2017 16:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q1/txt/msg00072.txt.bz2 Content-length: 1358 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21097 --- Comment #5 from Tom Tromey --- I can get the same unusual debuginfo from a simple test: pub struct Mod { v: i32 } pub enum ItemKind { Mod(Mod) } fn x() -> ItemKind { return ItemKind::Mod(Mod{v: 23}); } pub fn main() { match x() { ItemKind::Mod(z) =3D> { println!("{}", z.v); } } } This yields: <2><5d>: Abbrev Number: 7 (DW_TAG_structure_type) <5e> DW_AT_name : (indirect string, offset: 0x353): Mod <62> DW_AT_byte_size : 4 <3><63>: Abbrev Number: 8 (DW_TAG_member) <64> DW_AT_name : (indirect string, offset: 0x141): __0 <68> DW_AT_type : <0x6e> <6c> DW_AT_data_member_location: 0 <3><6d>: Abbrev Number: 0 <2><6e>: Abbrev Number: 7 (DW_TAG_structure_type) <6f> DW_AT_name : (indirect string, offset: 0x353): Mod <73> DW_AT_byte_size : 4 <3><74>: Abbrev Number: 8 (DW_TAG_member) <75> DW_AT_name : (indirect string, offset: 0x351): v <79> DW_AT_type : <0x5e9> <7d> DW_AT_data_member_location: 0 <3><7e>: Abbrev Number: 0 However, I couldn't get gdb to print the wrong type here. So, something else must be going on. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20921-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 02 17:02:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 91088 invoked by alias); 2 Feb 2017 17:02:01 -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 91057 invoked by uid 48); 2 Feb 2017 17:02:00 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21097] can't disambiguate between enum and other types for rust Date: Thu, 02 Feb 2017 17:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q1/txt/msg00073.txt.bz2 Content-length: 433 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21097 --- Comment #6 from Tom Tromey --- I had an outdated gdb. With my simple test case and a new gdb build I get: (gdb) ptype q::Mod type =3D struct q::Mod ( q::Mod, ) ... which is the wrong Mod. Also the output here is weird. Ideally it would print Mod(q::Mod). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20922-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 02 18:08:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88483 invoked by alias); 2 Feb 2017 18:08:26 -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 88458 invoked by uid 48); 2 Feb 2017 18:08:26 -0000 From: "mvidal at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21103] New: Invalid read in read_dbx_symtab Date: Thu, 02 Feb 2017 18:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mvidal at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q1/txt/msg00074.txt.bz2 Content-length: 5224 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21103 Bug ID: 21103 Summary: Invalid read in read_dbx_symtab Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: mvidal at gmail dot com Target Milestone: --- Created attachment 9792 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9792&action=3Dedit read_dbx_symtab invalid read Hi there! I've been fuzzing gdb with American Fuzzy Lop and AddressSanitizer. The attached file causes a segmentation fault due to an invalid read. Let me know if I should provide any additional information. GNU gdb (GDB) 7.12.50.20170131-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from id:000013,sig:06,src:003207,op:havoc,rep:16...=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D =3D=3D23107=3D=3DERROR: AddressSanitizer: global-buffer-overflow on address 0x000002451444 at pc 0xb28dfb bp 0x7fff0614c4e0 sp 0x7fff0614c4d8 READ of size 1 at 0x000002451444 thread T0 #0 0xb28dfa in read_dbx_symtab /home/maxi/binutils-gdb/gdb/dbxread.c:11= 25 #1 0xb298f3 in dbx_symfile_read /home/maxi/binutils-gdb/gdb/dbxread.c:5= 48 #2 0x1182430 in read_symbols /home/maxi/binutils-gdb/gdb/symfile.c:870 #3 0x1183869 in syms_from_objfile_1 /home/maxi/binutils-gdb/gdb/symfile.c:1071 #4 0x1183869 in syms_from_objfile /home/maxi/binutils-gdb/gdb/symfile.c:1087 #5 0x1183869 in symbol_file_add_with_addrs /home/maxi/binutils-gdb/gdb/symfile.c:1186 #6 0x11872ae in symbol_file_add_from_bfd /home/maxi/binutils-gdb/gdb/symfile.c:1277 #7 0x11872ae in symbol_file_add /home/maxi/binutils-gdb/gdb/symfile.c:1= 290 #8 0x11872ae in symbol_file_add_main_1 /home/maxi/binutils-gdb/gdb/symfile.c:1313 #9 0x11872ae in symbol_file_add_main(char const*, enum_flags) /home/maxi/binutils-gdb/gdb/symfile.c:1304 #10 0xf494d0 in symbol_file_add_main_adapter /home/maxi/binutils-gdb/gdb/main.c:427 #11 0xf49c87 in catch_command_errors_const /home/maxi/binutils-gdb/gdb/main.c:403 #12 0xf4c903 in captured_main_1 /home/maxi/binutils-gdb/gdb/main.c:1045 #13 0xf4c903 in captured_main /home/maxi/binutils-gdb/gdb/main.c:1140 #14 0xf4c903 in gdb_main(captured_main_args*) /home/maxi/binutils-gdb/gdb/main.c:1158 #15 0x44bfaa in main /home/maxi/binutils-gdb/gdb/gdb.c:32 #16 0x7f6c80edfb44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44) #17 0x45e6ae (/home/maxi/binutils-gdb/gdb/gdb+0x45e6ae) 0x000002451444 is located 28 bytes to the left of global variable 'bincls_allocated' from 'dbxread.c' (0x2451460) of size 4 0x000002451444 is located 4 bytes to the right of global variable 'symbuf' = from 'dbxread.c' (0x2445440) of size 49152 SUMMARY: AddressSanitizer: global-buffer-overflow /home/maxi/binutils-gdb/gdb/dbxread.c:1125 read_dbx_symtab Shadow bytes around the buggy address: 0x000080482230: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x000080482240: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x000080482250: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x000080482260: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x000080482270: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =3D>0x000080482280: 00 00 00 00 00 00 00 00[f9]f9 f9 f9 04 f9 f9 f9 0x000080482290: f9 f9 f9 f9 00 f9 f9 f9 f9 f9 f9 f9 00 f9 f9 f9 0x0000804822a0: f9 f9 f9 f9 04 f9 f9 f9 f9 f9 f9 f9 00 f9 f9 f9 0x0000804822b0: f9 f9 f9 f9 04 f9 f9 f9 f9 f9 f9 f9 04 f9 f9 f9 0x0000804822c0: f9 f9 f9 f9 04 f9 f9 f9 f9 f9 f9 f9 04 f9 f9 f9 0x0000804822d0: f9 f9 f9 f9 04 f9 f9 f9 f9 f9 f9 f9 00 f9 f9 f9 Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07=20 Heap left redzone: fa Heap right redzone: fb Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack partial redzone: f4 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user: f7 Contiguous container OOB:fc ASan internal: fe =3D=3D23107=3D=3DABORTING --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20923-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 02 18:30:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 12208 invoked by alias); 2 Feb 2017 18:30:45 -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 12072 invoked by uid 48); 2 Feb 2017 18:30:32 -0000 From: "mvidal at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21103] Invalid read in read_dbx_symtab Date: Thu, 02 Feb 2017 18:30: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mvidal at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00075.txt.bz2 Content-length: 402 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21103 Maximiliano Gomez Vidal changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidal at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20924-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 02 21:27:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 81319 invoked by alias); 2 Feb 2017 21:27:18 -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 81295 invoked by uid 48); 2 Feb 2017 21:27:17 -0000 From: "linasvepstas at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug guile/21104] New: 7.12.1 does not compile with latest guile (2.1.6) Date: Thu, 02 Feb 2017 21:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: guile X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: linasvepstas at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00076.txt.bz2 Content-length: 1059 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21104 Bug ID: 21104 Summary: 7.12.1 does not compile with latest guile (2.1.6) Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: guile Assignee: unassigned at sourceware dot org Reporter: linasvepstas at gmail dot com Target Milestone: --- GDB version 7.12.1 (January 2017 tarball) does not compile with the latest guile (version 2.1.6) -- it appears that gdb is using a variety of functions that are now deprecated, and accessing structures that are no longer extern= ally visible. For example: ../../gdb/guile/scm-ports.c:1097:41: error: invalid use of incomplete type =E2=80=98scm_t_port {aka struct scm_t_port}=E2=80=99 no surprise -- struct scm_t_port is no longer defined in libguile/ports.h -- there's only a forward declaration, and the structure itself is now opaque. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20925-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 02 21:29:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 84332 invoked by alias); 2 Feb 2017 21:29:29 -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 84292 invoked by uid 48); 2 Feb 2017 21:29:28 -0000 From: "linasvepstas at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug guile/21104] 7.12.1 does not compile with latest guile (2.1.6) Date: Thu, 02 Feb 2017 21:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: guile X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: linasvepstas at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00077.txt.bz2 Content-length: 406 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21104 Linas Vepstas changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linasvepstas at gmail dot = com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20926-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 03 04:11:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 37011 invoked by alias); 3 Feb 2017 04:11:39 -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 36963 invoked by uid 48); 3 Feb 2017 04:11:38 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21097] can't disambiguate between enum and other types for rust Date: Fri, 03 Feb 2017 04:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q1/txt/msg00078.txt.bz2 Content-length: 451 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21097 --- Comment #7 from Tom Tromey --- > Also the output here is weird. Ideally it would print Mod(q::Mod). Err... we shouldn't really access this directly. But 'ptype q::ItemKind' prints: type =3D enum q::ItemKind { Mod, } ... where I think Mod(Mod) would perhaps be more useful. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20927-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 03 04:26:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 59632 invoked by alias); 3 Feb 2017 04:26:03 -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 59604 invoked by uid 48); 3 Feb 2017 04:26:02 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21097] can't disambiguate between enum and other types for rust Date: Fri, 03 Feb 2017 04:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q1/txt/msg00079.txt.bz2 Content-length: 869 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21097 --- Comment #8 from Tom Tromey --- (In reply to Tom Tromey from comment #7) > But 'ptype q::ItemKind' prints: This happens because the DWARF for ItemKind doesn't have a name for the first member. <2><50>: Abbrev Number: 5 (DW_TAG_union_type) <51> DW_AT_name : (indirect string, offset: 0x357): ItemKind <55> DW_AT_byte_size : 4 <3><56>: Abbrev Number: 6 (DW_TAG_member) <57> DW_AT_type : <0x5d> <5b> DW_AT_data_member_location: 0 <3><5c>: Abbrev Number: 0 The "skip_to" logic in rust_print_type is wrong for this type. Manually setting skip_to=3D0 makes it print the right thing. Maybe this code is assuming that an enum must have more than one member. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20928-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 03 12:01:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 98662 invoked by alias); 3 Feb 2017 12:01:29 -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 98640 invoked by uid 48); 3 Feb 2017 12:01:28 -0000 From: "currygt52 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21106] New: Ctrl-C can not stop target during some file-IO Date: Fri, 03 Feb 2017 12:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: currygt52 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00080.txt.bz2 Content-length: 2459 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21106 Bug ID: 21106 Summary: Ctrl-C can not stop target during some file-IO Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: remote Assignee: unassigned at sourceware dot org Reporter: currygt52 at gmail dot com Target Milestone: --- Hi, My program uses file-IO to output a large buffer. I expect the pressed ctrl-c will stop the target during the WRITE file-IO. gdb behaves differently according to different versions. Current GDB on mainline will not stop target, bug previous GDB (7.11) will = do this. Please help to check which is correct. [Code] #include #include #define SZ 4096000 char buf[SZ]; int main(void) { memset (buf, '1', SZ); write (STDOUT_FILENO, buf, SZ); return 0; } [version HEAD] Sending packet: $m1daca8,800#23...Ack ^CPacket received: 313131...313131 Quit Sending packet: $F-1,4#04...Ack Packet received: Fclose,00000000 Sending packet: $F0#76...Ack Packet received: Fclose,00000001 Sending packet: $F0#76...Ack Packet received: W00 [Inferior 1 (Remote target) exited normally] [version 7.11] Sending packet: $ma34a8,800#92...Ack Packet received: 313131...313131^CQuit Sending packet: $F-1,4,C#73...Ack Packet received: T02 Sending packet: $g#67...Ack Packet received: ffffffffb4ffff07080000000100000005000000dca3010000803e00b4ffff0700000000000= 00000000000000000000000000000b0ffff07298900002884000073010020 Sending packet: $m8428,4#a3...Ack Packet received: 0446631c Sending packet: $qfThreadInfo#bb...Ack Packet received: m1 Sending packet: $qsThreadInfo#c8...Ack Packet received: l Program received signal SIGINT, Interrupt. 0x00008428 in _write () (gdb) c Continuing. Sending packet: $vCont;c#a8...Ack Packet received: Fclose,00000000 Sending packet: $F0#76...Ack Packet received: Fclose,00000001 Sending packet: $F0#76...Ack Packet received: W00 [Inferior 1 (Remote target) exited normally] [Step to reproduce] arm-none-eabi-gcc -O0 -g -mthumb -mcpu=3Dcortex-m3 -specs=3Drdimon.specs -l= rdimon -o write write.c qemu-system-arm -machine versatilepb -cpu cortex-m3 -nographic -semihosting -kernel write -S -gdb tcp::8888 gdb) target remote :8888, press ctrl-c immediately after sending continue command. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20929-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 04 05:23:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 38435 invoked by alias); 4 Feb 2017 05:23:12 -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 38383 invoked by uid 55); 4 Feb 2017 05:23:11 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug rust/21097] can't disambiguate between enum and other types for rust Date: Sat, 04 Feb 2017 05:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q1/txt/msg00081.txt.bz2 Content-length: 1512 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21097 --- Comment #9 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Df0fd41c19269= 84fd1a524ff551286cba694539a0 commit f0fd41c1926984fd1a524ff551286cba694539a0 Author: Tom Tromey Date: Fri Feb 3 22:11:46 2017 -0700 Fix ptype of single-member Rust enums While looking into PR rust/21097, I found that ptype of a single-element enum in Rust did not always format the result properly. In particular, it would leave out the members of a tuple struct. Further testing showed that it also did the wrong thing for ordinary struct members as well. This patch fixes these problems. I'm marking it as being associated with the PR, since that is where the discovery was made; but this doesn't actually fix that PR (which I think ultimately is due to a Rust compiler bug). Built and regtested on x86-64 Fedora 25, using the system Rust compiler. I'm checking this in. 2017-02-03 Tom Tromey PR rust/21097: * rust-lang.c (rust_print_type) : Handle enums with a single member. 2017-02-03 Tom Tromey PR rust/21097: * gdb.rust/simple.exp: Add new tests. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20930-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 06 07:49:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 62313 invoked by alias); 6 Feb 2017 07:49:16 -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 62272 invoked by uid 55); 6 Feb 2017 07:49:14 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tdep/20936] provide and use sparc32 and sparc64 target description XML files Date: Mon, 06 Feb 2017 07:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: 7.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00082.txt.bz2 Content-length: 2243 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20936 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Jose E. Marchesi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D3f7b46f2daa6= c396564d786bda9c81e66d4b9278 commit 3f7b46f2daa6c396564d786bda9c81e66d4b9278 Author: Ivo Raisr Date: Sun Feb 5 23:44:03 2017 -0800 gdb: provide and use sparc{32,64} target description XML files. gdb/ChangeLog: 2017-02-06 Ivo Raisr PR tdep/20936 Provide and use sparc32 and sparc64 target description XML files. * features/sparc/sparc32-cp0.xml, features/sparc/sparc32-cpu.xml, features/sparc/sparc32-fpu.xml: New files for sparc 32-bit. * features/sparc/sparc64-cp0.xml, features/sparc/sparc64-cpu.xml, features/sparc/sparc64-fpu.xml: New files for sparc 64-bit. * features/sparc/sparc32-solaris.xml: New file. * features/sparc/sparc64-solaris.xml: New file. * features/sparc/sparc32-solaris.c: Generated. * features/sparc/sparc64-solaris.c: Generated. * sparc-tdep.h: Account for differences in target descriptions. * sparc-tdep.c (sparc32_register_name): Use target provided registe= rs. (sparc32_register_type): Use target provided registers. (validate_tdesc_registers): New function. (sparc32_gdbarch_init): Use tdesc_has_registers. Set pseudoregister functions. * sparc64-tdep.c (sparc64_register_name): Use target provided registers. (sparc64_register_type): Use target provided registers. (sparc64_init_abi): Set pseudoregister functions. gdb/doc/ChangeLog: 2017-02-06 Ivo Raisr PR tdep/20936 * gdb.texinfo: (Standard Target Features): Document SPARC features. (Sparc Features): New node. gdb/testsuite/ChangeLog: 2017-02-06 Ivo Raisr PR tdep/20936 * gdb.xml/tdesc-regs.exp: Provide sparc core registers for the test= s. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20931-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 06 09:16:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78365 invoked by alias); 6 Feb 2017 09:16:24 -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 77648 invoked by uid 55); 6 Feb 2017 09:16:23 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug record/21005] Process record does not support instruction GDB 7.12 (rdrand %eax) Date: Mon, 06 Feb 2017 09:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: lgustavo at codesourcery dot com 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: 2017-q1/txt/msg00083.txt.bz2 Content-length: 1319 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21005 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Luis Machado : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D20b477a75c00= de06a92b9577fd74416699d2c37f commit 20b477a75c00de06a92b9577fd74416699d2c37f Author: Luis Machado Date: Mon Feb 6 03:12:00 2017 -0600 [BZ 21005] Add support for Intel 64 rdrand and rdseed record/replay This patch addresses BZ 21005, which is gdb failing to recognize an rdr= and instruction. It enables support for both rdrand and rdseed and handles extended regi= ster addressing (R8~R15) for 16-bit, 32-bit and 64-bit. gdb/ChangeLog 2017-02-06 Luis Machado * NEWS: Mention support for record/replay of Intel 64 rdrand and rdseed instructions. i386-tdep.c (i386_process_record): Handle Intel 64 rdrand and rseed. gdb/testsuite/ChangeLog: 2017-02-06 Luis Machado * gdb.reverse/insn-reverse.c: Include insn-reverse-x86.c. * gdb.reverse/insn-reverse-x86.c: New file. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20932-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 06 09:18:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 101560 invoked by alias); 6 Feb 2017 09:18:38 -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 99614 invoked by uid 48); 6 Feb 2017 09:18:36 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug record/21005] Process record does not support instruction GDB 7.12 (rdrand %eax) Date: Mon, 06 Feb 2017 09:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lgustavo at codesourcery dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: lgustavo at codesourcery dot com 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00084.txt.bz2 Content-length: 534 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21005 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Luis Machado --- Fixed in GDB master. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20933-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 07 17:22:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68027 invoked by alias); 7 Feb 2017 17:22:29 -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 67924 invoked by uid 48); 7 Feb 2017 17:22:28 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/16188] Verify PTRACE_TRACEME succeeded? Date: Tue, 07 Feb 2017 17:22: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to 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: 2017-q1/txt/msg00085.txt.bz2 Content-length: 586 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16188 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com Assignee|unassigned at sourceware dot org |sergiodj at redhat = dot com --- Comment #2 from Sergio Durigan Junior --- I'll work on this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20934-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 08 10:21:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 82499 invoked by alias); 8 Feb 2017 10:21:24 -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 82474 invoked by uid 48); 8 Feb 2017 10:21:23 -0000 From: "eriksohns at 123mail dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21114] New: gdb crash Date: Wed, 08 Feb 2017 10:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: eriksohns at 123mail dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00086.txt.bz2 Content-length: 2225 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21114 Bug ID: 21114 Summary: gdb crash Product: gdb Version: 7.7 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: eriksohns at 123mail dot org Target Milestone: --- I have a recurring problem debugging an application with gdb (using qtcreat= or); the debugger event log contains the following context information: =3Dbreakpoint-modified,bkpt=3D{number=3D"6",type=3D"breakpoint",disp=3D"kee= p",enabled=3D"y",addr=3D"",times=3D"0",original-location=3D"abort= "},{number=3D"6.1",enabled=3D"y",addr=3D"0x00007ffff11c5300",func=3D"__GI_a= bort",file=3D"abort.c",fullname=3D"/build/glibc-qK83Be/glibc-2.19/stdlib/ab= ort.c",line=3D"51",thread-groups=3D["i1"]},{number=3D"6.2",enabled=3D"y",ad= dr=3D"0x00007ffff11c5300",func=3D"__GI_abort",file=3D"abort.c",fullname=3D"= /build/glibc-qK83Be/glibc-2.19/stdlib/abort.c",line=3D"51",thread-groups=3D= ["i2"]} >~"/build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/record-full.c:1818: internal-error:= record_full_remove_breakpoint: removing unknown breakpoint\nA problem inte= rnal to GDB has been detected,\nfurther debugging may prove unreliable.\nQu= it this debugging session? " >~"(y or n) [answered Y; input not from terminal]\n" >~"/build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/record-full.c:1818: internal-error:= record_full_remove_breakpoint: removing unknown breakpoint\nA problem inte= rnal to GDB has been detected,\nfurther debugging may prove unreliable.\nCr= eate a core file of GDB? " >~"(y or n) [answered Y; input not from terminal]\n" dHANDLE GDB ERROR: The gdb process was ended forcefully dGDB PROCESS FINISHED, status 1, code 0 dThe gdb process exited somewhat unexpectedly. dNOTE: ENGINE SPONTANEOUS SHUTDOWN dState changed BY FORCE from InferiorRunOk(11) to EngineShutdownOk(22) [mas= ter] dState changed from EngineShutdownOk(22) to DebuggerFinished(23) [master] dQUEUE: FINISH DEBUGGER dNOTE: FINISH DEBUGGER dHANDLE RUNCONTROL FINISHED sDebugger finished. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20935-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 08 22:55:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 120450 invoked by alias); 8 Feb 2017 22:55: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 120424 invoked by uid 48); 8 Feb 2017 22:55:52 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21117] New: Occasional wrong thread numbering when following an exec Date: Wed, 08 Feb 2017 22:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00087.txt.bz2 Content-length: 1351 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21117 Bug ID: 21117 Summary: Occasional wrong thread numbering when following an exec Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: threads Assignee: unassigned at sourceware dot org Reporter: simon.marchi at ericsson dot com Target Milestone: --- I was playing with the mi-nsthrexec test, and noticed something odd. I am using the test executable like this: $ ./gdb -nx testsuite/outputs/gdb.mi/mi-nsthrexec/mi-nsthrexec -ex "b mai= n" -ex "r" and I just use the "continue" command over and over. The spawned thread ca= lls exec, so each time we just come back to main. Post-exec, we expect to alwa= ys see thread 1 hitting the breakpoint at main. That's what happens most of t= he time, but not always. Here's the result: http://pastebin.com/raw/tQYnBfEV As you can see, it goes from "Thread 1" to "Thread 12" to "Thread 49", etc.= =20 AFAIK, when any thread of a process execs, it's the main thread (the one for which tgid=3D=3Dpid in Linux terminology, pid=3D=3Dlwp in GDB terminology) = that survives, so we should always preserve Thread 1. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20936-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 09 11:00:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 114375 invoked by alias); 9 Feb 2017 11:00:58 -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 114326 invoked by uid 48); 9 Feb 2017 11:00:55 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21117] Occasional wrong thread numbering when following an exec Date: Thu, 09 Feb 2017 11:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: cc 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: 2017-q1/txt/msg00088.txt.bz2 Content-length: 1500 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21117 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- >>From the kernel's perspective, it should be the leader lwp that hits the breakpoint too, so either a kernel bug, or a gdb bug. From your logs, looks like the latter. >>From the logs, we can tell that the leader/process pid is "19676": > process 19676 is executing new program: /home/simark/build/binutils- > ^^^^^ I think that there's a good hint here, just before the first time we see a thread !=3D 1: > [New Thread 0x7ffff751a700 (LWP 19697)] > [Thread 0x7ffff7f8b700 (LWP 19676) exited] <<<< LEADER DETECTED AS EXITED > [New LWP 19676] <<<< LEADER RE-ADDED > process 19676 is executing new program: <<<< STILL SAME PID >=20 > Thread 10 "mi-nsthrexec" hit Breakpoint 1, main (argc=3D1, argv=3D0x7ffff= fffda98) So we detected the leader as exited, deleted it (most probably in linux-nat.c:check_zombie_leaders), and then when we get the exec event out of the kernel, we re-add the leader thread. This will give it a new gdb thread number. A "set debug lin-lwp 1" log probably makes that clearer. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20937-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 09 14:02:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88170 invoked by alias); 9 Feb 2017 14:02:21 -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 88145 invoked by uid 48); 9 Feb 2017 14:02:20 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21117] Occasional wrong thread numbering when following an exec Date: Thu, 09 Feb 2017 14:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q1/txt/msg00089.txt.bz2 Content-length: 892 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21117 --- Comment #2 from Pedro Alves --- Note that this isn't a case of a small race window. We have tests that exercise the case of the leader thread really exits before its child thread= s.=20 In which case the leader remains zombie until the children exit. But if on= e of the children execs instead, then the leader reappears then. It may be that the best fix for all of this is to stop deleting the leader thread when we detect it as zombie, but instead teach the core of gdb about that state: the thread exists, but you can't do anything with it other than collect exit status -- and leave the thread around. Easier to do when you consider only native debugging. Not so simple when you consider target rem= ote / RSP too. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20938-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 09 14:04:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 90569 invoked by alias); 9 Feb 2017 14:04:21 -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 90543 invoked by uid 48); 9 Feb 2017 14:04:20 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21117] Occasional wrong thread numbering when following an exec Date: Thu, 09 Feb 2017 14:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q1/txt/msg00090.txt.bz2 Content-length: 386 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21117 --- Comment #3 from Pedro Alves --- Note, IIRC, this "detected leader as zombie, so delete it" is what causes a number of racy failures when testing against gdbserver, around "continue to exit" tests in several testcases. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20939-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 09 15:26:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 70852 invoked by alias); 9 Feb 2017 15:26:33 -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 69532 invoked by uid 48); 9 Feb 2017 15:26:32 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21117] Occasional wrong thread numbering when following an exec Date: Thu, 09 Feb 2017 15:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: 2017-q1/txt/msg00091.txt.bz2 Content-length: 1645 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21117 --- Comment #4 from Simon Marchi --- (In reply to Pedro Alves from comment #1) > From the kernel's perspective, it should be the leader lwp that hits the > breakpoint too, so either a kernel bug, or a gdb bug. From your logs, lo= oks > like the latter. >=20 > From the logs, we can tell that the leader/process pid is "19676": >=20 > > process 19676 is executing new program: /home/simark/build/binutils- > > ^^^^^ >=20 > I think that there's a good hint here, just before the first time we see a > thread !=3D 1: >=20 > > [New Thread 0x7ffff751a700 (LWP 19697)] > > [Thread 0x7ffff7f8b700 (LWP 19676) exited] <<<< LEADER DETECTED AS EXIT= ED > > [New LWP 19676] <<<< LEADER RE-ADDED > > process 19676 is executing new program: <<<< STILL SAME PID > >=20 > > Thread 10 "mi-nsthrexec" hit Breakpoint 1, main (argc=3D1, argv=3D0x7ff= fffffda98) >=20 > So we detected the leader as exited, deleted it (most probably in > linux-nat.c:check_zombie_leaders), and then when we get > the exec event out of the kernel, we re-add the leader thread. > This will give it a new gdb thread number. >=20 > A "set debug lin-lwp 1" log probably makes that clearer. That's exactly what I observed. I put a conditional breakpoint on delete_thread_1: (gdb) b delete_thread_1 if ptid.lwp =3D=3D ptid.pid the breakpoint triggers when the bug manifests itself. We can see that delete_thread got called from check_zombie_leaders. That's exactly what --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20940-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 09 16:30:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 69437 invoked by alias); 9 Feb 2017 16:30:36 -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 69380 invoked by uid 48); 9 Feb 2017 16:30:30 -0000 From: "daniel.gutson at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21121] New: clock() result is altered by time spent on the CLI Date: Thu, 09 Feb 2017 16:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: daniel.gutson at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00092.txt.bz2 Content-length: 1062 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21121 Bug ID: 21121 Summary: clock() result is altered by time spent on the CLI Product: gdb Version: 7.11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: daniel.gutson at gmail dot com Target Milestone: --- Consider the following: #include #include int main() { const auto start =3D clock(); volatile auto pepe =3D start * 3; ++pepe; std::cout << clock() - start << std::endl; } By breaking in the ++pepe line, waiting in the CLI until continuing affects= the results shown. However, the time while the process is suspended does not affect clock() (w= hile not debugging). I think that waiting an arbitrary time in the CLI should not make the behav= ior as if clock() keeps counting. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20941-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 09 16:31:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 70275 invoked by alias); 9 Feb 2017 16:31:29 -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 70250 invoked by uid 48); 9 Feb 2017 16:31:29 -0000 From: "daniel.gutson at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21121] clock() result is altered by time spent on the CLI Date: Thu, 09 Feb 2017 16:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: daniel.gutson at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00093.txt.bz2 Content-length: 409 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21121 Daniel Gutson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |perezfederico at unc dot e= du.ar --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20942-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 09 16:39:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 110353 invoked by alias); 9 Feb 2017 16:39:00 -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 110310 invoked by uid 48); 9 Feb 2017 16:39:00 -0000 From: "daniel.gutson at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21121] clock() result is altered by time spent on the CLI Date: Thu, 09 Feb 2017 16:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: daniel.gutson at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00094.txt.bz2 Content-length: 400 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21121 Daniel Gutson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20943-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 09 17:35:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 57245 invoked by alias); 9 Feb 2017 17:35:38 -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 57202 invoked by uid 48); 9 Feb 2017 17:35:38 -0000 From: "daniel.gutson at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/9532] let "commands" select more than one breakpoint Date: Thu, 09 Feb 2017 17:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: daniel.gutson at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: tromey at redhat dot com X-Bugzilla-Target-Milestone: 7.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q1/txt/msg00095.txt.bz2 Content-length: 978 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9532 Daniel Gutson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.gutson at gmail dot= com --- Comment #5 from Daniel Gutson --- How has this been implemented? 'help' doesn't explain: (gdb) help commands Set commands to be executed when a breakpoint is hit. Give breakpoint number as argument after "commands". With no argument, the targeted breakpoint is the last one set. The commands themselves follow starting on the next line. Type a line containing "end" to indicate the end of them. Give "silent" as the first line to make the breakpoint silent; then no output is printed when it is hit, except what the commands print. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20944-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 09 17:46:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 97870 invoked by alias); 9 Feb 2017 17:46:10 -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 97837 invoked by uid 48); 9 Feb 2017 17:46:08 -0000 From: "mlen at mlen dot pl" To: gdb-prs@sourceware.org Subject: [Bug gdb/21051] nat/x86-linux-dregs.c:146: internal-error: void x86_linux_update_debug_registers(lwp_info*): Assertion `lwp_is_stopped (lwp)' failed. Date: Thu, 09 Feb 2017 17:46: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mlen at mlen dot pl X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00096.txt.bz2 Content-length: 6590 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21051 Mateusz Lenik changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mlen at mlen dot pl --- Comment #1 from Mateusz Lenik --- I am also able to reproduce this on both ArchLinux and Gentoo. 7.11 is the earliest version failing with this error I was able to find. Steps to reproduce in my case: 1) Install ruby and rake 2) touch Rakefile 3) gdb --args ruby -S rake -T GNU gdb (Gentoo 7.12.1 vanilla) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ruby...Reading symbols from /usr/lib64/debug//usr/bin/ruby23.debug...done. done. (gdb) set follow-fork-mode child (gdb) r Starting program: /usr/bin/ruby -S rake -T [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7ffff7ff6700 (LWP 26921)] [New process 26922] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". ./nat/x86-linux-dregs.c:146: internal-error: void x86_linux_update_debug_registers(lwp_info*): Assertion `lwp_is_stopped (lwp= )' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y This is a bug, please report it. For instructions, see: . ./nat/x86-linux-dregs.c:146: internal-error: void x86_linux_update_debug_registers(lwp_info*): Assertion `lwp_is_stopped (lwp= )' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) y Backtrace from the core: $ gdb $(which gdb) /var/cores/core.gdb.1486662173=20=20=20 GNU gdb (Gentoo 7.12.1 vanilla) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/gdb...Reading symbols from /usr/lib64/debug//usr/bin/gdb.debug...done. done. [New LWP 24243] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `gdb --args ruby -S rake -T'. Program terminated with signal SIGABRT, Aborted. #0 0x00007efefa67c0e8 in __GI_raise (sig=3Dsig@entry=3D6) at ../sysdeps/unix/sysv/linux/raise.c:54 54 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); (gdb) bt #0 0x00007efefa67c0e8 in __GI_raise (sig=3Dsig@entry=3D6) at ../sysdeps/unix/sysv/linux/raise.c:54 #1 0x00007efefa67d53a in __GI_abort () at abort.c:89 #2 0x0000000000752646 in dump_core () at utils.c:561 #3 0x0000000000754ce9 in internal_vproblem(internal_problem *, const char = *, int, const char *, typedef __va_list_tag __va_list_tag *) (problem=3Dproblem@entry=3D0x1b47220 , file=3D, line=3D, fmt=3D, ap=3Dap@entry=3D0x7ffe= 9b29cf80) at utils.c:772 #4 0x0000000000754da9 in internal_verror (file=3D, line=3D, fmt=3D, ap=3Dap@entry=3D0x7ffe9b29cf= 80) at utils.c:798 #5 0x000000000078e527 in internal_error (file=3Dfile@entry=3D0xc929d8 "./nat/x86-linux-dregs.c", line=3Dline@entry=3D146, fmt=3D) = at common/errors.c:55 #6 0x000000000056165e in x86_linux_update_debug_registers (lwp=3D0x351ee30= ) at nat/x86-linux-dregs.c:146 #7 0x00000000005520a3 in detach_one_lwp (lp=3Dlp@entry=3D0x351ee30, signo_p=3Dsigno_p@entry=3D0x0) at linux-nat.c:1431 #8 0x000000000055239f in detach_callback (lp=3D0x351ee30, data=3D) at linux-nat.c:1489 #9 0x0000000000554ab9 in iterate_over_lwps (filter=3D..., callback=3Dcallback@entry=3D0x552360 , data=3Ddata@entry=3D0x0) at linux-nat.c:984 #10 0x0000000000554ff6 in linux_nat_detach (ops=3D0x30a40c0, args=3D0x0, from_tty=3D0) at linux-nat.c:1511 #11 0x000000000055b48f in thread_db_detach (ops=3D, args=3D0= x0, from_tty=3D0) at linux-thread-db.c:1099 #12 0x0000000000668eae in handle_vfork_child_exec_or_exit (exec=3Dexec@entr= y=3D1) at infrun.c:976 #13 0x000000000066e53d in handle_inferior_event_1 (ecs=3D0x7ffe9b29d3f0) at infrun.c:5334 #14 handle_inferior_event (ecs=3Decs@entry=3D0x7ffe9b29d3f0) at infrun.c:54= 24 #15 0x00000000006705e6 in fetch_inferior_event (client_data=3D) at infrun.c:3972 #16 0x0000000000686865 in gdb_wait_for_event (block=3Dblock@entry=3D0) at event-loop.c:859 #17 0x0000000000686987 in gdb_do_one_event () at event-loop.c:322 #18 0x0000000000686b05 in gdb_do_one_event () at event-loop.c:360 #19 start_event_loop () at event-loop.c:371 #20 0x0000000000680668 in captured_command_loop (data=3Ddata@entry=3D0x0) at main.c:324 #21 0x000000000067d383 in catch_errors (func=3Dfunc@entry=3D0x680640 , func_args=3Dfunc_args@entry=3D0x0, errstring=3Derrstring@entry=3D0x177a56c "", mask=3Dmask@entry=3DRETURN_MASK= _ALL) at exceptions.c:236 #22 0x00000000006815a6 in captured_main (data=3D0x7ffe9b29d5c0) at main.c:1= 149 #23 gdb_main (args=3Dargs@entry=3D0x7ffe9b29d6e0) at main.c:1159 #24 0x0000000000411d15 in main (argc=3D, argv=3D) at gdb.c:32 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20945-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 09 18:06:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20680 invoked by alias); 9 Feb 2017 18:06:07 -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 20658 invoked by uid 48); 9 Feb 2017 18:06:07 -0000 From: "martingalvan at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21122] New: Documentation mistakes for breakpoint-related commands Date: Thu, 09 Feb 2017 18:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: martingalvan at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00097.txt.bz2 Content-length: 1310 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21122 Bug ID: 21122 Summary: Documentation mistakes for breakpoint-related commands Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: martingalvan at sourceware dot org Target Milestone: --- The current documentation states the following: "Some gdb commands accept a range of breakpoints on which to operate. A breakpoint range is either a single breakpoint number, like =E2=80=985=E2= =80=99, or two such numbers, in increasing order, separated by a hyphen, like =E2=80=985-7=E2= =80=99. When a breakpoint range is given to a command, all breakpoints in that range are operated on." However, this fails to mention that ranges can also be specified as space-separated lists of breakpoint numbers, like '5 6 7'. On a related issue, 'help commands' seems to imply that the 'commands' comm= and can only be applied to a single breakpoint at the time: (gdb) help commands Set commands to be executed when a breakpoint is hit. Give breakpoint number as argument after "commands". ... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20946-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 09 18:07:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23446 invoked by alias); 9 Feb 2017 18:07:29 -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 23419 invoked by uid 48); 9 Feb 2017 18:07:29 -0000 From: "martingalvan at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21122] Documentation mistakes for breakpoint-related commands Date: Thu, 09 Feb 2017 18:07: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: martingalvan at sourceware dot org 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: cc 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: 2017-q1/txt/msg00098.txt.bz2 Content-length: 499 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21122 Martin Galvan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.gutson at gmail dot= com, | |martingalvan at sourceware= dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20947-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 09 18:30:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 129918 invoked by alias); 9 Feb 2017 18:30:36 -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 129711 invoked by uid 48); 9 Feb 2017 18:30:23 -0000 From: "martingalvan at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21122] Documentation mistakes for breakpoint-related commands Date: Thu, 09 Feb 2017 18:30: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: martingalvan at sourceware dot org 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: attachments.created 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: 2017-q1/txt/msg00099.txt.bz2 Content-length: 344 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21122 --- Comment #1 from Martin Galvan --- Created attachment 9796 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9796&action=3Dedit Proposed rewording of the docs --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20948-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 09 21:47:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107476 invoked by alias); 9 Feb 2017 21:47:21 -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 107397 invoked by uid 48); 9 Feb 2017 21:47:20 -0000 From: "dje at google dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/21126] New: PIE displacement check needs to handle fully NULL'd GNU_RELRO Date: Thu, 09 Feb 2017 21:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dje at google dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00100.txt.bz2 Content-length: 2167 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21126 Bug ID: 21126 Summary: PIE displacement check needs to handle fully NULL'd GNU_RELRO Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: dje at google dot com Target Milestone: --- Evidently strip is now fully NULLing out PT_GNU_RELRO segments (as in even = the segment type is changed to PT_NULL). svr4_exec_displacement needs to be updated to handle this. There's no real reason to compare absolutely every segment header in this sanity check (see svr4_exec_displacement), and the cost to the user of accidentally getting it wrong is severe (completely unusable debug session). I think it would be better to let the test pass with a loud warning than to fail. [Setting aside a better test which is to just compare the build ids.] See also PR 11786. /* Strip modifies the flags and alignment of PT_GNU_RELRO= .=20=20=20=20 CentOS-5 has problems with filesz, memsz as well.=20= =20=20=20=20=20=20=20=20=20 See PR 11786. */ if (phdr2[i].p_type =3D=3D PT_GNU_RELRO) { Elf64_External_Phdr tmp_phdr =3D *phdrp; Elf64_External_Phdr tmp_phdr2 =3D *phdr2p; memset (tmp_phdr.p_filesz, 0, 8); memset (tmp_phdr.p_memsz, 0, 8); memset (tmp_phdr.p_flags, 0, 4); memset (tmp_phdr.p_align, 0, 8); memset (tmp_phdr2.p_filesz, 0, 8); memset (tmp_phdr2.p_memsz, 0, 8); memset (tmp_phdr2.p_flags, 0, 4); memset (tmp_phdr2.p_align, 0, 8); if (memcmp (&tmp_phdr, &tmp_phdr2, sizeof (tmp_phdr)) =3D=3D 0) continue; } --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20949-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 10 10:11:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 33875 invoked by alias); 10 Feb 2017 10:11:22 -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 33846 invoked by uid 48); 10 Feb 2017 10:11:21 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21122] Documentation mistakes for breakpoint-related commands Date: Fri, 10 Feb 2017 10:11: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: cc 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: 2017-q1/txt/msg00101.txt.bz2 Content-length: 861 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21122 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #2 from Pedro Alves --- > However, this fails to mention that ranges can also be specified as space- > separated lists of breakpoint numbers, like '5 6 7'. That only looks like a range because the numbers are ordered. Say, "7 4 9" doesn't look like a range to me. I'd call it a "list" instead. I think it'd be clearer if the section was reworded to speak in terms of "breakpoint lists". See "thread ID lists" in the manual. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20950-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 10 15:01:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109190 invoked by alias); 10 Feb 2017 15:01:18 -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 109160 invoked by uid 48); 10 Feb 2017 15:01:17 -0000 From: "martingalvan at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21122] Documentation mistakes for breakpoint-related commands Date: Fri, 10 Feb 2017 15:01: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: martingalvan at sourceware dot org 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: attachments.isobsolete attachments.created 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: 2017-q1/txt/msg00102.txt.bz2 Content-length: 771 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21122 Martin Galvan changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #9796|0 |1 is obsolete| | --- Comment #3 from Martin Galvan --- Created attachment 9797 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9797&action=3Dedit Proposed rewording of the docs Rewrote the docs to speak in terms of breakpoint "lists", as it's done with thread ID lists, and fixed a couple of minor mistakes. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20951-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 10 15:07:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 15726 invoked by alias); 10 Feb 2017 15:07:28 -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 15692 invoked by uid 48); 10 Feb 2017 15:07:27 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21122] Documentation mistakes for breakpoint-related commands Date: Fri, 10 Feb 2017 15:07: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q1/txt/msg00103.txt.bz2 Content-length: 682 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21122 --- Comment #4 from Pedro Alves --- In a couple places where it now says "accept a list", it might be worth it = to say "a space-separated list", as I don't think it's mentioned anywhere how elements are supposedly separated. We should probably update the "@cindex" entries too, which are still named = in terms of ranges. Maybe keep the ranges ones and add lists ones too. Otherwise looks great to me, thanks much for doing this, but I can't approve it. You should post this to gdb-patches, so Eli can review it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20952-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 10 16:40:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 57268 invoked by alias); 10 Feb 2017 16:40:28 -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 56743 invoked by uid 55); 10 Feb 2017 16:40:23 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21122] Documentation mistakes for breakpoint-related commands Date: Fri, 10 Feb 2017 16:40: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q1/txt/msg00104.txt.bz2 Content-length: 1464 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21122 --- Comment #5 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Martin Galvan : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D18da0c51da58= 527152e019924cc5105cd89765d6 commit 18da0c51da58527152e019924cc5105cd89765d6 Author: Martin Galvan Date: Fri Feb 10 13:37:31 2017 -0300 PR gdb/21122: Fix documentation mistakes for breakpoint commands Currently, the breakpoint documentation refers to some commands taking breakpoint "ranges" as arguments. We discussed this with Pedro and concluded that = it would be more accurate to speak in terms of breakpoint "lists", whose elements can optionally be ranges. I also fixed a couple of minor mistakes in the docs. gdb/ChangeLog: * breakpoint.c (_initialize_breakpoint): Update the help description of the 'commands' command to indicate that it takes a list argument. gdb/doc/ChangeLog: * gdb.texinfo (Breakpoints): Reword documentation to speak in terms= of space-separated breakpoint lists. Also add a missing @table command and @cindex for breakpoint lists. gdb/testsuite/ChangeLog: * gdb.base/help.exp: Update match pattern for testing 'help command= s'. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20953-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 10 16:55:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 87392 invoked by alias); 10 Feb 2017 16:55:31 -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 87351 invoked by uid 48); 10 Feb 2017 16:55:30 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21122] Documentation mistakes for breakpoint-related commands Date: Fri, 10 Feb 2017 16:55: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q1/txt/msg00105.txt.bz2 Content-length: 333 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21122 --- Comment #6 from Pedro Alves --- Martin, I've given your bugzilla account editbugs privileges now, meaning y= ou should be able to close this. Please give it a try. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20954-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 10 16:56:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88463 invoked by alias); 10 Feb 2017 16:56:27 -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 88438 invoked by uid 48); 10 Feb 2017 16:56:26 -0000 From: "martingalvan at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21122] Documentation mistakes for breakpoint-related commands Date: Fri, 10 Feb 2017 16:56: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: martingalvan at sourceware dot org 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00106.txt.bz2 Content-length: 533 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21122 Martin Galvan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Martin Galvan --- Done. Thanks! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20955-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 12 20:25:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 47164 invoked by alias); 12 Feb 2017 20:25:36 -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 47143 invoked by uid 48); 12 Feb 2017 20:25:35 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20757] gdb: DWARF-5 support Date: Sun, 12 Feb 2017 20:25: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan.kratochvil at redhat dot com 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: 2017-q1/txt/msg00107.txt.bz2 Content-length: 311 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20757 --- Comment #2 from Jan Kratochvil --- [PATCH 5/8] DWARF-5 basic functionality https://sourceware.org/ml/gdb-patches/2017-02/msg00303.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20956-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 13 08:58:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78929 invoked by alias); 13 Feb 2017 08:58:54 -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 78896 invoked by uid 48); 13 Feb 2017 08:58:53 -0000 From: "leopardsaga at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug server/13984] gdb stops controlling a thread after "Remote 'g' packet reply is too long: ..." error message Date: Mon, 13 Feb 2017 08:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: leopardsaga at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00108.txt.bz2 Content-length: 540 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13984 honghe changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leopardsaga at gmail dot c= om --- Comment #15 from honghe --- @Mehmet Ali SARIKAYA=20 You patch works with GDB 7.12 on Ubuntu 14.04. Thanks! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20957-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 14 17:30:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 29614 invoked by alias); 14 Feb 2017 17:30:46 -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 29308 invoked by uid 48); 14 Feb 2017 17:30:42 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug exp/21162] New: GDB internal error with unbounded array typecast expression Date: Tue, 14 Feb 2017 17:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00109.txt.bz2 Content-length: 806 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21162 Bug ID: 21162 Summary: GDB internal error with unbounded array typecast expression Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: exp Assignee: unassigned at sourceware dot org Reporter: arnez at linux dot vnet.ibm.com Target Milestone: --- GDB crashes with internal error when trying to evaluate the following expression: (gdb) p ((char*)(short[]){1})[1] /home/arnez/src/binutils-gdb/gdb/gdbtypes.c:4722: internal-error: type* copy_type(const type*): Assertion `TYPE_OBJFILE_OWNED (type)' failed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20958-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 14 18:03:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 11170 invoked by alias); 14 Feb 2017 18:03:07 -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 8719 invoked by uid 55); 14 Feb 2017 18:03:06 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug python/13598] need a pre-prompt event Date: Tue, 14 Feb 2017 18:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q1/txt/msg00110.txt.bz2 Content-length: 1614 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13598 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D3f77c7691fc5= ff92eef90f39bb972f25c7422fb0 commit 3f77c7691fc5ff92eef90f39bb972f25c7422fb0 Author: Tom Tromey Date: Wed Apr 29 09:44:24 2015 -0600 PR python/13598 - add before_prompt event This adds an event that is emitted just before GDB presents a prompt to the user. This provides Python code a way to react to whatever changes might have been made by the previous command. For example, in my GUI I use this to track changes to the selected frame and reflect them in the UI. Built and regtested on x86-64 Fedora 23. gdb/ChangeLog 2017-02-14 Tom Tromey PR python/13598: * python/python.c (gdbpy_before_prompt_hook): Emit before_prompt event. * python/py-evts.c (gdbpy_initialize_py_events): Add before_prompt registry. * python/py-events.h (events_object) : New field. gdb/doc/ChangeLog 2017-02-14 Tom Tromey PR python/13598: * python.texi (Events In Python): Document events.before_prompt. gdb/testsuite/ChangeLog 2017-02-14 Tom Tromey PR python/13598: * gdb.python/py-events.exp: Add before_prompt event tests. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20959-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 14 18:04:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 116502 invoked by alias); 14 Feb 2017 18:04:27 -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 116474 invoked by uid 48); 14 Feb 2017 18:04:27 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug python/13598] need a pre-prompt event Date: Tue, 14 Feb 2017 18:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution target_milestone 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: 2017-q1/txt/msg00111.txt.bz2 Content-length: 650 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13598 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tromey at sourceware dot o= rg Resolution|--- |FIXED Target Milestone|--- |8.0 --- Comment #2 from Tom Tromey --- Fix checked in. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20960-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 14 22:31:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 120448 invoked by alias); 14 Feb 2017 22:31:40 -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 120033 invoked by uid 48); 14 Feb 2017 22:31:39 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug exp/21162] GDB internal error with unbounded array typecast expression Date: Tue, 14 Feb 2017 22:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc target_milestone 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: 2017-q1/txt/msg00112.txt.bz2 Content-length: 440 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21162 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org Target Milestone|--- |8.0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20961-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 03:27:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27293 invoked by alias); 15 Feb 2017 03:27:14 -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 27252 invoked by uid 48); 15 Feb 2017 03:27:13 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug exp/21162] GDB internal error with unbounded array typecast expression Date: Wed, 15 Feb 2017 03:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q1/txt/msg00113.txt.bz2 Content-length: 504 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21162 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brobecker at gnat dot com --- Comment #1 from Joel Brobecker --- Is this a regression compared to 7.12? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20962-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 03:29:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31195 invoked by alias); 15 Feb 2017 03:29:10 -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 31170 invoked by uid 48); 15 Feb 2017 03:29:09 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug build/18294] gdb compilation fails on 32-bit Solaris: largefile vs. procfs Date: Wed, 15 Feb 2017 03:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.9 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q1/txt/msg00114.txt.bz2 Content-length: 701 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18294 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brobecker at gnat dot com --- Comment #1 from Joel Brobecker --- Can you confirm whether GDB 7.12 does better? Given that this isn't a regression, I don't think this PR should be blocking for 8.0. In other words, a fix by 8.0 would be great, but we shouldn't block 8.0 because of that (known) issue. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20963-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 03:33:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35105 invoked by alias); 15 Feb 2017 03:33:24 -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 35066 invoked by uid 48); 15 Feb 2017 03:33:23 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/19426] in non-stop mode, gdb should sometimes select the stopping thread Date: Wed, 15 Feb 2017 03:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q1/txt/msg00115.txt.bz2 Content-length: 635 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19426 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brobecker at gnat dot com --- Comment #9 from Joel Brobecker --- Hello. Can you guys tell me whether this PR should be blocking for 8.0? I couldn't see in the PR description and comments any element that would indi= cate that. Thanks! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20964-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 03:36:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 67999 invoked by alias); 15 Feb 2017 03:36:32 -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 67965 invoked by uid 48); 15 Feb 2017 03:36:31 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/18164] New version of GDB causes qDebug() and related functions not to work in Qt Creator. Date: Wed, 15 Feb 2017 03:36: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: 7.9 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com 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: cc target_milestone 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: 2017-q1/txt/msg00116.txt.bz2 Content-length: 897 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18164 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brobecker at gnat dot com Target Milestone|8.0 |--- --- Comment #1 from Joel Brobecker --- Can you tell us whether the same problem occurs with GDB 7.12 as well? Also, can you confirm why you selected 8.0 as the "Target Milestone"? For u= s, this means this bug is blocking for the 8.0 release creation. But if this i= sn't a regression, then I believe this bug to not be blocking. I'll therefore re= move the target milestone now, but feel free to correct me on this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20965-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 03:37:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 70751 invoked by alias); 15 Feb 2017 03:37:54 -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 70702 invoked by uid 48); 15 Feb 2017 03:37:52 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug build/18294] gdb compilation fails on 32-bit Solaris: largefile vs. procfs Date: Wed, 15 Feb 2017 03:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.9 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com 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: target_milestone 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: 2017-q1/txt/msg00117.txt.bz2 Content-length: 375 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18294 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|8.0 |--- --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20966-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 08:51:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 42546 invoked by alias); 15 Feb 2017 08:51:36 -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 42515 invoked by uid 48); 15 Feb 2017 08:51:35 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug exp/21162] GDB internal error with unbounded array typecast expression Date: Wed, 15 Feb 2017 08:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00118.txt.bz2 Content-length: 873 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21162 --- Comment #2 from Yao Qi --- (In reply to Joel Brobecker from comment #1) > Is this a regression compared to 7.12? No, 7.12.1 and 7.11.1 fails too. (gdb) run Starting program: /home/qiyao/source/gdb-7.11/build-7.11.1/gdb/gdb=20 Breakpoint 1, main (argc=3D1, argv=3D0x7fffffffe648) at ../../gdb-7.11.1/gdb/gdb.c:25 25 { (gdb) p ((char*)(short[]){1})[1] Python Exception Installation error: gdb.execute_unwinders function is missing:=20 ../../gdb-7.11.1/gdb/gdbtypes.c:4575: internal-error: copy_type: Assertion `TYPE_OBJFILE_OWNED (type)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20967-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 11:11:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4408 invoked by alias); 15 Feb 2017 11:11:02 -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 3979 invoked by uid 48); 15 Feb 2017 11:11:01 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/19426] in non-stop mode, gdb should sometimes select the stopping thread Date: Wed, 15 Feb 2017 11:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: target_milestone 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: 2017-q1/txt/msg00119.txt.bz2 Content-length: 486 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19426 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|8.0 |--- --- Comment #10 from Pedro Alves --- I don't think it should. Removing the milestone. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20968-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 11:30:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 70041 invoked by alias); 15 Feb 2017 11:30:36 -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 65356 invoked by uid 48); 15 Feb 2017 11:30:30 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21164] New: "maint print symbols,msymbols,psymbols" without arguments all crash Date: Wed, 15 Feb 2017 11:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00120.txt.bz2 Content-length: 1308 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21164 Bug ID: 21164 Summary: "maint print symbols,msymbols,psymbols" without arguments all crash Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- Current master,=20 $ gdb GNU gdb (GDB) 7.12.50.20170214-git [....] (gdb) maint print msymbols=20 Segmentation fault (core dumped) Likewise for "maint print psymbols/symbols". Started happening with: commit 34c41c681f4a0a0dfe0405c7d2aecf458520557a Author: Doug Evans AuthorDate: Mon Dec 19 08:33:46 2016 -0800 New syntax for mt print symbols,msymbols,psymbols. Before that commit: GNU gdb (GDB) 7.12.50.20161222-git (gdb) maint print symbols=20 Arguments missing: an output file name and an optional symbol file name (gdb) maint print psymbols=20 print-psymbols takes an output file name and optional symbol file name (gdb) maint print msymbols=20 print-msymbols takes an output file name and optional symbol file name --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20969-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 11:31:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 71817 invoked by alias); 15 Feb 2017 11:31:43 -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 71795 invoked by uid 48); 15 Feb 2017 11:31:42 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21164] "maint print symbols,msymbols,psymbols" without arguments all crash Date: Wed, 15 Feb 2017 11:31: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone 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: 2017-q1/txt/msg00121.txt.bz2 Content-length: 371 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21164 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20971-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 12:10:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 9070 invoked by alias); 15 Feb 2017 12:10:29 -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 9047 invoked by uid 48); 15 Feb 2017 12:10:28 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21165] [8.0 Regression] FAIL: gdb.ada/info_locals_renaming.exp: info locals (GDB internal error) Date: Wed, 15 Feb 2017 12:10: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone 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: 2017-q1/txt/msg00123.txt.bz2 Content-length: 371 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21165 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20970-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 12:10:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 8791 invoked by alias); 15 Feb 2017 12:10:21 -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 8766 invoked by uid 48); 15 Feb 2017 12:10:21 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21165] New: [8.0 Regression] FAIL: gdb.ada/info_locals_renaming.exp: info locals (GDB internal error) Date: Wed, 15 Feb 2017 12:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00122.txt.bz2 Content-length: 2072 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21165 Bug ID: 21165 Summary: [8.0 Regression] FAIL: gdb.ada/info_locals_renaming.exp: info locals (GDB internal error) Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- Diffing current master (7.12.50.20170215-git) gdb.sum against a log from 20161209, I see this regression: -PASS: gdb.ada/info_locals_renaming.exp: compilation foo.adb=20 -FAIL: gdb.ada/info_locals_renaming.exp: info locals (GDB internal error)= =20 gdb.log shows: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (gdb) info locals gv =3D /home/pedro/gdb/mygit/src/gdb/value.c:372: internal-error: int value_bits_any_optimized_out(const value*, int, int): Assertion `!value->la= zy' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) FAIL: gdb.ada/info_locals_renaming.ex= p: info locals (GDB internal error) Resyncing due to internal error. n This is a bug, please report it. For instructions, see: . /home/pedro/gdb/mygit/src/gdb/value.c:372: internal-error: int value_bits_any_optimized_out(const value*, int, int): Assertion `!value->la= zy' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) n (gdb) testcase /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.ada/info_locals_renaming.exp completed in 1 seconds ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Bisecting points at: e8b24d9ff5b9419fc079f5fe975fac6f499f8bfb is the first bad commit commit e8b24d9ff5b9419fc079f5fe975fac6f499f8bfb Author: Yao Qi Date: Tue Nov 8 16:02:42 2016 +0000 Remove parameter valaddr from la_val_print --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20972-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 12:55:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 61100 invoked by alias); 15 Feb 2017 12:55:11 -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 61068 invoked by uid 48); 15 Feb 2017 12:55:11 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/18164] New version of GDB causes qDebug() and related functions not to work in Qt Creator. Date: Wed, 15 Feb 2017 12:55: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: 7.9 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: cc 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: 2017-q1/txt/msg00124.txt.bz2 Content-length: 565 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18164 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #2 from Pedro Alves --- I'd also be useful to expand on what does "not work" mean. From the availa= ble info alone, I have no idea. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20973-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 14:53:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 44363 invoked by alias); 15 Feb 2017 14:53:40 -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 44322 invoked by uid 48); 15 Feb 2017 14:53:39 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/18164] New version of GDB causes qDebug() and related functions not to work in Qt Creator. Date: Wed, 15 Feb 2017 14:53: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: 7.9 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com 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: cc 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: 2017-q1/txt/msg00125.txt.bz2 Content-length: 379 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18164 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- CC|brobecker at gnat dot com | --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20975-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 15:29:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107960 invoked by alias); 15 Feb 2017 15:29:58 -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 107885 invoked by uid 48); 15 Feb 2017 15:29:58 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21166] FAIL: gdb.reverse/insn-reverse.exp: rdseed: x/i $pc Date: Wed, 15 Feb 2017 15:29: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q1/txt/msg00127.txt.bz2 Content-length: 428 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21166 --- Comment #1 from Pedro Alves --- gdb.log shows: (gdb) si Program received signal SIGILL, Illegal instruction. rdseed () at /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.reverse/insn-reverse-x86.c:154 154 __asm__ volatile ("rdseed %%ax;" : "=3Dr" (seed)); --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20974-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 15:29:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 104988 invoked by alias); 15 Feb 2017 15:29:19 -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 104503 invoked by uid 48); 15 Feb 2017 15:29:18 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21166] New: FAIL: gdb.reverse/insn-reverse.exp: rdseed: x/i $pc Date: Wed, 15 Feb 2017 15:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00126.txt.bz2 Content-length: 2551 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21166 Bug ID: 21166 Summary: FAIL: gdb.reverse/insn-reverse.exp: rdseed: x/i $pc Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- On current master, on x86-64 Fedora 23, I'm seeing this: +FAIL: gdb.reverse/insn-reverse.exp: rdseed: x/i $pc=20 +FAIL: gdb.reverse/insn-reverse.exp: rdseed: x/i $pc=20 +FAIL: gdb.reverse/insn-reverse.exp: rdseed: x/i $pc=20 +FAIL: gdb.reverse/insn-reverse.exp: rdseed: x/i $pc=20 +FAIL: gdb.reverse/insn-reverse.exp: rdseed: x/i $pc=20 [... many more of the same ... ] +FAIL: gdb.reverse/insn-reverse.exp: rdseed: compare registers on insn 0:mo= v=20=20=20 0x2008b7(%rip),%eax # 0x601058 =20 +FAIL: gdb.reverse/insn-reverse.exp: rdseed: compare registers on insn 1:te= st=20=20 %eax,%eax=20 +FAIL: gdb.reverse/insn-reverse.exp: rdseed: compare registers on insn 2:je= =20=20=20=20 0x4008b3 =20 +FAIL: gdb.reverse/insn-reverse.exp: rdseed: compare registers on insn 3:rd= seed %ax=20 +FAIL: gdb.reverse/insn-reverse.exp: rdseed: compare registers on insn 4:rd= seed %ax=20 +ERROR: tcl error sourcing /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.reverse/insn-reverse.exp.=20 +ERROR: can't read "insn_array(5)": no such element in array=20 + while executing +"gdb_assert { [string compare $pre_regs($i) $post_regs($i)] =3D=3D 0 } "c= ompare registers on insn $i:$insn_array($i)"" + ("uplevel" body line 47) + invoked from within +"uplevel 1 $body" + invoked from within +"with_test_prefix "$func" { + gdb_breakpoint $func + gdb_test "continue" + set last_insn "" + set test "disassemble $func" + gdb_test_multiple $test $test ..." + (procedure "test" line 5) + invoked from within +"test $testcase" + (file "/home/pedro/gdb/mygit/src/gdb/testsuite/gdb.reverse/insn-reverse.exp" line 128) + invoked from within +"source /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.reverse/insn-reverse.e= xp" + ("uplevel" body line 1) + invoked from within +"uplevel #0 source /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.reverse/insn-reverse.exp" + invoked from within +"catch "uplevel #0 source $test_file_name"" src/gdb/testsuite/gdb.reverse/machinestate.exp ... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20976-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 15:30:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 110231 invoked by alias); 15 Feb 2017 15:30:48 -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 110137 invoked by uid 48); 15 Feb 2017 15:30:47 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21166] FAIL: gdb.reverse/insn-reverse.exp: rdseed: x/i $pc Date: Wed, 15 Feb 2017 15:30: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q1/txt/msg00128.txt.bz2 Content-length: 1409 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21166 --- Comment #2 from Pedro Alves --- $ cat /proc/cpuinfo=20 processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 60 model name : Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz stepping : 3 microcode : 0x20 cpu MHz : 3645.776 cache size : 6144 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca = cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx= est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts bugs : bogomips : 5586.97 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: [....] --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20977-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 15 19:19:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 40181 invoked by alias); 15 Feb 2017 19:19:15 -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 40147 invoked by uid 48); 15 Feb 2017 19:19:14 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21164] "maint print symbols,msymbols,psymbols" without arguments all crash Date: Wed, 15 Feb 2017 19:19: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to 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: 2017-q1/txt/msg00129.txt.bz2 Content-length: 584 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21164 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com Assignee|unassigned at sourceware dot org |sergiodj at redhat = dot com --- Comment #1 from Sergio Durigan Junior --- Working on this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20978-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 16 00:11:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 77110 invoked by alias); 16 Feb 2017 00:11:19 -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 77084 invoked by uid 48); 16 Feb 2017 00:11:19 -0000 From: "antoine.tremblay at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21169] New: GDBServer on ARM can crash the inferior while single stepping Date: Thu, 16 Feb 2017 00:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: antoine.tremblay at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00130.txt.bz2 Content-length: 1227 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21169 Bug ID: 21169 Summary: GDBServer on ARM can crash the inferior while single stepping Product: gdb Version: 8.0 Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: antoine.tremblay at ericsson dot com Target Milestone: --- Single stepping on ARM with GDBServer can crash the inferior. The inferior will cash with SIGILL or SIGSEGV. This is due to the single stepping breakpoint insertion not being atomic in certain situations like inserting a thumb2 breakpoint on a 2 byte aligned address. See this thread on the mailing list for more info: https://sourceware.org/ml/gdb-patches/2017-01/msg00650.html See also: https://sourceware.org/ml/gdb-patches/2016-11/msg00230.html This is a regression compared to previous GDB since before GDBServer did no= t do the single stepping itself. GDB controlled the single-stepping and thus all threads are stopped when modifying memory, this avoided this crash. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20979-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 16 00:16:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 84773 invoked by alias); 16 Feb 2017 00:16:24 -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 84751 invoked by uid 48); 16 Feb 2017 00:16:24 -0000 From: "antoine.tremblay at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21169] GDBServer on ARM can crash the inferior while single stepping Date: Thu, 16 Feb 2017 00:16: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: antoine.tremblay at ericsson dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: version target_milestone 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: 2017-q1/txt/msg00131.txt.bz2 Content-length: 442 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21169 Antoine Tremblay changed: What |Removed |Added ---------------------------------------------------------------------------- Version|8.0 |HEAD Target Milestone|--- |8.0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20980-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 16 00:56:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 21030 invoked by alias); 16 Feb 2017 00:56:02 -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 20994 invoked by uid 55); 16 Feb 2017 00:56:01 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21164] "maint print symbols,msymbols,psymbols" without arguments all crash Date: Thu, 16 Feb 2017 00:56: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00132.txt.bz2 Content-length: 1762 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21164 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D99e8a4f9f883= 2da0f37c6f35b11629b01897800d commit 99e8a4f9f8832da0f37c6f35b11629b01897800d Author: Sergio Durigan Junior Date: Wed Feb 15 15:08:19 2017 -0500 PR gdb/21164: maint print {symbols,msymbols,psymbols} without args crash This is a fix for PR gdb/21164. The problem started to happen after: commit 34c41c681f4a0a0dfe0405c7d2aecf458520557a Author: Doug Evans AuthorDate: Mon Dec 19 08:33:46 2016 -0800 New syntax for mt print symbols,msymbols,psymbols. This change introduced new syntax for the mentioned commands, and improved the parsing of arguments by using 'gdb_buildargv'. However, it is necessary to check if the argv being built is not NULL, which can happen if the user doesn't provide any arguments to these commands. gdb/ChangeLog: 2017-02-15 Sergio Durigan Junior PR gdb/21164 * psymtab.c (maintenance_print_psymbols): Verify if 'argv' is not NULL before using it. * symmisc.c (maintenance_print_symbols): Likewise. (maintenance_print_msymbols): Likewise. gdb/testsuite/ChangeLog: gdb/ChangeLog: 2017-02-15 Sergio Durigan Junior PR gdb/21164 * gdb.base/maint.exp: Add testcases for when the commands do not have arguments. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20981-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 16 00:56:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 28402 invoked by alias); 16 Feb 2017 00:56:42 -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 28304 invoked by uid 48); 16 Feb 2017 00:56:42 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21164] "maint print symbols,msymbols,psymbols" without arguments all crash Date: Thu, 16 Feb 2017 00:56: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00133.txt.bz2 Content-length: 526 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21164 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Sergio Durigan Junior --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20982-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 16 03:08:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79638 invoked by alias); 16 Feb 2017 03:08:39 -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 79608 invoked by uid 48); 16 Feb 2017 03:08:38 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug exp/21162] GDB internal error with unbounded array typecast expression Date: Thu, 16 Feb 2017 03:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com X-Bugzilla-Status: UNCONFIRMED 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: target_milestone 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: 2017-q1/txt/msg00134.txt.bz2 Content-length: 683 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21162 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|8.0 |--- --- Comment #3 from Joel Brobecker --- Thanks for confirming, Yao. So this PR should not be blocking for 8.0, and I will remove the target milestone. Of course, we still have plenty of time u= ntil branching and eventually release, so if it gets fixed by then, all the bett= er! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20983-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 16 09:08:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 93420 invoked by alias); 16 Feb 2017 09:08:51 -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 93395 invoked by uid 48); 16 Feb 2017 09:08:50 -0000 From: "info at muratkaya dot com.tr" To: gdb-prs@sourceware.org Subject: [Bug gdb/21170] New: Selected architecture arm is not compatible with reported target architecture i386:x86-64 Date: Thu, 16 Feb 2017 09:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: info at muratkaya dot com.tr X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00135.txt.bz2 Content-length: 2481 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21170 Bug ID: 21170 Summary: Selected architecture arm is not compatible with reported target architecture i386:x86-64 Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: info at muratkaya dot com.tr Target Milestone: --- ##### SOURCE CODE ########### root@mksecurity:~# cat arm.c #include void foo(const char *s) { printf("%s", s); } int main(void) { foo("Hello World"); return 0; } #### READELF INFORMATION ####### root@mksecurity:~# arm-linux-gnueabihf-readelf -h arm.bin ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00=20 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: DYN (Shared object file) Machine: ARM Version: 0x1 Entry point address: 0x495 Start of program headers: 52 (bytes into file) Start of section headers: 9556 (bytes into file) Flags: 0x5000400, Version5 EABI, hard-float A= BI Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 9 Size of section headers: 40 (bytes) Number of section headers: 36 Section header string table index: 35 ###### DEBUGGING ######### gdb-peda$ r Starting program: /root/arm.bin=20 warning: Selected architecture arm is not compatible with reported target architecture i386:x86-64 warning: Architecture rejected target-supplied description /build/gdb-A87voC/gdb-7.12/gdb/i387-tdep.c:919: internal-error: void i387_supply_xsave(regcache*, int, const void*): Assertion `tdep->st0_regnum= >=3D I386_ST0_REGNUM' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. This is a bug, please report it. For instructions, see: . Aborted (core dumped) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20984-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 16 18:00:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 116542 invoked by alias); 16 Feb 2017 18:00:41 -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 116488 invoked by uid 48); 16 Feb 2017 18:00:40 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug exp/21162] GDB internal error with unbounded array typecast expression Date: Thu, 16 Feb 2017 18:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00136.txt.bz2 Content-length: 422 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21162 --- Comment #4 from Andreas Arnez --- This problem was introduced in April 2014 with GIT commit 80180f796d366d230822c07a15aa68971abf9d77 -- "type: add c99 variable length array support" (https://sourceware.org/ml/gdb-patches/2014-04/msg00160.html= ). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20985-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 16 18:09:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 10430 invoked by alias); 16 Feb 2017 18:09:11 -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 10396 invoked by uid 48); 16 Feb 2017 18:09:11 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug exp/21162] GDB internal error with unbounded array typecast expression Date: Thu, 16 Feb 2017 18:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q1/txt/msg00137.txt.bz2 Content-length: 369 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21162 --- Comment #5 from Andreas Arnez --- Created attachment 9832 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9832&action=3Dedit Test case for internal error with unbounded array typecast --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20986-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 16 20:37:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 101106 invoked by alias); 16 Feb 2017 20:37:27 -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 101080 invoked by uid 48); 16 Feb 2017 20:37:27 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/16188] Verify PTRACE_TRACEME succeeded? Date: Thu, 16 Feb 2017 20:37: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: 2017-q1/txt/msg00138.txt.bz2 Content-length: 287 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16188 --- Comment #3 from Sergio Durigan Junior --- Proposed fix: https://sourceware.org/ml/gdb-patches/2017-02/msg00451.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20987-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 17 13:06:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 51960 invoked by alias); 17 Feb 2017 13:06:55 -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 51927 invoked by uid 48); 17 Feb 2017 13:06:55 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/7349] RFE: Can't refer to previous watchpoint value in condition Date: Fri, 17 Feb 2017 13:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q1/txt/msg00139.txt.bz2 Content-length: 616 https://sourceware.org/bugzilla/show_bug.cgi?id=3D7349 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --- Comment #1 from Tom Tromey --- Came up again here: http://stackoverflow.com/questions/42287337/programmatic-access-to-old-and-= new-values-of-a-watchpoint-in-gdb/42298779#42298779 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20988-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 17 14:48:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 5302 invoked by alias); 17 Feb 2017 14:48:47 -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 5160 invoked by uid 48); 17 Feb 2017 14:48:46 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21178] New: add xmethod support for rust Date: Fri, 17 Feb 2017 14:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00140.txt.bz2 Content-length: 846 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21178 Bug ID: 21178 Summary: add xmethod support for rust Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- Currently it's difficult to get an individual element from a Vec in Rust. Example program: fn main() { let x =3D vec!(1,2,3,4); println!("{}", x[2]); } (gdb) p x $1 =3D Vec(len: 4, cap: 4) =3D {1, 2, 3, 4} (gdb) p x[0] Cannot subscript non-array type Maybe xmethods or something similar could be added to the rust language code in gdb. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20989-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 19 22:44:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 120319 invoked by alias); 19 Feb 2017 22:44:01 -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 120281 invoked by uid 48); 19 Feb 2017 22:44:00 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21165] [8.0 Regression] FAIL: gdb.ada/info_locals_renaming.exp: info locals (GDB internal error) Date: Sun, 19 Feb 2017 22:44: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to 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: 2017-q1/txt/msg00141.txt.bz2 Content-length: 535 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21165 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org Assignee|unassigned at sourceware dot org |qiyao at gcc dot gn= u.org --- Comment #1 from Yao Qi --- Mine. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20990-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 20 03:29:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68284 invoked by alias); 20 Feb 2017 03:29:55 -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 68254 invoked by uid 48); 20 Feb 2017 03:29:54 -0000 From: "currygt52 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21184] New: Unexpected display for flag/struct type in target description Date: Mon, 20 Feb 2017 03:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: currygt52 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00142.txt.bz2 Content-length: 2152 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21184 Bug ID: 21184 Summary: Unexpected display for flag/struct type in target description Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: currygt52 at gmail dot com Target Milestone: --- Hi, I get unexpected display when using the new target description feature "multibit flag and enum bitfields". The issue can be reproduced by explicitly hacking x86 target description as follow: 1. Modifying gdb/features/i386/64bit-core.xml and adding two new types, and modifying r14/r15 type. 2. Regenerate gdb/features/i386/amd64-avx-linux.c rm i386/amd64-avx-linux.c make GDB=3D XMLTOC=3Di386/amd64-avx-linux.xml i386/amd64-avx-l= inux.c 3. Rebuild gdbserver 4. Launch gdbserver and connect it with gdb 5. Access r14/r15 (gdb) p/x $r14 $1 =3D 0x0 (gdb) p $r14 $2 =3D [ BIT1_2=3D0 ] (gdb) set (long)$r14=3D0x2 (gdb) p/x $r14 $3 =3D 0x2 (gdb) p $r14 $4 =3D [ BIT1_2=3D2 ] <=3D=3D=3D I expect [ BIT1_2=3D1 ] (gdb) set (long)$r14=3D0x4 (gdb) p/x $r14 $5 =3D 0x4 (gdb) p $r14 $6 =3D [ BIT1_2=3D0 ] <=3D=3D=3D I expect [ BIT1_2=3D2 ] (gdb) p/x $r15 $7 =3D {BIT0 =3D 0x0, BIT1 =3D 0x0} (gdb) set (long)$r15=3D0x1 (gdb) p/x $r15 $8 =3D {BIT0 =3D 0xff, BIT1 =3D 0x0} <=3D=3D=3D I expect {BIT0 =3D 0x1, BI= T1 =3D 0x0} (gdb) p $r15 $9 =3D {BIT0 =3D -1, BIT1 =3D false} <=3D=3D=3D I expect {BIT0 =3D true, B= IT1 =3D false} Please help to check this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20991-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 20 04:27:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 55288 invoked by alias); 20 Feb 2017 04:27:38 -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 55256 invoked by uid 48); 20 Feb 2017 04:27:37 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21185] New: add i128 and u128 support to rust Date: Mon, 20 Feb 2017 04:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00143.txt.bz2 Content-length: 702 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 Bug ID: 21185 Summary: add i128 and u128 support to rust Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- Rust nightly has support for i128 and u128 types. gdb should add support for these at some point; certainly after the feature is ungated, but maybe before. See https://github.com/rust-lang/rust/issues/35118 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20992-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 20 11:07:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 7159 invoked by alias); 20 Feb 2017 11:07:11 -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 7113 invoked by uid 48); 20 Feb 2017 11:07:08 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] New: Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Mon, 20 Feb 2017 11:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q1/txt/msg00144.txt.bz2 Content-length: 1956 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 Bug ID: 21187 Summary: Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: mishra.nitish.88 at gmail dot com Target Milestone: --- Created attachment 9841 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9841&action=3Dedit Issue with gdb built and linked statically with gcc-6.2 I tried building GDB, version=3D 7.12.50.20170106, with gcc-6.1 and 6.2 on = AIX 7.2 platform. The static linking of GDB with libstdc++ and libgcc library l= eads to an issue of broken exception handling. Specifically, running invalid commands leads to core dump. Test_result: # ./gdb GNU gdb (GDB) 7.12.50.20170106-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "powerpc64-ibm-aix7.2.0.0". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) kill terminate called after throwing an instance of 'gdb_exception_RETURN_MASK_ERROR' IOT/Abort trap (core dumped) The test result and backtrace output is attached with the bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20993-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 20 11:42:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 105702 invoked by alias); 20 Feb 2017 11:42:53 -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 105578 invoked by uid 48); 20 Feb 2017 11:42:52 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Mon, 20 Feb 2017 11:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00145.txt.bz2 Content-length: 577 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 --- Comment #1 from Nitish K Mishra --- I am proposing a patch in which I have implemented option "--disable-static= lib" which will link GDB to libstdC++ and libgcc library dynamically, and will a= llow AIX user to build and run GDB. By default the linking will be static only, because it is working on other platforms.=20 The patch is attached with the bug and is tested on AIX-7.2 and Ubuntu-16.0= 4. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20994-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 20 11:52:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 318 invoked by alias); 20 Feb 2017 11:52:31 -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 131063 invoked by uid 48); 20 Feb 2017 11:52:30 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Mon, 20 Feb 2017 11:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc attachments.created 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: 2017-q1/txt/msg00146.txt.bz2 Content-length: 667 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 Nitish K Mishra changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mishra.nitish.88 at gmail = dot com --- Comment #2 from Nitish K Mishra --- Created attachment 9842 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9842&action=3Dedit Configure otion to disable static linking of libstdc++ and libgcc to GDB --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20995-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 20 12:50:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 42596 invoked by alias); 20 Feb 2017 12:50:35 -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 42570 invoked by uid 48); 20 Feb 2017 12:50:34 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/16188] Verify PTRACE_TRACEME succeeded? Date: Mon, 20 Feb 2017 12:50: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00147.txt.bz2 Content-length: 526 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16188 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Sergio Durigan Junior --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20996-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 20 12:50:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 42816 invoked by alias); 20 Feb 2017 12:50:36 -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 42740 invoked by uid 55); 20 Feb 2017 12:50:36 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/16188] Verify PTRACE_TRACEME succeeded? Date: Mon, 20 Feb 2017 12:50: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: 2017-q1/txt/msg00148.txt.bz2 Content-length: 2371 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16188 --- Comment #5 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D0db8980cc0ee= 05727c11f8b7c6674137a4d5de4e commit 0db8980cc0ee05727c11f8b7c6674137a4d5de4e Author: Sergio Durigan Junior Date: Tue Feb 14 18:27:23 2017 -0500 PR gdb/16188: Verify PTRACE_TRACEME succeeded This patch fixes PR gdb/16188, which is about the fact that fork_inferior doesn't verify the return value of the "traceme_fun" callback. On most targets, this callback is actually a wrapper to a ptrace call that does a PTRACE_TRACEME on the forked GDB process that will eventually become the inferior. Thanks to Pedro, this second version of the patch is simpler and more more logical. Basically, two helper functions are added: trace_start_error and trace_start_error_with_name. The former can be used when there is a customized error message to be printed to the user. The latter works like perror_with_name, so you just need to pass the function that error'd. Both helper functions mentioned above do basically the same thing: print the error message to stderr and call _exit, properly terminating the forked inferior. Most of the patch takes care of guarding the necessary system calls against errors on the "traceme_fun" callbacks. It is not right to call error on these situations, so I've replaced these calls with the proper helper function call. Regression-tested on BuildBot. Thanks, gdb/ChangeLog: 2017-02-20 Sergio Durigan Junior Pedro Alves PR gdb/16188 * darwin-nat.c (darwin_ptrace_me): Check if calls to system calls succeeded. * fork-child.c (trace_start_error): New function. (trace_start_error_with_name): Likewise. * gnu-nat.c (gnu_ptrace_me): Check if call to PTRACE succeeded. * inf-ptrace.c (inf_ptrace_me): Likewise. * inferior.h (trace_start_error): New prototype. (trace_start_error_with_name): Likewise. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20997-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 20 13:04:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 90508 invoked by alias); 20 Feb 2017 13:04:25 -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 90437 invoked by uid 55); 20 Feb 2017 13:04:25 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/16188] Verify PTRACE_TRACEME succeeded? Date: Mon, 20 Feb 2017 13:04: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: 2017-q1/txt/msg00149.txt.bz2 Content-length: 930 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16188 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D1b076f2540e5= 1055a7c6a4ee8fdfc604b54fb70a commit 1b076f2540e51055a7c6a4ee8fdfc604b54fb70a Author: Sergio Durigan Junior Date: Mon Feb 20 08:01:04 2017 -0500 Fix thinko on last commit On fork-child.c:trace_start_error, va_end should refer to 'ap', not 'args. This fixes it. Sorry about the breakage. gdb/ChangeLog: 2017-02-20 Sergio Durigan Junior PR gdb/16188 * fork-child.c (trace_start_error): Fix thinko. va_end should refer to 'ap', not 'args'. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20998-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 20 22:13:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 130580 invoked by alias); 20 Feb 2017 22:13:56 -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 130552 invoked by uid 48); 20 Feb 2017 22:13:56 -0000 From: "gareth at blacksphere dot co.nz" To: gdb-prs@sourceware.org Subject: [Bug remote/21188] New: Remote timeouts don't work correctly Date: Mon, 20 Feb 2017 22:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gareth at blacksphere dot co.nz X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00150.txt.bz2 Content-length: 932 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21188 Bug ID: 21188 Summary: Remote timeouts don't work correctly Product: gdb Version: 7.12 Status: UNCONFIRMED Severity: normal Priority: P2 Component: remote Assignee: unassigned at sourceware dot org Reporter: gareth at blacksphere dot co.nz Target Milestone: --- The timeout mechanism in ser-unix.c was changed in commit 048094acc. In do_hardwire_readchar(), the required timeout is broken into 1 second intervals and wait_for() is called. Before, wait_for() set VTIME and VMIN = so the read would block, but now it uses select() to block for the specified timeout. If wait_for() returns SERIAL_TIMEOUT, do_hardwire_readchar() retu= rns immediately, so the timeout is always only 1s. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-20999-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 20 22:23:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 106911 invoked by alias); 20 Feb 2017 22:23:43 -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 106869 invoked by uid 48); 20 Feb 2017 22:23:42 -0000 From: "gareth at blacksphere dot co.nz" To: gdb-prs@sourceware.org Subject: [Bug remote/21188] Remote timeouts don't work correctly Date: Mon, 20 Feb 2017 22:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gareth at blacksphere dot co.nz X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q1/txt/msg00151.txt.bz2 Content-length: 336 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21188 --- Comment #1 from Gareth McMullin --- Created attachment 9845 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9845&action=3Dedit Patch for suggested fix --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21000-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 21 07:57:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 100088 invoked by alias); 21 Feb 2017 07:57:40 -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 100056 invoked by uid 48); 21 Feb 2017 07:57:39 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Tue, 21 Feb 2017 07:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.isobsolete attachments.created 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: 2017-q1/txt/msg00152.txt.bz2 Content-length: 808 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 Nitish K Mishra changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #9842|0 |1 is obsolete| | --- Comment #3 from Nitish K Mishra --- Created attachment 9846 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9846&action=3Dedit Updated proposed patch file for this bug The patch file which I sent earlier has some issue while patching. I sent it mistakenly. Attaching the updated patch file now. Thanks and Regards, Nitish --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21001-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 21 22:19:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 499 invoked by alias); 21 Feb 2017 22:19:49 -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 472 invoked by uid 48); 21 Feb 2017 22:19:48 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug exp/20991] __int128 type support Date: Tue, 21 Feb 2017 22:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q1/txt/msg00153.txt.bz2 Content-length: 341 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20991 --- Comment #1 from Tom Tromey --- One super intrusive option would be to use GMP everywhere. Another possibility would be to redefine LONGEST as __int128 where available. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21002-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 22 03:47:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 87515 invoked by alias); 22 Feb 2017 03:47:57 -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 87491 invoked by uid 48); 22 Feb 2017 03:47:56 -0000 From: "ubergotenks at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21192] New: Incorrect/Undefined behavior when watching member variables in multi threaded environments Date: Wed, 22 Feb 2017 03:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ubergotenks at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00154.txt.bz2 Content-length: 2413 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21192 Bug ID: 21192 Summary: Incorrect/Undefined behavior when watching member variables in multi threaded environments Product: gdb Version: 7.11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: ubergotenks at gmail dot com Target Milestone: --- When attempting to watch a member variable so that it breaks when written t= o, normally i would use 'watch '. This works in single threaded code = and for local variables, but in multithreaded code, it will cause undefined behavior, even if the variable is only ever changed in the main thread. Usi= ng 'watch this.' instead solves this issue. Here is a simple test program using QT that demonstrates this behavior: //main.cpp int main(int argc, char* argv[]) { QApplication applicationInstance(argc, argv); testGDBCrash crasher; if (crasher.exec() !=3D QDialog::Accepted) return 0; return applicationInstance.exec(); } //testGDBCrash.h #ifndef TESTGDBCRASH_H #define TESTGDBCRASH_H #include #include class testGDBCrash : public QDialog { Q_OBJECT public:=20 testGDBCrash(QWidget * parent=3D0); Q_SLOT void TestCrash(); bool m_foo;=20 }; #endif // TESTGDBCRASH_H //testGDBCrash.cpp #include "testGDBCrash.h" #include #include testGDBCrash::testGDBCrash(QWidget* parent):QDialog(parent) { resize(200,100); QHBoxLayout * layout=3Dnew QHBoxLayout(this); QPushButton * pb=3Dnew QPushButton("crash",this); layout->addWidget(pb); setLayout(layout); show(); m_foo=3Dfalse; connect(pb,SIGNAL(clicked()),this,SLOT(TestCrash())); } void testGDBCrash::TestCrash() { if(m_foo) return; m_foo=3Dfalse; m_foo=3Dtrue; m_foo=3Dfalse; } Steps to crash: 1. Run 2. put a breakpoint on line 18 of testGDBCrash.cpp (the if statement) 3. hit the 'crash' button 4. watch m_foo 5. Continue GDB will either do strange stuff like tell you 'this' isnt defined, or it w= ill just not ever break. Note, changing step 4 to 'watch this.m_foo' will resol= ve the behavior and work as intended. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21003-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 22 09:51:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 69593 invoked by alias); 22 Feb 2017 09:51:35 -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 69569 invoked by uid 48); 22 Feb 2017 09:51:34 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Wed, 22 Feb 2017 09:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: version 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: 2017-q1/txt/msg00155.txt.bz2 Content-length: 384 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 Nitish K Mishra changed: What |Removed |Added ---------------------------------------------------------------------------- Version|7.12.1 |8.0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21004-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 22 09:52:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89370 invoked by alias); 22 Feb 2017 09:52:44 -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 87311 invoked by uid 48); 22 Feb 2017 09:52:43 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Wed, 22 Feb 2017 09:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: version 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: 2017-q1/txt/msg00156.txt.bz2 Content-length: 385 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 Nitish K Mishra changed: What |Removed |Added ---------------------------------------------------------------------------- Version|8.0 |7.12 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21005-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 22 11:22:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 70406 invoked by alias); 22 Feb 2017 11:22:19 -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 70377 invoked by uid 48); 22 Feb 2017 11:22:19 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Wed, 22 Feb 2017 11:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc target_milestone 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: 2017-q1/txt/msg00157.txt.bz2 Content-length: 440 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org Target Milestone|--- |8.0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21006-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 22 15:33:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 34512 invoked by alias); 22 Feb 2017 15:33:36 -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 34481 invoked by uid 48); 22 Feb 2017 15:33:35 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21194] New: ERROR: AddressSanitizer: heap-buffer-overflow on address Date: Wed, 22 Feb 2017 15:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00158.txt.bz2 Content-length: 4068 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21194 Bug ID: 21194 Summary: ERROR: AddressSanitizer: heap-buffer-overflow on address Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: qiyao at gcc dot gnu.org Target Milestone: --- I build GDB with CXXFLAGS=3D'-O0 -g3 -fsanitize=3Daddress' and run test inherit.exp, $ make check RUNTESTFLAGS=3D'inherit.exp' ^[[1m^[[31m=3D=3D507=3D=3DERROR: AddressSanitizer: heap-buffer-overflow on = address 0x60600015d438 at pc 0x7f2b4d918935 bp 0x7ffdfbf88ef0 sp 0x7ffdfbf88698^M ^[[1m^[[0m^[[1m^[[34mREAD of size 24 at 0x60600015d438 thread T0^[[1m^[[0m^M #0 0x7f2b4d918934 in __asan_memcpy (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x8c934)^M #1 0xba6ebe in value_contents_copy_raw(value*, long, value*, long, long) ../../binutils-gdb/gdb/value.c:1361^M #2 0xba6fb1 in value_contents_copy(value*, long, value*, long, long) ../../binutils-gdb/gdb/value.c:1390^M #3 0xbb0abe in value_from_component(value*, type*, long) ../../binutils-gdb/gdb/value.c:3802^M #4 0x5e7934 in gdbpy_apply_val_pretty_printer(extension_language_defn const*, type*, long, unsigned long, ui_file*, int, value*, value_print_opti= ons const*, language_defn const*) ../../binutils-gdb/gdb/python/py-prettyprint.c:729^M #5 0x8e8742 in apply_ext_lang_val_pretty_printer(type*, long, unsigned long, ui_file*, int, value*, value_print_options const*, language_defn cons= t*) ../../binutils-gdb/gdb/extension.c:518^M #6 0x7f0c14 in cp_print_value ../../binutils-gdb/gdb/cp-valprint.c:595^M #7 0x7edb50 in cp_print_value_fields(type*, type*, long, unsigned long, ui_file*, int, value*, value_print_options const*, type**, int) ../../binutils-gdb/gdb/cp-valprint.c:200^M #8 0x7ef9a9 in cp_print_value_fields_rtti(type*, unsigned char const*, long, unsigned long, ui_file*, int, value*, value_print_options const*, typ= e**, int) ../../binutils-gdb/gdb/cp-valprint.c:456^M #9 0x7b23e8 in c_val_print_struct ../../binutils-gdb/gdb/c-valprint.c:4= 12^M #10 0x7b2bee in c_val_print(type*, int, unsigned long, ui_file*, int, value*, value_print_options const*) ../../binutils-gdb/gdb/c-valprint.c:530= ^M #11 0xb98e97 in val_print(type*, long, unsigned long, ui_file*, int, value*, value_print_options const*, language_defn const*) ../../binutils-gdb/gdb/valprint.c:1120^M #12 0x7b38a2 in c_value_print(value*, ui_file*, value_print_options con= st*) ../../binutils-gdb/gdb/c-valprint.c:698^M #13 0xb99517 in value_print(value*, ui_file*, value_print_options const= *) ../../binutils-gdb/gdb/valprint.c:1233^M #14 0xa42be8 in print_formatted ../../binutils-gdb/gdb/printcmd.c:321^M #15 0xa46ac9 in print_value(value*, format_data const*) ../../binutils-gdb/gdb/printcmd.c:1233^M #16 0xa46d82 in print_command_1 ../../binutils-gdb/gdb/printcmd.c:1261 ................. ^[[1m^[[32m0x60600015d438 is located 0 bytes to the right of 56-byte region [0x60600015d400,0x60600015d438)^M ^[[1m^[[0m^[[1m^[[35mallocated by thread T0 here:^[[1m^[[0m^M #0 0x7f2b4d92479a in __interceptor_calloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x9879a)^M #1 0x7d1672 in xcalloc ../../binutils-gdb/gdb/common/common-utils.c:83^M #2 0x7d16be in xzalloc(unsigned long) ../../binutils-gdb/gdb/common/common-utils.c:93^M #3 0xba5b6a in allocate_value_contents ../../binutils-gdb/gdb/value.c:1039^M #4 0xbb1367 in value_fetch_lazy(value*) ../../binutils-gdb/gdb/value.c:3955^M #5 0xba951d in record_latest_value(value*) ../../binutils-gdb/gdb/value.c:1904^M #6 0xa4695c in print_value(value*, format_data const*) ../../binutils-gdb/gdb/printcmd.c:1222^M #7 0xa46d82 in print_command_1 ../../binutils-gdb/gdb/printcmd.c:1261^M #8 0xa46e3e in print_command ../../binutils-gdb/gdb/printcmd.c:1267^M --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21007-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 22 16:23:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23965 invoked by alias); 22 Feb 2017 16:23:31 -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 23937 invoked by uid 48); 22 Feb 2017 16:23:30 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21194] ERROR: AddressSanitizer: heap-buffer-overflow on address Date: Wed, 22 Feb 2017 16:23: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: 2017-q1/txt/msg00159.txt.bz2 Content-length: 1566 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21194 --- Comment #1 from Yao Qi --- If I add asserts in value_contents_copy_raw, it is triggered too, diff --git a/gdb/value.c b/gdb/value.c index 557c300..ae5ec78 100644 --- a/gdb/value.c +++ b/gdb/value.c @@ -1356,6 +1356,10 @@ value_contents_copy_raw (struct value *dst, LONGEST dst_offset, TARGET_CHAR_BIT * length)); /* Copy the data. */ + gdb_assert (length * unit_size + dst_offset * unit_size + <=3D TYPE_LENGTH (dst->enclosing_type)); + gdb_assert (length * unit_size + src_offset * unit_size + <=3D TYPE_LENGTH (src->enclosing_type)); memcpy (value_contents_all_raw (dst) + dst_offset * unit_size, value_contents_all_raw (src) + src_offset * unit_size, length * unit_size); ---------------------------------------------- print g_vD^M $91 =3D { =3D { =3D {va =3D 19, vx =3D 20}, _vptr.vB =3D 0x401300 <= vtable for vD+64>, vb =3D 21, vx =3D 22}, =3D /home/yao/SourceCode/gnu/gdb/git/gdb/value.c:1362: internal-error: void value_contents_copy_raw(value*, LONGEST, value*, LONGEST, LONGEST): Asserti= on `length * unit_size + src_offset * unit_size <=3D TYPE_LENGTH (src->enclosing_type)' failed.^M A problem internal to GDB has been detected,^M further debugging may prove unreliable.^M Quit this debugging session? (y or n) FAIL: gdb.cp/inherit.exp: print g_vD = (GDB internal error) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21008-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 22 16:27:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31904 invoked by alias); 22 Feb 2017 16:27:55 -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 31876 invoked by uid 48); 22 Feb 2017 16:27:54 -0000 From: "spencerbaugh at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug record/21195] New: Record immediately crashes with multiple inferiors Date: Wed, 22 Feb 2017 16:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: spencerbaugh at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00160.txt.bz2 Content-length: 3611 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21195 Bug ID: 21195 Summary: Record immediately crashes with multiple inferiors Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: record Assignee: unassigned at sourceware dot org Reporter: spencerbaugh at gmail dot com Target Milestone: --- While recording a program, if you add another inferior, GDB will crash: Current directory is /home/sbaugh/ GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: . (gdb) file hello Reading symbols from /home/sbaugh/hello...(no debugging symbols found)...do= ne. (gdb) start Temporary breakpoint 1 at 0x4007ba Starting program: /home/sbaugh/hello=20 warning: no loadable sections found in added symbol-file system-supplied DS= O at 0x7ffff7ffa000 Temporary breakpoint 1, 0x00000000004007ba in main () (gdb) record (gdb) add-inferior -exec hello Added inferior 2 Reading symbols from /home/sbaugh/hello...(no debugging symbols found)...do= ne. (gdb) infe 2 [Switching to inferior 2 [process 0] (/home/sbaugh/hello)] (gdb) start Temporary breakpoint 2 at 0x4007ba (2 locations) Starting program: /home/sbaugh/hello=20 /tmp/buildd/gdb-7.4.1+dfsg/gdb/record.c:1176: internal-error: record_wait_1: Assertion `(options & TARGET_WNOHANG) !=3D 0' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n)=20 I've confirmed this on HEAD as well. (I presume this bug is present in all versions of gdb with record) Snippet of backtrace: #3 0x000000000065a8c9 in internal_vproblem(internal_problem *, const char = *, int, const char *, typedef __va_list_tag __va_list_tag *) (problem=3Dproblem@entry=3D0xc3b740 , file=3D, line=3D, fmt=3D, ap=3Dap@entry=3D0x7ffcd0fbf1= c8) at utils.c:772 #4 0x000000000065aa39 in internal_verror (file=3D, line=3D, fmt=3D, ap=3Dap@entry=3D0x7ffcd0fbf1= c8) at utils.c:798 #5 0x0000000000695822 in internal_error (file=3Dfile@entry=3D0x861739 "record-full.c", line=3Dline@entry=3D1066, fmt=3D) at ./common/errors.c:55 #6 0x0000000000683a3b in record_full_wait_1 (options=3D, status=3D0x7ffcd0fbf4a0, ptid=3D..., ops=3D0xc64620 ) at record-full.c:1066 #7 record_full_wait (ops=3D0xc64620 , ptid=3D..., status=3D0x7ffcd0fbf4a0, options=3D) at record-full.c:1346 #8 0x00000000005aa20e in delegate_wait (self=3D, arg1=3D..., arg2=3D, arg3=3D) at target-delegates.c:116 #9 0x00000000005b9815 in target_wait (ptid=3D..., status=3Dstatus@entry=3D0x7ffcd0fbf4a0, options=3Doptions@entry=3D0) at tar= get.c:2289 #10 0x000000000044feca in startup_inferior (ntraps=3Dntraps@entry=3D1) at fork-child.c:465 The culprit seems to be that startup_inferior passes options=3D0 to wait, w= hile record_full_wait_1 asserts (options & TARGET_WNOHANG) !=3D 0. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21009-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 22 16:28:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 32497 invoked by alias); 22 Feb 2017 16:28:30 -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 32470 invoked by uid 48); 22 Feb 2017 16:28:30 -0000 From: "spencerbaugh at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug record/21195] Record immediately crashes with multiple inferiors Date: Wed, 22 Feb 2017 16:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: spencerbaugh at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: version 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: 2017-q1/txt/msg00161.txt.bz2 Content-length: 381 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21195 Spencer Baugh changed: What |Removed |Added ---------------------------------------------------------------------------- Version|HEAD |7.12.1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21010-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 22 19:45:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107249 invoked by alias); 22 Feb 2017 19:45:36 -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 107176 invoked by uid 48); 22 Feb 2017 19:45:29 -0000 From: "aetf at unlimitedcodeworks dot xyz" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21192] Incorrect/Undefined behavior when watching member variables in multi threaded environments Date: Wed, 22 Feb 2017 19:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: aetf at unlimitedcodeworks dot xyz X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00162.txt.bz2 Content-length: 691 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21192 Aetf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aetf at unlimitedcodeworks= dot xyz --- Comment #1 from Aetf --- This also affects the machine interface used by KDevelop which get confused when GDB outputs two responses for a single command. Detailed description can be found at https://bugs.kde.org/show_bug.cgi?id=3D376595#c15 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21011-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 23 10:41:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20389 invoked by alias); 23 Feb 2017 10:41:18 -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 420 invoked by uid 48); 23 Feb 2017 10:41:09 -0000 From: "massimo.b at gmx dot net" To: gdb-prs@sourceware.org Subject: [Bug remote/18772] gdb does not respond to CTRL-C Date: Thu, 23 Feb 2017 10:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 7.9 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: massimo.b at gmx dot net 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: cc 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: 2017-q1/txt/msg00163.txt.bz2 Content-length: 1310 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18772 Massimo B. changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |massimo.b at gmx dot net --- Comment #1 from Massimo B. --- This is 7.12.1 server and client. Having no breakpoints it is not possible to pause execution by CTRL+c at al= l, as it is done using the native gdb: server $ gdbserver --multi --attach localhost:8888 $(pgrep -f my_app) client $ gdb target extended-remote localhost:8888 Remote debugging using localhost:8888 Reading /lib64/libdl.so.2 from remote target... Reading /lib64/libSegFault.so from remote target... ... Reading /lib64/ld-linux-x86-64.so.2 from remote target... 0x00007f6b26857923 in __select_nocancel () from target:/lib64/libc.so.6 (gdb) where #0 0x00007f6b26857923 in __select_nocancel () from target:/lib64/libc.so.6 ... #9 0x00000000004497ee in main (argc=3D14, argv=3D0x7ffe8e4b0af8) at main.c= pp:245 (gdb) c Continuing. ^C^CThe target is not responding to interrupt requests. Stop debugging it? (y or n) y Disconnected from target. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21012-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 23 17:05:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 18312 invoked by alias); 23 Feb 2017 17:05:58 -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 16117 invoked by uid 48); 23 Feb 2017 17:05:55 -0000 From: "jose.marchesi at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21196] New: Build is broken with Python < 2.7 Date: Thu, 23 Feb 2017 17:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: jose.marchesi at oracle dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00164.txt.bz2 Content-length: 2092 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21196 Bug ID: 21196 Summary: Build is broken with Python < 2.7 Product: gdb Version: HEAD Status: UNCONFIRMED Severity: critical Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: jose.marchesi at oracle dot com Target Milestone: --- The build is currently broken with Python 2.6: g++ -g -O2 -I. -I../../gdb -I../../gdb/common -I../../gdb/config -DLOCALEDIR=3D"\"/usr/local/share/locale\"" -DHAVE_CONFIG_H -I../../gdb/../include/opcode -I../../gdb/../opcodes/.. -I../../gdb/../readline/.. -I../.. gdb/../zlib -I../bfd -I../../gdb/../bfd -I../../gdb/../include -I../libdecnumber -I../../gdb/../libdecnumber=20 -I../../gdb/gnulib/import -Ibuild-gnulib/import -DTUI=3D1=20 -I/usr/include/python2.6 -I/usr/include/python2.6 -Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscrip= ts -Wempty-body -Wunused-but-set-parameter -Wunused-but-set-variable -Wno-sign-compare -Wno-write-strings -Wno-narrowing -Wformat-nonliteral -We= rror -c -o py-record-btrace.o -MT py-record-btrace.o -MMD -MP -MF .deps/py-record-btrace.Tpo -fno-strict-aliasing -DNDEBUG -fwrapv ../../gdb/python/py-record-btrace.c ../../gdb/python/py-record-btrace.c: In function PyObject* btpy_insn_data(PyObject*, void*): ../../gdb/python/py-record-btrace.c:333:10: error: =C3=A2=E2=82=AC=CB=9CPyMemoryView_FromObject=C3=A2=E2=82=AC=E2=84=A2 was no= t declared in this scope return PyMemoryView_FromObject (object); ^~~~~~~~~~~~~~~~~~~~~~~ ../../gdb/python/py-record-btrace.c:333:10: note: suggested alternative: =C3=A2=E2=82=AC=CB=9CPyBuffer_FromObject=C3=A2=E2=82=AC=E2=84=A2 return PyMemoryView_FromObject (object); ^~~~~~~~~~~~~~~~~~~~~~~ PyBuffer_FromObject make: *** [py-record-btrace.o] Error 1 Looks like the Memory View object was introduced in Python 2.7. Salud! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21013-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 23 17:21:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 48019 invoked by alias); 23 Feb 2017 17:21:58 -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 47984 invoked by uid 48); 23 Feb 2017 17:21:57 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21166] FAIL: gdb.reverse/insn-reverse.exp: rdseed: x/i $pc Date: Thu, 23 Feb 2017 17:21: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lgustavo at codesourcery dot com 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: cc 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: 2017-q1/txt/msg00165.txt.bz2 Content-length: 601 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21166 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lgustavo at codesourcery d= ot com --- Comment #3 from Luis Machado --- Odd. So this is getting past the feature test even though it doesn't support rdseed. Is rdrand supported just fine? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21014-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 23 17:25:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53137 invoked by alias); 23 Feb 2017 17:25:20 -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 53082 invoked by uid 48); 23 Feb 2017 17:25:18 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21166] FAIL: gdb.reverse/insn-reverse.exp: rdseed: x/i $pc Date: Thu, 23 Feb 2017 17:25: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lgustavo at codesourcery dot com 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: 2017-q1/txt/msg00166.txt.bz2 Content-length: 1675 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21166 --- Comment #4 from Luis Machado --- Ah, that particular processor doesn't support rdseed, that's why. Mine does: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 78 model name : Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz stepping : 3 microcode : 0x74 cpu MHz : 1094.843 cache size : 4096 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 22 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca = cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx= est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsa= vec xgetbv1 dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp bugs : bogomips : 5615.80 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: I guess i'll need a different mechanism to test rdrand and rdseed support separately. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21015-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 23 19:31:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 65592 invoked by alias); 23 Feb 2017 19:31:12 -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 65564 invoked by uid 48); 23 Feb 2017 19:31:11 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21166] FAIL: gdb.reverse/insn-reverse.exp: rdseed: x/i $pc Date: Thu, 23 Feb 2017 19:31: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lgustavo at codesourcery dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: lgustavo at codesourcery dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to 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: 2017-q1/txt/msg00167.txt.bz2 Content-length: 588 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21166 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at sourceware dot org |lgustavo at codesou= rcery dot com --- Comment #5 from Luis Machado --- Proposed fix sent to the mailing list. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21016-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 23 20:46:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89817 invoked by alias); 23 Feb 2017 20:46:29 -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 89793 invoked by uid 48); 23 Feb 2017 20:46:28 -0000 From: "lgustavo at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21166] FAIL: gdb.reverse/insn-reverse.exp: rdseed: x/i $pc Date: Thu, 23 Feb 2017 20:46: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lgustavo at codesourcery dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: lgustavo at codesourcery dot com 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00168.txt.bz2 Content-length: 568 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21166 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Luis Machado --- Fix pushed as c26db3b33b7274946e42c6656ee1c0911cefb865 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21017-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 23 22:17:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 18265 invoked by alias); 23 Feb 2017 22:17: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 18225 invoked by uid 48); 23 Feb 2017 22:17:52 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20757] gdb: DWARF-5 support Date: Thu, 23 Feb 2017 22:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: dep_changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan.kratochvil at redhat dot com 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00169.txt.bz2 Content-length: 536 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20757 Bug 20757 depends on bug 20755, which changed state. Bug 20755 Summary: readelf: DWARF-5 support https://sourceware.org/bugzilla/show_bug.cgi?id=3D20755 What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21018-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 23 22:20:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 26264 invoked by alias); 23 Feb 2017 22:20:05 -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 26237 invoked by uid 48); 23 Feb 2017 22:20:05 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20757] gdb: DWARF-5 support Date: Thu, 23 Feb 2017 22:20: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan.kratochvil at redhat dot com 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00170.txt.bz2 Content-length: 764 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20757 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Jan Kratochvil --- Now checked-in (except DWO and .debug_names) as a patch series, primarily: commit 43988095a5a4c53e6d5b00a6335454919c4fac55 Author: Jan Kratochvil Date: Mon Feb 20 20:53:21 2017 +0100 DWARF-5 basic functionality --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21019-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 23 23:51:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 55884 invoked by alias); 23 Feb 2017 23:50:59 -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 55854 invoked by uid 48); 23 Feb 2017 23:50:59 -0000 From: "mephi42 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20981] Dynamic library debugging on MacOS X 10.12 (Sierra) and dyld 15 is broken Date: Thu, 23 Feb 2017 23:50: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mephi42 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00171.txt.bz2 Content-length: 378 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20981 mephi42 at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mephi42 at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21020-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 24 09:06:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 22776 invoked by alias); 24 Feb 2017 09:06:31 -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 22747 invoked by uid 48); 24 Feb 2017 09:06:30 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug server/21169] GDBServer on ARM can crash the inferior while single stepping Date: Fri, 24 Feb 2017 09:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc component 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: 2017-q1/txt/msg00172.txt.bz2 Content-length: 443 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21169 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org Component|gdb |server --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21021-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 24 09:27:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 120797 invoked by alias); 24 Feb 2017 09:27:47 -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 120763 invoked by uid 48); 24 Feb 2017 09:27:46 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Fri, 24 Feb 2017 09:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created 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: 2017-q1/txt/msg00173.txt.bz2 Content-length: 690 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 Nitish K Mishra changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #9846|0 |1 is obsolete| | --- Comment #4 from Nitish K Mishra --- Created attachment 9850 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9850&action=3Dedit Updated proposed patch file for this bug Proposed patch for configure.ac file. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21022-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 24 12:58:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127620 invoked by alias); 24 Feb 2017 12:58:38 -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 127586 invoked by uid 48); 24 Feb 2017 12:58:37 -0000 From: "alexandre.nunes at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18584] "Duplicate variable object name" using pretty-printing when variable not initialized Date: Fri, 24 Feb 2017 12:58: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: alexandre.nunes at gmail dot com 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: cc 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: 2017-q1/txt/msg00174.txt.bz2 Content-length: 396 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18584 alexandre.nunes at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexandre.nunes at gmail d= ot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21023-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 27 10:53:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 108866 invoked by alias); 27 Feb 2017 10:53:45 -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 108829 invoked by uid 48); 27 Feb 2017 10:53:45 -0000 From: "hd at bue dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/21200] New: rl78-elf-gdb.exe crashes when trying to run program in debugger Date: Mon, 27 Feb 2017 10:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hd at bue dot de X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00175.txt.bz2 Content-length: 4022 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21200 Bug ID: 21200 Summary: rl78-elf-gdb.exe crashes when trying to run program in debugger Product: gdb Version: 7.8 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: hd at bue dot de Target Milestone: --- In Renesas e2studio, run under Windows 10, rl78-elf-gdb.exe crashes when program is run. Downloading the program to the hardware works fine. Single stepping seems to work ok but as soon as the run button is clicked,rl78-elf-gdb.exe crashes. This is what is output to the console window: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D GNU gdb (GDB) 7.8.2-20161206-Build_1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=3Di686-pc-mingw32 --target=3Drl78-elf". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help".=20=20 Type "apropos word" to search for commands related to "word". monitor set_io_access_width,RW,2,f00e0-f00e2,f0108-f011e,f0122-f012a,f0134,f0138,f0= 148-f014a,f0150-f0152,f0158-f015a,f0162-f016a,f0174,f0190-f019e,f01b2-f01be= ,f02f2,f02fa,fff10-fff12,fff18-fff1a,fff44-fff4a monitor set_io_access_width,RW,2,fff64-fff6e,fff90,fffb2-fffb8,fffd0,fffd4,fffd8,ff= fdc,fffe0-ffff6 monitor set_io_access_width,R,2,f0100-f0106,f0120,f0140-f0142,f0160,f0180-f018e,f01= a0-f01b0,fff1e monitor set_io_access_width,RW,1,f0010-f0013,f0030-f0031,f0033-f0035,f003c,f003e,f0= 040-f0041,f0050-f0051,f0055,f0060,f006c,f006e,f0070-f0071,f0073-f0074,f0076= -f0078,f0090,f00a0,f00a8,f00ac-f00af,f00e8,f00f0 monitor set_io_access_width,RW,1,f00f3-f00f5,f00fe,f0100,f0102,f0104,f0106,f0108,f0= 10a,f010c,f010e,f0120,f0122,f0124,f0126,f012a,f0134,f0138,f0140,f0142,f0148= ,f014a,f0160,f0162,f0164,f0166,f016a,f0174,f01a0 monitor set_io_access_width,RW,1,f01a2,f01a4,f01a6,f01a8,f01aa,f01ac,f01ae,f01b0,f0= 1b2,f01b4,f01b8,f01ba,f01bc,f01be,f0230-f0234,f02f0,fff00-fff06,fff0c-fff0e= ,fff10,fff12,fff1a-fff1b,fff1f-fff26,fff2c,fff2e monitor set_io_access_width,RW,1,fff30-fff32,fff38-fff39,fff44,fff46,fff48,fff4a,ff= f50-fff52,fff66-fff67,fff92-fff9e,fffa0-fffa6,fffa8-fffac,fffb0-fffbd,fffd0= -fffd1,fffd4-fffd5,fffd8-fffd9,fffdc-fffdd monitor set_io_access_width,RW,1,fffe0-fffef,ffffe Program received signal Warning: the current language does not match this frame. Program received signal SIGTRAP, Trace/breakpoint trap. PowerON_Reset () at ../src/r_reset_program.asm:65 65 movw sp,#_stack /* Set stack pointer */ ../../RL78_python_GDB/gdb/dwarf2-frame.c:687: internal-error: Unknown CFI encountered. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session?=20 This is a bug, please report it.This application has requested the Runtime = to terminate it in an unusual way. Please contact the application's support team for more information. For instructions, see: . (y or n) [answered Y; input not from terminal] ../../RL78_python_GDB/gdb/dwarf2-frame.c:687: internal-error: Unknown CFI encountered. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21024-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 27 11:58:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 58176 invoked by alias); 27 Feb 2017 11:58:47 -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 58144 invoked by uid 48); 27 Feb 2017 11:58:46 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Mon, 27 Feb 2017 11:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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: 2017-q1/txt/msg00176.txt.bz2 Content-length: 324 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 --- Comment #5 from Nitish K Mishra --- Created attachment 9860 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9860&action=3Dedit ChangeLog --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21026-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 28 18:50:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 22795 invoked by alias); 28 Feb 2017 18:50:49 -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 22769 invoked by uid 48); 28 Feb 2017 18:50:48 -0000 From: "ake.rehnman at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18051] gdb hang in "start" command w/ remote target Date: Tue, 28 Feb 2017 18:50: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ake.rehnman at gmail dot com 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: 2017-q1/txt/msg00178.txt.bz2 Content-length: 2533 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18051 --- Comment #2 from Ake --- Same result when issuing run cmd. Possibly missing "clear_proceed_status (0= )" in run_command_1 before calling proceed. I have tested adding clear_proceed_status (0) before call to proceed with g= ood result. gdb version 7.12.1 LOG BEFORE CHANGE: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D (gdb) b main Breakpoint 1 at 0x82c6: file led.c, line 121. (gdb) run The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /cygdrive/c/temp/test1/led.elf infrun: infrun_async(1) infrun: proceed (addr=3D0x6000, signal=3DGDB_SIGNAL_0) infrun: resume (step=3D0, signal=3DGDB_SIGNAL_0), trap_expected=3D0, curren= t thread [Remote target] at 0x6000 infrun: prepare_to_wait infrun: target_wait (-1.0.0, status) =3D infrun: -1.0.0 [Thread 0], infrun: status->kind =3D ignore infrun: TARGET_WAITKIND_IGNORE infrun: prepare_to_wait infrun: target_wait (-1.0.0, status) =3D infrun: 42000.0.0 [Remote target], infrun: status->kind =3D stopped, signal =3D GDB_SIGNAL_TRAP infrun: TARGET_WAITKIND_STOPPED infrun: stop_pc =3D 0x82c6 infrun: quietly stopped infrun: stop_waiting infrun: clear_step_over_info infrun: infrun_async(0) AFTER ADDING clear_proceed_status(0): =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D (gdb) b main Breakpoint 1 at 0x82c6: file led.c, line 121. (gdb) run The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /cygdrive/c/temp/test1/led.elf infrun: infrun_async(1) infrun: clear_proceed_status_thread (Remote target) infrun: proceed (addr=3D0x6000, signal=3DGDB_SIGNAL_0) infrun: resume (step=3D0, signal=3DGDB_SIGNAL_0), trap_expected=3D0, curren= t thread [Remote target] at 0x6000 infrun: prepare_to_wait infrun: target_wait (-1.0.0, status) =3D infrun: -1.0.0 [Thread 0], infrun: status->kind =3D ignore infrun: TARGET_WAITKIND_IGNORE infrun: prepare_to_wait infrun: target_wait (-1.0.0, status) =3D infrun: 42000.0.0 [Remote target], infrun: status->kind =3D stopped, signal =3D GDB_SIGNAL_TRAP infrun: TARGET_WAITKIND_STOPPED infrun: stop_pc =3D 0x82c6 infrun: BPSTAT_WHAT_STOP_NOISY infrun: stop_waiting infrun: clear_step_over_info --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21025-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 28 18:50:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 21162 invoked by alias); 28 Feb 2017 18:50:05 -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 21123 invoked by uid 48); 28 Feb 2017 18:50:04 -0000 From: "ake.rehnman at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18051] gdb hang in "start" command w/ remote target Date: Tue, 28 Feb 2017 18:50: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ake.rehnman at gmail dot com 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: cc attachments.created 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: 2017-q1/txt/msg00177.txt.bz2 Content-length: 604 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18051 Ake changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ake.rehnman at gmail dot c= om --- Comment #1 from Ake --- Created attachment 9863 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9863&action=3Dedit Missing clear_proceed_status(0) in run_command_1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21027-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 28 21:15:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89183 invoked by alias); 28 Feb 2017 21:15:39 -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 88339 invoked by uid 48); 28 Feb 2017 21:15:23 -0000 From: "chrisj at rtems dot org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/21206] New: gdb-7.12.1 for arm-rtems4.12 fails to build on FreeBSD 11.0 Date: Tue, 28 Feb 2017 21:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: chrisj at rtems dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00179.txt.bz2 Content-length: 6472 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21206 Bug ID: 21206 Summary: gdb-7.12.1 for arm-rtems4.12 fails to build on FreeBSD 11.0 Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: critical Priority: P2 Component: corefiles Assignee: unassigned at sourceware dot org Reporter: chrisj at rtems dot org Target Milestone: --- Note, HEAD is also broken. The arm-rtems4.12 target is broken in gdb-7.12.1 and binutils-gdb.git HEAD = on FreeBSD 11.0. Configure command is: $ ../binutils-gdb/configure --build=3Dx86_64-freebsd11.0 --host=3Dx86_64-freebsd11.0 --target=3Darm-rtems4.12 --verbose --disable-nls --without-included-gettext --disable-win32-registry --disable-werror --enable-sim --without-zlib --with-expat --with-python --prefix=3D/opt/work/rtems/4.12 --bindir=3D/opt/work/rtems/4.12/bin --exec-prefix=3D/opt/work/rtems/4.12 --includedir=3D/opt/work/rtems/4.12/in= clude --libdir=3D/opt/work/rtems/4.12/lib --mandir=3D/opt/work/rtems/4.12/share/m= an --infodir=3D/opt/work/rtems/4.12/share/info Host compiler is /usr/bin/c++.=20 It looks like something in the recent gnulib updates breaks on FreeBSD 11.0. The error from building on HEAD is: /usr/bin/c++ -O2 -pipe -fbracket-depth=3D1024 -I/opt/work/chris/rtems/rsb/rtems-source-builder.git/rtems/build/tmp/sb-chr= is/4.12/rtems-arm/opt/work/rtems/4.12/include -std=3Dgnu++11 -I. -I../../binutils-gdb/gdb -I../../binutils-gdb/gdb/com= mon -I../../binutils-gdb/gdb/config -DLOCALEDIR=3D"\"/opt/work/rtems/4.12/share/locale\"" -DHAVE_CONFIG_H -I../../binutils-gdb/gdb/../include/ opcode -I../../binutils-gdb/gdb/../opcodes/.. -I../../binutils-gdb/gdb/../readline/.. -I../../binutils-gdb/gdb/../zlib -I../bfd -I../../binutils-gdb/gdb/../bfd -I../../binutils-gdb/gdb/../include -I../libdecnumber -I../../binutils-gdb/gdb/../libdecnumber=20 -I../../binutils-gdb/gdb/gnulib/import -Ibuild-gnulib/import -DTUI=3D1=20 -I/opt/work/rtems/4.12/include -I/usr/local/inclu de/python2.7 -I/usr/local/include/python2.7 -Wall -Wpointer-arith -Wno-unus= ed -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-b= ody -Wunused-but-set-parameter -Wunused-but-set-variable -Wno-sign-compare -Wno-write-strings -Wno-narrowing -Wformat-nonliteral -c -o gdb.o -MT gdb.o -MMD -MP -MF .deps/gdb.Tpo ../../binutils-gdb/gdb/gdb.c c++: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated warning: unknown warning option '-Wunused-but-set-parameter'; did you mean '-Wunused-parameter'? [-Wunknown-warning-option] warning: unknown warning option '-Wunused-but-set-variable'; did you mean '-Wunused-const-variable'? [-Wunknown-warning-option] In file included from ../../binutils-gdb/gdb/gdb.c:19: In file included from ../../binutils-gdb/gdb/defs.h:28: In file included from ../../binutils-gdb/gdb/common/common-defs.h:52: In file included from build-gnulib/import/stdio.h:53: build-gnulib/import/stddef.h:106:3: error: typedef redefinition with differ= ent types ('union max_align_t' vs 'long double') } max_align_t; ^ /usr/include/c++/v1/stddef.h:57:21: note: previous definition is here typedef long double max_align_t; ^ In file included from ../../binutils-gdb/gdb/gdb.c:19: In file included from ../../binutils-gdb/gdb/defs.h:53: ../../binutils-gdb/gdb/ui-file.h:93:28: warning: struct 'ui_file' was previously declared as a class [-Wmismatched-tags] extern int ui_file_isatty (struct ui_file *); ^ ../../binutils-gdb/gdb/ui-file.h:26:7: note: previous use is here class ui_file ^ ../../binutils-gdb/gdb/ui-file.h:93:28: note: did you mean class here? extern int ui_file_isatty (struct ui_file *); ^~~~~~ class ../../binutils-gdb/gdb/ui-file.h:95:28: warning: struct 'ui_file' was previously declared as a class [-Wmismatched-tags] extern void ui_file_write (struct ui_file *file, const char *buf, ^ ../../binutils-gdb/gdb/ui-file.h:26:7: note: previous use is here class ui_file ^ ../../binutils-gdb/gdb/ui-file.h:95:28: note: did you mean class here? extern void ui_file_write (struct ui_file *file, const char *buf, ^~~~~~ class ../../binutils-gdb/gdb/ui-file.h:98:39: warning: struct 'ui_file' was previously declared as a class [-Wmismatched-tags] extern void ui_file_write_async_safe (struct ui_file *file, const char *buf, ^ ../../binutils-gdb/gdb/ui-file.h:26:7: note: previous use is here class ui_file ^ ../../binutils-gdb/gdb/ui-file.h:98:39: note: did you mean class here? extern void ui_file_write_async_safe (struct ui_file *file, const char *buf, ^~~~~~ class ../../binutils-gdb/gdb/ui-file.h:101:27: warning: struct 'ui_file' was previously declared as a class [-Wmismatched-tags] extern long ui_file_read (struct ui_file *file, char *buf, long length_buf); ^ ../../binutils-gdb/gdb/ui-file.h:26:7: note: previous use is here class ui_file ^ ../../binutils-gdb/gdb/ui-file.h:101:27: note: did you mean class here? extern long ui_file_read (struct ui_file *file, char *buf, long length_buf); ^~~~~~ class In file included from ../../binutils-gdb/gdb/gdb.c:19: ../../binutils-gdb/gdb/defs.h:327:8: warning: struct 'ui_file' was previous= ly declared as a class [-Wmismatched-tags] struct ui_file *, int, char *); ^ ../../binutils-gdb/gdb/ui-file.h:26:7: note: previous use is here class ui_file ^ ../../binutils-gdb/gdb/defs.h:327:8: note: did you mean class here? struct ui_file *, int, char *); ^~~~~~ class ../../binutils-gdb/gdb/defs.h:338:57: warning: struct 'ui_file' was previou= sly declared as a class [-Wmismatched-tags] extern void print_address (struct gdbarch *, CORE_ADDR, struct ui_file *); ^ ../../binutils-gdb/gdb/ui-file.h:26:7: note: previous use is here class ui_file ^ --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21028-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 01 09:47:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 80474 invoked by alias); 1 Mar 2017 09:47:24 -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 80445 invoked by uid 48); 1 Mar 2017 09:47:22 -0000 From: "xhpohanka at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/21208] New: Inspecting std:set causes gdb to hang when using gdb/mi interface and pretty printing Date: Wed, 01 Mar 2017 09:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: xhpohanka at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q1/txt/msg00180.txt.bz2 Content-length: 1193 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21208 Bug ID: 21208 Summary: Inspecting std:set causes gdb to hang when using gdb/mi interface and pretty printing Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: mi Assignee: unassigned at sourceware dot org Reporter: xhpohanka at gmail dot com Target Milestone: --- Created attachment 9865 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9865&action=3Dedit gdb log Following code causes problem to mi interpreter with pretty printing enabled #include #include using namespace std; int main() { set foo; // non POD type needed here foo.insert("bar"); return 0; } Following commands can be used to reproduce the issue gdb --interpreter=3Dmi ./test br main -enable-pretty-printing -exec-run -var-create - * foo -var-list-children var1 Listing children of foo causes very long loop that sometimes never finishes. Detailed log is attached. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21029-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 01 09:48:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 81455 invoked by alias); 1 Mar 2017 09:48:30 -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 81320 invoked by uid 48); 1 Mar 2017 09:48:20 -0000 From: "xhpohanka at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/21208] Inspecting std::set causes gdb to hang when using gdb/mi interface and pretty printing Date: Wed, 01 Mar 2017 09:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: xhpohanka at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: short_desc 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: 2017-q1/txt/msg00181.txt.bz2 Content-length: 603 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21208 Jan Pohanka changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Inspecting std:set causes |Inspecting std::set causes |gdb to hang when using |gdb to hang when using |gdb/mi interface and pretty |gdb/mi interface and pretty |printing |printing --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21030-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 02 08:38:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 30968 invoked by alias); 2 Mar 2017 08:38:13 -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 30932 invoked by uid 48); 2 Mar 2017 08:38:12 -0000 From: "dimhen at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/7349] RFE: Can't refer to previous watchpoint value in condition Date: Thu, 02 Mar 2017 08:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dimhen at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q1/txt/msg00182.txt.bz2 Content-length: 397 https://sourceware.org/bugzilla/show_bug.cgi?id=3D7349 Dmitry G. Djachenko changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimhen at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21031-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 02 17:25:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122972 invoked by alias); 2 Mar 2017 17:25:21 -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 122889 invoked by uid 48); 2 Mar 2017 17:25:20 -0000 From: "dzabraew at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21213] New: garbarge collector eats gdb.selected_thread() Date: Thu, 02 Mar 2017 17:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dzabraew at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00183.txt.bz2 Content-length: 1564 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21213 Bug ID: 21213 Summary: garbarge collector eats gdb.selected_thread() Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: dzabraew at gmail dot com Target Milestone: --- Hi, gdb developers! I found following bug: (gdb) pi gdb.selected_thread().inferior (gdb) pi gdb.selected_thread().inferior (gdb) pi gdb.selected_thread().inferior Python Exception 'NoneType' object has no attribute 'inferior':=20 Error while executing Python code. (gdb) info threads Id Target Id Frame=20 * 1 Thread 0x7f54f0474740 (LWP 584) "mc" 0x00007f54ef055c33 in select () from /lib/x86_64-linux-gnu/libc.so.6 Seems tube problem in `thpy_get_inferior` function, file: gdb/python/py-infthread.c. following path fixes this problem ----------begin-patch--------- --- /tmp/py-infthread.c.OLD 2017-03-02 20:23:53.919146955 +0300 +++ /tmp/py-infthread.c.NEW 2017-03-02 20:24:14.319146366 +0300 @@ -160,6 +160,7 @@ thread_object *thread_obj =3D (thread_object *) self; THPY_REQUIRE_VALID (thread_obj); + Py_INCREF (thread_obj->inf_obj); return thread_obj->inf_obj; } ----------end-patch----------- --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21032-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 02 22:04:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 46153 invoked by alias); 2 Mar 2017 22:04:05 -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 46122 invoked by uid 48); 2 Mar 2017 22:04:05 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/21206] gdb-7.12.1 for arm-rtems4.12 fails to build on FreeBSD 11.0 Date: Thu, 02 Mar 2017 22:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00184.txt.bz2 Content-length: 529 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21206 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org --- Comment #1 from Yao Qi --- Is your compiler clang? I have no problem building gdb with clang++-3.6 on Linux. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21033-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 02 22:19:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 84213 invoked by alias); 2 Mar 2017 22:19:39 -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 84178 invoked by uid 48); 2 Mar 2017 22:19:38 -0000 From: "chrisj at rtems dot org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/21206] gdb-7.12.1 for arm-rtems4.12 fails to build on FreeBSD 11.0 Date: Thu, 02 Mar 2017 22:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: chrisj at rtems dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00185.txt.bz2 Content-length: 1833 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21206 --- Comment #2 from Chris Johns --- (In reply to Yao Qi from comment #1) > Is your compiler clang? I have no problem building gdb with clang++-3.6 = on > Linux. Yes, this is the default compiler for FreeBSD 11.0: $ /usr/bin/c++ --version FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0) Target: x86_64-unknown-freebsd11.0 Thread model: posix InstalledDir: /usr/bin I was just looking into this on gdb's git HEAD branch and it seems gnulib's configure is using the default CPP which is a C compiler however GDB is not= C++ and so the generated header file 'stddef.h' is not really suitable. The top= of config.log for gnulib has 'CPP=3D' I suspect this needs to be the C++ compi= ler. I hacked gnulib/configure adding to the top something like: CPP=3D"/usr/bin/c++ -E" and 'stddef.h' was correctly created. I could not figure out how to specify 'CPP=3D$CXX' to gnulib's configure. I did try setting CPP to CXX when calli= ng the top level configure however building the binutils parts fails which is to be expected. The build did fail on further on with: In file included from ../../binutils-gdb/gdb/dwarf2read.c:72: ../../binutils-gdb/gdb/common/gdb_unlinker.h:35:35: error: '__nonnull__' attribute is invalid for the implicit this argument unlinker (const char *filename) ATTRIBUTE_NONNULL (1) ^ ~ ../../binutils-gdb/gdb/../include/ansidecl.h:169:48: note: expanded from ma= cro 'ATTRIBUTE_NONNULL' # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m))) So it looks like there are other issues. FYI this issue is currently a blocker for RTEMS's 4.12 release. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21034-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 02 22:21:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 85990 invoked by alias); 2 Mar 2017 22:21:42 -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 85945 invoked by uid 48); 2 Mar 2017 22:21:41 -0000 From: "chrisj at rtems dot org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/21206] gdb-7.12.1 for arm-rtems4.12 fails to build on FreeBSD 11.0 Date: Thu, 02 Mar 2017 22:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: chrisj at rtems dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00186.txt.bz2 Content-length: 446 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21206 --- Comment #3 from Chris Johns --- (In reply to Chris Johns from comment #2) > I was just looking into this on gdb's git HEAD branch and it seems gnulib= 's > configure is using the default CPP which is a C compiler however GDB is n= ot > C++ Sorry I meant GDB *is* a C++ program. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21035-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 03 14:14:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 26632 invoked by alias); 3 Mar 2017 14:14:01 -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 26585 invoked by uid 55); 3 Mar 2017 14:14:00 -0000 From: "ro at CeBiTec dot Uni-Bielefeld.DE" To: gdb-prs@sourceware.org Subject: [Bug build/18294] gdb compilation fails on 32-bit Solaris: largefile vs. procfs Date: Fri, 03 Mar 2017 14:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.9 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE 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: 2017-q1/txt/msg00187.txt.bz2 Content-length: 714 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18294 --- Comment #2 from Rainer Orth --- > --- Comment #1 from Joel Brobecker --- > Can you confirm whether GDB 7.12 does better? I just tried 7.12.1 on i386-pc-solaris2.10: same failure. > Given that this isn't a regression, I don't think this PR should be block= ing > for 8.0. In other words, a fix by 8.0 would be great, but we shouldn't bl= ock > 8.0 because of that (known) issue. How is this not a regression? Worked in 7.8, broke build in 7.9 pretty much looks like a regression to me ;-) Rainer --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21036-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 03 14:24:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 91798 invoked by alias); 3 Mar 2017 14:24:34 -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 91709 invoked by uid 55); 3 Mar 2017 14:24:28 -0000 From: "brobecker at adacore dot com" To: gdb-prs@sourceware.org Subject: [Bug build/18294] gdb compilation fails on 32-bit Solaris: largefile vs. procfs Date: Fri, 03 Mar 2017 14:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.9 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at adacore dot com 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: 2017-q1/txt/msg00188.txt.bz2 Content-length: 835 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18294 --- Comment #3 from brobecker at adacore dot com --- > I just tried 7.12.1 on i386-pc-solaris2.10: same failure. Darn... >=20 > > for 8.0. In other words, a fix by 8.0 would be great, but we shouldn't = block > > 8.0 because of that (known) issue. >=20 > How is this not a regression? Worked in 7.8, broke build in 7.9 > pretty much looks like a regression to me ;-) It depends on how you define regression, of course. For the purpose of a new release, we only consider the previous version/branch. If the previous release/branch already had the issue, then we no longer consider it blocking, basically because create a new release without the fix wouldn't make things worse for that platform. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21037-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 03 17:17:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 6898 invoked by alias); 3 Mar 2017 17:17:31 -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 6776 invoked by uid 55); 3 Mar 2017 17:17:30 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21165] [8.0 Regression] FAIL: gdb.ada/info_locals_renaming.exp: info locals (GDB internal error) Date: Fri, 03 Mar 2017 17:17: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00189.txt.bz2 Content-length: 1580 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21165 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Yao Qi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D7d45f3df96ca= 108f6d7d0c5e4279e22b820145fa commit 7d45f3df96ca108f6d7d0c5e4279e22b820145fa Author: Yao Qi Date: Fri Mar 3 17:16:19 2017 +0000 Fetch lazy value before calling val_print As reported in PR 21165, (gdb) info locals^M gv =3D /home/yao/SourceCode/gnu/gdb/git/gdb/value.c:372: internal-error= : int value_bits_any_optimized_out(const value*, int, int): Assertion `!value->la= zy' failed.^M A problem internal to GDB has been detected,^M further debugging may prove unreliable.^M Quit this debugging session? (y or n) FAIL: gdb.ada/info_locals_renaming.exp: info locals (GDB internal error) Resyncing due to internal error. This internal error is caused by e8b24d9 (Remove parameter valaddr from la_val_print). Commit e8b24d9 removes some calls to value_contents_for_printing, but value_fetch_lazy is not called, so the internal error above is triggered. This patch adds value_fetch_lazy call before val_print. gdb: 2017-03-03 Yao Qi PR gdb/21165 * ada-valprint.c (ada_val_print_ref): Call value_fetch_lazy if value is lazy. * valprint.c (common_val_print): Likewise. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21038-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 03 17:18:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 7861 invoked by alias); 3 Mar 2017 17:18:04 -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 7829 invoked by uid 48); 3 Mar 2017 17:18:04 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21165] [8.0 Regression] FAIL: gdb.ada/info_locals_renaming.exp: info locals (GDB internal error) Date: Fri, 03 Mar 2017 17:18: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.0 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00190.txt.bz2 Content-length: 505 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21165 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Yao Qi --- Patch is pushed in. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21039-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 03 17:24:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 33875 invoked by alias); 3 Mar 2017 17:24:59 -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 33084 invoked by uid 48); 3 Mar 2017 17:24:59 -0000 From: "sameer.varyani at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21214] New: exec_file_attach uses gdb_realpath instead of gdb_realpath_keepfile Date: Fri, 03 Mar 2017 17:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.10 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sameer.varyani at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00191.txt.bz2 Content-length: 1349 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21214 Bug ID: 21214 Summary: exec_file_attach uses gdb_realpath instead of gdb_realpath_keepfile Product: gdb Version: 7.10 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: sameer.varyani at gmail dot com Target Milestone: --- exec_file_attach is used atleast in 2 different scenarios: 1. When attaching to a running process. 2. When the underlying executable is modified and gdb tries to reload the symbols + exec. In the second case, argv[0] is modified to the linked file if the executabl= e is a link, which breaks the executable as it relies on the file name/path. A similar bug was reported for an earlier version of gdb and was fixed for = only the first time the symbol file is read, but not for reload. most likely fix: this is based on source from gdb-7.10(ftp://sourceware.org/pub/gdb/snapshots/branch/gdb-7.10.0.20151204.= tar.xz) diff exec.c exec.c.orig 274c274 < canonical_pathname =3D gdb_realpath_keepfile (scratch_pathname); --- > canonical_pathname =3D gdb_realpath (scratch_pathname); --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21040-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 03 17:25:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 73846 invoked by alias); 3 Mar 2017 17:25:36 -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 73816 invoked by uid 48); 3 Mar 2017 17:25:36 -0000 From: "sameer.varyani at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21214] exec_file_attach uses gdb_realpath instead of gdb_realpath_keepfile Date: Fri, 03 Mar 2017 17:25: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.10 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sameer.varyani at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00192.txt.bz2 Content-length: 394 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21214 sameer.varyani at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sameer.varyani at gmail do= t com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21041-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 03 22:08:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 39391 invoked by alias); 3 Mar 2017 22:08:10 -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 39362 invoked by uid 48); 3 Mar 2017 22:08:10 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21216] New: regression: TUI by: Eliminate make_cleanup_ui_file_delete / make ui_file a class hierarchy Date: Fri, 03 Mar 2017 22:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00193.txt.bz2 Content-length: 4160 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21216 Bug ID: 21216 Summary: regression: TUI by: Eliminate make_cleanup_ui_file_delete / make ui_file a class hierarchy Product: gdb Version: 8.0 Status: NEW Severity: normal Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Target Milestone: --- PASS: 187808b04f61df1c38fda0921e2d9eeb53e332ee =3D a commit before the FAIL one below $ gdb -tui [ TUI source window ] GNU gdb (GDB) 7.12.50.20170202-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . ---Type to continue, or q to quit--- FAIL: d7e747318f4d04af033f16325f9b6d74f67079ec is the first bad commit commit d7e747318f4d04af033f16325f9b6d74f67079ec Author: Pedro Alves Date: Thu Feb 2 11:11:47 2017 +0000 Eliminate make_cleanup_ui_file_delete / make ui_file a class hierarchy $ gdb -tui [ TUI source window ] GNU gdb (GDB) 7.12.50.20170202-git Copyright (C) 2017 Free Software Foundati= on, Inc. =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 Type "show configuration" for configuration deta= ils. For bug reporting instructions, please see: =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20 . =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 Find the GDB manual and other documentation resour= ces online at: =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 . =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 ---Type to continue, or q to quit--- --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21042-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 03 22:09:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 42164 invoked by alias); 3 Mar 2017 22:09:08 -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 42126 invoked by uid 48); 3 Mar 2017 22:09:07 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21216] regression: TUI by: Eliminate make_cleanup_ui_file_delete / make ui_file a class hierarchy Date: Fri, 03 Mar 2017 22:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to target_milestone 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: 2017-q1/txt/msg00194.txt.bz2 Content-length: 549 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21216 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jan.kratochvil at redhat d= ot com Assignee|unassigned at sourceware dot org |palves at redhat do= t com Target Milestone|--- |8.0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21043-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Mar 04 05:43:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 17398 invoked by alias); 4 Mar 2017 05:43:42 -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 17339 invoked by uid 48); 4 Mar 2017 05:43:36 -0000 From: "gpmfuchs at gmx dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/17229] infinite loop in linux_check_ptrace_features Date: Sat, 04 Mar 2017 05:43: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.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gpmfuchs at gmx dot de 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: cc 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: 2017-q1/txt/msg00195.txt.bz2 Content-length: 922 https://sourceware.org/bugzilla/show_bug.cgi?id=3D17229 gpmfuchs at gmx dot de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gpmfuchs at gmx dot de --- Comment #2 from gpmfuchs at gmx dot de --- I've run repeatedly into this bug. My use case is a c++-program which forks whenever an assert is hit or a watch-timer is triggered, then it redirects stdout/stderr to a tmpfile and execl to gdb, in order to get a bug report. The bug means in my case, that gdb fills it's tmpfile with "linux_check_ptrace_features: failed to kill child" until the /tmp mount is full. Which means it starves the autotest-system of memory, triggering random OOM-kills, and as a result crashing the autobuild-system. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21044-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Mar 04 17:32:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3678 invoked by alias); 4 Mar 2017 17:32:26 -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 3646 invoked by uid 48); 4 Mar 2017 17:32:25 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Sat, 04 Mar 2017 17:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: mishra.nitish.88 at gmail dot com X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed 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: 2017-q1/txt/msg00196.txt.bz2 Content-length: 1526 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-03-04 CC| |brobecker at gnat dot com Assignee|unassigned at sourceware dot org |mishra.nitish.88 at= gmail dot com Ever confirmed|0 |1 --- Comment #6 from Joel Brobecker --- To get your patch reviewed, and hopefully included in the official sources,= can you please send it to gdb-patches@, using the information outlined in the following page, please? https://sourceware.org/gdb/wiki/ContributionChecklist People don't necessarily follow the patches sent here. I think this is also mentioned in the ContributionChecklist above, but do ping us after a couple= of weeks if we haven't answered, and every week thereafter. As a comment to your patch, the style you used for the AC_ARG_ENABLE is a b= it different from the style we've been using so far. Not necessarily wrong, but there is value for us in trying to keep the style consistent. So could you = have a look at the other uses of AC_ARG_ENABLE in gdb/configure.ac, and try to mimick that with your patch? Thank you. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21045-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Mar 04 17:41:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 13417 invoked by alias); 4 Mar 2017 17:41:29 -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 13383 invoked by uid 48); 4 Mar 2017 17:41:28 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug server/21169] GDBServer on ARM can crash the inferior while single stepping Date: Sat, 04 Mar 2017 17:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q1/txt/msg00197.txt.bz2 Content-length: 989 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21169 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brobecker at gnat dot com --- Comment #1 from Joel Brobecker --- For the record: We discussed this PR on gdb-patches@, and what we ended up saying is that this PR is not strictly a 7.12 -> 8.0 regression, but that it is enough of an issue that this PR is sufficiently of an issue that we can try getting the fix in 8.0. Antoine should be this PR's champion, and if it doesn't get fixed by our tentative 8.0 release date, we'll consid= er the option of delaying the release by a week or two, if that makes a difference. See: https://www.sourceware.org/ml/gdb-patches/2017-02/msg00467.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21046-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Mar 05 12:58:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63021 invoked by alias); 5 Mar 2017 12:58:26 -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 62994 invoked by uid 48); 5 Mar 2017 12:58:25 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/21218] New: Regression: GDB dumps core when escaping newline in multi line command Date: Sun, 05 Mar 2017 12:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00198.txt.bz2 Content-length: 1247 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21218 Bug ID: 21218 Summary: Regression: GDB dumps core when escaping newline in multi line command Product: gdb Version: 7.12 Status: NEW Severity: normal Priority: P2 Component: cli Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Target Milestone: --- https://bugzilla.redhat.com/show_bug.cgi?id=3D1429172 by Georg Sauthoff $ gdb ls Reading symbols from ls...Reading symbols from /usr/lib/debug/usr/bin/ls.debug...done. done. (gdb) b main Breakpoint 1 at 0x3990: file ../src/ls.c, line 1347. (gdb) commands=20 Type commands for breakpoint(s) 1, one per line. End with a line saying just "end". >silent >print \ (gdb) argc >end readline: readline_callback_read_char() called with no handler! zsh: abort (core dumped) gdb -q ls regressed by: commit 3b12939dfc2399200f243851fd55d0e392b64165 Author: Pedro Alves Date: Tue Jun 21 01:11:51 2016 +0100 Replace the sync_execution global with a new enum prompt_state tristate --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21047-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Mar 05 12:59:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64027 invoked by alias); 5 Mar 2017 12:59:29 -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 63988 invoked by uid 48); 5 Mar 2017 12:59:29 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/21218] Regression: GDB dumps core when escaping newline in multi line command Date: Sun, 05 Mar 2017 12:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: cc attachments.created 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: 2017-q1/txt/msg00199.txt.bz2 Content-length: 602 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21218 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jan.kratochvil at redhat d= ot com --- Comment #1 from Jan Kratochvil --- Created attachment 9870 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9870&action=3Dedit new testcase --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21048-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Mar 05 13:00:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64621 invoked by alias); 5 Mar 2017 13:00:01 -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 64519 invoked by uid 48); 5 Mar 2017 12:59:59 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/21218] Regression: GDB dumps core when escaping newline in multi line command Date: Sun, 05 Mar 2017 13:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to target_milestone 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: 2017-q1/txt/msg00200.txt.bz2 Content-length: 465 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21218 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |palves at redhat do= t com Target Milestone|--- |8.0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21049-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 06 12:41:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41105 invoked by alias); 6 Mar 2017 12:41:30 -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 41078 invoked by uid 48); 6 Mar 2017 12:41:29 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21220] New: "restore" for large data structures extremely slow on GNU/Linux Date: Mon, 06 Mar 2017 12:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00201.txt.bz2 Content-length: 874 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21220 Bug ID: 21220 Summary: "restore" for large data structures extremely slow on GNU/Linux Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: arnez at linux dot vnet.ibm.com Target Milestone: --- On GNU/Linux, restoring a large array does not complete in reasonable time: (gdb) p sizeof bigarray $1 =3D 16777216 (gdb) dump bin mem foo.bin &bigarray &bigarray[sizeof bigarray] (gdb) restore foo.bin binary &bigarray Restoring binary file foo.bin into memory (0x10002060 to 0x11002060) This operation appears to hang. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21050-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 06 13:20:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 99980 invoked by alias); 6 Mar 2017 13:20:30 -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 99947 invoked by uid 48); 6 Mar 2017 13:20:29 -0000 From: "prakhar.bahuguna at arm dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21221] New: gdb hangs while stepping an empty loop Date: Mon, 06 Mar 2017 13:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: prakhar.bahuguna at arm dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q1/txt/msg00202.txt.bz2 Content-length: 1096 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21221 Bug ID: 21221 Summary: gdb hangs while stepping an empty loop Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: prakhar.bahuguna at arm dot com Target Milestone: --- Created attachment 9871 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9871&action=3Dedit Reproducer test case Given the empty for loop in the reproducer with a large number of iteration= s, gdb hangs while attempting to step over a single iteration of the loop. The server hangs and must be interrupted manually. The issue does not present itself if the loop contains an instruction - add= ing __asm("NOP"); inside the loop is sufficient to suppress the bug and allow t= he loop to be stepped correctly. This issue can be reproduced on trunk for both ARM and x86 platforms. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21051-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 06 14:42:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 129439 invoked by alias); 6 Mar 2017 14:42:15 -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 129409 invoked by uid 48); 6 Mar 2017 14:42:14 -0000 From: "ilg at livius dot net" To: gdb-prs@sourceware.org Subject: [Bug gdb/21221] gdb hangs while stepping an empty loop Date: Mon, 06 Mar 2017 14:42: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ilg at livius dot net X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00203.txt.bz2 Content-length: 388 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21221 Liviu Ionescu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ilg at livius dot net --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21052-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 06 15:06:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 105578 invoked by alias); 6 Mar 2017 15:06:57 -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 105552 invoked by uid 48); 6 Mar 2017 15:06:57 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] New: A function with a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Mon, 06 Mar 2017 15:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q1/txt/msg00204.txt.bz2 Content-length: 1100 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 Bug ID: 21222 Summary: A function with a particular number of arguments corrupts a value calculated on the stack when stepping through the function Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: kungfujesus06 at gmail dot com Target Milestone: --- Created attachment 9872 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9872&action=3Dedit Minimal test case Sorry for the convoluted summary, I'm not entirely sure how or why it happe= ns.=20 The results are fine when not attached to the debugger (or in the test case= I'm providing, not stepping into the function).=20=20 I compiled with -O0 and -g3. Put a break point in testFunc, step through w= ith step or next, and you'll see a corrupted value. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21053-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 06 15:19:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 6441 invoked by alias); 6 Mar 2017 15:19:36 -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 6405 invoked by uid 48); 6 Mar 2017 15:19:35 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Mon, 06 Mar 2017 15:19: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: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00205.txt.bz2 Content-length: 386 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #1 from Adam Stylinski --- Also not entirely sure it matters (it certainly might be calling convention dependent), but this happens on x86_64. I've not tried to reproduce it on = any other architecture. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21054-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 06 16:04:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 110975 invoked by alias); 6 Mar 2017 16:04:28 -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 110934 invoked by uid 48); 6 Mar 2017 16:04:27 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21220] "restore" for large data structures extremely slow on GNU/Linux Date: Mon, 06 Mar 2017 16:04: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00206.txt.bz2 Content-length: 322 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21220 --- Comment #1 from Andreas Arnez --- Suggested fix posted to gdb-patches mailing list: https://sourceware.org/ml/gdb-patches/2017-03/msg00042.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21055-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 06 21:09:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 121919 invoked by alias); 6 Mar 2017 21:09:27 -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 121893 invoked by uid 48); 6 Mar 2017 21:09:27 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Mon, 06 Mar 2017 21:09: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: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00207.txt.bz2 Content-length: 1281 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com --- Comment #2 from Keith Seitz --- (In reply to Adam Stylinski from comment #0) > Created attachment 9872 [details] > Minimal test case >=20 > Sorry for the convoluted summary, I'm not entirely sure how or why it > happens. The results are fine when not attached to the debugger (or in t= he > test case I'm providing, not stepping into the function).=20=20 It is not clear to me what you mean here. Does the attached test case demonstrate the problem? > I compiled with -O0 and -g3. Put a break point in testFunc, step through > with step or next, and you'll see a corrupted value. I cannot reproduce this with HEAD or 7.12.1.20170306-git. Is it possible that the compiler is re-using unused registers? "info frame", "info addr", and "disass" should be helpful here to determine if this is the happening. Out of curiosity, what compiler are you using? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21056-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 06 23:42:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 34622 invoked by alias); 6 Mar 2017 23:42:14 -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 34577 invoked by uid 48); 6 Mar 2017 23:42:12 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Mon, 06 Mar 2017 23:42: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: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00208.txt.bz2 Content-length: 5244 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #3 from Adam Stylinski --- (In reply to Keith Seitz from comment #2) > (In reply to Adam Stylinski from comment #0) > > Created attachment 9872 [details] > > Minimal test case > >=20 > > Sorry for the convoluted summary, I'm not entirely sure how or why it > > happens. The results are fine when not attached to the debugger (or in= the > > test case I'm providing, not stepping into the function).=20=20 >=20 > It is not clear to me what you mean here. Does the attached test case > demonstrate the problem? >=20 > > I compiled with -O0 and -g3. Put a break point in testFunc, step throu= gh > > with step or next, and you'll see a corrupted value. >=20 > I cannot reproduce this with HEAD or 7.12.1.20170306-git. >=20 > Is it possible that the compiler is re-using unused registers? "info fram= e", > "info addr", and "disass" should be helpful here to determine if this is = the > happening. >=20 > Out of curiosity, what compiler are you using? Yep, that test case does produce the behavior for me. I used g++, that bit might matter. I forgot to add one important bit: I added -march=3Dnative, = which my case is a Haswell based CPU. But...all optimizations should be turned o= ff, so I'm not entirely sure what that's about. In any case, while not attache= d to the debugger, I do not get this issue. adam@Crushinator:~$ g++ -v Using built-in specs. COLLECT_GCC=3Dg++ COLLECT_LTO_WRAPPER=3D/usr/lib/gcc/x86_64-pc-linux-gnu/6.3.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /build/gcc/src/gcc/configure --prefix=3D/usr --libdir=3D/u= sr/lib --libexecdir=3D/usr/lib --mandir=3D/usr/share/man --infodir=3D/usr/share/in= fo --with-bugurl=3Dhttps://bugs.archlinux.org/ --enable-languages=3Dc,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=3Dposix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=3Dgnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=3Dgnu --enable-gnu-indirect-function --disable-multilib --disable-werror --enable-checking=3Drelease Thread model: posix gcc version 6.3.1 20170109 (GCC)=20 adam@Crushinator:~$ /lib/libc.so.6=20 GNU C Library (GNU libc) stable release version 2.24, by Roland McGrath et = al. Copyright (C) 2016 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled by GNU CC version 6.1.1 20160802. Available extensions: crypt add-on version 2.1 by Michael Glad and others GNU Libidn by Simon Josefsson Native POSIX Threads Library by Ulrich Drepper et al BIND-8.2.3-T5B libc ABIs: UNIQUE IFUNC For bug reporting instructions, please see: . adam@Crushinator:~$ gdb --version GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". Without debugger: adam@Crushinator:~$ ./testfunc.out=20 lambda =3D 0.031557 With: adam@Crushinator:~$ g++ -O0 -g3 -march=3Dnative testfunc.cpp -o testfunc.out adam@Crushinator:~$ gdb ./testfunc.out=20 GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./testfunc.out...done. (gdb) break testFunc Breakpoint 1 at 0x400550: file testfunc.cpp, line 12. (gdb) r Starting program: /home/adam/testfunc.out=20 Breakpoint 1, testFunc (a=3D0x0, n=3D0, sx=3D0x0, sy=3D0x0, rc=3D0x0, nr=3D= 0, b=3D4, f=3D9.50000026e+09, c=3D0x0, d=3D0x0, e=3D0x0, gx=3D0x0, gy=3D0x0) at testf= unc.cpp:12 12 float lambda =3D C_LIGHT / f; (gdb) n 13 printf("lambda =3D %f\n", lambda); (gdb) p lambda $1 =3D -5.38359187e+25 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21057-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 06 23:47:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 43651 invoked by alias); 6 Mar 2017 23:47:47 -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 43607 invoked by uid 48); 6 Mar 2017 23:47:45 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Mon, 06 Mar 2017 23:47: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: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00209.txt.bz2 Content-length: 2103 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #4 from Adam Stylinski --- Also I did search the registers as well, and it's not in the register it sh= ould be in (xmm0) or any of the other vector registers either. I've compiled wi= th -fno-omit-frame-pointer and I still see the issue. The number of arguments= to the function seems to have an affect on whether or not the issue happens. = That was the bare minimum number of arguments before the issue showed up.=20 (gdb) disass Dump of assembler code for function testFunc(float*, unsigned long, float*, float*, float*, float, int, float, float**, float**, float**, float*, float= *): 0x0000000000400526 <+0>: push %rbp 0x0000000000400527 <+1>: mov %rsp,%rbp 0x000000000040052a <+4>: sub $0x50,%rsp 0x000000000040052e <+8>: mov %rdi,-0x18(%rbp) 0x0000000000400532 <+12>: mov %rsi,-0x20(%rbp) 0x0000000000400536 <+16>: mov %rdx,-0x28(%rbp) 0x000000000040053a <+20>: mov %rcx,-0x30(%rbp) 0x000000000040053e <+24>: mov %r8,-0x38(%rbp) 0x0000000000400542 <+28>: vmovss %xmm0,-0x3c(%rbp) 0x0000000000400547 <+33>: mov %r9d,-0x40(%rbp) 0x000000000040054b <+37>: vmovss %xmm1,-0x44(%rbp) 0x0000000000400550 <+42>: vmovss 0x11c(%rip),%xmm0 # 0x400674 0x0000000000400558 <+50>: vdivss -0x44(%rbp),%xmm0,%xmm0 0x000000000040055d <+55>: vmovss %xmm0,-0x4(%rbp) =3D> 0x0000000000400562 <+60>: vcvtss2sd -0x4(%rbp),%xmm2,%xmm2 0x0000000000400567 <+65>: vmovq %xmm2,%rax 0x000000000040056c <+70>: vmovq %rax,%xmm0 0x0000000000400571 <+75>: mov $0x400664,%edi 0x0000000000400576 <+80>: mov $0x1,%eax 0x000000000040057b <+85>: callq 0x400420 0x0000000000400580 <+90>: nop 0x0000000000400581 <+91>: leaveq=20 0x0000000000400582 <+92>: retq=20=20=20 End of assembler dump. Here are the register contents: http://pastebin.com/Mq4QVu24 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21058-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 06 23:52:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 52593 invoked by alias); 6 Mar 2017 23:52: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 52563 invoked by uid 48); 6 Mar 2017 23:52:21 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Mon, 06 Mar 2017 23:52: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: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00210.txt.bz2 Content-length: 516 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #5 from Adam Stylinski --- I also should show that is in fact corrupting the stack value through the printf statement: (gdb) n lambda =3D -53835918688661714623266816.000000 14 } Even if this was a case of just a display bug it is a debugger bug and it'd= be nice to see the correct value. Schrodingbugs are troublesome, heh. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21059-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 06 23:56:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 59046 invoked by alias); 6 Mar 2017 23:56:19 -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 59015 invoked by uid 48); 6 Mar 2017 23:56:18 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Mon, 06 Mar 2017 23:56: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: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00211.txt.bz2 Content-length: 361 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #6 from Adam Stylinski --- Playing around with -march arguments, it appears this bug might be specific= to using the VEX encoded instructions as opposed to the vanilla SSE ones. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21060-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 05:29:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89898 invoked by alias); 7 Mar 2017 05:29:39 -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 89872 invoked by uid 48); 7 Mar 2017 05:29:38 -0000 From: "richard at wetafx dot co.nz" To: gdb-prs@sourceware.org Subject: [Bug gdb/21225] New: Which version of gdb should I use for best reliability Date: Tue, 07 Mar 2017 05:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: richard at wetafx dot co.nz X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00212.txt.bz2 Content-length: 1431 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21225 Bug ID: 21225 Summary: Which version of gdb should I use for best reliability Product: gdb Version: 7.12 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: richard at wetafx dot co.nz Target Milestone: --- It seems that gdb has not been reliable for about a decade. I have been using various workarounds and hacks to avoid the problems. I have to juggle which version of gdb to use to succeed for a particular debugging task. Fortunately, the --readnow option can help in some of those circumstances e= ven with the tremendous overhead. However, gdb can still get confused and unresponsive. So, in the end, my question is quite simple: Which version of gdb should I use for the best chance of reliability? As a side question, do the developers of gdb ever use gdb to debug gdb? As additional questions, do the developers of gdb ever debug code that use = C++ or DSOs? Do the developers ever look at examples that are larger than 10K? (To answer a potential response question, yes I am getting a bit fed up. A= nd if I am getting fed up, there are many more that have given up on gdb being= a useful tool.) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21061-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 08:55:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 39317 invoked by alias); 7 Mar 2017 08:55:10 -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 39278 invoked by uid 55); 7 Mar 2017 08:55:09 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Tue, 07 Mar 2017 08:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: mishra.nitish.88 at gmail dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00213.txt.bz2 Content-length: 2122 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 --- Comment #7 from Nitish K Mishra --- Hi, Sure, I will send the patch to gdb-patches mailing list after changing the code as per your comment. Thanks for the help. Thanks and Regards, Nitish On Sat, Mar 4, 2017 at 11:02 PM, brobecker at gnat dot com wrote: > https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 > > Joel Brobecker changed: > > What |Removed |Added > -------------------------------------------------------------------------= --- > Status|UNCONFIRMED |NEW > Last reconfirmed| |2017-03-04 > CC| |brobecker at gnat dot com > Assignee|unassigned at sourceware dot org |mishra.nitish.88 = at gmail dot com > Ever confirmed|0 |1 > > --- Comment #6 from Joel Brobecker --- > To get your patch reviewed, and hopefully included in the official source= s, can > you please send it to gdb-patches@, using the information outlined in the > following page, please? > > https://sourceware.org/gdb/wiki/ContributionChecklist > > People don't necessarily follow the patches sent here. I think this is al= so > mentioned in the ContributionChecklist above, but do ping us after a coup= le of > weeks if we haven't answered, and every week thereafter. > > As a comment to your patch, the style you used for the AC_ARG_ENABLE is a= bit > different from the style we've been using so far. Not necessarily wrong, = but > there is value for us in trying to keep the style consistent. So could yo= u have > a look at the other uses of AC_ARG_ENABLE in gdb/configure.ac, and try to > mimick that with your patch? > > Thank you. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You are the assignee for the bug. > You reported the bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21062-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 10:20:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 91526 invoked by alias); 7 Mar 2017 10:20:54 -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 91383 invoked by uid 48); 7 Mar 2017 10:20:53 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21226] New: DW_OP_stack_value pieces yield wrong data on big-endian targets Date: Tue, 07 Mar 2017 10:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00214.txt.bz2 Content-length: 1593 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21226 Bug ID: 21226 Summary: DW_OP_stack_value pieces yield wrong data on big-endian targets Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: arnez at linux dot vnet.ibm.com Target Milestone: --- The guality test case pr54970.c from the GCC test suite yields lots of fail= s on s390x. The test case defines a local variable a like this: int a[] =3D { 1, 2, 3 }; and the compiler optimizes the variable away, leaving only a DWARF representation. That's intentional; the test case verifies that the variab= le can still be displayed correctly in GDB. But on s390x it can't. All eleme= nts are shown as zero instead. The compiler represents the array as a DWARF composite location with three DW_OP_stack_value pieces. Each piece is 4 bytes long, and on s390x a DWARF stack value is 8 bytes long. So GDB extracts 4 bytes out of the stack valu= e.=20 But it always uses the *lowest-addressed* bytes, independent from endiannes= s, where GCC obviously meant the *least significant* bytes to be used. On big-endian systems the lowest-addressed bytes are always zero in this case. This problem should affect all big-endian systems, whenever a DWARF location involves a DW_OP_stack_value piece that is smaller than the address size. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21063-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 10:39:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 21384 invoked by alias); 7 Mar 2017 10:39:30 -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 21334 invoked by uid 48); 7 Mar 2017 10:39:30 -0000 From: "erangi at cs dot technion.ac.il" To: gdb-prs@sourceware.org Subject: [Bug tui/21227] New: GDB crashes when switching layout from asm to src Date: Tue, 07 Mar 2017 10:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: erangi at cs dot technion.ac.il X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00215.txt.bz2 Content-length: 25005 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21227 Bug ID: 21227 Summary: GDB crashes when switching layout from asm to src Product: gdb Version: 7.11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: erangi at cs dot technion.ac.il Target Milestone: --- While debugging using gdbtui, GDB crashed when I switched layouts from asm = to src. This happened to me twice. The issue I was trying to fix appears after= an hour of execution, and I couldn't reproduce the crash on shorter runs. The crash report: *** Error in `/usr/bin/gdb': double free or corruption (!prev): 0x000000000954f820 *** =3D=3D=3D=3D=3D=3D=3D Backtrace: =3D=3D=3D=3D=3D=3D=3D=3D=3D /lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f1cc30047e5] /lib/x86_64-linux-gnu/libc.so.6(+0x7fe0a)[0x7f1cc300ce0a] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f1cc301098c] /usr/bin/gdb[0x4f6304] /usr/bin/gdb(tui_free_win_content+0x20)[0x4f6d00] /usr/bin/gdb(tui_free_all_source_wins_content+0x30)[0x4f6d50] /usr/bin/gdb[0x4f9722] /usr/bin/gdb[0x4f9e29] /usr/bin/gdb(tui_set_layout_by_name+0x9b)[0x4fa2cb] /usr/bin/gdb[0x4fa3f9] /usr/bin/gdb(execute_command+0x256)[0x69db16] /usr/bin/gdb[0x5d487c] /usr/bin/gdb[0x5d4f5f] /lib/x86_64-linux-gnu/libreadline.so.6(rl_callback_read_char+0x145)[0x7f1cc= 50286f5] /usr/bin/gdb[0x5d48d9] /usr/bin/gdb(stdin_event_handler+0x23)[0x5d4923] /usr/bin/gdb[0x5d3705] /usr/bin/gdb(gdb_do_one_event+0xb9)[0x5d38a9] /usr/bin/gdb(start_event_loop+0x4e)[0x5d39ee] /usr/bin/gdb[0x5cd3b3] /usr/bin/gdb(catch_errors+0x9d)[0x5ca1cd] /usr/bin/gdb[0x5cdfa6] /usr/bin/gdb(catch_errors+0x9d)[0x5ca1cd] /usr/bin/gdb(gdb_main+0x1b)[0x5ce87b] /usr/bin/gdb(main+0x35)[0x45eca5] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f1cc2fad830] /usr/bin/gdb(_start+0x29)[0x45ece9] =3D=3D=3D=3D=3D=3D=3D Memory map: =3D=3D=3D=3D=3D=3D=3D=3D 00400000-00a29000 r-xp 00000000 08:13 23200263=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 /usr/bin/gdb 00c29000-00c2a000 r--p 00629000 08:13 23200263=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 /usr/bin/gdb 00c2a000-00c3e000 rw-p 0062a000 08:13 23200263=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 /usr/bin/gdb 00c3e000-00c61000 rw-p 00000000 00:00 0 027a4000-0aac5000 rw-p 00000000 00:00 0 [h= eap] 7f1cb4000000-7f1cb4021000 rw-p 00000000 00:00 0 7f1cb4021000-7f1cb8000000 ---p 00000000 00:00 0 7f1cbbb7b000-7f1cbbb91000 r-xp 00000000 08:13 1835073=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f1cbbb91000-7f1cbbd90000 ---p 00016000 08:13 1835073=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f1cbbd90000-7f1cbbd91000 r--p 00015000 08:13 1835073=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f1cbbd91000-7f1cbbd92000 rw-p 00016000 08:13 1835073=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f1cbbd92000-7f1cbc012000 r--p 00620000 08:13 26216540=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.23.so 7f1cbc012000-7f1cbc177000 r--p 000df000 08:13 26216545=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libm-2.23.so 7f1cbc177000-7f1cbc196000 r--p 000b7000 08:13 4328132=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/.build-id/4d/7f52f335dc9665c2dcf308ce6514a6ae86dede.debug 7f1cbc196000-7f1cbc198000 r-xp 00000000 08:13 23204900=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/gconv/UTF-32.so 7f1cbc198000-7f1cbc397000 ---p 00002000 08:13 23204900=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/gconv/UTF-32.so 7f1cbc397000-7f1cbc398000 r--p 00001000 08:13 23204900=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/gconv/UTF-32.so 7f1cbc398000-7f1cbc399000 rw-p 00002000 08:13 23204900=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/gconv/UTF-32.so 7f1cbc399000-7f1cbc564000 r--p 006d6000 00:2c 28357232=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /home/erangi/yahoo/piwi/libpiwi.so 7f1cbc564000-7f1cbc5b4000 r--p 0089f000 08:13 26216540=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.23.so 7f1cbc5b4000-7f1cbc684000 r--p 0052b000 08:13 26216540=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.23.so 7f1cbc684000-7f1cbc720000 r--p 00490000 08:13 26216540=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.23.so 7f1cbc720000-7f1cbcb9e000 r--p 00013000 08:13 26216540=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.23.so 7f1cbcb9e000-7f1cbcbde000 rw-p 00000000 00:00 0 7f1cbcbec000-7f1cbcbf4000 r--p 00023000 08:13 26216533=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/librt-2.23.so 7f1cbcbf4000-7f1cbcbfe000 r--p 0006d000 00:2c 28357232=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /home/erangi/yahoo/piwi/libpiwi.so 7f1cbcbfe000-7f1cbcc06000 r--p 0002e000 08:13 23204321=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/libtbb.so.2 7f1cbcc06000-7f1cbcc16000 r--p 00000000 08:13 26216537=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libdl-2.23.so 7f1cbcc16000-7f1cbcc3d000 r--p 005fa000 08:13 26216540=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.23.so 7f1cbcc3d000-7f1cbcc4b000 r--p 00053000 08:13 26214755=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libgcc_s.so.1 7f1cbcc4b000-7f1cbcc57000 r--p 00048000 08:13 26214755=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libgcc_s.so.1 7f1cbcc57000-7f1cbccde000 r--p 00006000 08:13 26216545=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libm-2.23.so 7f1cbccde000-7f1cbcd1e000 rw-p 00000000 00:00 0 7f1cbcd23000-7f1cbcd28000 r--p 00092000 08:13 26214755=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libgcc_s.so.1 7f1cbcd28000-7f1cbcd70000 r--p 00001000 08:13 26214755=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libgcc_s.so.1 7f1cbcd70000-7f1cbcd9e000 r--p 000ac000 08:13 26216545=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libm-2.23.so 7f1cbcd9e000-7f1cbcf44000 r--p 03749000 00:2c 3177188=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cbcf44000-7f1cbd270000 r--p 05281000 00:2c 3177188=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cbd270000-7f1cbdb84000 r--p 038ee000 00:2c 3177188=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cbdb84000-7f1cbdc45000 r--p 03689000 00:2c 3177188=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cbdc45000-7f1cc0e1c000 r--p 004b3000 00:2c 3177188=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cc0e1c000-7f1cc11f1000 rw-p 00000000 00:00 0 7f1cc11f1000-7f1cc1226000 r--p 004f4000 00:2c 28357232=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cc1226000-7f1cc1292000 r--p 008a0000 00:2c 28357232=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cc1292000-7f1cc1441000 r--p 00528000 00:2c 28357232=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cc1441000-7f1cc145f000 r--p 004d7000 00:2c 28357232=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cc145f000-7f1cc18ba000 r--p 0007d000 00:2c 28357232=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cc18ba000-7f1cc18c2000 r-xp 00000000 08:13 1835076=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libthread_db-1.0.so 7f1cc18c2000-7f1cc1ac1000 ---p 00008000 08:13 1835076=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libthread_db-1.0.so 7f1cc1ac1000-7f1cc1ac2000 r--p 00007000 08:13 1835076=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libthread_db-1.0.so 7f1cc1ac2000-7f1cc1ac3000 rw-p 00008000 08:13 1835076=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libthread_db-1.0.so 7f1cc1ac7000-7f1cc1ae0000 r--p 00000000 08:13 26216533=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/librt-2.23.so 7f1cc1ae0000-7f1cc1b62000 r--p 00003000 08:13 4328132=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/.build-id/4d/7f52f335dc9665c2dcf308ce6514a6ae86dede.debug 7f1cc1b62000-7f1cc1b9a000 r--p 0007f000 08:13 26216526=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.23.so 7f1cc1b9a000-7f1cc1c1b000 rw-p 00000000 00:00 0 7f1cc1c1b000-7f1cc1d3b000 r--p 004cd000 00:2c 13462680=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cc1d3c000-7f1cc1d42000 r--p 00060000 08:13 26214755=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libgcc_s.so.1 7f1cc1d42000-7f1cc1d5b000 r--p 00098000 08:13 4328132=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/.build-id/4d/7f52f335dc9665c2dcf308ce6514a6ae86dede.debug 7f1cc1d5b000-7f1cc1dbc000 r--p 00001000 08:13 26216526=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.23.so 7f1cc1dbc000-7f1cc1ddb000 r--p 0023c000 00:2c 13462680=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cc1ddd000-7f1cc1de4000 r--p 000d9000 08:13 26216545=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libm-2.23.so 7f1cc1de4000-7f1cc1de9000 r--p 0001c000 08:13 26216533=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/librt-2.23.so 7f1cc1de9000-7f1cc1df1000 r--p 000b0000 08:13 4328132=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/.build-id/4d/7f52f335dc9665c2dcf308ce6514a6ae86dede.debug 7f1cc1df1000-7f1cc1df7000 r--p 000d5000 08:13 4328132=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/.build-id/4d/7f52f335dc9665c2dcf308ce6514a6ae86dede.debug 7f1cc1df7000-7f1cc1e0c000 r--p 00084000 08:13 4328132=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/.build-id/4d/7f52f335dc9665c2dcf308ce6514a6ae86dede.debug 7f1cc1e0c000-7f1cc1e1b000 r--p 0006b000 08:13 26216526=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.23.so 7f1cc1e1b000-7f1cc1e62000 r--p 005ec000 00:2c 13462680=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cc1e62000-7f1cc20d6000 r--p 0025a000 00:2c 13462680=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cc20d6000-7f1cc22c4000 r--p 00044000 00:2c 13462680=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cc22c4000-7f1cc2344000 rw-p 00000000 00:00 0 7f1cc2344000-7f1cc234a000 r--p 0003b000 00:2c 13462680=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cc234a000-7f1cc2353000 r--p 000b6000 08:13 26216526=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.23.so 7f1cc2384000-7f1cc2604000 rw-p 00000000 00:00 0 7f1cc2604000-7f1cc2672000 r-xp 00000000 08:13 1835158=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libpcre.so.3.13.2 7f1cc2672000-7f1cc2872000 ---p 0006e000 08:13 1835158=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libpcre.so.3.13.2 7f1cc2872000-7f1cc2873000 r--p 0006e000 08:13 1835158=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libpcre.so.3.13.2 7f1cc2873000-7f1cc2874000 rw-p 0006f000 08:13 1835158=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libpcre.so.3.13.2 7f1cc2874000-7f1cc2878000 r-xp 00000000 08:13 1835113=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libuuid.so.1.3.0 7f1cc2878000-7f1cc2a77000 ---p 00004000 08:13 1835113=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libuuid.so.1.3.0 7f1cc2a77000-7f1cc2a78000 r--p 00003000 08:13 1835113=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libuuid.so.1.3.0 7f1cc2a78000-7f1cc2a79000 rw-p 00004000 08:13 1835113=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libuuid.so.1.3.0 7f1cc2a79000-7f1cc2b88000 r-xp 00000000 08:13 1835592=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2 7f1cc2b88000-7f1cc2d87000 ---p 0010f000 08:13 1835592=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2 7f1cc2d87000-7f1cc2d88000 r--p 0010e000 08:13 1835592=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2 7f1cc2d88000-7f1cc2d89000 rw-p 0010f000 08:13 1835592=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2 7f1cc2d89000-7f1cc2d8a000 rw-p 00000000 00:00 0 7f1cc2d8a000-7f1cc2d8c000 r-xp 00000000 08:13 1835078=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libutil-2.23.so 7f1cc2d8c000-7f1cc2f8b000 ---p 00002000 08:13 1835078=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libutil-2.23.so 7f1cc2f8b000-7f1cc2f8c000 r--p 00001000 08:13 1835078=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libutil-2.23.so 7f1cc2f8c000-7f1cc2f8d000 rw-p 00002000 08:13 1835078=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libutil-2.23.so 7f1cc2f8d000-7f1cc314c000 r-xp 00000000 08:13 1835120=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libc-2.23.so 7f1cc314c000-7f1cc334c000 ---p 001bf000 08:13 1835120=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libc-2.23.so 7f1cc334c000-7f1cc3350000 r--p 001bf000 08:13 1835120=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libc-2.23.so 7f1cc3350000-7f1cc3352000 rw-p 001c3000 08:13 1835120=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libc-2.23.so 7f1cc3352000-7f1cc3356000 rw-p 00000000 00:00 0 7f1cc3356000-7f1cc338e000 r-xp 00000000 08:13 23200275=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/libbabeltrace-ctf.so.1.0.0 7f1cc338e000-7f1cc358d000 ---p 00038000 08:13 23200275=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/libbabeltrace-ctf.so.1.0.0 7f1cc358d000-7f1cc358f000 r--p 00037000 08:13 23200275=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/libbabeltrace-ctf.so.1.0.0 7f1cc358f000-7f1cc3590000 rw-p 00039000 08:13 23200275=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/libbabeltrace-ctf.so.1.0.0 7f1cc3590000-7f1cc359c000 r-xp 00000000 08:13 23200233=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/libbabeltrace.so.1.0.0 7f1cc359c000-7f1cc379b000 ---p 0000c000 08:13 23200233=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/libbabeltrace.so.1.0.0 7f1cc379b000-7f1cc379c000 r--p 0000b000 08:13 23200233=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/libbabeltrace.so.1.0.0 7f1cc379c000-7f1cc379d000 rw-p 0000c000 08:13 23200233=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/libbabeltrace.so.1.0.0 7f1cc379d000-7f1cc37be000 r-xp 00000000 08:13 1835213=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/liblzma.so.5.0.0 7f1cc37be000-7f1cc39bd000 ---p 00021000 08:13 1835213=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/liblzma.so.5.0.0 7f1cc39bd000-7f1cc39be000 r--p 00020000 08:13 1835213=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/liblzma.so.5.0.0 7f1cc39be000-7f1cc39bf000 rw-p 00021000 08:13 1835213=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/liblzma.so.5.0.0 7f1cc39bf000-7f1cc39e5000 r-xp 00000000 08:13 1835167=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libexpat.so.1.6.0 7f1cc39e5000-7f1cc3be5000 ---p 00026000 08:13 1835167=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libexpat.so.1.6.0 7f1cc3be5000-7f1cc3be7000 r--p 00026000 08:13 1835167=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libexpat.so.1.6.0 7f1cc3be7000-7f1cc3be8000 rw-p 00028000 08:13 1835167=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libexpat.so.1.6.0 7f1cc3be8000-7f1cc3c00000 r-xp 00000000 08:13 1835127=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libpthread-2.23.so 7f1cc3c00000-7f1cc3dff000 ---p 00018000 08:13 1835127=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libpthread-2.23.so 7f1cc3dff000-7f1cc3e00000 r--p 00017000 08:13 1835127=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libpthread-2.23.so 7f1cc3e00000-7f1cc3e01000 rw-p 00018000 08:13 1835127=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libpthread-2.23.so 7f1cc3e01000-7f1cc3e05000 rw-p 00000000 00:00 0 7f1cc3e05000-7f1cc41c3000 r-xp 00000000 08:13 23211230=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 7f1cc41c3000-7f1cc43c2000 ---p 003be000 08:13 23211230=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 7f1cc43c2000-7f1cc43c4000 r--p 003bd000 08:13 23211230=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 7f1cc43c4000-7f1cc445b000 rw-p 003bf000 08:13 23211230=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 7f1cc445b000-7f1cc448c000 rw-p 00000000 00:00 0 7f1cc448c000-7f1cc4594000 r-xp 00000000 08:13 1835126=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libm-2.23.so 7f1cc4594000-7f1cc4793000 ---p 00108000 08:13 1835126=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libm-2.23.so 7f1cc4793000-7f1cc4794000 r--p 00107000 08:13 1835126=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libm-2.23.so 7f1cc4794000-7f1cc4795000 rw-p 00108000 08:13 1835126=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libm-2.23.so 7f1cc4795000-7f1cc47ba000 r-xp 00000000 08:13 1835221=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7f1cc47ba000-7f1cc49b9000 ---p 00025000 08:13 1835221=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7f1cc49b9000-7f1cc49bd000 r--p 00024000 08:13 1835221=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7f1cc49bd000-7f1cc49be000 rw-p 00028000 08:13 1835221=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7f1cc49be000-7f1cc49df000 r-xp 00000000 08:13 1835185=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libncurses.so.5.9 7f1cc49df000-7f1cc4bde000 ---p 00021000 08:13 1835185=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libncurses.so.5.9 7f1cc4bde000-7f1cc4bdf000 r--p 00020000 08:13 1835185=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libncurses.so.5.9 7f1cc4bdf000-7f1cc4be0000 rw-p 00021000 08:13 1835185=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libncurses.so.5.9 7f1cc4be0000-7f1cc4be3000 r-xp 00000000 08:13 1835112=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libdl-2.23.so 7f1cc4be3000-7f1cc4de2000 ---p 00003000 08:13 1835112=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libdl-2.23.so 7f1cc4de2000-7f1cc4de3000 r--p 00002000 08:13 1835112=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libdl-2.23.so 7f1cc4de3000-7f1cc4de4000 rw-p 00003000 08:13 1835112=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libdl-2.23.so 7f1cc4de4000-7f1cc4dfd000 r-xp 00000000 08:13 1835955=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libz.so.1.2.8 7f1cc4dfd000-7f1cc4ffc000 ---p 00019000 08:13 1835955=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libz.so.1.2.8 7f1cc4ffc000-7f1cc4ffd000 r--p 00018000 08:13 1835955=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libz.so.1.2.8 7f1cc4ffd000-7f1cc4ffe000 rw-p 00019000 08:13 1835955=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libz.so.1.2.8 7f1cc4ffe000-7f1cc503b000 r-xp 00000000 08:13 1837537=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libreadline.so.6.3 7f1cc503b000-7f1cc523b000 ---p 0003d000 08:13 1837537=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libreadline.so.6.3 7f1cc523b000-7f1cc523d000 r--p 0003d000 08:13 1837537=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libreadline.so.6.3 7f1cc523d000-7f1cc5243000 rw-p 0003f000 08:13 1837537=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libreadline.so.6.3 7f1cc5243000-7f1cc5244000 rw-p 00000000 00:00 0 7f1cc5244000-7f1cc526a000 r-xp 00000000 08:13 1835074=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/ld-2.23.so 7f1cc526c000-7f1cc5277000 r--p 00061000 08:13 26216526=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.23.so 7f1cc5277000-7f1cc5287000 r--p 00243000 08:13 26216545=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libm-2.23.so 7f1cc5287000-7f1cc52a8000 r--p 0008c000 08:13 26216545=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/libm-2.23.so 7f1cc52a8000-7f1cc5440000 r--p 00000000 08:13 23205801=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/locale/locale-archive 7f1cc5440000-7f1cc544a000 rw-p 00000000 00:00 0 7f1cc544b000-7f1cc544c000 rw-p 00000000 00:00 0 7f1cc544c000-7f1cc5453000 r--p 00079000 08:13 26216526=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.23.so 7f1cc5453000-7f1cc5454000 rw-p 00000000 00:00 0 7f1cc5454000-7f1cc5460000 r--p 00231000 00:2c 13462680=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 [debugged program] 7f1cc5460000-7f1cc5467000 r--s 00000000 08:13 23204883=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 /usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache 7f1cc5467000-7f1cc5469000 rw-p 00000000 00:00 0 7f1cc5469000-7f1cc546a000 r--p 00025000 08:13 1835074=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/ld-2.23.so 7f1cc546a000-7f1cc546b000 rw-p 00026000 08:13 1835074=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/ld-2.23.so 7f1cc546b000-7f1cc546c000 rw-p 00000000 00:00 0 7fff9bf1d000-7fff9bf3e000 rw-p 00000000 00:00 0=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 [stack] 7fff9bf45000-7fff9bf47000 r--p 00000000 00:00 0 [v= var] 7fff9bf47000-7fff9bf49000 r-xp 00000000 00:00 0 [v= dso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 [vsyscall] --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21065-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 12:13:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78387 invoked by alias); 7 Mar 2017 12:13:57 -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 78361 invoked by uid 48); 7 Mar 2017 12:13:56 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Tue, 07 Mar 2017 12:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: mishra.nitish.88 at gmail dot com X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created 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: 2017-q1/txt/msg00217.txt.bz2 Content-length: 628 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 Nitish K Mishra changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #9860|0 |1 is obsolete| | --- Comment #9 from Nitish K Mishra --- Created attachment 9878 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9878&action=3Dedit Updated ChangeLog --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21064-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 12:13:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 77524 invoked by alias); 7 Mar 2017 12:13:13 -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 77473 invoked by uid 48); 7 Mar 2017 12:13:13 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Tue, 07 Mar 2017 12:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: mishra.nitish.88 at gmail dot com X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created 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: 2017-q1/txt/msg00216.txt.bz2 Content-length: 624 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 Nitish K Mishra changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #9850|0 |1 is obsolete| | --- Comment #8 from Nitish K Mishra --- Created attachment 9877 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9877&action=3Dedit Updated patch --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21067-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 12:21:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 2419 invoked by alias); 7 Mar 2017 12:21:24 -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 2324 invoked by uid 55); 7 Mar 2017 12:21:23 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Tue, 07 Mar 2017 12:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: mishra.nitish.88 at gmail dot com X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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: 2017-q1/txt/msg00219.txt.bz2 Content-length: 344 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 --- Comment #11 from Nitish K Mishra --- Created attachment 9880 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9880&action=3Dedit disable_static_linking.patch --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21066-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 12:21:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 2314 invoked by alias); 7 Mar 2017 12:21: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 2282 invoked by uid 55); 7 Mar 2017 12:21:23 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Tue, 07 Mar 2017 12:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: mishra.nitish.88 at gmail dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00218.txt.bz2 Content-length: 2816 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 --- Comment #10 from Nitish K Mishra --- Hi, I have updated the patch as per your comment and sent it to gdb-patches@ and have uploaded the same to the PR 21187 on bugzilla. I am attaching one copy here as well. Please find the attachme= nt. One thing more, Yao Qi told me that configure.ac file is maintained by gcc community, So I should sent the patch to gcc-patches@ and get approval from there. So, I am mailing one copy of the patch there as well. I am new to the community, so, don't have much exposure here. Anything else I need to do or follow-up ? Thanks and Regards, Nitish On Tue, Mar 7, 2017 at 2:24 PM, Nitish Kumar Mishra wrote: > Hi, > > Sure, I will send the patch to gdb-patches mailing list after changing > the code as per your comment. > Thanks for the help. > > Thanks and Regards, > Nitish > > > On Sat, Mar 4, 2017 at 11:02 PM, brobecker at gnat dot com > wrote: >> https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 >> >> Joel Brobecker changed: >> >> What |Removed |Added >> ------------------------------------------------------------------------= ---- >> Status|UNCONFIRMED |NEW >> Last reconfirmed| |2017-03-04 >> CC| |brobecker at gnat dot c= om >> Assignee|unassigned at sourceware dot org |mishra.nitish.88= at gmail dot com >> Ever confirmed|0 |1 >> >> --- Comment #6 from Joel Brobecker --- >> To get your patch reviewed, and hopefully included in the official sourc= es, can >> you please send it to gdb-patches@, using the information outlined in the >> following page, please? >> >> https://sourceware.org/gdb/wiki/ContributionChecklist >> >> People don't necessarily follow the patches sent here. I think this is a= lso >> mentioned in the ContributionChecklist above, but do ping us after a cou= ple of >> weeks if we haven't answered, and every week thereafter. >> >> As a comment to your patch, the style you used for the AC_ARG_ENABLE is = a bit >> different from the style we've been using so far. Not necessarily wrong,= but >> there is value for us in trying to keep the style consistent. So could y= ou have >> a look at the other uses of AC_ARG_ENABLE in gdb/configure.ac, and try to >> mimick that with your patch? >> >> Thank you. >> >> -- >> You are receiving this mail because: >> You are on the CC list for the bug. >> You are the assignee for the bug. >> You reported the bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21068-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 12:23:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4808 invoked by alias); 7 Mar 2017 12:23:35 -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 4782 invoked by uid 48); 7 Mar 2017 12:23:34 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21226] DW_OP_stack_value pieces yield wrong data on big-endian targets Date: Tue, 07 Mar 2017 12:23: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00220.txt.bz2 Content-length: 421 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21226 --- Comment #1 from Andreas Arnez --- An old version of GDB's DWARF stack value piece handling took the pieces fr= om the LSB end, as it should. But this was broken when adding typed DWARF sta= ck support (bug 12617, commit 8a9b8146fd) in May 2011. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21069-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 12:37:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 51223 invoked by alias); 7 Mar 2017 12:37:08 -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 51194 invoked by uid 48); 7 Mar 2017 12:37:08 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Tue, 07 Mar 2017 12:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: mishra.nitish.88 at gmail dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00221.txt.bz2 Content-length: 497 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 --- Comment #12 from Nitish K Mishra --- Please ignore "Updated patch" and "Updated ChangeLog" attachment, as they a= re duplicate of "disable_static_linking.patch" and "Changelog.txt" respectivel= y. Mistakenly, I uploaded the files here and sent it via mail as well, so they= got duplicated. Sorry for the inconvenience. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21070-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 12:59:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 73727 invoked by alias); 7 Mar 2017 12:59:42 -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 71858 invoked by uid 48); 7 Mar 2017 12:59:40 -0000 From: "orgads at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20977] GDB exception handling is broken on i686-w64-mingw32 Date: Tue, 07 Mar 2017 12:59: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: orgads at gmail 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: 7.12.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q1/txt/msg00222.txt.bz2 Content-length: 2424 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20977 Orgad Shaneh changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |orgads at gmail dot com --- Comment #5 from Orgad Shaneh --- It still happens with 7.12.1 when I type an invalid command. Trace: 1 msvcrt!abort 2 uw_init_context_1 3 _Unwind_RaiseException 4 __cxa_throw 5 throw_exception_cxx common-exceptions.c 303 6 throw_exception common-exceptions.c 317 7 throw_it common-exceptions.c 373 8 throw_verror common-exceptions.c 379 9 verror utils.c 525 10 error errors.c 43 11 undef_cmd_error cli-decode.c 1475 12 lookup_cmd cli-decode.c 1517 13 execute_command top.c 630 14 command_handler event-top.c 641 15 command_line_handler event-top.c 833 16 gdb_rl_callback_handler event-top.c 213 17 rl_callback_read_char callback.c 220 18 gdb_rl_callback_read_char_wrapper_noexcept event-top.c 175 19 gdb_rl_callback_read_char_wrapper event-top.c 192 20 stdin_event_handler event-top.c 568 21 handle_file_event event-loop.c 733 22 gdb_wait_for_event event-loop.c 884 23 gdb_do_one_event event-loop.c 347 24 gdb_do_one_event common-exceptions.h 225 25 start_event_loop event-loop.c 371 26 captured_command_loop main.c 324 27 catch_errors exceptions.c 236 28 captured_main main.c 1149 29 gdb_main main.c 1159 30 main gdb.c 32 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21071-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 13:02:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 13017 invoked by alias); 7 Mar 2017 13:02:44 -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 11196 invoked by uid 48); 7 Mar 2017 13:02:43 -0000 From: "orgads at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21078] gdb compiled with mingw32 crashes on Windows7 when entering any invalid command Date: Tue, 07 Mar 2017 13:02: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: orgads at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00223.txt.bz2 Content-length: 2454 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21078 Orgad Shaneh changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |orgads at gmail dot com --- Comment #1 from Orgad Shaneh --- Looks like a C++ exception is thrown by error(), but it is not catched in catch_errors(). Trace: 1 msvcrt!abort 2 uw_init_context_1 3 _Unwind_RaiseException 4 __cxa_throw 5 throw_exception_cxx common-exceptions.c 303 6 throw_exception common-exceptions.c 317 7 throw_it common-exceptions.c 373 8 throw_verror common-exceptions.c 379 9 verror utils.c 525 10 error errors.c 43 11 undef_cmd_error cli-decode.c 1475 12 lookup_cmd cli-decode.c 1517 13 execute_command top.c 630 14 command_handler event-top.c 641 15 command_line_handler event-top.c 833 16 gdb_rl_callback_handler event-top.c 213 17 rl_callback_read_char callback.c 220 18 gdb_rl_callback_read_char_wrapper_noexcept event-top.c 175 19 gdb_rl_callback_read_char_wrapper event-top.c 192 20 stdin_event_handler event-top.c 568 21 handle_file_event event-loop.c 733 22 gdb_wait_for_event event-loop.c 884 23 gdb_do_one_event event-loop.c 347 24 gdb_do_one_event common-exceptions.h 225 25 start_event_loop event-loop.c 371 26 captured_command_loop main.c 324 27 catch_errors exceptions.c 236 28 captured_main main.c 1149 29 gdb_main main.c 1159 30 main gdb.c 32 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21072-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 14:52:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 102826 invoked by alias); 7 Mar 2017 14:52:04 -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 102787 invoked by uid 48); 7 Mar 2017 14:52:03 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20977] GDB exception handling is broken on i686-w64-mingw32 Date: Tue, 07 Mar 2017 14:52: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: 7.12.1 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: 2017-q1/txt/msg00224.txt.bz2 Content-length: 2510 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20977 --- Comment #6 from Yao Qi --- (In reply to Orgad Shaneh from comment #5) > It still happens with 7.12.1 when I type an invalid command. Trace: >=20 > 1 msvcrt!abort > 2 uw_init_context_1 > 3 _Unwind_RaiseException > 4 __cxa_throw > 5 throw_exception_cxx common-exceptions.c 303 > 6 throw_exception common-exceptions.c 317 > 7 throw_it common-exceptions.c 373 > 8 throw_verror common-exceptions.c 379 > 9 verror utils.c 525 > 10 error errors.c 43 > 11 undef_cmd_error cli-decode.c 1475 > 12 lookup_cmd cli-decode.c 1517 > 13 execute_command top.c 630 > 14 command_handler event-top.c 641 > 15 command_line_handler event-top.c 833 > 16 gdb_rl_callback_handler event-top.c 213 > 17 rl_callback_read_char callback.c 220 > 18 gdb_rl_callback_read_char_wrapper_noexcept event-top.c 175 > 19 gdb_rl_callback_read_char_wrapper event-top.c 192 > 20 stdin_event_handler event-top.c 568 > 21 handle_file_event event-loop.c 733 > 22 gdb_wait_for_event event-loop.c 884 > 23 gdb_do_one_event event-loop.c 347 > 24 gdb_do_one_event common-exceptions.h 225 > 25 start_event_loop event-loop.c 371 > 26 captured_command_loop main.c 324 > 27 catch_errors exceptions.c 236 > 28 captured_main main.c 1149 > 29 gdb_main main.c 1159 > 30 main gdb.c 32 What is your compiler building GDB? So far, we only tested on DW2 and SJLJ exception implementations. If your compiler is MSVC, Structured Exception Handling (SEH) is possibly used. As far as I am aware of, we didn't test it before. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21073-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 14:53:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 6029 invoked by alias); 7 Mar 2017 14:53:40 -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 5988 invoked by uid 48); 7 Mar 2017 14:53:39 -0000 From: "orgads at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20977] GDB exception handling is broken on i686-w64-mingw32 Date: Tue, 07 Mar 2017 14:53: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: orgads at gmail 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: 7.12.1 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: 2017-q1/txt/msg00225.txt.bz2 Content-length: 426 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20977 --- Comment #7 from Orgad Shaneh --- > What is your compiler building GDB? mingw32 (on msys2 environment). It works fine with mingw64, but fails with = 32. There's actually a separate bug report for this: https://sourceware.org/bugzilla/show_bug.cgi?id=3D21078 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21074-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 15:05:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66135 invoked by alias); 7 Mar 2017 15:05:25 -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 66103 invoked by uid 48); 7 Mar 2017 15:05:24 -0000 From: "orgads at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21078] gdb compiled with mingw32 crashes on Windows7 when entering any invalid command Date: Tue, 07 Mar 2017 15:05: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: orgads at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00226.txt.bz2 Content-length: 269 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21078 --- Comment #2 from Orgad Shaneh --- Actually the exception should be catched in gdb_rl_callback_handler. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21075-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 15:14:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 96423 invoked by alias); 7 Mar 2017 15:14:13 -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 96380 invoked by uid 48); 7 Mar 2017 15:14:12 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20977] GDB exception handling is broken on i686-w64-mingw32 Date: Tue, 07 Mar 2017 15:14: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: 7.12.1 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: 2017-q1/txt/msg00227.txt.bz2 Content-length: 618 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20977 --- Comment #8 from Yao Qi --- (In reply to Orgad Shaneh from comment #7) > > What is your compiler building GDB? >=20 > mingw32 (on msys2 environment). It works fine with mingw64, but fails with > 32. >=20 Could you elaborate on what does work and what doesn't (mingw32 and mingw64= )?=20 This PR is about i686-w64-mingw32, and it was fixed. > There's actually a separate bug report for this: > https://sourceware.org/bugzilla/show_bug.cgi?id=3D21078 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21076-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 15:17:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107119 invoked by alias); 7 Mar 2017 15:17:38 -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 107089 invoked by uid 48); 7 Mar 2017 15:17:38 -0000 From: "orgads at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20977] GDB exception handling is broken on i686-w64-mingw32 Date: Tue, 07 Mar 2017 15:17: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: orgads at gmail 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: 7.12.1 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: 2017-q1/txt/msg00228.txt.bz2 Content-length: 455 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20977 --- Comment #9 from Orgad Shaneh --- > Could you elaborate on what does work and what doesn't (mingw32 and mingw= 64)? This PR is about i686-w64-mingw32, and it was fixed. mingw64 seems to work fine. mingw32 (i686-w64-mingw32) crashes when entering an invalid command. Tested with 7.12.1. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21077-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 15:20:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109961 invoked by alias); 7 Mar 2017 15:20:59 -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 109879 invoked by uid 48); 7 Mar 2017 15:20:58 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20977] GDB exception handling is broken on i686-w64-mingw32 Date: Tue, 07 Mar 2017 15:20: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat 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: 7.12.1 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: 2017-q1/txt/msg00229.txt.bz2 Content-length: 366 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20977 --- Comment #10 from Pedro Alves --- #1 - What does "i686-w64-mingw32-gcc -v" say? Is this a SJLJ or a DW2 toolchain? #2 - Could you try relinking gdb without -static-libgcc and -static-libstdc= ++ ? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21078-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 15:38:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64219 invoked by alias); 7 Mar 2017 15:38:55 -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 64183 invoked by uid 48); 7 Mar 2017 15:38:54 -0000 From: "orgads at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20977] GDB exception handling is broken on i686-w64-mingw32 Date: Tue, 07 Mar 2017 15:38: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: orgads at gmail 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: 7.12.1 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: 2017-q1/txt/msg00230.txt.bz2 Content-length: 430 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20977 --- Comment #11 from Orgad Shaneh --- > #1 - What does "i686-w64-mingw32-gcc -v" say? Is this a SJLJ or a DW2 to= olchain? --disable-sjlj-exceptions --with-dwarf2 > #2 - Could you try relinking gdb without -static-libgcc and -static-libst= dc++ ? That solves it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21079-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 15:46:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 116496 invoked by alias); 7 Mar 2017 15:46:24 -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 116456 invoked by uid 48); 7 Mar 2017 15:46:23 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20977] GDB exception handling is broken on i686-w64-mingw32 Date: Tue, 07 Mar 2017 15:46: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat 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: 7.12.1 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: 2017-q1/txt/msg00231.txt.bz2 Content-length: 406 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20977 --- Comment #12 from Pedro Alves --- > > #2 - Could you try relinking gdb without -static-libgcc and -static-lib= stdc++ ? > That solves it. OK, there's a pending patch to add a configure option to disable those alre= ady. See bug 21187. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21080-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 15:56:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 30106 invoked by alias); 7 Mar 2017 15:56:09 -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 30077 invoked by uid 48); 7 Mar 2017 15:56:09 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/12616] gdb does not implement DW_AT_data_bit_offset Date: Tue, 07 Mar 2017 15:56: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: HEAD X-Bugzilla-Keywords: archer X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: arnez at linux dot vnet.ibm.com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to 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: 2017-q1/txt/msg00232.txt.bz2 Content-length: 475 https://sourceware.org/bugzilla/show_bug.cgi?id=3D12616 Andreas Arnez changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at sourceware dot org |arnez at linux dot = vnet.ibm.com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21081-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 15:59:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35068 invoked by alias); 7 Mar 2017 15:59:01 -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 35039 invoked by uid 48); 7 Mar 2017 15:59:01 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/12616] gdb does not implement DW_AT_data_bit_offset Date: Tue, 07 Mar 2017 15:59: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: HEAD X-Bugzilla-Keywords: archer X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: arnez at linux dot vnet.ibm.com 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00233.txt.bz2 Content-length: 826 https://sourceware.org/bugzilla/show_bug.cgi?id=3D12616 Andreas Arnez changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Andreas Arnez --- (In reply to cvs-commit@gcc.gnu.org from comment #3) > The master branch has been updated by Andreas Arnez : >=20 > https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git; > h=3Dda5b30da2d1167591aa8d71b543f97bfdc2ec2a2 This commit fixes the missing support for DW_AT_data_bit_offset. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21082-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 16:05:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 58851 invoked by alias); 7 Mar 2017 16:05:38 -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 58824 invoked by uid 48); 7 Mar 2017 16:05:37 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21220] "restore" for large data structures extremely slow on GNU/Linux Date: Tue, 07 Mar 2017 16:05: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: arnez at linux dot vnet.ibm.com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed 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: 2017-q1/txt/msg00234.txt.bz2 Content-length: 586 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21220 Andreas Arnez changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-03-07 Assignee|unassigned at sourceware dot org |arnez at linux dot = vnet.ibm.com Ever confirmed|0 |1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21083-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 16:08:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 72143 invoked by alias); 7 Mar 2017 16:08:24 -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 72119 invoked by uid 48); 7 Mar 2017 16:08:23 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21226] DW_OP_stack_value pieces yield wrong data on big-endian targets Date: Tue, 07 Mar 2017 16:08: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: arnez at linux dot vnet.ibm.com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: 2017-q1/txt/msg00235.txt.bz2 Content-length: 417 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21226 Andreas Arnez changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |arnez at linux dot = vnet.ibm.com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21084-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 16:09:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 73678 invoked by alias); 7 Mar 2017 16:09:07 -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 73600 invoked by uid 48); 7 Mar 2017 16:09:06 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21226] DW_OP_stack_value pieces yield wrong data on big-endian targets Date: Tue, 07 Mar 2017 16:09: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: arnez at linux dot vnet.ibm.com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed 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: 2017-q1/txt/msg00236.txt.bz2 Content-length: 496 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21226 Andreas Arnez changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-03-07 Ever confirmed|0 |1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21085-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 17:18:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 129079 invoked by alias); 7 Mar 2017 17:18:18 -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 129036 invoked by uid 48); 7 Mar 2017 17:18:16 -0000 From: "orgads at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21078] gdb compiled with mingw32 crashes on Windows7 when entering any invalid command Date: Tue, 07 Mar 2017 17:18: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: orgads at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00237.txt.bz2 Content-length: 303 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21078 --- Comment #3 from Orgad Shaneh --- Linking without -static-libstdc++ and -static-libgcc fixes this. There's a pending patch in bug 21187. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21086-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 17:48:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31946 invoked by alias); 7 Mar 2017 17:48:46 -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 31913 invoked by uid 48); 7 Mar 2017 17:48:45 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/21206] gdb-7.12.1 for arm-rtems4.12 fails to build on FreeBSD 11.0 Date: Tue, 07 Mar 2017 17:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: jhb at FreeBSD dot org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00238.txt.bz2 Content-length: 1786 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21206 jhb at FreeBSD dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jhb at FreeBSD dot org --- Comment #4 from jhb at FreeBSD dot org --- The issue is that the gnulib test checks for max_align_t using the C compil= er but gdb is then compiled as C++. On FreeBSD 11.0, max_align_t is not defin= ed in C, but is defined by libc++ when using C++. Thus, the configure tests gnulib runs don't find max_align_t, but when compiling with C++ the definit= ion in libc++'s triggers the error. I've fixed this in FreeBSD upstream by defining a proper max_align_t (the o= ne in libc++ doesn't match the ABI of the one GCC uses) in both C and C++ in t= he base OS . Additionally, in the port of gdb in the FreeBSD ports = tree I use a local patch to disable the use of max_align_t from the gnulib heade= r as a workaround for FreeBSD versions without max_align_t defined in C. The relevant commits to FreeBSD are: https://svnweb.freebsd.org/base?view=3Drevision&revision=3D307756 https://svnweb.freebsd.org/base?view=3Drevision&revision=3D309274 (both of which are merged to 11 and will be present in 11.1 when it is released). The hacky patch I use in the gdb port on FreeBSD is: https://svnweb.freebsd.org/ports/head/devel/gdb/files/patch-gdb-gnulib-impo= rt-stddef.in.h?view=3Dco (The irony is that neither GDB nor binutils even use max_align_t.) I chose to fix the issue in this was as I considered the lack of max_align_t (which C11 requires) when compiling C in FreeBSD the bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21087-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 21:44:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 34829 invoked by alias); 7 Mar 2017 21:44:48 -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 34790 invoked by uid 48); 7 Mar 2017 21:44:47 -0000 From: "chrisj at rtems dot org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/21206] gdb-7.12.1 for arm-rtems4.12 fails to build on FreeBSD 11.0 Date: Tue, 07 Mar 2017 21:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: chrisj at rtems dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00239.txt.bz2 Content-length: 606 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21206 Chris Johns changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #5 from Chris Johns --- Thanks John, the patches resolve the issue for me. I will close this bug as invalid as it does not effect GDB. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21088-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 07 23:59:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 105966 invoked by alias); 7 Mar 2017 23:59:50 -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 105915 invoked by uid 48); 7 Mar 2017 23:59:49 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21216] [8.0 regression]: TUI line breaks regression Date: Tue, 07 Mar 2017 23:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc 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: 2017-q1/txt/msg00240.txt.bz2 Content-length: 611 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21216 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|regression: TUI by: |[8.0 regression]: TUI line |Eliminate |breaks regression |make_cleanup_ui_file_delete | |/ make ui_file a class | |hierarchy | --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21089-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 00:19:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 130842 invoked by alias); 8 Mar 2017 00:19:09 -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 130818 invoked by uid 55); 8 Mar 2017 00:19:08 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tui/21216] [8.0 regression]: TUI line breaks regression Date: Wed, 08 Mar 2017 00:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00241.txt.bz2 Content-length: 2603 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21216 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D9753a2f6d74d= c92d2ad94993a5479ee0edbc6887 commit 9753a2f6d74dc92d2ad94993a5479ee0edbc6887 Author: Pedro Alves Date: Wed Mar 8 00:14:59 2017 +0000 Fix PR tui/21216: TUI line breaks regression Commit d7e747318f4d04 ("Eliminate make_cleanup_ui_file_delete / make ui_file a class hierarchy") regressed the TUI's command window. Newlines miss doing a "carriage return", resulting in output like: ~~~~~~~~~~~~~~~~~~ (gdb) helpList of classes of commands: aliases -- Aliases of other comma= nds =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20 breakpoints -- Making program stop at certain points ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Before the commit mentioned above, the default ui_file->to_write implementation had a hack that would defer into the ui_file->to_fputs method. The TUI's ui_file did not implement the to_write method, so all writes would end up going to the ncurses window via tui_file_fputs -> tui_puts. After the commit above, the hack is gone, but the TUI's ui_file still does not implement the ui_file::write method. Since tui_file inherits from stdio_file, writing to a tui_file ends up doing fwrite on the FILE stream the TUI is "associated" with, via stdio_file::write, instead of writing to the ncurses window. The fix is to have tui_file override the "write" method. New test included. gdb/ChangeLog: 2017-03-08 Pedro Alves PR tui/21216 * tui/tui-file.c (tui_file::write): New. * tui/tui-file.h (tui_file): Override "write". * tui/tui-io.c (do_tui_putc, update_start_line): New functions, factored out from ... (tui_puts): ... here. (tui_putc): Use them. (tui_write): New function. * tui/tui-io.h (tui_write): Declare. gdb/testsuite/ChangeLog: 2017-03-08 Pedro Alves PR tui/21216 * gdb.tui/tui-nl-filtered-output.exp: New file. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21090-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 00:20:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3637 invoked by alias); 8 Mar 2017 00:20:38 -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 3578 invoked by uid 48); 8 Mar 2017 00:20:38 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21216] [8.0 regression]: TUI line breaks regression Date: Wed, 08 Mar 2017 00:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00242.txt.bz2 Content-length: 535 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21216 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Pedro Alves --- Fixed. Thanks for bisecting/reporting. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21091-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 07:47:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79928 invoked by alias); 8 Mar 2017 07:47:50 -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 79893 invoked by uid 48); 8 Mar 2017 07:47:49 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/21206] gdb-7.12.1 for arm-rtems4.12 fails to build on FreeBSD 11.0 Date: Wed, 08 Mar 2017 07:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: 2017-q1/txt/msg00243.txt.bz2 Content-length: 816 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21206 --- Comment #6 from Yao Qi --- (In reply to Chris Johns from comment #2) >=20 > The build did fail on further on with: >=20 > In file included from ../../binutils-gdb/gdb/dwarf2read.c:72: > ../../binutils-gdb/gdb/common/gdb_unlinker.h:35:35: error: '__nonnull__' > attribute is invalid for the implicit this argument > unlinker (const char *filename) ATTRIBUTE_NONNULL (1) > ^ ~ > ../../binutils-gdb/gdb/../include/ansidecl.h:169:48: note: expanded from > macro 'ATTRIBUTE_NONNULL' > # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m))) >=20 Yes, I saw this fail in my Linux build too. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21092-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 09:34:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35205 invoked by alias); 8 Mar 2017 09:34:37 -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 35166 invoked by uid 55); 8 Mar 2017 09:34:37 -0000 From: "mishra.nitish.88 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Wed, 08 Mar 2017 09:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mishra.nitish.88 at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: mishra.nitish.88 at gmail dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00244.txt.bz2 Content-length: 3418 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 --- Comment #13 from Nitish K Mishra --- Hi, I got a review comment from Bernhard Reutner-Fischer from gcc community and have updated the patch accordingly. Actually the first two changes in the earlier patch is not needed as these changes are already there in the gdb-7.12.1 release. But using "git diff" is still showing those changes. I am not sure why ? Anyways, I have updated the patch accordingly. Please find the attachment. Thanks and Regards, Nitish K Mishra On Tue, Mar 7, 2017 at 5:50 PM, Nitish Kumar Mishra wrote: > Hi, > > I have updated the patch as per your comment and sent it to > gdb-patches@ and have uploaded the same to the PR 21187 > on bugzilla. I am attaching one copy here as well. Please find the attach= ment. > One thing more, Yao Qi told me that configure.ac file is maintained by > gcc community, So I should sent the patch to gcc-patches@ > and get approval from there. So, I am mailing one copy of the patch > there as well. > I am new to the community, so, don't have much exposure here. Anything > else I need to do or follow-up ? > > Thanks and Regards, > Nitish > > On Tue, Mar 7, 2017 at 2:24 PM, Nitish Kumar Mishra > wrote: >> Hi, >> >> Sure, I will send the patch to gdb-patches mailing list after changing >> the code as per your comment. >> Thanks for the help. >> >> Thanks and Regards, >> Nitish >> >> >> On Sat, Mar 4, 2017 at 11:02 PM, brobecker at gnat dot com >> wrote: >>> https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 >>> >>> Joel Brobecker changed: >>> >>> What |Removed |Added >>> -----------------------------------------------------------------------= ----- >>> Status|UNCONFIRMED |NEW >>> Last reconfirmed| |2017-03-04 >>> CC| |brobecker at gnat dot = com >>> Assignee|unassigned at sourceware dot org |mishra.nitish.8= 8 at gmail dot com >>> Ever confirmed|0 |1 >>> >>> --- Comment #6 from Joel Brobecker --- >>> To get your patch reviewed, and hopefully included in the official sour= ces, can >>> you please send it to gdb-patches@, using the information outlined in t= he >>> following page, please? >>> >>> https://sourceware.org/gdb/wiki/ContributionChecklist >>> >>> People don't necessarily follow the patches sent here. I think this is = also >>> mentioned in the ContributionChecklist above, but do ping us after a co= uple of >>> weeks if we haven't answered, and every week thereafter. >>> >>> As a comment to your patch, the style you used for the AC_ARG_ENABLE is= a bit >>> different from the style we've been using so far. Not necessarily wrong= , but >>> there is value for us in trying to keep the style consistent. So could = you have >>> a look at the other uses of AC_ARG_ENABLE in gdb/configure.ac, and try = to >>> mimick that with your patch? >>> >>> Thank you. >>> >>> -- >>> You are receiving this mail because: >>> You are on the CC list for the bug. >>> You are the assignee for the bug. >>> You reported the bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21093-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 11:27:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4460 invoked by alias); 8 Mar 2017 11:27: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 4440 invoked by uid 48); 8 Mar 2017 11:27:23 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/21218] Regression: GDB dumps core when escaping newline in multi line command Date: Wed, 08 Mar 2017 11:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00245.txt.bz2 Content-length: 2568 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21218 --- Comment #2 from Pedro Alves --- I have a local fix. Turns out that commit ended up exposing a "latent" bug= .=20 The problem is that gdb_readline_wrapper ends up calling display_gdb_prompt with a NULL prompt parameter, which has special meaning - it signals that w= e're printing the primary prompt, when what we want is a secondary prompt. While tightening the test, I noticed that the commit before the one that exposed the crash also behaved incorrectly: PASS: gdb.base/commands.exp: commands print \ (gdb) argc FAIL: gdb.base/commands.exp: input line split with backslash (timeout) I.e., gdb wouldn't crash, but it'd print the gdb prompt when it shouldn't. Going further back, to try to find the commit that introduced that problem,= in order to try to confirm what I think GDB should be printing after the \ (i.= e., nothing, instead of a ">" or something else), I found that that problem was originally introduced right when gdb_readline_wrapper was originally added: commit 782a7b8ef9c096357073a9c177fb1e21b282cec0 Author: Daniel Jacobowitz AuthorDate: Wed Jan 3 21:46:12 2007 +0000 Commit: Daniel Jacobowitz CommitDate: Wed Jan 3 21:46:12 2007 +0000 2007-01-03 Jan Kratochvil Daniel Jacobowitz And with that commit, gdb started crashing in this use case: (gdb) commands Type commands for when breakpoint 1 is hit, one per line. End with a line saying just "end". >print \ Program received signal SIGSEGV, Segmentation fault. strlen () at ../sysdeps/x86_64/strlen.S:106 106 movdqu (%rax), %xmm12 (top-gdb) bt #0 0x00007ffff6f256fa in strlen () at ../sysdeps/x86_64/strlen.S:106 #1 0x00000000004d8cbb in display_gdb_prompt (new_prompt=3D0x0) at src/gdb/event-top.c:298 #2 0x0000000000448ca7 in gdb_readline_wrapper (prompt=3D0x0) at src/gdb/top.c:806 #3 0x0000000000449178 in command_line_input (prompt_arg=3D0x7fffffffd290 "= >", repeat=3D1, annotation_suffix=3D0x61295d "commands") at src/gdb/top.c:1011 Kind of funny this issue survived so long unnoticed and with different manifestations. Just before that commit, GDB behaved like this: (gdb) commands Type commands for when breakpoint 1 is hit, one per line. End with a line saying just "end". >print \ 1 >end (gdb)=20 ... which is what my (yet-unposted) patch will restore GDB back to. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21094-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 12:28:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68855 invoked by alias); 8 Mar 2017 12:28:09 -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 68043 invoked by uid 55); 8 Mar 2017 12:28:09 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug cli/21218] Regression: GDB dumps core when escaping newline in multi line command Date: Wed, 08 Mar 2017 12:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00246.txt.bz2 Content-length: 2982 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21218 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D6e5d74e74756= fafe59e8198c4cc462cf7c57e12c commit 6e5d74e74756fafe59e8198c4cc462cf7c57e12c Author: Pedro Alves Date: Wed Mar 8 11:41:35 2017 +0000 Fix PR 21218: GDB dumps core when escaping newline in multi-line command With commit 3b12939dfc2399 ("Replace the sync_execution global with a new enum prompt_state tristate"), GDB started aborting if you try splitting an input line with a continuation char (backslash) while in a multi-line command: (gdb) commands Type commands for breakpoint(s) 1, one per line. End with a line saying just "end". >print \ (gdb) 1 # note "(gdb)" incorrectly printed here. >end readline: readline_callback_read_char() called with no handler! $ That abort is actually a symptom of an old problem introduced when gdb_readline_wrapper was rewritten to use asynchronous readline, back in 2007. Note how the "(gdb)" prompt is printed above in the "(gdb) 1" line. Clearly it shouldn't be there, but it already was before the commit mentioned above. Fixing that also fixes the readline abort shown above. The problem starts when command_line_input passes a NULL prompt to gdb_readline_wrapper when it finds previous incomplete input due to a backslash, trying to fetch more input without printing another ">" secondary prompt. That itself should not be a problem, because passing NULL to gdb_readline_wrapper has the same meaning as passing a pointer to empty string, since gdb_readline_wrapper exposes the same interface as 'readline(char *)'. However, gdb_readline_wrapper passes the prompt argument directly to display_gdb_prompt, and for the latter, a NULL prompt argument has a different meaning - it requests printing the primary prompt. Before commit 782a7b8ef9c096 (which rewrote gdb_readline_wrapper to use asynchronous readline), GDB behaved like this: (gdb) commands [....] >print \ 1 >end (gdb) The above is what this commit restores GDB back to. New test included. gdb/ChangeLog: 2017-03-08 Pedro Alves PR cli/21218 * top.c (gdb_readline_wrapper): Avoid passing NULL to display_gdb_prompt. (command_line_input): Add comment. gdb/testsuite/ChangeLog: 2017-03-08 Pedro Alves Jan Kratochvil PR cli/21218 * gdb.base/commands.exp (backslash_in_multi_line_command_test): New proc. (top level): Call it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21095-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 12:29:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 96276 invoked by alias); 8 Mar 2017 12:29:06 -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 96248 invoked by uid 48); 8 Mar 2017 12:29:05 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/21218] Regression: GDB dumps core when escaping newline in multi line command Date: Wed, 08 Mar 2017 12:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00247.txt.bz2 Content-length: 502 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21218 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Pedro Alves --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21096-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 15:18:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 130254 invoked by alias); 8 Mar 2017 15:18:07 -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 130224 invoked by uid 48); 8 Mar 2017 15:18:06 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21225] Which version of gdb should I use for best reliability Date: Wed, 08 Mar 2017 15:18: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.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00248.txt.bz2 Content-length: 2268 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21225 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- The first question is so open ended that it's impossible to answer in any detail. For one, I have no idea what exactly you mean by "reliable". But obviously the general answer should be "the latest version". GDB is consta= ntly improving. For the rest of the questions, "yes to all". > do the developers of gdb ever use gdb to debug gdb? Of course. > do the developers of gdb ever debug code that use C++=20 Yes. GDB is a C++11 program now [1], so we're dogfooding C++ nowadays. A = few problems became more evident, but none that we didn't know about already. We have two major projects going on to improve C++ debugging. One is using= G++ for C++ expression evaluation, via the "compile" command. The G++ side is going to be in GCC 7, and the GDB side is being prepared for submission. T= he other is improving the linespec parser and symbol search so that it becomes possible to set breakpoints on functions with gdb ignoring namespaces. I c= an point you at testing branches for all of this if you're interested in helpi= ng out. The wiki has pointers to these and other ongoing projects. > or DSOs?=20=20 Yes, of course. Specific suggestions on what should be improved are welcom= e. > Do the developers ever look at examples that are larger than 10K? Yes. We know of houses that have many users that load huge programs into G= DB.=20 Some even employ GDB maintainers. We have tests in our testsuite to exerci= se some use cases with representative "huge" programs. There's a lot of scope= for improvement, of course. > (To answer a potential response question, yes I am getting a bit fed up. = And=20 > if I am getting fed up, there are many more that have given up on gdb bei= ng a=20 > useful tool.) I'm sorry to hear that. [1] https://sourceware.org/gdb/wiki/cxx-conversion --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21097-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 15:24:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 46933 invoked by alias); 8 Mar 2017 15:24:59 -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 46902 invoked by uid 48); 8 Mar 2017 15:24:58 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/19712] AT_EXECFN and trimmed "Core was generated by" Date: Wed, 08 Mar 2017 15:24: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q1/txt/msg00249.txt.bz2 Content-length: 976 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19712 --- Comment #1 from Pedro Alves --- Diffing two test directories I noticed: -PASS: gdb.base/corefile.exp: args: -core=3Dcorefile.core=20 -PASS: gdb.base/corefile.exp: args: execfile -core=3Dcorefile.core=20 -PASS: gdb.base/corefile.exp: core-file command=20 +PASS: gdb.base/corefile.exp: args: -core=3Dcorefile.core (with bad program name)=20 +PASS: gdb.base/corefile.exp: args: execfile -core=3Dcorefile.core (with b= ad program name)=20 +PASS: gdb.base/corefile.exp: core-file command (with bad program name)=20 The reason for that was exactly a too-long filename: -Core was generated by `/home/pedro/brno/pedro/gdb/mygit/build/gdb/testsuite/outputs/gdb.base/core= file/'. +[New LWP 21803] +Core was generated by `/home/pedro/brno/pedro/gdb/mygit/cxx-convertion/build-gcc-5.3.1-cxx11/gdb/= tests'. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21098-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 15:48:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 46521 invoked by alias); 8 Mar 2017 15:48:56 -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 46458 invoked by uid 48); 8 Mar 2017 15:48:55 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug corefiles/21206] gdb-7.12.1 for arm-rtems4.12 fails to build on FreeBSD 11.0 Date: Wed, 08 Mar 2017 15:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q1/txt/msg00250.txt.bz2 Content-length: 562 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21206 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #7 from Pedro Alves --- I've reported a GCC bug for the missing diagnostic: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D79961 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21099-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 16:21:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79413 invoked by alias); 8 Mar 2017 16:21:43 -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 79375 invoked by uid 55); 8 Mar 2017 16:21:42 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/21206] gdb-7.12.1 for arm-rtems4.12 fails to build on FreeBSD 11.0 Date: Wed, 08 Mar 2017 16:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: 2017-q1/txt/msg00251.txt.bz2 Content-length: 1387 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21206 --- Comment #8 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D15c22686d0e3= 3d87262bc9075296eeddd7d955f7 commit 15c22686d0e33d87262bc9075296eeddd7d955f7 Author: Pedro Alves Date: Wed Mar 8 15:52:16 2017 +0000 gdb: Fix ATTRIBUTE_NONNULL usage Should fix the build failure with Clang mentioned at : In file included from ../../binutils-gdb/gdb/dwarf2read.c:72: ../../binutils-gdb/gdb/common/gdb_unlinker.h:35:35: error: '__nonnull_= _' attribute is invalid for the implicit this argument unlinker (const char *filename) ATTRIBUTE_NONNULL (1) ^ ~ ../../binutils-gdb/gdb/../include/ansidecl.h:169:48: note: expanded fr= om macro 'ATTRIBUTE_NONNULL' # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m))) gdb/ChangeLog: 2017-03-08 Pedro Alves PR 21206 * common/gdb_unlinker.h (unlinker::unlinker): Attribute nonnull goes to argument 2, not 1. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21100-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 18:29:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 25411 invoked by alias); 8 Mar 2017 18:29:32 -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 23346 invoked by uid 48); 8 Mar 2017 18:29:31 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21226] DW_OP_stack_value pieces yield wrong data on big-endian targets Date: Wed, 08 Mar 2017 18:29: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: arnez at linux dot vnet.ibm.com 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: 2017-q1/txt/msg00252.txt.bz2 Content-length: 294 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21226 --- Comment #2 from Andreas Arnez --- I posted a proposed fix: https://sourceware.org/ml/gdb-patches/2017-03/msg00110.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21101-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 19:53:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4837 invoked by alias); 8 Mar 2017 19:53:56 -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 4804 invoked by uid 55); 8 Mar 2017 19:53:55 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/18360] internal error when using "interrupt -a" Date: Wed, 08 Mar 2017 19:53: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q1/txt/msg00253.txt.bz2 Content-length: 4536 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18360 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dc65d6b55b3a5= 92906c470c566f57ad8ceacc1605 commit c65d6b55b3a592906c470c566f57ad8ceacc1605 Author: Pedro Alves Date: Wed Mar 8 18:54:34 2017 +0000 Fix PR18360 - internal error when using "interrupt -a" If you do "interrupt -a" just while some thread is stepping over a breakpoint, gdb trips on an internal error. The test added by this patch manages to trigger this consistently by spawning a few threads that are constantly tripping on a conditional breakpoint whose condition always evaluates to false. With current gdb, you get: ~~~ interrupt -a .../src/gdb/inline-frame.c:343: internal-error: void skip_inline_frames(ptid_t): Assertion `find_inline_frame_state (ptid) =3D= =3D NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=3Don: iter=3D= 0: interrupt -a (GDB internal error) [...] .../src/gdb/inline-frame.c:343: internal-error: void skip_inline_frames(ptid_t): Assertion `find_inline_frame_state (ptid) =3D= =3D NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=3Doff: iter= =3D0: wait for stops (GDB internal error) ~~~ The assertion triggers because we're processing a stop for a thread that had already stopped before and thus had already its inline-frame state filled in. Calling handle_inferior_event_1 directly within a "thread_stop_requested" observer is something that I've wanted to get rid of before, for being fragile. Nowadays, infrun is aware of threads with pending events, so we can use that instead, and let the normal fetch_inferior_event -> handle_inferior_event code path handle the forced stop. The change to finish_step_over is necessary because sometimes a thread that was told to PTRACE_SINGLESTEP reports back a SIGSTOP instead of a SIGTRAP (i.e., we tell it to single-step, and then interrupt it quick enough that on the kernel side the thread dequeues the SIGTOP before ever having had a chance of executing the instruction to be stepped). SIGSTOP gets translated to a GDB_SIGNAL_0. And then finish_step_over would miss calling clear_step_over_info, and thus miss restarting the other threads (which in this case of threads with pending events, means setting their "resumed" flag, so their pending events can be consumed). And now that we always restart threads in finish_step_over, we no longer need to do that in handle_signal_stop. Tested on x86_64 Fedora 23, native and gdbserver. gdb/ChangeLog: 2017-03-08 Pedro Alves PR gdb/18360 * infrun.c (start_step_over, do_target_resume, resume) (restart_threads): Assert we're not resuming a thread that is meant to be stopped. (infrun_thread_stop_requested_callback): Delete. (infrun_thread_stop_requested): If the thread is internally stopped, queue a pending stop event and clear the thread's inline-frame state. (handle_stop_requested): New function. (handle_syscall_event, handle_inferior_event_1): Use handle_stop_requested. (handle_stop_requested): New function. (handle_signal_stop): Set the thread's stop_signal here instead of at caller. (finish_step_over): Clear step over info unconditionally. (handle_signal_stop): If the user had interrupted the event thread, consider the stop a random signal. (handle_signal_stop) : Don't restart threads here. (stop_waiting): Don't clear step-over info here. gdb/testsuite/ChangeLog: 2017-03-08 Pedro Alves PR gdb/18360 * gdb.threads/interrupt-while-step-over.c: New file. * gdb.threads/interrupt-while-step-over.exp: New file. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21102-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 19:56:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 8691 invoked by alias); 8 Mar 2017 19:56:21 -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 8662 invoked by uid 48); 8 Mar 2017 19:56:20 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18360] internal error when using "interrupt -a" Date: Wed, 08 Mar 2017 19:56: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat 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: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-q1/txt/msg00254.txt.bz2 Content-length: 555 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18360 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |8.0 --- Comment #3 from Pedro Alves --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21103-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 19:57:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 9771 invoked by alias); 8 Mar 2017 19:57:26 -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 9745 invoked by uid 48); 8 Mar 2017 19:57:26 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18360] internal error when using "interrupt -a" Date: Wed, 08 Mar 2017 19:57: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson 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: 8.0 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: 2017-q1/txt/msg00255.txt.bz2 Content-length: 217 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18360 --- Comment #4 from Simon Marchi --- Thanks! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21104-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 08 21:28:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 113619 invoked by alias); 8 Mar 2017 21:28:47 -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 113402 invoked by uid 48); 8 Mar 2017 21:28:47 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/8218] ptype claims destructors have arg Date: Wed, 08 Mar 2017 21:28: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to 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: 2017-q1/txt/msg00256.txt.bz2 Content-length: 1418 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8218 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com Assignee|unassigned at sourceware dot org |keiths at redhat do= t com --- Comment #4 from Keith Seitz --- (In reply to Tom Tromey from comment #3) > Arguably it is still a gdb bug since the parameter is marked artificial. > I think that gdb may be making an explicit choice here, though, since > c_type_print_args explicitly prints artificial arguments. Yeah, this just bit me, too, while trying to write some tests using cp_test_ptype_class. It kept failing on the dtor, "~foo(int)". The problem here is that cp_type_print_method_args doesn't ignore artificial arguments, except possibly the first one if the method isn't static. [That seems equally dubious to me, too. Compilers don't *have* to implement metho= ds using artificial `this'. :-)] In any case, I'm working up a patch. To see ~foo(int) in 2017 is just plain disheartening! I don't think this should harm Clang in any way, but if there is test suite massaging needed, I don't think there would be a problem with that. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21105-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 09 16:37:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 72014 invoked by alias); 9 Mar 2017 16:37:25 -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 71894 invoked by uid 48); 9 Mar 2017 16:37:24 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Thu, 09 Mar 2017 16:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan.kratochvil at redhat dot com X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc target_milestone 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: 2017-q1/txt/msg00257.txt.bz2 Content-length: 586 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com Target Milestone|--- |8.0 --- Comment #11 from Pedro Alves --- We should really get that series in. Tentatively setting milestone to 8.0. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21106-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 09 17:04:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 69647 invoked by alias); 9 Mar 2017 17:04:53 -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 69619 invoked by uid 48); 9 Mar 2017 17:04:52 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Thu, 09 Mar 2017 17:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: 2017-q1/txt/msg00258.txt.bz2 Content-length: 647 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jan.kratochvil at redhat dot com |keiths at redhat do= t com --- Comment #12 from Keith Seitz --- (In reply to Pedro Alves from comment #11) > We should really get that series in. Tentatively setting milestone to 8.= 0. I'm working on it. Should arrive in the next day or two. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21107-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 09 21:58:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 102238 invoked by alias); 9 Mar 2017 21:58:58 -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 102207 invoked by uid 48); 9 Mar 2017 21:58:57 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/20399] casts.cc test case fails to compile Date: Thu, 09 Mar 2017 21:58: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat 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: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution target_milestone 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: 2017-q1/txt/msg00259.txt.bz2 Content-length: 778 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20399 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |keiths at redhat dot com Resolution|--- |FIXED Target Milestone|--- |8.0 --- Comment #2 from Keith Seitz --- It was in the rvalue reference patch set, but Jan fixed this separately in commit d41a5c096ec613f7df33d5d5ea4c0e512ac1e87a. AFAICT, this did not make 7.12. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21108-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 09 22:09:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 121104 invoked by alias); 9 Mar 2017 22:09:29 -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 121065 invoked by uid 48); 9 Mar 2017 22:09:28 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/18881] bogus 'Cannot resolve function foo to any overloaded instance' Date: Thu, 09 Mar 2017 22:09: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: 7.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com 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: cc 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: 2017-q1/txt/msg00260.txt.bz2 Content-length: 930 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18881 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com --- Comment #1 from Keith Seitz --- Is this still a problem? This appears to be working since 7.9: $ ./gdb -ex 'b bar' -ex r -ex 'p FOO1(b)' -ex 'p FOO2(b)' \ -ex 'p foo((A)b)' -ex 'p foo((A)b) ? foo((A)b) : foo((A)b)' ~/tmp/18881 Breakpoint 1, bar (b=3D0x7fffffffd9bf) at 18881.cc:14 14 if (FOO2 (b)) $1 =3D (const U *) 0x7fffffffd9bf $2 =3D (const U *) 0x7fffffffd9bf $3 =3D (const U *) 0x7fffffffd9bf $4 =3D (const U *) 0x7fffffffd9bf (gdb) show version GNU gdb (GDB) 7.9.1.20150702-cvs [snip] --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21110-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 09 22:23:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23199 invoked by alias); 9 Mar 2017 22:23:25 -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 23137 invoked by uid 48); 9 Mar 2017 22:23:24 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/16106] C++ expression parsing meta-bug Date: Thu, 09 Mar 2017 22:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: dep_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: keiths at redhat dot com 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: bug_status resolution 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: 2017-q1/txt/msg00262.txt.bz2 Content-length: 546 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16106 Bug 16106 depends on bug 15169, which changed state. Bug 15169 Summary: unhandled overload resolution case https://sourceware.org/bugzilla/show_bug.cgi?id=3D15169 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21109-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 09 22:23:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23020 invoked by alias); 9 Mar 2017 22:23:24 -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 22991 invoked by uid 48); 9 Mar 2017 22:23:23 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/15169] unhandled overload resolution case Date: Thu, 09 Mar 2017 22:23: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat 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 cc resolution 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: 2017-q1/txt/msg00261.txt.bz2 Content-length: 973 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15169 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |keiths at redhat dot com Resolution|--- |FIXED --- Comment #1 from Keith Seitz --- This appears to work since at least 7.9: & gdb-7.9 ~/tmp/15169 -ex start -ex "p overload(1,f)" Reading symbols from /home/keiths/tmp/15169...done. Temporary breakpoint 1 at 0x400629: file 15169.cc, line 7. Starting program: /home/keiths/tmp/15169=20 Temporary breakpoint 1, main () at 15169.cc:7 7 return overload(0, f); $1 =3D 1 Please file a new bug if there are still unaddressed problems. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21111-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 09 22:30:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 62341 invoked by alias); 9 Mar 2017 22:30:42 -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 45782 invoked by uid 48); 9 Mar 2017 22:30:29 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/15372] ref qualifiers and overloading Date: Thu, 09 Mar 2017 22:30: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: archer X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com 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: cc see_also 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: 2017-q1/txt/msg00263.txt.bz2 Content-length: 1151 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15372 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com See Also| |http://sourceware.org/bugzi | |lla/show_bug.cgi?id=3D14441 --- Comment #1 from Keith Seitz --- Many years later, we have DWARF support for rvalue references and we even h= ave pending support for them in GDB (see c++/14441). However, that patch series still has some problems with overload resolution. I'm using this bug to track these problems. In our test suite, we (will) ha= ve: FAIL: gdb.cp/rvalue-ref-overload.exp: lvalue reference overload FAIL: gdb.cp/rvalue-ref-overload.exp: rvalue reference overload FAIL: gdb.cp/rvalue-ref-params.exp: print value of f1 on Child&& in f2 These will be marked KFAIL and linked to this bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21112-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 09 22:30:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63805 invoked by alias); 9 Mar 2017 22:30:44 -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 62905 invoked by uid 48); 9 Mar 2017 22:30:43 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Thu, 09 Mar 2017 22:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: see_also 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: 2017-q1/txt/msg00264.txt.bz2 Content-length: 475 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://sourceware.org/bugz | |illa/show_bug.cgi?id=3D153= 72 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21113-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 10 02:13:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 21299 invoked by alias); 10 Mar 2017 02:13:39 -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 20184 invoked by uid 48); 10 Mar 2017 02:13:38 -0000 From: "yuri at tsoft dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21239] New: gdb doesn't show any threads for some users Date: Fri, 10 Mar 2017 02:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: yuri at tsoft dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00265.txt.bz2 Content-length: 743 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21239 Bug ID: 21239 Summary: gdb doesn't show any threads for some users Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: yuri at tsoft dot com Target Milestone: --- 'info thread' doesn't print anything under some users, and works find under others. gdb should at least report what the problem is when threads aren't availabl= e, the output shouldn't be just blank. Found on FreeBSD 11 amd64. gdb-7.12.1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21114-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 10 18:34:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 44124 invoked by alias); 10 Mar 2017 18:34: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 44091 invoked by uid 55); 10 Mar 2017 18:34:23 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug c++/8218] ptype claims destructors have arg Date: Fri, 10 Mar 2017 18:34: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: keiths at redhat dot com 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: 2017-q1/txt/msg00266.txt.bz2 Content-length: 1542 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8218 --- Comment #5 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Keith Seitz : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D5f4d10850850= cd95af5e95a16848c8c07a273d88 commit 5f4d10850850cd95af5e95a16848c8c07a273d88 Author: Keith Seitz Date: Fri Mar 10 10:32:09 2017 -0800 c++/8218: Destructors w/arguments. For a long time now, c++/8218 has noted that GDB is printing argument t= ypes for destructors: (gdb) ptype A type =3D class A { public: ~A(int); } This happens because cp_type_print_method_args doesn't ignore artificial arguments. [It ignores the first `this' pointer because it simply skips the first argument for any non-static function.] This patch fixes this: (gdb) ptype A type =3D class A { public: ~A(); } I've adjusted gdb.cp/templates.exp to account for this and added a new passing regexp. gdb/ChangeLog PR c++/8218 * c-typeprint.c (cp_type_print_method_args): Skip artificial argume= nts. gdb/testsuite/ChangeLog PR c++/8128 * gdb.cp/templates.exp (test_ptype_of_templates): Remove argument type from destructor regexps. Add a branch which actually passes the test. Adjust "ptype t5i" test names. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21115-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 10 18:34:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 44413 invoked by alias); 10 Mar 2017 18:34:25 -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 44334 invoked by uid 55); 10 Mar 2017 18:34:25 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug c++/8128] setting a breakpoint on C++ member functions Date: Fri, 10 Mar 2017 18:34: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 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: 2017-q1/txt/msg00267.txt.bz2 Content-length: 1542 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8128 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Keith Seitz : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D5f4d10850850= cd95af5e95a16848c8c07a273d88 commit 5f4d10850850cd95af5e95a16848c8c07a273d88 Author: Keith Seitz Date: Fri Mar 10 10:32:09 2017 -0800 c++/8218: Destructors w/arguments. For a long time now, c++/8218 has noted that GDB is printing argument t= ypes for destructors: (gdb) ptype A type =3D class A { public: ~A(int); } This happens because cp_type_print_method_args doesn't ignore artificial arguments. [It ignores the first `this' pointer because it simply skips the first argument for any non-static function.] This patch fixes this: (gdb) ptype A type =3D class A { public: ~A(); } I've adjusted gdb.cp/templates.exp to account for this and added a new passing regexp. gdb/ChangeLog PR c++/8218 * c-typeprint.c (cp_type_print_method_args): Skip artificial argume= nts. gdb/testsuite/ChangeLog PR c++/8128 * gdb.cp/templates.exp (test_ptype_of_templates): Remove argument type from destructor regexps. Add a branch which actually passes the test. Adjust "ptype t5i" test names. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21116-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 10 20:51:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 38332 invoked by alias); 10 Mar 2017 20:51:04 -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 38302 invoked by uid 48); 10 Mar 2017 20:51:03 -0000 From: "tcurdt at vafer dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] New: arm-none-eabi-gdb crashes on start Date: Fri, 10 Mar 2017 20:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: tcurdt at vafer dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00268.txt.bz2 Content-length: 14448 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 Bug ID: 21240 Summary: arm-none-eabi-gdb crashes on start Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: critical Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: tcurdt at vafer dot org Target Milestone: --- When just running: $ arm-none-eabi-gdb GNU gdb (GNU Tools for ARM Embedded Processors) 7.12.0.20161204-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copyi= ng" and "show warranty" for details. This GDB was configured as "--host=3Dx86_64-apple-darwin10 --target=3Darm-none-eabi". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". Abort trap: 6 I get a SIGABRT Process: arm-none-eabi-gdb [19569] Path:=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 /usr/local/Caskroom/gcc-arm-embedded/6.2,2016q4/gcc-arm-none-eabi-6_2-2016q= 4/bin/arm-none-eabi-gdb Identifier: arm-none-eabi-gdb Version: ??? Code Type: X86-64 (Native) Parent Process: bash [16866] Responsible: arm-none-eabi-gdb [19569] User ID: 501 Date/Time: 2017-03-10 21:45:04.843 +0100 OS Version: Mac OS X 10.12.3 (16D32) Report Version: 12 Anonymous UUID: C5809969-9982-626B-185C-C71743BF1FC0 Sleep/Wake UUID: CBDB9DCF-CE80-4E0E-A87E-1BFC300D5143 Time Awake Since Boot: 910000 seconds Time Since Wake: 17000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Application Specific Information: abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff8bb4cdd6 __pthread_kill += 10 1 libsystem_pthread.dylib 0x00007fff8bc38787 pthread_kill + 90 2 libsystem_c.dylib 0x00007fff8bab2420 abort + 129 3 arm-none-eabi-gdb 0x000000010658b0a1 uw_init_context_= 1 + 88 4 arm-none-eabi-gdb 0x000000010658b498 _Unwind_RaiseException + 62 5 arm-none-eabi-gdb 0x0000000106589868 __cxa_throw + 90 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff599a= 4a48 rdx: 0x0000000000000000 rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff599a= 4a70 rsp: 0x00007fff599a4a48 r8: 0x0000000000000040 r9: 0x00007f951a600240 r10: 0x000000000800= 0000 r11: 0x0000000000000206 r12: 0x0000000106589868 r13: 0x00007fff599a5020 r14: 0x00007fff9486= b3c0 r15: 0x000000010659f9b0 rip: 0x00007fff8bb4cdd6 rfl: 0x0000000000000206 cr2: 0x00007fff8bc3= 648b Logical CPU: 0 Error Code: 0x02000148 Trap Number: 133 Binary Images: 0x10625a000 - 0x106768fef +arm-none-eabi-gdb (???) <6A807F40-BB0B-35D2-AFC2-6AE3BAF605BC> /usr/local/bin/arm-none-eabi-gdb 0x10742f000 - 0x10746c267 dyld (421.2) <947FC440-80F9-32F7-A773-6FC418FE1AB7> /usr/lib/dyld 0x7fff8a47b000 - 0x7fff8a47cff3 libSystem.B.dylib (1238) <9CB018AF-54E9-300F-82BE-81FE553C9154> /usr/lib/libSystem.B.dylib 0x7fff8a594000 - 0x7fff8a594ff3 libauto.dylib (187) <5BBF6A00-CC76-389D-84E7-CA88EDADE683> /usr/lib/libauto.dylib 0x7fff8a5b5000 - 0x7fff8a60bff7 libc++.1.dylib (307.4) /usr/lib/libc++.1.dylib 0x7fff8a60c000 - 0x7fff8a636fff libc++abi.dylib (307.2) <1CEF8ABB-7E6D-3C2F-8E0A-E7884478DD23> /usr/lib/libc++abi.dylib 0x7fff8b07a000 - 0x7fff8b0abffb libncurses.5.4.dylib (51.30.1) /usr/lib/libncurses.5.4.dylib 0x7fff8b126000 - 0x7fff8b4f6d97 libobjc.A.dylib (706) /usr/lib/libobjc.A.dylib 0x7fff8b940000 - 0x7fff8b944ff7 libcache.dylib (79) <0C8092D3-600F-3ADD-A036-F225B6CDCA43> /usr/lib/system/libcache.dylib 0x7fff8b945000 - 0x7fff8b950ff7 libcommonCrypto.dylib (60092.3= 0.2) /usr/lib/system/libcommonCrypto.dylib 0x7fff8b951000 - 0x7fff8b958fff libcompiler_rt.dylib (62) /usr/lib/system/libcompiler_rt.dylib 0x7fff8b959000 - 0x7fff8b961fff libcopyfile.dylib (138) <64E285D9-5485-333B-AEE7-8B0C8FB9275F> /usr/lib/system/libcopyfile.dylib 0x7fff8b962000 - 0x7fff8b9e5fdf libcorecrypto.dylib (442.30.20) <2074B932-FD79-30A9-8E90-AF25C49F2AF1> /usr/lib/system/libcorecrypto.dylib 0x7fff8b9e6000 - 0x7fff8ba18fff libdispatch.dylib (703.30.5) /usr/lib/system/libdispatch.dylib 0x7fff8ba19000 - 0x7fff8ba1eff3 libdyld.dylib (421.2) <6F506653-FFF6-3DB8-84F1-109AE3C52F32> /usr/lib/system/libdyld.dylib 0x7fff8ba1f000 - 0x7fff8ba1fffb libkeymgr.dylib (28) <1A318923-1200-3B06-B432-5007D82F195D> /usr/lib/system/libkeymgr.dylib 0x7fff8ba2d000 - 0x7fff8ba2dfff liblaunch.dylib (972.30.7) <15FACC21-079A-3BDF-9AFB-4253EFDEB587> /usr/lib/system/liblaunch.dylib 0x7fff8ba2e000 - 0x7fff8ba33fff libmacho.dylib (894) /usr/lib/system/libmacho.dylib 0x7fff8ba34000 - 0x7fff8ba36ff3 libquarantine.dylib (85) /usr/lib/system/libquarantine.dylib 0x7fff8ba37000 - 0x7fff8ba38ffb libremovefile.dylib (45) /usr/lib/system/libremovefile.dylib 0x7fff8ba39000 - 0x7fff8ba51ff7 libsystem_asl.dylib (349.30.2) /usr/lib/system/libsystem_asl.dylib 0x7fff8ba52000 - 0x7fff8ba52ff7 libsystem_blocks.dylib (67) /usr/lib/system/libsystem_blocks.dyl= ib 0x7fff8ba53000 - 0x7fff8bae0fef libsystem_c.dylib (1158.30.7) <2F881962-03CB-3B9D-A782-D98C1BBA4E3D> /usr/lib/system/libsystem_c.dylib 0x7fff8bae1000 - 0x7fff8bae4ffb libsystem_configuration.dylib (888.30.2) <4FE3983C-E4ED-3939-A578-03AD29C99788> /usr/lib/system/libsystem_configuration.dylib 0x7fff8bae5000 - 0x7fff8bae8fff libsystem_coreservices.dylib (41.4) <1A572B9E-0C47-320F-8C64-7990D0A5FB5A> /usr/lib/system/libsystem_coreservices.dylib 0x7fff8bae9000 - 0x7fff8bb01ff3 libsystem_coretls.dylib (121.3= 1.1) <4676F06D-274D-31BE-B61C-4D7A4AEF4858> /usr/lib/system/libsystem_coretls.dy= lib 0x7fff8bb02000 - 0x7fff8bb08fff libsystem_dnssd.dylib (765.30.= 11) /usr/lib/system/libsystem_dnssd.dylib 0x7fff8bb09000 - 0x7fff8bb32ff7 libsystem_info.dylib (503.30.1) <9ED9121C-F111-3FAD-BC2F-C95DEE1C9362> /usr/lib/system/libsystem_info.dylib 0x7fff8bb33000 - 0x7fff8bb55ff7 libsystem_kernel.dylib (3789.4= 1.3) /usr/lib/system/libsystem_kernel.dyl= ib 0x7fff8bb56000 - 0x7fff8bb9dfe7 libsystem_m.dylib (3121.4) <266DB92B-A86F-3691-80FB-1B26AD73CFF3> /usr/lib/system/libsystem_m.dylib 0x7fff8bb9e000 - 0x7fff8bbbcff7 libsystem_malloc.dylib (116.30= .3) /usr/lib/system/libsystem_malloc.dyl= ib 0x7fff8bbbd000 - 0x7fff8bc14ffb libsystem_network.dylib (856.30.16) <4AE368E9-605D-379D-B04C-2AC7455B8250> /usr/lib/system/libsystem_network.dylib 0x7fff8bc15000 - 0x7fff8bc1eff3 libsystem_networkextension.dyl= ib (563.30.15) /usr/lib/system/libsystem_networkextension.dylib 0x7fff8bc1f000 - 0x7fff8bc28ff3 libsystem_notify.dylib (165.20= .1) /usr/lib/system/libsystem_notify.dyl= ib 0x7fff8bc29000 - 0x7fff8bc31fe7 libsystem_platform.dylib (126.= 1.2) <3CA06D4E-C00A-36DE-AA65-3A390097D1F6> /usr/lib/system/libsystem_platform.d= ylib 0x7fff8bc32000 - 0x7fff8bc3cff7 libsystem_pthread.dylib (218.3= 0.1) /usr/lib/system/libsystem_pthread.dy= lib 0x7fff8bc3d000 - 0x7fff8bc40ff7 libsystem_sandbox.dylib (592.3= 1.1) <7BBFDF96-293F-3DD9-B3A4-7C168280B441> /usr/lib/system/libsystem_sandbox.dy= lib 0x7fff8bc41000 - 0x7fff8bc42fff libsystem_secinit.dylib (24) <5C1F1E47-0F7D-3E25-8DEB-D9DB1F902281> /usr/lib/system/libsystem_secinit.dy= lib 0x7fff8bc43000 - 0x7fff8bc4afff libsystem_symptoms.dylib (532.30.6) <5D990CF5-B58F-39F7-B375-99B4EC62CFBD> /usr/lib/system/libsystem_symptoms.dylib 0x7fff8bc4b000 - 0x7fff8bc6bff7 libsystem_trace.dylib (518.30.= 7) <6D34D1EA-2A3C-3D2D-803E-A666E6AEEE52> /usr/lib/system/libsystem_trace.dylib 0x7fff8bc6c000 - 0x7fff8bc71ffb libunwind.dylib (35.3) <9F7C2AD8-A9A7-3DE4-828D-B0F0F166AAA0> /usr/lib/system/libunwind.dylib 0x7fff8bc72000 - 0x7fff8bc9bff7 libxpc.dylib (972.30.7) <65E41BB6-EBD5-3D93-B0BE-B190CEE4DD93> /usr/lib/system/libxpc.dylib External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 553418 thread_create: 0 thread_set_state: 3395 VM Region Summary: ReadOnly portion of Libraries: Total=3D127.0M resident=3D0K(0%) swapped_out_or_unallocated=3D127.0M(100%) Writable regions: Total=3D40.6M written=3D0K(0%) resident=3D0K(0%) swapped_out=3D0K(0%) unallocated=3D40.6M(100%) VIRTUAL REGION=20 REGION TYPE SIZE COUNT (non-coalesced)=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D= =3D=3D =3D=3D=3D=3D=3D=3D=3D=20 Kernel Alloc Once 8K 2=20 MALLOC 28.2M 9=20 MALLOC guard page 16K 4=20 MALLOC_LARGE (reserved) 128K 2 reserved VM address space (unallocated) SBRK (reserved) 4096K 2 reserved VM address space (unallocated) STACK GUARD 56.0M 2=20 Stack 8192K 2=20 VM_ALLOCATE 4K 2=20 __DATA 1840K 45=20 __LINKEDIT 113.8M 4=20 __TEXT 13.1M 43=20 shared memory 8K 3=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D= =3D=3D =3D=3D=3D=3D=3D=3D=3D=20 TOTAL 225.1M 108=20 TOTAL, minus reserved VM space 221.0M 108=20 Model: MacBookAir6,2, BootROM MBA61.0099.B26, 2 processors, Intel Core = i7, 1.7 GHz, 8 GB, SMC 2.13f15 Graphics: Intel HD Graphics 5000, Intel HD Graphics 5000, Built-In Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x483943434E4E4E384A544D4C41522D4E544D Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x483943434E4E4E384A544D4C41522D4E544D AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x117), Broadcom BCM43xx 1.0 (7.21.171.68.1a5) Bluetooth: Version 5.0.3f1, 3 services, 27 devices, 1 incoming serial p= orts Network Service: Wi-Fi, AirPort, en0 Serial ATA Device: APPLE SSD SD0256F, 251 GB USB Device: USB 3.0 Bus USB Device: Card Reader USB Device: BRCM20702 Hub USB Device: Bluetooth USB Host Controller USB Device: STM32 STLink Thunderbolt Bus: MacBook Air, Apple Inc., 23.6 The exact version I am talking about is: $ arm-none-eabi-gdb --version GNU gdb (GNU Tools for ARM Embedded Processors) 7.12.0.20161204-git With the following configuration: $ arm-none-eabi-gdb --configuration This GDB was configured as follows: configure --host=3Dx86_64-apple-darwin10 --target=3Darm-none-eabi --with-auto-load-dir=3D:${prefix}/share/auto-load --with-auto-load-safe-path=3D:${prefix}/share/auto-load --with-expat =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 --with-gdb-datadir=3D/tmp/jenkins-GCC-6-build_build-toolchain-mac-93_201612= 16_1481890191/install-native/arm-none-eabi/share/gdb (relocatable) =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 --with-jit-reader-dir=3D/tmp/jenkins-GCC-6-build_build-toolchain-mac-93_201= 61216_1481890191/install-native/lib/gdb (relocatable) --without-libunwind-ia64 --without-lzma --without-guile =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 --with-separate-debug-dir=3D/tmp/jenkins-GCC-6-build_build-toolchain-mac-93= _20161216_1481890191/install-native/lib/debug (relocatable) =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 --with-system-gdbinit=3D/tmp/jenkins-GCC-6-build_build-toolchain-mac-93_201= 61216_1481890191/install-native/x86_64-apple-darwin10/arm-none-eabi/lib/gdb= init (relocatable) --without-babeltrace ("Relocatable" means the directory can be moved with the GDB installati= on tree, and GDB will still find it.) It might be me doing something wrong after all - but this should never happ= en. Any thoughts? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21117-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 10 20:56:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 56421 invoked by alias); 10 Mar 2017 20:56:01 -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 56391 invoked by uid 48); 10 Mar 2017 20:56:00 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Fri, 10 Mar 2017 20:56: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: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00269.txt.bz2 Content-length: 1197 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #7 from Keith Seitz --- As you note, this is likely a display problem. So the next question is, what does "info addr lambda" say? I wonder if the debug info is incorrect. On my system (which does not support VEX): 12 float lambda =3D C_LIGHT / f; (gdb) n 13 printf("lambda =3D %f\n", lambda); (gdb) p lambda $1 =3D 0.031557098 (gdb) info addr lambda Symbol "lambda" is a complex DWARF expression: 0: DW_OP_fbreg -20 =2E (gdb) inf frame Stack level 0, frame at 0x7fffffffd990: rip =3D 0x400679 in testFunc (21222.cc:13); saved rip =3D 0x4006dd called by frame at 0x7fffffffd9d0 source language c++. Arglist at 0x7fffffffd980, args: a=3D0x0, n=3D0, sx=3D0x0, sy=3D0x0, rc=3D= 0x0, nr=3D0,=20 b=3D4, f=3D9.50000026e+09, c=3D0x0, d=3D0x0, e=3D0x0, gx=3D0x0, gy=3D0x0 Locals at 0x7fffffffd980, Previous frame's sp is 0x7fffffffd990 Saved registers: rbp at 0x7fffffffd980, rip at 0x7fffffffd988 (gdb) p *(float*)(0x7fffffffd990-20) $2 =3D 0.031557098 What compiler/version are you using? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21118-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 10 21:00:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 69029 invoked by alias); 10 Mar 2017 21:00:46 -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 68901 invoked by uid 48); 10 Mar 2017 21:00:45 -0000 From: "tcurdt at vafer dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Fri, 10 Mar 2017 21:00: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: tcurdt at vafer dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00270.txt.bz2 Content-length: 1411 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 --- Comment #1 from tcurdt at vafer dot org --- Turns out I still had some old gdb configuration in my gdbinit fb -[NSException raise] fb -[NSAssertionHandler handleFailureInFunction:file:lineNumber:descripti= on:] fb -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] fb NSKVODeallocateBreak fb objc_exception_throw fb malloc_printf fb szone_error fb malloc_error_break fb CGPostError fb _objc_error fb objc_exception_during_finalize_error fb auto_zone_resurrection_error fb auto_refcount_underflow_error fb -[_NSZombie init] fb -[_NSZombie retainCount] fb -[_NSZombie retain] fb -[_NSZombie release] fb -[_NSZombie autorelease] fb -[_NSZombie methodSignatureForSelector:] fb -[_NSZombie respondsToSelector:] fb -[_NSZombie forwardInvocation:] fb -[_NSZombie class] fb -[_NSZombie dealloc] # set env NSZombieEnabled YES # set env NSDeallocateZombies NO # set env MallocCheckHeapEach 10000 # set env MallocCheckHeapStart 10000 # set env MallocScribble 1 # set env MallocGuardEdges 1 # set env MallocCheckHeapAbort 1 # set env MallocStackLogging 1 # set env MallocStackLoggingNoCompact 1 set env CFZombie 5 Once I commented that out/removed it, it started without problems. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21119-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 10 21:01:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 71141 invoked by alias); 10 Mar 2017 21:01:10 -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 71047 invoked by uid 48); 10 Mar 2017 21:01:10 -0000 From: "tcurdt at vafer dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Fri, 10 Mar 2017 21:01: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tcurdt at vafer dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_severity 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: 2017-q1/txt/msg00271.txt.bz2 Content-length: 359 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 tcurdt at vafer dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21120-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 10 21:07:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 80373 invoked by alias); 10 Mar 2017 21:07:53 -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 80330 invoked by uid 48); 10 Mar 2017 21:07:51 -0000 From: "tcurdt at vafer dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Fri, 10 Mar 2017 21:07: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tcurdt at vafer dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00272.txt.bz2 Content-length: 27044 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 --- Comment #2 from tcurdt at vafer dot org --- Unfortunately calling $ arm-none-eabi-gdb --tui --eval-command=3D"target remote localhost:4242" main.elf crash as soon as I hit return to continue =20=20=20=20 =E2=94=8C=E2=94=80=E2=94=80stm32l/src/gpio.c=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=90 =E2=94=822 * stm32_gpio.c=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=823 *=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=824 * Created on: 13-06-2012=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=825 * Author: Tomek=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=826 */=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=827=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=828 #include =20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=829 #include =20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8210 #include =20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8211=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8212=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8213 /* initialize pins */=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8214 void GPIO_Init(gpio_t *GPIOx, gpio_init_t *init)=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 >=E2=94=8215 {=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8216 int i;=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8217 /* for every pin */=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8218 for (i =3D 0; i < 16 && init->pins; i++) {= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8219 /* bit position */=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8220 if (init->pins & (1 << i)) {=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8221 /* clear mode */=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8222 GPIOx->MODER &=3D ~(0x3 << = (i * 2));=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8223 GPIOx->MODER |=3D init->mode= << (i * 2);=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8224 /* speed and output mode con= figuration */=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 =E2=94=82 =E2=94=8225 if ((init->mode =3D=3D GPIO_= OUTPUT) || (init->mode =3D=3D GPIO_ALT)) {=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=82 =E2=94=8226 /* Speed mode config= uration */=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 =E2=94=8227 GPIOx->OSPEEDR &=3D = ~(0x3 << (i * 2));=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20 =E2=94=82 =E2=94=8228 GPIOx->OSPEEDR |=3D = init->speed << (i * 2);=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=82 =E2=94=8229 /* Output mode confi= guration */=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=82 Abort trap: 6=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=98 shodan:led tcurdt$ > In: GPIO_Init=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20 L15 PC: 0x8000144=20 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copyin= g" and "show warranty" for details. This GDB was configured as "--host=3Dx86_64-apple-darwin10 --target=3Darm-none-eabi". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from main.elf...done. ---Type to continue, or q to quit--- Process: arm-none-eabi-gdb [20104] Path:=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 /usr/local/Caskroom/gcc-arm-embedded/6.2,2016q4/gcc-arm-none-eabi-6_2-2016q= 4/bin/arm-none-eabi-gdb Identifier: arm-none-eabi-gdb Version: ??? Code Type: X86-64 (Native) Parent Process: bash [16866] Responsible: arm-none-eabi-gdb [20104] User ID: 501 Date/Time: 2017-03-10 22:03:51.535 +0100 OS Version: Mac OS X 10.12.3 (16D32) Report Version: 12 Anonymous UUID: C5809969-9982-626B-185C-C71743BF1FC0 Sleep/Wake UUID: CBDB9DCF-CE80-4E0E-A87E-1BFC300D5143 Time Awake Since Boot: 910000 seconds Time Since Wake: 18000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Application Specific Information: abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff8bb4cdd6 __pthread_kill + = 10 1 libsystem_pthread.dylib 0x00007fff8bc38787 pthread_kill + 90 2 libsystem_c.dylib 0x00007fff8bab2420 abort + 129 3 arm-none-eabi-gdb 0x0000000106f6f0a1 uw_init_context_1= + 88 4 arm-none-eabi-gdb 0x0000000106f6f498 _Unwind_RaiseException + 62 5 arm-none-eabi-gdb 0x0000000106f6d868 __cxa_throw + 90 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff58fc0= 028=20 rdx: 0x0000000000000000 rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff58fc0= 050=20 rsp: 0x00007fff58fc0028 r8: 0x0000000000000040 r9: 0x00007ff3995371c0 r10: 0x0000000008000= 000=20 r11: 0x0000000000000206 r12: 0x0000000106f6d868 r13: 0x00007fff58fc0600 r14: 0x00007fff9486b= 3c0=20 r15: 0x00007ff3998be210 rip: 0x00007fff8bb4cdd6 rfl: 0x0000000000000206 cr2: 0x00007fff8bc36= 48b Logical CPU: 0 Error Code: 0x02000148 Trap Number: 133 Binary Images: 0x106c3e000 - 0x10714cfef +arm-none-eabi-gdb (???) <6A807F40-BB0B-35D2-AFC2-6AE3BAF605BC> /usr/local/bin/arm-none-eabi-gdb 0x117371000 - 0x1173ae267 dyld (421.2) <947FC440-80F9-32F7-A773-6FC418FE1AB7> /usr/lib/dyld 0x7fff8a47b000 - 0x7fff8a47cff3 libSystem.B.dylib (1238) <9CB018AF-54E9-300F-82BE-81FE553C9154> /usr/lib/libSystem.B.dylib 0x7fff8a594000 - 0x7fff8a594ff3 libauto.dylib (187) <5BBF6A00-CC76-389D-84E7-CA88EDADE683> /usr/lib/libauto.dylib 0x7fff8a5b5000 - 0x7fff8a60bff7 libc++.1.dylib (307.4) /usr/lib/libc++.1.dylib 0x7fff8a60c000 - 0x7fff8a636fff libc++abi.dylib (307.2) <1CEF8ABB-7E6D-3C2F-8E0A-E7884478DD23> /usr/lib/libc++abi.dylib 0x7fff8b07a000 - 0x7fff8b0abffb libncurses.5.4.dylib (51.30.1) /usr/lib/libncurses.5.4.dylib 0x7fff8b126000 - 0x7fff8b4f6d97 libobjc.A.dylib (706) /usr/lib/libobjc.A.dylib 0x7fff8b940000 - 0x7fff8b944ff7 libcache.dylib (79) <0C8092D3-600F-3ADD-A036-F225B6CDCA43> /usr/lib/system/libcache.dylib 0x7fff8b945000 - 0x7fff8b950ff7 libcommonCrypto.dylib (60092.30= .2) /usr/lib/system/libcommonCrypto.dylib 0x7fff8b951000 - 0x7fff8b958fff libcompiler_rt.dylib (62) /usr/lib/system/libcompiler_rt.dylib 0x7fff8b959000 - 0x7fff8b961fff libcopyfile.dylib (138) <64E285D9-5485-333B-AEE7-8B0C8FB9275F> /usr/lib/system/libcopyfile.dylib 0x7fff8b962000 - 0x7fff8b9e5fdf libcorecrypto.dylib (442.30.20) <2074B932-FD79-30A9-8E90-AF25C49F2AF1> /usr/lib/system/libcorecrypto.dylib 0x7fff8b9e6000 - 0x7fff8ba18fff libdispatch.dylib (703.30.5) /usr/lib/system/libdispatch.dylib 0x7fff8ba19000 - 0x7fff8ba1eff3 libdyld.dylib (421.2) <6F506653-FFF6-3DB8-84F1-109AE3C52F32> /usr/lib/system/libdyld.dylib 0x7fff8ba1f000 - 0x7fff8ba1fffb libkeymgr.dylib (28) <1A318923-1200-3B06-B432-5007D82F195D> /usr/lib/system/libkeymgr.dylib 0x7fff8ba2d000 - 0x7fff8ba2dfff liblaunch.dylib (972.30.7) <15FACC21-079A-3BDF-9AFB-4253EFDEB587> /usr/lib/system/liblaunch.dylib 0x7fff8ba2e000 - 0x7fff8ba33fff libmacho.dylib (894) /usr/lib/system/libmacho.dylib 0x7fff8ba34000 - 0x7fff8ba36ff3 libquarantine.dylib (85) /usr/lib/system/libquarantine.dylib 0x7fff8ba37000 - 0x7fff8ba38ffb libremovefile.dylib (45) /usr/lib/system/libremovefile.dylib 0x7fff8ba39000 - 0x7fff8ba51ff7 libsystem_asl.dylib (349.30.2) /usr/lib/system/libsystem_asl.dylib 0x7fff8ba52000 - 0x7fff8ba52ff7 libsystem_blocks.dylib (67) /usr/lib/system/libsystem_blocks.dyl= ib 0x7fff8ba53000 - 0x7fff8bae0fef libsystem_c.dylib (1158.30.7) <2F881962-03CB-3B9D-A782-D98C1BBA4E3D> /usr/lib/system/libsystem_c.dylib 0x7fff8bae1000 - 0x7fff8bae4ffb libsystem_configuration.dylib (888.30.2) <4FE3983C-E4ED-3939-A578-03AD29C99788> /usr/lib/system/libsystem_configuration.dylib 0x7fff8bae5000 - 0x7fff8bae8fff libsystem_coreservices.dylib (4= 1.4) <1A572B9E-0C47-320F-8C64-7990D0A5FB5A> /usr/lib/system/libsystem_coreservices.dylib 0x7fff8bae9000 - 0x7fff8bb01ff3 libsystem_coretls.dylib (121.31= .1) <4676F06D-274D-31BE-B61C-4D7A4AEF4858> /usr/lib/system/libsystem_coretls.dy= lib 0x7fff8bb02000 - 0x7fff8bb08fff libsystem_dnssd.dylib (765.30.1= 1) /usr/lib/system/libsystem_dnssd.dylib 0x7fff8bb09000 - 0x7fff8bb32ff7 libsystem_info.dylib (503.30.1) <9ED9121C-F111-3FAD-BC2F-C95DEE1C9362> /usr/lib/system/libsystem_info.dylib 0x7fff8bb33000 - 0x7fff8bb55ff7 libsystem_kernel.dylib (3789.41= .3) /usr/lib/system/libsystem_kernel.dyl= ib 0x7fff8bb56000 - 0x7fff8bb9dfe7 libsystem_m.dylib (3121.4) <266DB92B-A86F-3691-80FB-1B26AD73CFF3> /usr/lib/system/libsystem_m.dylib 0x7fff8bb9e000 - 0x7fff8bbbcff7 libsystem_malloc.dylib (116.30.= 3) /usr/lib/system/libsystem_malloc.dyl= ib 0x7fff8bbbd000 - 0x7fff8bc14ffb libsystem_network.dylib (856.30= .16) <4AE368E9-605D-379D-B04C-2AC7455B8250> /usr/lib/system/libsystem_network.dy= lib 0x7fff8bc15000 - 0x7fff8bc1eff3 libsystem_networkextension.dylib (563.30.15) /usr/lib/system/libsystem_networkextension.dylib 0x7fff8bc1f000 - 0x7fff8bc28ff3 libsystem_notify.dylib (165.20.= 1) /usr/lib/system/libsystem_notify.dyl= ib 0x7fff8bc29000 - 0x7fff8bc31fe7 libsystem_platform.dylib (126.1= .2) <3CA06D4E-C00A-36DE-AA65-3A390097D1F6> /usr/lib/system/libsystem_platform.d= ylib 0x7fff8bc32000 - 0x7fff8bc3cff7 libsystem_pthread.dylib (218.30= .1) /usr/lib/system/libsystem_pthread.dy= lib 0x7fff8bc3d000 - 0x7fff8bc40ff7 libsystem_sandbox.dylib (592.31= .1) <7BBFDF96-293F-3DD9-B3A4-7C168280B441> /usr/lib/system/libsystem_sandbox.dy= lib 0x7fff8bc41000 - 0x7fff8bc42fff libsystem_secinit.dylib (24) <5C1F1E47-0F7D-3E25-8DEB-D9DB1F902281> /usr/lib/system/libsystem_secinit.dy= lib 0x7fff8bc43000 - 0x7fff8bc4afff libsystem_symptoms.dylib (532.3= 0.6) <5D990CF5-B58F-39F7-B375-99B4EC62CFBD> /usr/lib/system/libsystem_symptoms.d= ylib 0x7fff8bc4b000 - 0x7fff8bc6bff7 libsystem_trace.dylib (518.30.7) <6D34D1EA-2A3C-3D2D-803E-A666E6AEEE52> /usr/lib/system/libsystem_trace.dylib 0x7fff8bc6c000 - 0x7fff8bc71ffb libunwind.dylib (35.3) <9F7C2AD8-A9A7-3DE4-828D-B0F0F166AAA0> /usr/lib/system/libunwind.dylib 0x7fff8bc72000 - 0x7fff8bc9bff7 libxpc.dylib (972.30.7) <65E41BB6-EBD5-3D93-B0BE-B190CEE4DD93> /usr/lib/system/libxpc.dylib External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 554073 thread_create: 0 thread_set_state: 3395 VM Region Summary: ReadOnly portion of Libraries: Total=3D127.0M resident=3D0K(0%) swapped_out_or_unallocated=3D127.0M(100%) Writable regions: Total=3D48.6M written=3D0K(0%) resident=3D0K(0%) swapped_out=3D0K(0%) unallocated=3D48.6M(100%) VIRTUAL REGION=20 REGION TYPE SIZE COUNT (non-coalesced)=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D= =3D =3D=3D=3D=3D=3D=3D=3D=20 Kernel Alloc Once 8K 2=20 MALLOC 36.2M 9=20 MALLOC guard page 16K 4=20 MALLOC_LARGE (reserved) 128K 2 reserved VM add= ress space (unallocated) SBRK (reserved) 4096K 2 reserved VM add= ress space (unallocated) STACK GUARD 56.0M 2=20 Stack 8192K 2=20 VM_ALLOCATE 4K 2=20 __DATA 1840K 45=20 __LINKEDIT 113.8M 4=20 __TEXT 13.1M 43=20 shared memory 12K 4=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D= =3D =3D=3D=3D=3D=3D=3D=3D=20 TOTAL 233.1M 109=20 TOTAL, minus reserved VM space 229.0M 109=20 Model: MacBookAir6,2, BootROM MBA61.0099.B26, 2 processors, Intel Core i= 7, 1.7 GHz, 8 GB, SMC 2.13f15 Graphics: Intel HD Graphics 5000, Intel HD Graphics 5000, Built-In Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x483943434E4E4E384A544D4C41522D4E544D Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x483943434E4E4E384A544D4C41522D4E544D AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x117), Broadcom BCM43xx 1.0 (7.21.171.68.1a5) Bluetooth: Version 5.0.3f1, 3 services, 27 devices, 1 incoming serial po= rts Network Service: Wi-Fi, AirPort, en0 Serial ATA Device: APPLE SSD SD0256F, 251 GB USB Device: USB 3.0 Bus USB Device: Card Reader USB Device: BRCM20702 Hub USB Device: Bluetooth USB Host Controller USB Device: STM32 STLink Thunderbolt Bus: MacBook Air, Apple Inc., 23.6 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21121-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 10 21:10:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 86736 invoked by alias); 10 Mar 2017 21:10:43 -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 86712 invoked by uid 48); 10 Mar 2017 21:10:42 -0000 From: "tcurdt at vafer dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Fri, 10 Mar 2017 21:10: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tcurdt at vafer dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00273.txt.bz2 Content-length: 1158 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 --- Comment #3 from tcurdt at vafer dot org --- Another try - also crashes: $ arm-none-eabi-gdb main.elf=20 GNU gdb (GNU Tools for ARM Embedded Processors) 7.12.0.20161204-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=3Dx86_64-apple-darwin10 --target=3Darm-none-eabi". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from main.elf...done. (gdb) tar ext :4242 Remote debugging using :4242 GPIO_Init (Abort trap: 6 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21122-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 10 21:12:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88736 invoked by alias); 10 Mar 2017 21:12:45 -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 88709 invoked by uid 48); 10 Mar 2017 21:12:45 -0000 From: "tcurdt at vafer dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Fri, 10 Mar 2017 21:12: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tcurdt at vafer dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00274.txt.bz2 Content-length: 1086 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 --- Comment #4 from tcurdt at vafer dot org --- Seems like just loading the elf is a problem: $ arm-none-eabi-gdb=20 GNU gdb (GNU Tools for ARM Embedded Processors) 7.12.0.20161204-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=3Dx86_64-apple-darwin10 --target=3Darm-none-eabi". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) load main.elf Abort trap: 6 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21123-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 10 21:28:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127519 invoked by alias); 10 Mar 2017 21:28:13 -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 127480 invoked by uid 48); 10 Mar 2017 21:28:12 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Fri, 10 Mar 2017 21:28: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: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00275.txt.bz2 Content-length: 2509 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #8 from Adam Stylinski --- (In reply to Keith Seitz from comment #7) > As you note, this is likely a display problem. >=20 > So the next question is, what does "info addr lambda" say? I wonder if the > debug info is incorrect. >=20 > On my system (which does not support VEX): >=20 > 12 float lambda =3D C_LIGHT / f; > (gdb) n > 13 printf("lambda =3D %f\n", lambda); > (gdb) p lambda > $1 =3D 0.031557098 > (gdb) info addr lambda > Symbol "lambda" is a complex DWARF expression: > 0: DW_OP_fbreg -20 > . > (gdb) inf frame > Stack level 0, frame at 0x7fffffffd990: > rip =3D 0x400679 in testFunc (21222.cc:13); saved rip =3D 0x4006dd > called by frame at 0x7fffffffd9d0 > source language c++. > Arglist at 0x7fffffffd980, args: a=3D0x0, n=3D0, sx=3D0x0, sy=3D0x0, rc= =3D0x0, nr=3D0,=20 > b=3D4, f=3D9.50000026e+09, c=3D0x0, d=3D0x0, e=3D0x0, gx=3D0x0, gy=3D= 0x0 > Locals at 0x7fffffffd980, Previous frame's sp is 0x7fffffffd990 > Saved registers: > rbp at 0x7fffffffd980, rip at 0x7fffffffd988 > (gdb) p *(float*)(0x7fffffffd990-20) > $2 =3D 0.031557098 >=20 > What compiler/version are you using? I'm using g++ 6.3.1. I believe this is more than a display issue, as if I attach the debugger here when the binary performs the printf I see the corrupted value. There's definitely something going on with GDB & VEX instructions (this doesn't happen if using the legacy SSE ones).=20=20 Breakpoint 1, testFunc (a=3D0x0, n=3D0, sx=3D0x0, sy=3D0x0, rc=3D0x0, nr=3D= 0, b=3D4, f=3D9.50000026e+09, c=3D0x0, d=3D0x0, e=3D0x0, gx=3D0x0, gy=3D0x0) at testf= unc.cpp:12 12 float lambda =3D C_LIGHT / f; (gdb) n 13 printf("lambda =3D %f\n", lambda); (gdb) info addr lambda Symbol "lambda" is a complex DWARF expression: 0: DW_OP_fbreg -20 =2E (gdb) inf frame Stack level 0, frame at 0x7fffffffde80: rip =3D 0x400562 in testFunc (testfunc.cpp:13); saved rip =3D 0x4005c6 called by frame at 0x7fffffffdec0 source language c++. Arglist at 0x7fffffffde70, args: a=3D0x0, n=3D0, sx=3D0x0, sy=3D0x0, rc=3D= 0x0, nr=3D0, b=3D4, f=3D9.50000026e+09, c=3D0x0, d=3D0x0, e=3D0x0, gx=3D0x0, gy=3D0x0 Locals at 0x7fffffffde70, Previous frame's sp is 0x7fffffffde80 Saved registers: rbp at 0x7fffffffde70, rip at 0x7fffffffde78 (gdb) p *(float*)(0x7fffffffde80 - 20) $1 =3D -5.38359187e+25 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21124-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Mar 11 00:54:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 96418 invoked by alias); 11 Mar 2017 00:54:24 -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 95867 invoked by uid 48); 11 Mar 2017 00:54:24 -0000 From: "msebor at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/18881] bogus 'Cannot resolve function foo to any overloaded instance' Date: Sat, 11 Mar 2017 00:54: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: 7.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gmail dot com 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: cc 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: 2017-q1/txt/msg00276.txt.bz2 Content-length: 987 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18881 Martin Sebor changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msebor at gmail dot com --- Comment #2 from Martin Sebor --- It looks fixed in GDB 7.10.1-31.fc23. The output also looks correct (the "const" in 7.9.1 output, i.e., "(const U *) 0x7fffffffd9bf" does not). $ gcc -g3 t.cpp && gdb -batch -ex 'b bar' -ex r -ex 'p FOO1(b)' -ex 'p FOO2= (b)' -ex 'p foo((A)b)' -ex 'p foo((A)b) ? foo((A)b) : foo((A)b)' a.out Breakpoint 1 at 0x40051e: file t.cpp, line 14. Breakpoint 1, bar (b=3D0x7fffffffe1af) at t.cpp:14 14 if (FOO2 (b)) $1 =3D (U *) 0x7fffffffe1af $2 =3D (U *) 0x7fffffffe1af $3 =3D (U *) 0x7fffffffe1af $4 =3D (U *) 0x7fffffffe1af --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21125-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 13 17:09:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 113568 invoked by alias); 13 Mar 2017 17:09:46 -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 113539 invoked by uid 48); 13 Mar 2017 17:09:45 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE isntructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Mon, 13 Mar 2017 17:09: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: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: short_desc 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: 2017-q1/txt/msg00277.txt.bz2 Content-length: 828 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 Adam Stylinski changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|A function with a |A function with VEX encoded |particular number of |SSE isntructions and a |arguments corrupts a value |particular number of |calculated on the stack |arguments corrupts a value |when stepping through the |calculated on the stack |function |when stepping through the | |function --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21126-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 13 17:10:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 113972 invoked by alias); 13 Mar 2017 17:10:01 -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 113948 invoked by uid 48); 13 Mar 2017 17:10:00 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Mon, 13 Mar 2017 17:10: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: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: short_desc 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: 2017-q1/txt/msg00278.txt.bz2 Content-length: 828 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 Adam Stylinski changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|A function with VEX encoded |A function with VEX encoded |SSE isntructions and a |SSE instructions and a |particular number of |particular number of |arguments corrupts a value |arguments corrupts a value |calculated on the stack |calculated on the stack |when stepping through the |when stepping through the |function |function --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21127-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 13 23:07:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 10722 invoked by alias); 13 Mar 2017 23:07:03 -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 10691 invoked by uid 48); 13 Mar 2017 23:07:03 -0000 From: "msebor at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/15242] function-like cast notation Date: Mon, 13 Mar 2017 23:07: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gmail dot com 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: cc 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: 2017-q1/txt/msg00279.txt.bz2 Content-length: 830 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15242 Martin Sebor changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msebor at gmail dot com --- Comment #1 from Martin Sebor --- This missing functionality causes trouble when evaluating GCC predefined ma= cros like __DBL_MAX__. For example, in GNU gdb (GDB) Fedora 7.12.1-47.fc25: (gdb) p __DBL_MAX__ A syntax error in expression, near `1.79769313486231570815e+308L)'. (gdb) info macro __DBL_MAX__ Defined at /ssd/src/gcc/79800/gcc/gimple-fold.c:0 -D__DBL_MAX__=3Ddouble(1.79769313486231570815e+308L) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21128-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 14 11:17:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 105074 invoked by alias); 14 Mar 2017 11:17:58 -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 105043 invoked by uid 48); 14 Mar 2017 11:17:57 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/15242] function-like cast notation Date: Tue, 14 Mar 2017 11:17: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: cc 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: 2017-q1/txt/msg00280.txt.bz2 Content-length: 834 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15242 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #2 from Pedro Alves --- We should obviously fix that, but I thought I'd mention the workaround for folks that come here after running into this: (gdb) macro define __DBL_MAX__ ((double)1.79769313486231570815e+308L) I.e., redefine the macro to something that gdb understands. Evaluating expressions that involve __DBL_MAX__ will now use GDB's definition instead = of the originally compiled in one. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21129-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 14 18:22:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 25911 invoked by alias); 14 Mar 2017 18:22:01 -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 25866 invoked by uid 55); 14 Mar 2017 18:22:00 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21220] "restore" for large data structures extremely slow on GNU/Linux Date: Tue, 14 Mar 2017 18:22: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: arnez at linux dot vnet.ibm.com 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: 2017-q1/txt/msg00281.txt.bz2 Content-length: 2064 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21220 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Andreas Arnez : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D87c336f60ecc= c6506ff19369c29575f43fea02ea commit 87c336f60eccc6506ff19369c29575f43fea02ea Author: Andreas Arnez Date: Tue Mar 14 19:20:46 2017 +0100 inf-ptrace: Do not stop memory transfers after a single word When inf_ptrace_xfer_partial performs a memory transfer via ptrace with PT_READ_I, PT_WRITE_I (aka PTRACE_PEEKTEXT, PTRACE_POKETEXT), etc., then it currently transfers at most one word. This behavior yields degraded performance, particularly if the caller has significant preparation work for each invocation. And indeed it has for writing, in memory_xfer_partial in target.c, where all of the remaining data to be transferred is copied to a temporary buffer each time, for breakpoint shadow handling. Thus large writes have quadratic runtime and can take hours. Note: On GNU/Linux targets GDB usually does not use inf_ptrace_xfer_partial for large memory transfers, but attempts a sing= le read/write from/to /proc//mem instead. However, the kernel may reject writes to /proc//mem (such as kernels prior to 2.6.39), or /proc may not be mounted. In both cases GDB falls back to the ptrace mechanism. This patch fixes the performance issue by attempting to fulfill the who= le transfer request in inf_ptrace_xfer_partial, using a loop around the ptrace call. gdb/ChangeLog: PR gdb/21220 * inf-ptrace.c (inf_ptrace_xfer_partial): In "case TARGET_OBJECT_MEMORY", extract the logic for ptrace peek/poke... (inf_ptrace_peek_poke): ...here. New function. Now also loop over ptrace peek/poke until end of buffer or error. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21130-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 14 18:28:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36474 invoked by alias); 14 Mar 2017 18:28:12 -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 36449 invoked by uid 48); 14 Mar 2017 18:28:11 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21220] "restore" for large data structures extremely slow on GNU/Linux Date: Tue, 14 Mar 2017 18:28: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: arnez at linux dot vnet.ibm.com 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00282.txt.bz2 Content-length: 798 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21220 Andreas Arnez changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Andreas Arnez --- (In reply to cvs-commit@gcc.gnu.org from comment #2) > The master branch has been updated by Andreas Arnez : >=20 > https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git; > h=3D87c336f60eccc6506ff19369c29575f43fea02ea The above commit should fix the bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21131-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 15 20:41:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 52245 invoked by alias); 15 Mar 2017 20:41:49 -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 52205 invoked by uid 48); 15 Mar 2017 20:41:48 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug python/18779] collection of issues handling C strings in python Date: Wed, 15 Mar 2017 20:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: cc 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: 2017-q1/txt/msg00283.txt.bz2 Content-length: 867 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18779 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.marchi at ericsson d= ot com --- Comment #2 from Simon Marchi --- I just tried to use LazyString for the first time, and I stumbled on similar problems. My big question is: how do you get a Python string out of the LazyString? I ended up doing lazy_string.value().address.string() After reading the doc, I expected lazy_string.value() to return a gdb.Value= () representing a char*. I guess it works if the string is nul-terminated onl= y... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21132-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 16 16:31:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 46664 invoked by alias); 16 Mar 2017 16:31:22 -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 46630 invoked by uid 55); 16 Mar 2017 16:31:20 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug python/17728] gdb.LazyString is confused by typedefs Date: Thu, 16 Mar 2017 16:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q1/txt/msg00284.txt.bz2 Content-length: 1776 https://sourceware.org/bugzilla/show_bug.cgi?id=3D17728 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Doug Evans : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D34b433203b5f= 56149c27a8dfea21a921392cb158 commit 34b433203b5f56149c27a8dfea21a921392cb158 Author: Doug Evans Date: Wed Mar 15 15:35:13 2017 -0700 Fix various python lazy string bugs. gdb/ChangeLog: PR python/17728, python/18439, python/18779 * python/py-lazy-string.c (lazy_string_object): Clarify use of LENG= TH member. Change type of TYPE member to PyObject *. All uses update= d. (stpy_convert_to_value): Fix handling of TYPE_CODE_PTR. (gdbpy_create_lazy_string_object): Flag bad length values. Handle TYPE_CODE_ARRAY with possibly different user-provided length. Handle typedefs in incoming type. (stpy_lazy_string_elt_type): New function. (gdbpy_extract_lazy_string): Call it. * python/py-value.c (valpy_lazy_string): Flag bad length values. Fix handling of TYPE_CODE_PTR. Handle TYPE_CODE_ARRAY. Handle typedefs in incoming type. gdb/testsuite/ChangeLog: PR python/17728, python/18439, python/18779 * gdb.python/py-value.c (main) Delete locals sptr, sn. * gdb.python/py-lazy-string.c (pointer): New typedef. (main): New locals ptr, array, typedef_ptr. * gdb.python/py-value.exp: Move lazy string tests to ... * gdb.python/py-lazy-string.exp: ... here. Add more tests for poin= ter, array, typedef lazy strings. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21133-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 16 17:24:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 117475 invoked by alias); 16 Mar 2017 17:24:22 -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 117374 invoked by uid 48); 16 Mar 2017 17:24:17 -0000 From: "dje at google dot com" To: gdb-prs@sourceware.org Subject: [Bug python/18439] lazy string value method ignores length Date: Thu, 16 Mar 2017 17:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dje at google dot com 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: 2017-q1/txt/msg00285.txt.bz2 Content-length: 1764 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18439 --- Comment #1 from dje at google dot com --- [manually copied from 17728] The master branch has been updated by Doug Evans : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D34b433203b5f= 56149c27a8dfea21a921392cb158 commit 34b433203b5f56149c27a8dfea21a921392cb158 Author: Doug Evans Date: Wed Mar 15 15:35:13 2017 -0700 Fix various python lazy string bugs. gdb/ChangeLog: PR python/17728, python/18439, python/18779 * python/py-lazy-string.c (lazy_string_object): Clarify use of LENG= TH member. Change type of TYPE member to PyObject *. All uses update= d. (stpy_convert_to_value): Fix handling of TYPE_CODE_PTR. (gdbpy_create_lazy_string_object): Flag bad length values. Handle TYPE_CODE_ARRAY with possibly different user-provided length. Handle typedefs in incoming type. (stpy_lazy_string_elt_type): New function. (gdbpy_extract_lazy_string): Call it. * python/py-value.c (valpy_lazy_string): Flag bad length values. Fix handling of TYPE_CODE_PTR. Handle TYPE_CODE_ARRAY. Handle typedefs in incoming type. gdb/testsuite/ChangeLog: PR python/17728, python/18439, python/18779 * gdb.python/py-value.c (main) Delete locals sptr, sn. * gdb.python/py-lazy-string.c (pointer): New typedef. (main): New locals ptr, array, typedef_ptr. * gdb.python/py-value.exp: Move lazy string tests to ... * gdb.python/py-lazy-string.exp: ... here. Add more tests for poin= ter, array, typedef lazy strings. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21134-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 16 17:25:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 2185 invoked by alias); 16 Mar 2017 17:25:34 -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 2142 invoked by uid 48); 16 Mar 2017 17:25:33 -0000 From: "dje at google dot com" To: gdb-prs@sourceware.org Subject: [Bug python/18779] collection of issues handling C strings in python Date: Thu, 16 Mar 2017 17:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dje at google dot com 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: 2017-q1/txt/msg00286.txt.bz2 Content-length: 1764 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18779 --- Comment #3 from dje at google dot com --- [manually copied from 17728] The master branch has been updated by Doug Evans : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D34b433203b5f= 56149c27a8dfea21a921392cb158 commit 34b433203b5f56149c27a8dfea21a921392cb158 Author: Doug Evans Date: Wed Mar 15 15:35:13 2017 -0700 Fix various python lazy string bugs. gdb/ChangeLog: PR python/17728, python/18439, python/18779 * python/py-lazy-string.c (lazy_string_object): Clarify use of LENG= TH member. Change type of TYPE member to PyObject *. All uses update= d. (stpy_convert_to_value): Fix handling of TYPE_CODE_PTR. (gdbpy_create_lazy_string_object): Flag bad length values. Handle TYPE_CODE_ARRAY with possibly different user-provided length. Handle typedefs in incoming type. (stpy_lazy_string_elt_type): New function. (gdbpy_extract_lazy_string): Call it. * python/py-value.c (valpy_lazy_string): Flag bad length values. Fix handling of TYPE_CODE_PTR. Handle TYPE_CODE_ARRAY. Handle typedefs in incoming type. gdb/testsuite/ChangeLog: PR python/17728, python/18439, python/18779 * gdb.python/py-value.c (main) Delete locals sptr, sn. * gdb.python/py-lazy-string.c (pointer): New typedef. (main): New locals ptr, array, typedef_ptr. * gdb.python/py-value.exp: Move lazy string tests to ... * gdb.python/py-lazy-string.exp: ... here. Add more tests for poin= ter, array, typedef lazy strings. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21135-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 16 17:37:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 29189 invoked by alias); 16 Mar 2017 17:37:09 -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 29165 invoked by uid 48); 16 Mar 2017 17:37:09 -0000 From: "andre.poenitz at digia dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21256] New: [Feature Request] Access symbols in an object file Date: Thu, 16 Mar 2017 17:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: andre.poenitz at digia dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00287.txt.bz2 Content-length: 858 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21256 Bug ID: 21256 Summary: [Feature Request] Access symbols in an object file Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: andre.poenitz at digia dot com Target Milestone: --- While the functionality can be emulated by running using something on top of gdb.execute('maint print msymbols %s' % objfile.filename), it would be convenient to be able to access symbols in an object file (e.g. obtained us= ing a new_objfile handler) more directly. I guess I am looking for some kind of "inverse" of Symtab.objfile here. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21136-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 16 17:38:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35652 invoked by alias); 16 Mar 2017 17:38:44 -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 35616 invoked by uid 48); 16 Mar 2017 17:38:43 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug python/18779] collection of issues handling C strings in python Date: Thu, 16 Mar 2017 17:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: 2017-q1/txt/msg00288.txt.bz2 Content-length: 375 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18779 --- Comment #4 from Simon Marchi --- I tested quickly, it looks good, awesome! Thanks! >>> s >>> print(s.value().type) char [8] >>> print(s.value()) "lalalala" --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21137-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 16 17:43:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 40852 invoked by alias); 16 Mar 2017 17:43:24 -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 40815 invoked by uid 48); 16 Mar 2017 17:43:23 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21256] [Feature Request] Access symbols in an object file Date: Thu, 16 Mar 2017 17:43: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00289.txt.bz2 Content-length: 411 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21256 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.marchi at ericsson d= ot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21138-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 16 17:54:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 24812 invoked by alias); 16 Mar 2017 17:54:38 -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 24788 invoked by uid 48); 16 Mar 2017 17:54:37 -0000 From: "andre.poenitz at qt dot io" To: gdb-prs@sourceware.org Subject: [Bug gdb/10886] Crash of gdb 7.0 as shipped with Unbuntu 9.10, probably due to a double free. Date: Thu, 16 Mar 2017 17:54: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.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: andre.poenitz at qt dot io X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: OBSOLETE X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.1 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00290.txt.bz2 Content-length: 553 https://sourceware.org/bugzilla/show_bug.cgi?id=3D10886 Andre' changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |OBSOLETE --- Comment #3 from Andre' --- I guess that's not relevant anymore. Resolving as 'obsolete' --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21139-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 16 17:55:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 29668 invoked by alias); 16 Mar 2017 17:55:17 -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 29642 invoked by uid 48); 16 Mar 2017 17:55:16 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21257] New: gdb.Type.name is empty for pointer/array types Date: Thu, 16 Mar 2017 17:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00291.txt.bz2 Content-length: 745 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21257 Bug ID: 21257 Summary: gdb.Type.name is empty for pointer/array types Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: simon.marchi at ericsson dot com Target Milestone: --- >>> gdb.lookup_type('int').name 'int' >>> gdb.lookup_type('int').pointer().name >>> gdb.lookup_type('int').array(5).name The later two commands return None. It seems to me like they should return 'int *' and 'int [5]' respectively. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21140-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 17 14:58:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78895 invoked by alias); 17 Mar 2017 14:58:51 -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 78864 invoked by uid 55); 17 Mar 2017 14:58:51 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/19637] bound_registers.py uses type "long", but long merged with "int" in python3 Date: Fri, 17 Mar 2017 14:58: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q1/txt/msg00292.txt.bz2 Content-length: 863 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19637 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D7503099f3e29= 739d34cb1224d54fba96404e6e61 commit 7503099f3e29739d34cb1224d54fba96404e6e61 Author: Jonah Graham Date: Fri Mar 17 14:57:44 2017 +0000 Fix PR gdb/19637: bound_registers.py: Add support for Python 3 Fix this the same way gdb/python/lib/gdb/printing.py handles it. gdb/Changelog: 2017-03-17 Jonah Graham PR gdb/19637 * python/lib/gdb/printer/bound_registers.py: Add support for Python 3. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21141-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 17 15:01:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 87516 invoked by alias); 17 Mar 2017 15:01:17 -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 87490 invoked by uid 48); 17 Mar 2017 15:01:16 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/19637] bound_registers.py uses type "long", but long merged with "int" in python3 Date: Fri, 17 Mar 2017 15:01: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat 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: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution target_milestone 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: 2017-q1/txt/msg00293.txt.bz2 Content-length: 634 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19637 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |palves at redhat dot com Resolution|--- |FIXED Target Milestone|--- |8.0 --- Comment #5 from Pedro Alves --- Fix pushed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21142-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 17 16:25:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 22235 invoked by alias); 17 Mar 2017 16:25:27 -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 15397 invoked by uid 55); 17 Mar 2017 16:25:15 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug remote/21188] Remote timeouts don't work correctly Date: Fri, 17 Mar 2017 16:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00294.txt.bz2 Content-length: 2171 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21188 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D9bcbdca808b5= f9fec6217d20bd4b48a56008c460 commit 9bcbdca808b5f9fec6217d20bd4b48a56008c460 Author: Pedro Alves Date: Fri Mar 17 16:08:12 2017 +0000 PR remote/21188: Fix remote serial timeout As Gareth McMullin reports at , the timeout mechanism in ser-unix.c was broken by commit 048094acc ("target remote: Don't rely on immediate_quit (introduce quit handlers)"). Instead of applying a local fix, and since we now finally always use interrupt_select [1], let's get rid of hardwire_readchar entirely, and use ser_base_readchar instead, which has similar timeout handling, except for the bug. Smoke tested with: $ socat -d -d pty,raw,echo=3D0 pty,raw,echo=3D0 2017/03/14 14:08:13 socat[4994] N PTY is /dev/pts/14 2017/03/14 14:08:13 socat[4994] N PTY is /dev/pts/15 2017/03/14 14:08:13 socat[4994] N starting data transfer loop with FDs [3,3] and [5,5] $ gdbserver /dev/pts/14 PROG $ gdb PROG -ex "tar rem /dev/pts/15" and then a few continues/ctrl-c's, plus killing gdbserver and socat. [1] - See FIXME comments being removed. gdb/ChangeLog: 2017-03-17 Pedro Alves PR remote/21188 * ser-base.c (ser_base_wait_for): Add comment. (do_ser_base_readchar): Improve comment based on the ser-unix.c's version. * ser-unix.c (hardwire_raw): Remove reference to scb->current_timeout. (wait_for, do_hardwire_readchar, hardwire_readchar): Delete. (hardwire_ops): Install ser_base_readchar instead of hardwire_readchar. * serial.h (struct serial) : Remove fields. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21144-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 17 16:27:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 28258 invoked by alias); 17 Mar 2017 16:27:25 -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 28223 invoked by uid 48); 17 Mar 2017 16:27:25 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21188] Remote timeouts don't work correctly Date: Fri, 17 Mar 2017 16:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat 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: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone 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: 2017-q1/txt/msg00296.txt.bz2 Content-length: 371 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21188 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21143-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 17 16:27:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27763 invoked by alias); 17 Mar 2017 16:27:17 -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 27729 invoked by uid 48); 17 Mar 2017 16:27:16 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21188] Remote timeouts don't work correctly Date: Fri, 17 Mar 2017 16:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat 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 cc resolution 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: 2017-q1/txt/msg00295.txt.bz2 Content-length: 586 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21188 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |palves at redhat dot com Resolution|--- |FIXED --- Comment #3 from Pedro Alves --- Should be fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21145-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 17 16:57:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 82420 invoked by alias); 17 Mar 2017 16:57:56 -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 82391 invoked by uid 48); 17 Mar 2017 16:57:54 -0000 From: "emachado at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug tui/21227] GDB crashes when switching layout from asm to src Date: Fri, 17 Mar 2017 16:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: emachado at sourceware dot org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00297.txt.bz2 Content-length: 728 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21227 Edjunior Machado changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emachado at sourceware dot= org --- Comment #1 from Edjunior Machado --- Looks similar to the regression fixed by this commit: https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommitdiff;h= =3D5f6fd321915fae0194e01322d22cad4e451e8d20 Could you please confirm if this is still valid on upstream gdb? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21146-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 17 19:05:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94973 invoked by alias); 17 Mar 2017 19:05:58 -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 94944 invoked by uid 48); 17 Mar 2017 19:05:58 -0000 From: "perhaad at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18074] crash using "info frame" Date: Fri, 17 Mar 2017 19:05: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: perhaad at gmail dot com 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: cc 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: 2017-q1/txt/msg00298.txt.bz2 Content-length: 395 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18074 Perhaad Mistry changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |perhaad at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21147-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Mar 18 02:26:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 48512 invoked by alias); 18 Mar 2017 02:26:46 -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 48482 invoked by uid 48); 18 Mar 2017 02:26:45 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/18215] need to save/reset/restore tty settings when popping into a shell from tui mode Date: Sat, 18 Mar 2017 02:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: cc 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: 2017-q1/txt/msg00299.txt.bz2 Content-length: 411 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18215 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.marchi at ericsson d= ot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21148-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Mar 19 13:30:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 5005 invoked by alias); 19 Mar 2017 13:30:40 -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 4969 invoked by uid 48); 19 Mar 2017 13:30:39 -0000 From: "elouan.appere@club-internet.fr" To: gdb-prs@sourceware.org Subject: [Bug gdb/21272] New: Missing call to to_can_do_single_step for arm-none-eabi Date: Sun, 19 Mar 2017 13:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: elouan.appere@club-internet.fr X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q1/txt/msg00300.txt.bz2 Content-length: 1319 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21272 Bug ID: 21272 Summary: Missing call to to_can_do_single_step for arm-none-eabi Product: gdb Version: 7.12 Status: UNCONFIRMED Severity: critical Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: elouan.appere@club-internet.fr Target Milestone: --- Created attachment 9906 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9906&action=3Dedit Logging ouput from GDB (with debug remote and debug target both set to 1) I'm currently implementing a GDB remote stub on an ARMv6 target (--target=3Darm-none-eabi). This stub does _not_ support single-stepping vi= a the OS or via hardware. The stub replies "PacketSize=3D516;qXfer:features:read+;QThreadEvents+;vContSupported+;swbre= ak+;QStartNoAckMode+" to "qSupported", and "vCont;c;C" to "vCont?". In spite of this, to_target_can_do_single_step is never called, and GDB sen= ds a vCont packet containing 's', which the remote stub does not support. Please find enclosed the logging ouput from GDB (with debug remote and debug target both set to 1). Any thoughts? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21149-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 20 19:57:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 108039 invoked by alias); 20 Mar 2017 19:57:42 -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 108008 invoked by uid 48); 20 Mar 2017 19:57:42 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug server/21169] GDBServer on ARM can crash the inferior while single stepping Date: Mon, 20 Mar 2017 19:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: antoine.tremblay at ericsson dot com X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: 2017-q1/txt/msg00301.txt.bz2 Content-length: 467 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21169 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |antoine.tremblay at= ericsson dot c | |om --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21152-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 20 20:50:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 17239 invoked by alias); 20 Mar 2017 20:50:20 -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 17188 invoked by uid 55); 20 Mar 2017 20:50:19 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Mon, 20 Mar 2017 20:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00304.txt.bz2 Content-length: 1278 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 --- Comment #15 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Keith Seitz : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Da65cfae5f8b2= 68158c23a862e7a996d15bbcef0e commit a65cfae5f8b268158c23a862e7a996d15bbcef0e Author: Artemiy Volkov Date: Mon Mar 20 13:47:41 2017 -0700 Add ability to return rvalue reference values from value_ref Parameterize value_ref() by the kind of reference type the value of whi= ch is requested. Change all callers to use the new API. gdb/ChangeLog PR gdb/14441 * ada-lang.c (ada_evaluate_subexp): Adhere to the new value_ref() interface. * c-valprint.c (c_value_print): Likewise. * infcall.c (value_arg_coerce): Likewise. * python/py-value.c (valpy_reference_value): Likewise. * valops.c (value_cast, value_reinterpret_cast) (value_dynamic_cast, typecmp): Likewise. (value_ref): Parameterize by kind of return value reference type. * value.h (value_ref): Add new parameter "refcode". --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21158-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 20 20:50:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20314 invoked by alias); 20 Mar 2017 20:50:54 -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 20283 invoked by uid 55); 20 Mar 2017 20:50:53 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Mon, 20 Mar 2017 20:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00310.txt.bz2 Content-length: 4297 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 --- Comment #21 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Keith Seitz : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Daa0061181ab0= 0081e9907447561e589d6edee9f2 commit aa0061181ab00081e9907447561e589d6edee9f2 Author: Artemiy Volkov Date: Mon Mar 20 13:47:54 2017 -0700 Convert lvalue reference type check to general reference type check In almost all contexts (except for overload resolution rules and expres= sion semantics), lvalue and rvalue references are equivalent. That means tha= t in all but these cases we can replace a TYPE_CODE_REF check to a TYPE_IS_REFER= ENCE check and, for switch statements, add a case label for a rvalue referen= ce type next to a case label for an lvalue reference type. This patch does exac= tly that. gdb/ChangeLog PR gdb/14441 * aarch64-tdep.c (aarch64_type_align) (aarch64_extract_return_value, aarch64_store_return_value): Change lvalue reference type checks to general reference type checks. * amd64-tdep.c (amd64_classify): Likewise. * amd64-windows-tdep.c (amd64_windows_passed_by_integer_register): Likewise. * arm-tdep.c (arm_type_align, arm_extract_return_value) (arm_store_return_value): Likewise. * ax-gdb.c (gen_fetch, gen_cast): Likewise. * c-typeprint.c (c_print_type): Likewise. * c-varobj.c (adjust_value_for_child_access, c_value_of_variable) (cplus_number_of_children, cplus_describe_child): Likewise. * compile/compile-c-symbols.c (generate_vla_size): Likewise. * completer.c (expression_completer): Likewise. * cp-support.c (make_symbol_overload_list_adl_namespace): Likewise. * darwin-nat-info.c (info_mach_region_command): Likewise. * dwarf2loc.c (entry_data_value_coerce_ref) (value_of_dwarf_reg_entry): Likewise. * eval.c (ptrmath_type_p, evaluate_subexp_standard) (evaluate_subexp_for_address, evaluate_subexp_for_sizeof): Likewise. * findvar.c (extract_typed_address, store_typed_address): Likewise. * gdbtypes.c (rank_one_type): Likewise. * hppa-tdep.c (hppa64_integral_or_pointer_p): Likewise. * infcall.c (value_arg_coerce): Likewise. * language.c (pointer_type): Likewise. * m32c-tdep.c (m32c_reg_arg_type, m32c_m16c_address_to_pointer): Likewise. * m88k-tdep.c (m88k_integral_or_pointer_p): Likewise. * mn10300-tdep.c (mn10300_type_align): Likewise. * msp430-tdep.c (msp430_push_dummy_call): Likewise. * ppc-sysv-tdep.c (do_ppc_sysv_return_value) (ppc64_sysv_abi_push_param, ppc64_sysv_abi_return_value): Likewise. * printcmd.c (print_formatted, x_command): Likewise. * python/py-type.c (typy_get_composite, typy_template_argument): Likewise. * python/py-value.c (valpy_referenced_value) (valpy_get_dynamic_type, value_has_field): Likewise. * s390-linux-tdep.c (s390_function_arg_integer): Likewise. * sparc-tdep.c (sparc_integral_or_pointer_p): Likewise. * sparc64-tdep.c (sparc64_integral_or_pointer_p): Likewise. * spu-tdep.c (spu_scalar_value_p): Likewise. * symtab.c (lookup_symbol_aux): Likewise. * typeprint.c (whatis_exp, print_type_scalar): Likewise. * valarith.c (binop_types_user_defined_p, unop_user_defined_p): Likewise. * valops.c (value_cast_pointers, value_cast) (value_reinterpret_cast, value_dynamic_cast, value_addr, typecmp) (value_struct_elt, value_struct_elt_bitpos) (value_find_oload_method_list, find_overload_match) (value_rtti_indirect_type): Likewise. * valprint.c (val_print_scalar_type_p, generic_val_print): Likewise. * value.c (value_actual_type, value_as_address, unpack_long) (pack_long, pack_unsigned_long, coerce_ref_if_computed) (coerce_ref): Likewise. * varobj.c (varobj_get_value_type): Likewise. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21150-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 20 20:50:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 16081 invoked by alias); 20 Mar 2017 20:50:10 -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 16038 invoked by uid 55); 20 Mar 2017 20:50:09 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Mon, 20 Mar 2017 20:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00302.txt.bz2 Content-length: 1295 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 --- Comment #13 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Keith Seitz : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Df9aeb8d499fa= 12610610dc19618230304c698f6c commit f9aeb8d499fa12610610dc19618230304c698f6c Author: Artemiy Volkov Date: Mon Mar 20 13:47:30 2017 -0700 Add definitions for rvalue reference types This patch introduces preliminal definitions regarding C++11 rvalue references to the gdb type system. In addition to an enum type_code entry, a field= in struct type and an accessor macro for that which are created similarly = to the lvalue references counterparts, we also introduce a TYPE_REFERENCE convenience macro used to check for both kinds of references simultaneously as they= are equivalent in many contexts. gdb/Changelog PR gdb/14441 * gdbtypes.h (enum type_code) : New constant. (TYPE_IS_REFERENCE): New macro. (struct type): Add rvalue_reference_type field. (TYPE_RVALUE_REFERENCE_TYPE): New macro. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21153-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 20 20:50:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 17852 invoked by alias); 20 Mar 2017 20:50:25 -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 17791 invoked by uid 55); 20 Mar 2017 20:50:25 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Mon, 20 Mar 2017 20:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00305.txt.bz2 Content-length: 1210 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 --- Comment #16 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Keith Seitz : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D53cc15f5fe1f= 5e2358994d4f60f1c2aa9115004d commit 53cc15f5fe1f5e2358994d4f60f1c2aa9115004d Author: Artemiy Volkov Date: Mon Mar 20 13:47:43 2017 -0700 Support rvalue reference type in parser This patch implements correct parsing of C++11 rvalue reference typenam= es. This is done in full similarity to the handling of regular references by adding a '&&' token handling in c-exp.y, defining an rvalue reference type pie= ce, and implementing a follow type derivation in follow_types(). gdb/ChangeLog PR gdb/14441 * c-exp.y (ptr_operator): Handle the '&&' token in the typename. * parse.c (insert_type): Change assert statement. (follow_types): Handle rvalue reference types. * parser-defs.h (enum type_pieces) : New constant. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21154-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 20 20:50:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 18748 invoked by alias); 20 Mar 2017 20:50:37 -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 18526 invoked by uid 55); 20 Mar 2017 20:50:30 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Mon, 20 Mar 2017 20:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00306.txt.bz2 Content-length: 1029 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 --- Comment #17 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Keith Seitz : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3De4347c89f3a1= 4b480fc88581d1363835f7b99b68 commit e4347c89f3a14b480fc88581d1363835f7b99b68 Author: Artemiy Volkov Date: Mon Mar 20 13:47:46 2017 -0700 Implement demangling for rvalue reference type names This patch fixes demangling of names containing rvalue reference typena= mes by handling DEMANGLE_COMPONENT_RVALUE_REFERENCE demangle component. gdb/ChangeLog PR gdb/14441 * cp-name-parser.y (ptr_operator): Handle the '&&' token in typename. * cp-support.c (replace_typedefs): Handle DEMANGLE_COMPONENT_RVALUE_REFERENCE. * python/py-type.c (typy_lookup_type): Likewise. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21157-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 20 20:50:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 19972 invoked by alias); 20 Mar 2017 20:50:49 -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 19794 invoked by uid 55); 20 Mar 2017 20:50:47 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Mon, 20 Mar 2017 20:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00309.txt.bz2 Content-length: 1810 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 --- Comment #20 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Keith Seitz : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D3fcf899da106= 890f3948093c2424f9dff67d6fe0 commit 3fcf899da106890f3948093c2424f9dff67d6fe0 Author: Artemiy Volkov Date: Mon Mar 20 13:47:52 2017 -0700 Support rvalue references in the gdb python module (includes doc/) This patch adds the ability to inspect rvalue reference types and values using the gdb python module. This is achieved by creating two wrappers for valpy_reference_value(), using the ReferenceExplorer class to handle the objects of rvalue reference types and placing necessary checks for a TYPE_CODE_RVALUE_REF type code next to the checks for a TYPE_CODE_REF t= ype code. gdb/ChangeLog PR gdb/14441 * doc/python.texi (Types in Python): Add TYPE_CODE_RVALUE_REF to table of constants. * python/lib/gdb/command/explore.py: Support exploring values of rvalue reference types. * python/lib/gdb/types.py: Implement get_basic_type() for rvalue reference types. * python/py-type.c (pyty_codes) : New constant. * python/py-value.c (valpy_getitem): Add an rvalue reference check. (valpy_reference_value): Add new parameter "refcode". (valpy_lvalue_reference_value, valpy_rvalue_reference_value): New wrappers for valpy_reference_value(). * python/py-xmethods.c (gdbpy_get_xmethod_result_type) (gdbpy_invoke_xmethod): Likewise. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21156-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 20 20:50:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 19681 invoked by alias); 20 Mar 2017 20:50:46 -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 19477 invoked by uid 55); 20 Mar 2017 20:50:44 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Mon, 20 Mar 2017 20:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00308.txt.bz2 Content-length: 1056 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 --- Comment #19 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Keith Seitz : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D4297a3f00299= 74c62628d69b6f3f9ef25f01ea7d commit 4297a3f0029974c62628d69b6f3f9ef25f01ea7d Author: Artemiy Volkov Date: Mon Mar 20 13:47:50 2017 -0700 Support DW_TAG_rvalue_reference type Make gdb DWARF reader understand the DW_TAG_rvalue_reference type tag. Handling of this tag is done in the existing read_tag_reference_type() function,= to which we add a new parameter representing the kind of reference type (lvalue vs rvalue). gdb/ChangeLog PR gdb/14441 * dwarf2read.c (process_die, read_type_die_1): Handle the DW_TAG_rvalue_reference_type DIE. (read_tag_reference_type): Add new parameter "refcode". --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21155-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 20 20:50:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 19015 invoked by alias); 20 Mar 2017 20:50:40 -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 18730 invoked by uid 55); 20 Mar 2017 20:50:36 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Mon, 20 Mar 2017 20:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00307.txt.bz2 Content-length: 1213 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 --- Comment #18 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Keith Seitz : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3De1cb32134764= 85a01aa11ecedfa186e386cb4bdb commit e1cb3213476485a01aa11ecedfa186e386cb4bdb Author: Artemiy Volkov Date: Mon Mar 20 13:47:48 2017 -0700 Implement printing of rvalue reference types and values This patch provides the ability to print out names of rvalue reference types and values of those types. This is done in full similarity to regular references, and as with them, we don't print out "const" suffix because= all rvalue references are const. gdb/ChangeLog PR gdb/14441 * c-typeprint.c (c_print_type, c_type_print_varspec_prefix) (c_type_print_modifier, c_type_print_varspec_suffix) (c_type_print_base): Support printing rvalue reference types. * c-valprint.c (c_val_print, c_value_print): Support printing rvalue reference values. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21151-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 20 20:50:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 16664 invoked by alias); 20 Mar 2017 20:50:14 -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 16633 invoked by uid 55); 20 Mar 2017 20:50:14 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Mon, 20 Mar 2017 20:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00303.txt.bz2 Content-length: 2329 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 --- Comment #14 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Keith Seitz : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D3b22433085e4= cfee83f5c52f3baa8fb9bc67f8dd commit 3b22433085e4cfee83f5c52f3baa8fb9bc67f8dd Author: Artemiy Volkov Date: Mon Mar 20 13:47:39 2017 -0700 Change {lookup,make}_reference_type API Parameterize lookup_reference_type() and make_reference_type() by the k= ind of reference type we want to look up. Create two wrapper functions lookup_{lvalue,rvalue}_reference_type() for lookup_reference_type() to simplify the API. Change all callers to use the new API. gdb/Changelog PR gdb/14441 * dwarf2read.c (read_tag_reference_type): Use lookup_lvalue_reference_type() instead of lookup_reference_type(). * eval.c (evaluate_subexp_standard): Likewise. * f-exp.y: Likewise. * gdbtypes.c (make_reference_type, lookup_reference_type): Generalize with rvalue reference types. (lookup_lvalue_reference_type, lookup_rvalue_reference_type): New convenience wrappers for lookup_reference_type(). * gdbtypes.h (make_reference_type, lookup_reference_type): Add a reference kind parameter. (lookup_lvalue_reference_type, lookup_rvalue_reference_type): Add wrappers for lookup_reference_type(). * guile/scm-type.c (gdbscm_type_reference): Use lookup_lvalue_reference_type() instead of lookup_reference_type(). * guile/scm-value.c (gdbscm_value_dynamic_type): Likewise. * parse.c (follow_types): Likewise. * python/py-type.c (typy_reference, typy_lookup_type): Likewise. * python/py-value.c (valpy_get_dynamic_type, valpy_getitem): Likewise. * python/py-xmethods.c (gdbpy_get_xmethod_result_type) (gdbpy_invoke_xmethod): Likewise. * stabsread.c: Provide extra argument to make_reference_type() call. * valops.c (value_ref, value_rtti_indirect_type): Use lookup_lvalue_reference_type() instead of lookup_reference_type(). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21160-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 20 20:51:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 21258 invoked by alias); 20 Mar 2017 20:51:13 -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 21229 invoked by uid 55); 20 Mar 2017 20:51:13 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Mon, 20 Mar 2017 20:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00312.txt.bz2 Content-length: 2191 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 --- Comment #23 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Keith Seitz : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dc0f55cc689a5= 7deb342b988b8f0ecb908f0a76e1 commit c0f55cc689a57deb342b988b8f0ecb908f0a76e1 Author: Artemiy Volkov Date: Mon Mar 20 13:47:59 2017 -0700 Add rvalue reference tests and docs This patch adds tests for the initial rvalue reference support patchset= .=20 All of the new tests are practically mirrored regular references tests and, except for the demangler ones, are introduced in new files, which are set to be compiled with -std=3Dgnu++11. Tested are printing of rvalue reference = types and values, rvalue reference parameters in function overloading, demangling= of function names containing rvalue reference parameters, casts to rvalue reference types, application of the sizeof operator to rvalue reference types and values, and support for rvalue references within the gdb python mod= ule. gdb/ChnageLog PR gdb/14441 * NEWS: Mention support for rvalue references in GDB and python. * doc/gdb.texinfo (C Plus Plus Expressions): Mention that GDB supports both lvalue and rvalue references. gdb/testsuite/ChangeLog PR gdb/14441 * gdb.cp/demangle.exp: Add rvalue reference tests. * gdb.cp/rvalue-ref-casts.cc: New file. * gdb.cp/rvalue-ref-casts.exp: New file. * gdb.cp/rvalue-ref-overload.cc: New file. * gdb.cp/rvalue-ref-overload.exp: New file. * gdb.cp/rvalue-ref-params.cc: New file. * gdb.cp/rvalue-ref-params.exp: New file. * gdb.cp/rvalue-ref-sizeof.cc: New file. * gdb.cp/rvalue-ref-sizeof.exp: New file. * gdb.cp/rvalue-ref-types.cc: New file. * gdb.cp/rvalue-ref-types.exp: New file. * gdb.python/py-rvalue-ref-value-cc.cc: New file. * gdb.python/py-rvalue-ref-value-cc.exp: New file. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21159-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 20 20:51:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20677 invoked by alias); 20 Mar 2017 20:51:00 -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 20635 invoked by uid 55); 20 Mar 2017 20:50:59 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Mon, 20 Mar 2017 20:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q1/txt/msg00311.txt.bz2 Content-length: 1724 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 --- Comment #22 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Keith Seitz : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D15c0a2a93056= 48095f5586a02b5a5017e1643e99 commit 15c0a2a9305648095f5586a02b5a5017e1643e99 Author: Artemiy Volkov Date: Mon Mar 20 13:47:57 2017 -0700 Add rvalue references to overloading resolution This patch introduces changes to rank_one_type() dealing with ranking an rvalue reference type when selecting a best viable function from a set of candidate functions. The 4 new added rules for rvalue references are: 1) An rvalue argument cannot be bound to a non-const lvalue reference parameter and an lvalue argument cannot be bound to an rvalue reference parameter. [C++11 13.3.3.1.4p3] 2) If a conversion to one type of reference is an identity conversion, = and a conversion to the second type of reference is a non-identity conversion, choose the first type. [C++11 13.3.3.2p3] 3) An rvalue should be first tried to bind to an rvalue reference, and = then to an lvalue reference. [C++11 13.3.3.2p3] 4) An lvalue reference to a function gets higher priority than an rvalue reference to a function. [C++11 13.3.3.2p3] This patch is not exactly correct. See c++/15372 for tracking overload resolution bugs. gdb/ChangeLog PR gdb/14441 * gdbtypes.c (rank_one_type): Implement overloading resolution rules regarding rvalue references. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21161-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 20 21:52:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 96208 invoked by alias); 20 Mar 2017 21:52:03 -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 96180 invoked by uid 48); 20 Mar 2017 21:52:02 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/14441] Need to support DW_TAG_rvalue_reference_type Date: Mon, 20 Mar 2017 21:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: 8.0 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00313.txt.bz2 Content-length: 528 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14441 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #24 from Keith Seitz --- Pushed in time for 8.0 release. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21162-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 21 11:47:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 21693 invoked by alias); 21 Mar 2017 11:47:19 -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 21662 invoked by uid 55); 21 Mar 2017 11:47:18 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tdep/20928] Decode %ccr into individual flags in sparcv9 register output Date: Tue, 21 Mar 2017 11:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: 7.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00314.txt.bz2 Content-length: 1252 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20928 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Jose E. Marchesi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D5badf10a18af= 78c57dd4ce8e6a6ead7f46e1a878 commit 5badf10a18af78c57dd4ce8e6a6ead7f46e1a878 Author: Ivo Raisr Date: Tue Mar 21 04:39:33 2017 -0700 Decode properly flags of %ccr register on sparc64. While at it, decode also properly one-bit flags for %fsr (accrued and current exception flags were mixed up). ChangeLog entry: 2017-03-21 Ivo Raisr PR tdep/20928 * gdb/sparc-tdep.h (gdbarch_tdep) : New field. * gdb/sparc64-tdep.c (sparc64_ccr_type): New function. (sparc64_fsr_type): Fix %fsr decoding. ChangeLog entry for testsuite: 2017-03-21 Ivo Raisr PR tdep/20928 * gdb.arch/sparc64-regs.exp: New file. * gdb.arch/sparc64-regs.S: Likewise. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21163-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 21 15:37:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66061 invoked by alias); 21 Mar 2017 15:37:41 -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 66031 invoked by uid 55); 21 Mar 2017 15:37:40 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug remote/21188] Remote timeouts don't work correctly Date: Tue, 21 Mar 2017 15:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 8.0 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: 2017-q1/txt/msg00315.txt.bz2 Content-length: 1212 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21188 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Simon Marchi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D0e7b8f61069f= 1219ca53a9dd927ba55c9a7eefd4 commit 0e7b8f61069f1219ca53a9dd927ba55c9a7eefd4 Author: Simon Marchi Date: Tue Mar 21 11:35:42 2017 -0400 Remove remaining reference to struct serial::current_timeout I get this when trying to build for --host=3Dx68_64-w64-mingw32: /home/emaisin/src/binutils-gdb/gdb/ser-mingw.c: In function 'void ser_windows_raw(serial*)': /home/emaisin/src/binutils-gdb/gdb/ser-mingw.c:166:8: error: 'struct serial' has no member named 'current_timeout' scb->current_timeout =3D 0; ^~~~~~~~~~~~~~~ It is just a leftover from 9bcbdca808b5f9fec6217d20bd4b48a56008c460 PR remote/21188: Fix remote serial timeout gdb/ChangeLog: * ser-mingw.c (ser_windows_raw): Remove reference to struct serial::current_timeout. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21164-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 22 02:21:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 67660 invoked by alias); 22 Mar 2017 02:21: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 67636 invoked by uid 48); 22 Mar 2017 02:21:22 -0000 From: "349988077 at qq dot com" To: gdb-prs@sourceware.org Subject: [Bug compile/21284] New: all FLAGS should be add "-static" when using mingw_gcc_5.3.0 Date: Wed, 22 Mar 2017 02:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: compile X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: 349988077 at qq dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00316.txt.bz2 Content-length: 1650 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21284 Bug ID: 21284 Summary: all FLAGS should be add "-static" when using mingw_gcc_5.3.0 Product: gdb Version: 7.12 Status: UNCONFIRMED Severity: normal Priority: P2 Component: compile Assignee: unassigned at sourceware dot org Reporter: 349988077 at qq dot com Target Milestone: --- I have downloaded gdb7.12.tar.gz and mingw-get-setup.exe. Running mingw-get-setup.exe, i got a development environment of mingw. The gcc version is 5.3.0. When i configured gdb as "../gdb-7.12/configure --disable-werror" in the mingw, it succeed, then "make" is succeed too. Result : I tried to running gdb as ./gdb/gdb in my build dir, and typed "s" as a command in the command line, when i enterd "Enter", command "s" was trying = to=20 executed, but i got messgae below: "This application has requested the Runtime to terminate it in an unusual way. please contact the application's support team for more information" Then , gdb crashed. The gdb failed in the function of "thow_error()", it may need some "*.dll"= =E3=80=82 Later=EF=BC=9A I configured gdb as "../gdb-7.12/configure --disable-werror" in the mingw, it succeed=EF=BC=9BOpened Makefile and added "-static" to all the FL= AGS; Then "make" is succeed too. This time=EF=BC=8C gdb was running normally=EF=BC=81 =EF=BC=88By the way=EF=BC=8Ci can not compiled gdb7.12 success when using m= ingw gcc 4.6.1 and mingw gcc 4.8.1=EF=BC=89 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21165-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 22 11:23:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 19949 invoked by alias); 22 Mar 2017 11:23:44 -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 19903 invoked by uid 55); 22 Mar 2017 11:23:43 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/19637] bound_registers.py uses type "long", but long merged with "int" in python3 Date: Wed, 22 Mar 2017 11:23: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 8.0 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: 2017-q1/txt/msg00317.txt.bz2 Content-length: 795 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19637 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Yao Qi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D9d736fbf01d2= 0bc03804fa0cb49d99fdf6628fab commit 9d736fbf01d20bc03804fa0cb49d99fdf6628fab Author: Jonah Graham Date: Wed Mar 22 11:19:44 2017 +0000 Import sys in gdb/python/lib/gdb/printer/bound_registers.py Pick up missing bits from the patch merged in. 2017-03-22 Jonah Graham PR gdb/19637 * python/lib/gdb/printer/bound_registers.py: Import sys. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21166-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 23 05:45:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 2539 invoked by alias); 23 Mar 2017 05:45:04 -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 2481 invoked by uid 48); 23 Mar 2017 05:45:02 -0000 From: "al.drozdov at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/21293] New: step into function doesn't work for shared libraries built with -Wl,-znow Date: Thu, 23 Mar 2017 05:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: al.drozdov at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q1/txt/msg00318.txt.bz2 Content-length: 1144 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21293 Bug ID: 21293 Summary: step into function doesn't work for shared libraries built with -Wl,-znow Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: al.drozdov at gmail dot com Target Milestone: --- Created attachment 9932 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9932&action=3Dedit Minimal project to reproduce the bug If a shared library is created with -Wl,-znow option then gdb cannot step i= nto its internal functions. Instead, it behaves as if 'next' command was just typed. But it is still possible to make breakpoints on the library functions gdb cannot step into, and then gdb successfully stops on them. It seems that this because ".rela.plt" section is absent on the libraries b= uilt with -Wl,-znow. gdb 7.12.1 on Ubuntu 6.04.2 x86_64, ld 2.26.1. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21167-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 23 05:50:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 8446 invoked by alias); 23 Mar 2017 05:50:37 -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 8423 invoked by uid 48); 23 Mar 2017 05:50:36 -0000 From: "al.drozdov at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/21293] step into function doesn't work for shared libraries built with -Wl,-znow Date: Thu, 23 Mar 2017 05:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: al.drozdov at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00319.txt.bz2 Content-length: 404 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21293 Alexander Drozdov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |al.drozdov at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21169-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 23 05:57:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49203 invoked by alias); 23 Mar 2017 05:57:37 -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 35654 invoked by uid 48); 23 Mar 2017 05:57:06 -0000 From: "al.drozdov at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/21293] step into function doesn't work for shared libraries built with -Wl,-znow Date: Thu, 23 Mar 2017 05:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: al.drozdov at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00321.txt.bz2 Content-length: 271 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21293 --- Comment #1 from Alexander Drozdov --- *** Bug 21292 has been marked as a duplicate of this bug. *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21168-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 23 05:57:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 38037 invoked by alias); 23 Mar 2017 05:57:09 -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 11509 invoked by uid 48); 23 Mar 2017 05:55:17 -0000 From: "al.drozdov at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/21292] New: step into function doesn't work for shared libraries built with -Wl,-znow Date: Thu, 23 Mar 2017 05:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: al.drozdov at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone resolution Message-ID: 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: 2017-q1/txt/msg00320.txt.bz2 Content-length: 1215 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21292 Bug ID: 21292 Summary: step into function doesn't work for shared libraries built with -Wl,-znow Product: gdb Version: 7.12.1 Status: RESOLVED Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: al.drozdov at gmail dot com Target Milestone: --- Status: RESOLVED Resolution: DUPLICATE If a shared library is created with -Wl,-znow option then gdb cannot step i= nto its internal functions. Instead, it behaves as if 'next' command was just typed. But it is still possible to make breakpoints on the library functions gdb cannot step into, and then gdb successfully stops on them. It seems that this because ".rela.plt" section is absent on the libraries b= uilt with -Wl,-znow. gdb 7.12.1 on Ubuntu 6.04.2 x86_64, ld 2.26.1. --- Comment #1 from Alexander Drozdov --- Duplicate of 21293 *** This bug has been marked as a duplicate of bug 21293 *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21170-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Mar 25 23:12:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 17549 invoked by alias); 25 Mar 2017 23:12:50 -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 17524 invoked by uid 48); 25 Mar 2017 23:12:50 -0000 From: "freddie_chopin at op dot pl" To: gdb-prs@sourceware.org Subject: [Bug python/21308] New: Cannot get non-type template argument if it is a const-qualified member pointer Date: Sat, 25 Mar 2017 23:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: freddie_chopin at op dot pl X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00322.txt.bz2 Content-length: 2725 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21308 Bug ID: 21308 Summary: Cannot get non-type template argument if it is a const-qualified member pointer Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: freddie_chopin at op dot pl Target Milestone: --- Source code: -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- struct C { int a; }; template struct D {}; int main() { D<&C::a> d; return 0; } -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- It's not possible to get non-type template argument with Python API if it i= s a const-qualified member pointer. Any attempt results in "RuntimeError: Templ= ate argument is optimized out". See log for details: -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- $ g++ -g -ggdb3 gdb.cpp=20 $ gdb ./a.out=20 GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./a.out...done. (gdb) b main Breakpoint 1 at 0x4004ca: file gdb.cpp, line 9. (gdb) run Starting program: /home/freddie/test/a.out=20 Breakpoint 1, main () at gdb.cpp:9 9 return 0; (gdb) python print(gdb.selected_frame().read_var('d').type.template_argument(0)) Traceback (most recent call last): File "", line 1, in RuntimeError: Template argument is optimized out Error while executing Python code. (gdb)=20 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- If I remove "const" from the template (so "template", not= hing more changed), it works fine: -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- ... (gdb) python print(gdb.selected_frame().read_var('d').type.template_argument(0)) &C::a -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- Any ideas whether it's a bug or maybe I'm doing something wrong? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21171-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Mar 26 21:43:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63282 invoked by alias); 26 Mar 2017 21:43:05 -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 63251 invoked by uid 48); 26 Mar 2017 21:43:04 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug external/20207] kernel RFE: aarch64: ptrace: BAS: Support any contiguous range Date: Sun, 26 Mar 2017 21:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: external X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q1/txt/msg00323.txt.bz2 Content-length: 874 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20207 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Jan Kratochvil --- f43365ee17f8 selftests: arm64: add test for unaligned/inexact watchpoint handling 0ddb8e0b784b arm64: Allow hw watchpoint of length 3,5,6 and 7 fdfeff0f9e3d arm64: hw_breakpoint: Handle inexact watchpoint addresses b08fb180bb88 arm64: Allow hw watchpoint at varied offset from base address 651be3cb0853 hw_breakpoint: Allow watchpoint of length 3,5,6 and 7 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21172-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 27 21:12:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20129 invoked by alias); 27 Mar 2017 21:12:29 -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 20082 invoked by uid 48); 27 Mar 2017 21:12:28 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/19806] Aarch64: watchpoints set on non-8-byte-aligned addresses are always missed Date: Mon, 27 Mar 2017 21:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan.kratochvil at redhat dot com 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: 2017-q1/txt/msg00324.txt.bz2 Content-length: 417 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19806 --- Comment #4 from Jan Kratochvil --- [patch] aarch64: PR 19806: watchpoints: false negatives + PR 20207 contiguo= us ones https://sourceware.org/ml/gdb-patches/2017-03/msg00470.html Message-ID: <20170327210753.GA29656@host1.jankratochvil.net> --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21173-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 28 11:46:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 61576 invoked by alias); 28 Mar 2017 11:46:25 -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 61533 invoked by uid 48); 28 Mar 2017 11:46:24 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug server/21321] New: AddressSanitizer: heap-use-after-free in gdbserver/linux-low.c Date: Tue, 28 Mar 2017 11:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00325.txt.bz2 Content-length: 3560 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21321 Bug ID: 21321 Summary: AddressSanitizer: heap-use-after-free in gdbserver/linux-low.c Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: server Assignee: unassigned at sourceware dot org Reporter: qiyao at gcc dot gnu.org Target Milestone: --- I build GDBserver with CXXFLAGS=3D'-O0 -g3 -fsanitize=3Daddress', and run G= DB tests with GDBserver like this, $ make check RUNTESTFLAGS=3D"--target_board=3D'native-gdbserver' process-dies-while-detaching.exp" I get the asan error, (gdb) FAIL: gdb.threads/process-dies-while-detaching.exp: single-process: continue: killed outside: continue Remote debugging from host 127.0.0.1^M =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D^M ^[[1m^[[31m=3D=3D26184=3D=3DERROR: AddressSanitizer: heap-use-after-free on= address 0x611000020b10 at pc 0x48026c bp 0x7fff34b15a20 sp 0x7fff34b15a18^M ^[[1m^[[0m^[[1m^[[34mWRITE of size 4 at 0x611000020b10 thread T0^[[1m^[[0m^M #0 0x48026b in linux_wait_1 /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:3845^M #1 0x4811ea in linux_wait /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:3990^M #2 0x453fea in target_wait(ptid, target_waitstatus*, int) /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/target.c:268^M #3 0x453a8a in mywait(ptid, target_waitstatus*, int, int) /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/target.c:214^M #4 0x44b53b in resume /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/server.c:2786^M ....... ^M ^[[1m^[[32m0x611000020b10 is located 80 bytes inside of 216-byte region [0x611000020ac0,0x611000020b98)^M ^[[1m^[[0m^[[1m^[[35mfreed by thread T0 here:^[[1m^[[0m^M #0 0x2b1500432631 in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.1+0x54631)^M #1 0x4722e8 in delete_lwp /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:415^M #2 0x47a7ed in linux_low_filter_event /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:2504^M #3 0x47bdc0 in linux_wait_for_event_filtered /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:2800^M #4 0x481c1f in wait_for_sigstop /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:4150^M #5 0x482660 in stop_all_lwps /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:4287^M #6 0x48018b in linux_wait_1 /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:3813^M #7 0x4811ea in linux_wait /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:3990^M ...^M ^[[1m^[[35mpreviously allocated by thread T0 here:^[[1m^[[0m^M #0 0x2b15004329a1 in __interceptor_calloc (/usr/lib/x86_64-linux-gnu/libasan.so.1+0x549a1)^M #1 0x4147b6 in xcalloc /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/../common/common-utils.c:83^M #2 0x4748c0 in add_lwp /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:937^M #3 0x4731a3 in handle_extended_wait /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:624^M #4 0x47ac69 in linux_low_filter_event /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:2568^M #5 0x47bdc0 in linux_wait_for_event_filtered /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:2800^. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21174-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 28 17:29:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 61256 invoked by alias); 28 Mar 2017 17:29:12 -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 61220 invoked by uid 48); 28 Mar 2017 17:29:10 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Tue, 28 Mar 2017 17:29: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: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00326.txt.bz2 Content-length: 3703 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #9 from Adam Stylinski --- Any luck reproducing this? I was able to do it on another distro with GDB 7.12, though the stack corruption wasn't nearly as noticeable (increasing t= he number of arguments can affect this, though).=20 GNU gdb (Gentoo 7.12 vanilla) 7.12 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./test.out...done. (gdb) break testFunc Breakpoint 1 at 0x400550: file test.cpp, line 12. (gdb) r Starting program: /home/adam/test.out=20 Breakpoint 1, testFunc (a=3D0x0, n=3D0, sx=3D0x0, sy=3D0x0, rc=3D0x0, nr=3D= 0, b=3D4, f=3D9.50000026e+09, c=3D0x0, d=3D0x0, e=3D0x0, gx=3D0x0, gy=3D0x0) at test.= cpp:12 12 float lambda =3D C_LIGHT / f; (gdb) n 13 printf("lambda =3D %f\n", lambda); (gdb) p lambda $1 =3D 0.030302437 (gdb) disas Dump of assembler code for function testFunc(float*, unsigned long, float*, float*, float*, float, int, float, float**, float**, float**, float*, float= *): 0x0000000000400526 <+0>: push %rbp 0x0000000000400527 <+1>: mov %rsp,%rbp 0x000000000040052a <+4>: sub $0x50,%rsp 0x000000000040052e <+8>: mov %rdi,-0x18(%rbp) 0x0000000000400532 <+12>: mov %rsi,-0x20(%rbp) 0x0000000000400536 <+16>: mov %rdx,-0x28(%rbp) 0x000000000040053a <+20>: mov %rcx,-0x30(%rbp) 0x000000000040053e <+24>: mov %r8,-0x38(%rbp) 0x0000000000400542 <+28>: vmovss %xmm0,-0x3c(%rbp) 0x0000000000400547 <+33>: mov %r9d,-0x40(%rbp) 0x000000000040054b <+37>: vmovss %xmm1,-0x44(%rbp) 0x0000000000400550 <+42>: vmovss 0x10c(%rip),%xmm0 # 0x400664 0x0000000000400558 <+50>: vdivss -0x44(%rbp),%xmm0,%xmm0 0x000000000040055d <+55>: vmovss %xmm0,-0x4(%rbp) =3D> 0x0000000000400562 <+60>: vcvtss2sd -0x4(%rbp),%xmm2,%xmm2 0x0000000000400567 <+65>: vmovq %xmm2,%rax 0x000000000040056c <+70>: vmovq %rax,%xmm0 0x0000000000400571 <+75>: mov $0x400654,%edi 0x0000000000400576 <+80>: mov $0x1,%eax 0x000000000040057b <+85>: callq 0x400400 0x0000000000400580 <+90>: nop 0x0000000000400581 <+91>: leaveq=20 0x0000000000400582 <+92>: retq=20=20=20 End of assembler dump. (gdb) n lambda =3D 0.030302 14 } (gdb)=20 main () at test.cpp:21 21 return 0; (gdb)=20 22 } adam@eggsbenedict ~ $ ./test.out=20 lambda =3D 0.031557 Here's after adding one more argument to the function signature and stepping through the function call in the debugger: Breakpoint 1, testFunc (a=3D0x0, n=3D0, sx=3D0x0, sy=3D0x0, rc=3D0x0, nr=3D= 0, b=3D4, f=3D9.50000026e+09, c=3D0x0, d=3D0x0, e=3D0x0, gx=3D0x0, gy=3D0x0, gz=3D0x0= ) at test.cpp:12 12 float lambda =3D C_LIGHT / f; (gdb) n 13 printf("lambda =3D %f\n", lambda); (gdb) n lambda =3D -98857.093750 14 } So some static allocation somewhere is probably being overrun. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21175-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 28 18:16:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 19169 invoked by alias); 28 Mar 2017 18:16:24 -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 18772 invoked by uid 48); 28 Mar 2017 18:16:24 -0000 From: "dje at google dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21322] New: Reset pspace->executing_startup on connection close? Date: Tue, 28 Mar 2017 18:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dje at google dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00327.txt.bz2 Content-length: 1514 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21322 Bug ID: 21322 Summary: Reset pspace->executing_startup on connection close? Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: remote Assignee: unassigned at sourceware dot org Reporter: dje at google dot com Target Milestone: --- On Fuchsia the dynamic linker loads the main executable, so during startup = the executable doesn't actually exist in memory for awhile. I've been using the "executing_startup" flag to track this. If I have the remote server exit this flag is left set which leads to things like "b main" not being able to find main. Perhaps that's a bug in itself, though it's not unreasonable either (in the window during startup main hasn= 't been loaded, and for PIE still needs to be relocated as well). Anyways, if remote_unpush_target resets current_program_space->executing_startup the problem goes away. As for where the right place to reset this flag is, not sure yet. (gdb) mon quit Sending packet: $qRcmd,71756974#d1...Ack Packet received: OK (gdb) Remote connection closed # reset remote server (gdb) target ext ... # reconnect with new server (gdb) b main Function "main" not defined. Make breakpoint pending on future shared library load? (y or [n]) n (gdb) p main $1 =3D {int (int, char **)} 0x1508
--=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21176-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 28 18:33:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63907 invoked by alias); 28 Mar 2017 18:33:49 -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 63882 invoked by uid 48); 28 Mar 2017 18:33:48 -0000 From: "jwakely.gcc at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21323] New: GDB thinks char16_t and char32_t are signed in C++ Date: Tue, 28 Mar 2017 18:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jwakely.gcc at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00328.txt.bz2 Content-length: 2404 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21323 Bug ID: 21323 Summary: GDB thinks char16_t and char32_t are signed in C++ Product: gdb Version: 7.11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: jwakely.gcc at gmail dot com Target Milestone: --- tmp$ cat c.c #include int main() { char16_t u16 =3D 0xf000; char32_t u32 =3D 0xf0000000; return 0; } tmp$ gcc c.c -g tmp$ gdb -q -ex "br 6" -ex run -ex "p u16" -ex "p u32" -ex cont -ex quit a.= out=20 Reading symbols from a.out...done. Breakpoint 1 at 0x4004e7: file c.c, line 6. Starting program: /tmp/a.out=20 Breakpoint 1, main () at c.c:6 6 return 0; $1 =3D 61440 u'=EF=80=80' $2 =3D 4026531840 U'\xf0000000' Continuing. [Inferior 1 (process 1258) exited normally] tmp$ g++ c.c -g tmp$ gdb -q -ex "br 6" -ex run -ex "p u16" -ex "p u32" -ex cont -ex quit a.= out=20 Reading symbols from a.out...done. Breakpoint 1 at 0x4005a7: file c.c, line 6. Starting program: /tmp/a.out=20 Breakpoint 1, main () at c.c:6 6 return 0; $1 =3D -4096 u'=EF=80=80' $2 =3D -268435456 U'\xf0000000' Continuing. [Inferior 1 (process 1276) exited normally] tmp$ gdb --version GNU gdb (GDB) Fedora 7.11.1-86.fc24 ... The C++ standard is clear that they're unsigned types: Types char16_t and char32_t denote distinct types with the same size, signedness, and alignment as uint_least16_t and uint_least32_t, respectivel= y, in , called the underlying types. Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21177-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 28 20:35:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 123041 invoked by alias); 28 Mar 2017 20:35:21 -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 123019 invoked by uid 48); 28 Mar 2017 20:35:20 -0000 From: "brian at ubuntu dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21324] New: gdb hangs when 'thread apply all bt full' is used Date: Tue, 28 Mar 2017 20:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: brian at ubuntu dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00329.txt.bz2 Content-length: 6135 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21324 Bug ID: 21324 Summary: gdb hangs when 'thread apply all bt full' is used Product: gdb Version: unknown Status: NEW Severity: critical Priority: P2 Component: threads Assignee: unassigned at sourceware dot org Reporter: brian at ubuntu dot com Target Milestone: --- I run a service which does automated retracing of crashes from Ubuntu syste= ms and discovered that gdb was hanging (using 100% CPU and not returning anyth= ing) when retracing crashes from vim on Ubuntu 16.10. I can recreate this by running 'thread apply all bt full' (or 'thread apply= 3 bt full' in this case) which then prints only the following: Thread 3 (Thread 0x7ff4636a8700 (LWP 7203)): I tried using strace on the gdb process but only received: $ sudo strace -p 16418=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 strace: Process 16418 attached strace: [ Process PID=3D16418 runs in x32 mode. ] I've seen this behavior with these versions of gdb: GNU gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git GNU gdb (Ubuntu 7.11.90.20161005-0ubuntu1) 7.11.90.20161005-git GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1 I also tried a 7.9 version of gdb and that produced a backtrace. GNU gdb (Ubuntu 7.9-1ubuntu1) 7.9 The backtrace: Thread 2 (LWP 3015): #0 0x00007fe23ecc9ea3 in select () at ../sysdeps/unix/syscall-template.S:84 No locals. #1 0x00007fe23f27ae48 in time_sleep () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #2 0x00007fe23f353427 in PyEval_EvalFrameEx () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #3 0x00007fe23f413a74 in _PyEval_EvalCodeWithName.lto_priv.1712 () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #4 0x00007fe23f413b53 in PyEval_EvalCodeEx () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #5 0x00007fe23f295e25 in function_call.lto_priv () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #6 0x00007fe23f383457 in PyObject_Call () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #7 0x00007fe23f34c3c7 in PyEval_EvalFrameEx () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #8 0x00007fe23f35364b in PyEval_EvalFrameEx () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #9 0x00007fe23f35364b in PyEval_EvalFrameEx () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #10 0x00007fe23f413a74 in _PyEval_EvalCodeWithName.lto_priv.1712 () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #11 0x00007fe23f413b53 in PyEval_EvalCodeEx () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #12 0x00007fe23f295d28 in function_call.lto_priv () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #13 0x00007fe23f383457 in PyObject_Call () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #14 0x00007fe23f3cfb0c in method_call.lto_priv () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #15 0x00007fe23f383457 in PyObject_Call () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #16 0x00007fe23f412577 in PyEval_CallObjectWithKeywords () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #17 0x00007fe23f32c0e2 in t_bootstrap () from /tmp/apport_sandbox_kH9R1m/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 No symbol table info available. #18 0x00007fe23ef9a6ca in start_thread (arg=3D0x7fe23a74f700) at pthread_create.c:333 __res =3D pd =3D 0x7fe23a74f700 now =3D unwind_buf =3D {cancel_jmp_buf =3D {{jmp_buf =3D {140609620080384, -1451514129212077889, 0, 140725579832159, 140609620081088, 140609620080384, 1449978205402990783, 1449968195707373759}, mask_was_saved =3D 0}}, priv =3D= {pad =3D {0x0, 0x0, 0x0, 0x0}, data =3D {prev =3D 0x0, cleanup =3D 0x0, canceltyp= e =3D 0}}} not_first_call =3D pagesize_m1 =3D sp =3D freesize =3D __PRETTY_FUNCTION__ =3D "start_thread" #19 0x00007fe23ecd40af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 No locals. While I have many different core files that produce this behavior, I don't = want to make them publicly available since it isn't my data. I am happy to any required debugging. For completeness here is the full gdb command: /usr/bin/gdb --ex 'set debug-file-directory /mnt/sec-machines/apport-sandbox-dir/Ubuntu 16.10/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-prefix /mnt/sec-machines/apport-sandbox-dir/Ubuntu 16.10/amd64/report-sandbox' --ex 'add-auto-load-safe-path /mnt/sec-machines/apport-sandbox-dir/Ubuntu 16.10/amd64/report-sandbox' --ex 'set solib-search-path /mnt/sec-machines/apport-sandbox-dir/Ubuntu 16.10/amd64/report-sandbox/lib/x86_64-linux-gnu' --ex 'file "/mnt/sec-machines/apport-sandbox-dir/Ubuntu 16.10/amd64/report-sandbox//usr/bin/vim.gtk"' --ex 'core-file /tmp/apport_core_vx39d9bm' I used "Critical" for the severity since "Serious" wasn't available. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21178-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 29 02:07:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 124458 invoked by alias); 29 Mar 2017 02:07:03 -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 124429 invoked by uid 48); 29 Mar 2017 02:07:02 -0000 From: "brian at ubuntu dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21324] gdb hangs when 'thread apply all bt full' is used Date: Wed, 29 Mar 2017 02:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: brian at ubuntu dot com 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: 2017-q1/txt/msg00330.txt.bz2 Content-length: 352 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21324 --- Comment #1 from brian at ubuntu dot com --- I forgot to mention that the first version of gdb with which I received this hang was GNU gdb (Ubuntu 7.10-1ubuntu2) 7.10 from Ubuntu 15.10. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21179-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 29 02:09:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 11164 invoked by alias); 29 Mar 2017 02:09:05 -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 11082 invoked by uid 48); 29 Mar 2017 02:09:05 -0000 From: "brian at ubuntu dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21324] gdb hangs when 'thread apply all bt full' is used Date: Wed, 29 Mar 2017 02:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: brian at ubuntu dot com 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: cc 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: 2017-q1/txt/msg00331.txt.bz2 Content-length: 402 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21324 brian at ubuntu dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brian at ubuntu dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21180-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 29 13:13:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89453 invoked by alias); 29 Mar 2017 13:13:02 -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 86889 invoked by uid 48); 29 Mar 2017 13:13:00 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21323] GDB thinks char16_t and char32_t are signed in C++ Date: Wed, 29 Mar 2017 13:13: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00332.txt.bz2 Content-length: 1097 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21323 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- Hmm, thanks. Should be easy to fix. I see: /* Allocate a TYPE_CODE_INT type structure associated with GDBARCH. BIT is the type size in bits. If UNSIGNED_P is non-zero, set the type's TYPE_UNSIGNED flag. NAME is the type name. */ struct type * arch_integer_type (struct gdbarch *gdbarch, int bit, int unsigned_p, const char *name) { ... } static void * gdbtypes_post_init (struct gdbarch *gdbarch) { ... /* Wide character types. */ builtin_type->builtin_char16 =3D arch_integer_type (gdbarch, 16, 0, "char16_t"); builtin_type->builtin_char32 =3D arch_integer_type (gdbarch, 32, 0, "char32_t"); --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21181-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 29 13:53:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31014 invoked by alias); 29 Mar 2017 13:53:01 -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 30978 invoked by uid 48); 29 Mar 2017 13:53:00 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21323] GDB thinks char16_t and char32_t are signed in C++ Date: Wed, 29 Mar 2017 13:53: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00333.txt.bz2 Content-length: 810 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21323 --- Comment #2 from Pedro Alves --- Funny thing is that I can't reproduce here, even with 7.11.1 (FSF). I suspect that gdb is picking char16_t/char32_t definitions from the debug info. What was the compiler versions you used? I tried F23's gcc 5.3.1 and gcc7/trunk. Seems like I can only make gdb use those built in types with the "x /s" com= mand (from looking at commit 9a22f0d0). Related, I noticed that GDB is not aware that char16_t and char32_t are built-in types in C++: $ gdb [...] (gdb) set language c++ (gdb) ptype char32_t No symbol table is loaded. Use the "file" command. Looks like fixing that requires tweaking c-exp.y. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21184-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 29 14:10:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 90081 invoked by alias); 29 Mar 2017 14:10:44 -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 89951 invoked by uid 48); 29 Mar 2017 14:10:36 -0000 From: "anatol.pomozov at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Wed, 29 Mar 2017 14:10: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: anatol.pomozov at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00336.txt.bz2 Content-length: 411 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 Anatol Pomozov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anatol.pomozov at gmail do= t com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21183-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 29 14:10:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89970 invoked by alias); 29 Mar 2017 14:10:38 -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 89890 invoked by uid 48); 29 Mar 2017 14:10:32 -0000 From: "anatol.pomozov at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Wed, 29 Mar 2017 14:10: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: anatol.pomozov at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00335.txt.bz2 Content-length: 411 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 Anatol Pomozov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anatol.pomozov at gmail do= t com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21182-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 29 14:10:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89405 invoked by alias); 29 Mar 2017 14:10:14 -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 89370 invoked by uid 48); 29 Mar 2017 14:10:13 -0000 From: "anatol.pomozov at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug guile/21104] 7.12.1 does not compile with latest guile (2.1.6) Date: Wed, 29 Mar 2017 14:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: guile X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: anatol.pomozov at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q1/txt/msg00334.txt.bz2 Content-length: 1643 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21104 Anatol Pomozov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anatol.pomozov at gmail do= t com --- Comment #1 from Anatol Pomozov --- I confirm that the issue exists at Arch Linux if I try to compile gdb with guile 2.2 ./guile/scm-ports.c:1097:41: error: invalid use of incomplete type =E2=80= =98scm_t_port {aka struct scm_t_port}=E2=80=99 pt->write_end =3D pt->write_buf + pt->write_buf_size; ^~ In file included from /usr/include/guile/2.2/libguile/fports.h:28:0, from /usr/include/guile/2.2/libguile.h:57, from ./guile/guile-internal.h:29, from ./guile/scm-ports.c:28: /usr/include/guile/2.2/libguile/ports.h:82:16: note: forward declaration of =E2=80=98scm_t_port {aka struct scm_t_port}=E2=80=99 typedef struct scm_t_port scm_t_port; ^~~~~~~~~~ make[2]: *** [Makefile:2537: scm-ports.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory '/build/avr-gdb/src/gdb-7.12.1/gdb' make[1]: *** [Makefile:9161: all-gdb] Error 2 make[1]: Leaving directory '/build/avr-gdb/src/gdb-7.12.1' make: *** [Makefile:850: all] Error 2 Do you plan to port gdb to the new guile API? Is there a workaround that ca= n we use to prevent this compilation issue? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21185-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 29 17:41:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68824 invoked by alias); 29 Mar 2017 17:41:33 -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 68464 invoked by uid 48); 29 Mar 2017 17:41:33 -0000 From: "jlquinn at us dot ibm.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21328] New: checkpoint deadlock Date: Wed, 29 Mar 2017 17:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jlquinn at us dot ibm.com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00337.txt.bz2 Content-length: 4076 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21328 Bug ID: 21328 Summary: checkpoint deadlock Product: gdb Version: 7.12 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jlquinn at us dot ibm.com Target Milestone: --- I've been having this problem often. I set a breakpoint. I then create a checkpoint when I hit the breakpoint. I execute some, then restart. I try= to create a new checkpoint and gdb spins. If I C-c and backtrace, I see: (gdb) checkp ^C Program received signal SIGINT, Interrupt. 0x00002aaab2210aa1 in sys_futex (v3=3D0, a2=3D0x0, t=3D0x7fffffffc960, v=3D= , o=3D128, a=3D0x2aaab2421740 ) at /scratch/usr/jlquinn/itold/mnlp/libcommon/3rd_party/gperftools-src/src/base= /linux_syscall_support.h:2363 2363 int, v3) The program being debugged was signaled while in a function called from GDB. GDB remains in the frame where the signal was received. To change this behavior use "set unwindonsignal on". Evaluation of the expression containing the function (fork) will be abandoned. When the function is done executing, GDB will silently stop. (gdb) bt #0 0x00002aaab2210aa1 in sys_futex (v3=3D0, a2=3D0x0, t=3D0x7fffffffc960, v=3D, o=3D128, a=3D0x2aaab2421740 ) at /scratch/usr/jlquinn/itold/mnlp/libcommon/3rd_party/gperftools-src/src/base= /linux_syscall_support.h:2363 #1 base::internal::SpinLockDelay (w=3D0x2aaab2421740 , value=3D2, loop=3D) at /scratch/usr/jlquinn/itold/mnlp/libcommon/3rd_party/gperftools-src/src/base= /spinlock_linux-inl.h:84 #2 0x00002aaab2210864 in SpinLock::SlowLock (this=3D0x2aaab2421740 ) at /scratch/usr/jlquinn/itold/mnlp/libcommon/3rd_party/gperftools-src/src/base= /spinlock.cc:119 #3 0x00002aaab220bcd5 in SpinLock::Lock (this=3D0x2aaab2421740 ) at /scratch/usr/jlquinn/itold/mnlp/libcommon/3rd_party/gperftools-src/src/base= /spinlock.h:71 #4 tcmalloc::CentralCacheLockAll () at /scratch/usr/jlquinn/itold/mnlp/libcommon/3rd_party/gperftools-src/src/stat= ic_vars.cc:57 #5 0x0000003a1a4acc65 in fork () from /lib64/libc.so.6 #6 #7 NMTDecoder::init_profile (this=3D0x2b93230, name=3D"test", path=3D"/scratch/usr/jlquinn/profiles/test", filename=3D"profile.param") at /scratch/usr/jlquinn/itold/mnlp/libmt/src/nmt/NMTDecoder.C:142 #8 0x00002aaaab0ac93d in actII_nmt::init_profile (this=3D0x2b93180, name= =3D"test", path=3D"/scratch/usr/jlquinn/profiles/test", filename=3D"profile.param", lo= ad=3Dtrue) at /scratch/usr/jlquinn/itold/mnlp/libmt/src/trlblues/actII_nmt.C:80 #9 0x00002aaaab0e691e in (anonymous namespace)::Trlblues_modular::init_pro= file (this=3D0xf1bba0, name=3D"test") at /scratch/usr/jlquinn/itold/mnlp/libmt/src/trlblues/trlblues_modular.C:207 #10 0x00002aaaab0e5f00 in (anonymous namespace)::Trlblues_modular::init (this=3D0xf1bba0, begin_module=3D"", end_module=3D"") at /scratch/usr/jlquinn/itold/mnlp/libmt/src/trlblues/trlblues_modular.C:166 #11 0x0000000000436e35 in main (argc=3D4, argv=3D0x7fffffffde48) at /scratch/usr/jlquinn/itold/mnlp/libmt/src/trlblues/trl.C:632 (gdb) c Continuing. ^C Program received signal SIGINT, Interrupt. 0x00002aaab2210aa1 in sys_futex (v3=3D0, a2=3D0x0, t=3D0x7fffffffc960, v=3D= , o=3D128, a=3D0x2aaab2421740 ) at /scratch/usr/jlquinn/itold/mnlp/libcommon/3rd_party/gperftools-src/src/base= /linux_syscall_support.h:2363 2363 int, v3) I can't move beyond this point. Sometimes I have to restart gdb. This is CentOS 6.8, gcc 4.4.7. My program has OpenMP enabled but OMP_NUM_THREADS=3D1. I also have not reached any omp constructs yet. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21186-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 29 17:51:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 5305 invoked by alias); 29 Mar 2017 17:51:28 -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 5268 invoked by uid 48); 29 Mar 2017 17:51:26 -0000 From: "jwakely.gcc at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21323] GDB thinks char16_t and char32_t are signed in C++ Date: Wed, 29 Mar 2017 17:51: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jwakely.gcc at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00338.txt.bz2 Content-length: 2430 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21323 --- Comment #3 from Jonathan Wakely --- (In reply to Pedro Alves from comment #2) > Funny thing is that I can't reproduce here, even with 7.11.1 (FSF). > I suspect that gdb is picking char16_t/char32_t definitions from the debug > info. > What was the compiler versions you used? I tried F23's gcc 5.3.1 and > gcc7/trunk. Sorry for not including that info, it didn't seem relevant, beause I get it with F24's system GCC: tmp$ g++ -v Using built-in specs. COLLECT_GCC=3Dg++ COLLECT_LTO_WRAPPER=3D/usr/libexec/gcc/x86_64-redhat-linux/6.3.1/lto-wrapper Target: x86_64-redhat-linux Configured with: ../configure --enable-bootstrap --enable-languages=3Dc,c++,objc,obj-c++,fortran,ada,go,lto --prefix=3D/usr --mandir=3D/usr/share/man --infodir=3D/usr/share/info --with-bugurl=3Dhttp://bugzilla.redhat.com/bugzilla --enable-shared --enable-threads=3Dposix --enable-checking=3Drelease --enable-multilib --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=3Dgnu --enable-plugin --enable-initfini-array --disable-libgcj --with-isl --enable-libmpx --enable-gnu-indirect-function --with-tune=3Dgeneric --with-arch_32=3Di686 --build=3Dx86_64-redhat-linux Thread model: posix gcc version 6.3.1 20161221 (Red Hat 6.3.1-1) (GCC)=20 tmp$ ~/gcc/latest/bin/g++ -v Using built-in specs. COLLECT_GCC=3D/home/jwakely/gcc/latest/bin/g++ COLLECT_LTO_WRAPPER=3D/home/jwakely/gcc/7/libexec/gcc/x86_64-pc-linux-gnu/7= .0.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /home/jwakely/src/gcc/gcc/configure --prefix=3D/home/jwakely/gcc/7 --with-system-zlib --with-gnu-ld --with-gnu-= as --enable-libstdcxx-debug --disable-maintainer-mode --disable-bootstrap --disable-libitm --disable-libvtv --disable-libcilkrts --enable-languages=3Dc,c++,lto --without-isl : (reconfigured) : (reconfigu= red) /home/jwakely/src/gcc/gcc/configure --prefix=3D/home/jwakely/gcc/7 --with-system-zlib --with-gnu-ld --with-gnu-as --enable-libstdcxx-debug --disable-maintainer-mode --disable-bootstrap --disable-libitm --disable-li= bvtv --disable-libcilkrts --without-isl --enable-languages=3Dc,c++,lto --no-crea= te --no-recursion Thread model: posix gcc version 7.0.1 20170328 (experimental) (GCC) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21187-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 29 17:54:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 24912 invoked by alias); 29 Mar 2017 17:54:41 -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 24445 invoked by uid 48); 29 Mar 2017 17:54:39 -0000 From: "jwakely.gcc at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21323] GDB thinks char16_t and char32_t are signed in C++ Date: Wed, 29 Mar 2017 17:54: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jwakely.gcc at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00339.txt.bz2 Content-length: 1170 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21323 --- Comment #4 from Jonathan Wakely --- Oops, I meant to say I get it with F24's system gcc and also trunk (the two versions shown in the previous comment). Ah, but I don't see this with GCC 5.4.1 and earlier: tmp$ ~/gcc/5.4.0/bin/g++ c.c -g tmp$ gdb -q -ex "br 6" -ex run -ex "p u16" -ex "p u32" -ex cont -ex quit a.= out Reading symbols from a.out...done. Breakpoint 1 at 0x400597: file c.c, line 6. Starting program: /tmp/a.out=20 Breakpoint 1, main () at c.c:6 6 return 0; $1 =3D 61440 u'=EF=80=80' $2 =3D 4026531840 U'\xf0000000' Continuing. [Inferior 1 (process 22097) exited normally] tmp$=20 tmp$ ~/gcc/6.1.0/bin/g++ c.c -g tmp$ gdb -q -ex "br 6" -ex run -ex "p u16" -ex "p u32" -ex cont -ex quit a.= out Reading symbols from a.out...done. Breakpoint 1 at 0x400597: file c.c, line 6. Starting program: /tmp/a.out=20 Breakpoint 1, main () at c.c:6 6 return 0; $1 =3D -4096 u'=EF=80=80' $2 =3D -268435456 U'\xf0000000' Continuing. [Inferior 1 (process 22120) exited normally] --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21188-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 29 18:00:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 55539 invoked by alias); 29 Mar 2017 18:00:01 -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 55499 invoked by uid 48); 29 Mar 2017 18:00:00 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21323] GDB thinks char16_t and char32_t are signed in C++ Date: Wed, 29 Mar 2017 18:00: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00340.txt.bz2 Content-length: 467 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21323 --- Comment #5 from Pedro Alves --- Ah, I think I tested incorrectly before, because I can reproduce it with g++ trunk now too. Sorry about that. And the difference between g++ < 6 and >=3D 6 is simply the default C++ dia= lect.=20 I can reproduce it with g++ 5.3.1, as long as I pass -std=3Dgnu++11. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21190-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 30 16:10:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 60108 invoked by alias); 30 Mar 2017 16:10:58 -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 58348 invoked by uid 48); 30 Mar 2017 16:10:57 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21335] Support DW_TAG_base_type with no name Date: Thu, 30 Mar 2017 16:10: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q1/txt/msg00342.txt.bz2 Content-length: 296 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21335 --- Comment #1 from Pedro Alves --- Forgot the reference: [1] - gcc PR80263 - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D80263 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21189-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 30 16:10:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 125826 invoked by alias); 30 Mar 2017 16:10:11 -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 125797 invoked by uid 48); 30 Mar 2017 16:10:10 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21335] New: Support DW_TAG_base_type with no name Date: Thu, 30 Mar 2017 16:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00341.txt.bz2 Content-length: 1311 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21335 Bug ID: 21335 Summary: Support DW_TAG_base_type with no name Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- In order to address GCC PR80263 (gcc's internal type "sizetype" leaks out as base type name in the DWARF info) [1], GCC may start emitting base types wi= th no name, which became valid with DWARF5. >>From page DWARF5, page 103: A base type entry may have a DW_AT_name attribute whose value=20 is a null-terminated string containing the name of the base type as recognized by the programming language of the compilation unit=20 containing the base type entry. While in DWARF4 said: A base type entry has a DW_AT_name attribute whose value is a=20 null-terminated string containing the name of the base type as=20 recognized by the programming language of the compilation unit=20 containing the base type entry. We need to be sure that GDB supports this correctly before GCC stops emitti= ng the name. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21191-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 30 17:36:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79912 invoked by alias); 30 Mar 2017 17:36:07 -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 79876 invoked by uid 48); 30 Mar 2017 17:36:06 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21323] GDB thinks char16_t and char32_t are signed in C++ Date: Thu, 30 Mar 2017 17:36: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00343.txt.bz2 Content-length: 278 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21323 --- Comment #6 from Pedro Alves --- Fix(es) posted: https://sourceware.org/ml/gdb-patches/2017-03/msg00529.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21192-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 30 19:40:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68422 invoked by alias); 30 Mar 2017 19:40:59 -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 67843 invoked by uid 48); 30 Mar 2017 19:40:58 -0000 From: "elouan.appere@club-internet.fr" To: gdb-prs@sourceware.org Subject: [Bug gdb/21272] Missing call to to_can_do_single_step for arm-none-eabi Date: Thu, 30 Mar 2017 19:40: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.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: elouan.appere@club-internet.fr X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00344.txt.bz2 Content-length: 304 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21272 --- Comment #1 from Elouan App=C3=A9r=C3=A9 --- I've submitted a patch: https://sourceware.org/ml/gdb-patches/2017-03/msg00454.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21193-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 30 23:45:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41187 invoked by alias); 30 Mar 2017 23:45:49 -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 41165 invoked by uid 48); 30 Mar 2017 23:45:48 -0000 From: "Doug.Gilmore at imgtec dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21337] New: [mips] segfault when re-reading symbols with remote debugging. Date: Thu, 30 Mar 2017 23:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: Doug.Gilmore at imgtec dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q1/txt/msg00345.txt.bz2 Content-length: 834 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21337 Bug ID: 21337 Summary: [mips] segfault when re-reading symbols with remote debugging. Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: Doug.Gilmore at imgtec dot com Target Milestone: --- Created attachment 9955 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9955&action=3Dedit transcript for reproducing problem. This problem was introduced with commit g3e29f34. Transcript attached (normal run and run under valgrind). Will send a patch to gdb-patches. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21194-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 31 08:22:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 28747 invoked by alias); 31 Mar 2017 08:22:26 -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 28724 invoked by uid 48); 31 Mar 2017 08:22:26 -0000 From: "huganle at 163 dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21339] New: got segmentation error when call c function PyString_FromString() if installed python-dbg Date: Fri, 31 Mar 2017 08:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: huganle at 163 dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q1/txt/msg00346.txt.bz2 Content-length: 707 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21339 Bug ID: 21339 Summary: got segmentation error when call c function PyString_FromString() if installed python-dbg Product: gdb Version: 7.7 Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: huganle at 163 dot com Target Milestone: --- detail description can be seen from http://stackoverflow.com/questions/42239848/can-i-call-host-process-functio= n-with-c-string-in-gdb --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21195-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 31 08:29:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 39387 invoked by alias); 31 Mar 2017 08:29:49 -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 39360 invoked by uid 48); 31 Mar 2017 08:29:49 -0000 From: "huganle at 163 dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21339] got segmentation error when call c function PyString_FromString() if installed python-dbg Date: Fri, 31 Mar 2017 08:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: huganle at 163 dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00347.txt.bz2 Content-length: 257 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21339 --- Comment #1 from huganle --- My test enviroment is on debian8 with python2.7.9 and gdb7.7.1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21196-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 31 16:16:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41469 invoked by alias); 31 Mar 2017 16:16:25 -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 41433 invoked by uid 48); 31 Mar 2017 16:16:23 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21339] got segmentation error when call c function PyString_FromString() if installed python-dbg Date: Fri, 31 Mar 2017 16:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: WAITING 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: bug_status cf_reconfirmed_on cc everconfirmed 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: 2017-q1/txt/msg00348.txt.bz2 Content-length: 915 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21339 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2017-03-31 CC| |sergiodj at redhat dot com Ever confirmed|0 |1 --- Comment #2 from Sergio Durigan Junior --- Hi, thanks for the report. GDB 7.7.1 is somewhat old. Could you please try to reproduce this bug using the HEAD revision on our git repository? You can get it from: git://sourceware.org/git/binutils-gdb.git Let me know if you need help compiling GDB. Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21197-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 31 17:54:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107950 invoked by alias); 31 Mar 2017 17:54:08 -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 107916 invoked by uid 48); 31 Mar 2017 17:54:07 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug testsuite/8595] environ.exp could run on more platforms Date: Fri, 31 Mar 2017 17:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to 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: 2017-q1/txt/msg00349.txt.bz2 Content-length: 640 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8595 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com Assignee|unasigned at sourceware dot org |sergiodj at redhat = dot com --- Comment #2 from Sergio Durigan Junior --- Patch posted: https://sourceware.org/ml/gdb-patches/2017-03/msg00551.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21198-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 31 23:17:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107113 invoked by alias); 31 Mar 2017 23:17:27 -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 107076 invoked by uid 48); 31 Mar 2017 23:17:26 -0000 From: "Doug.Gilmore at imgtec dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21337] [mips] segfault when re-reading symbols with remote debugging. Date: Fri, 31 Mar 2017 23:17: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: Doug.Gilmore at imgtec dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q1/txt/msg00350.txt.bz2 Content-length: 295 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21337 --- Comment #1 from Doug Gilmore --- Patch sent out for review: https://sourceware.org/ml/gdb-patches/2017-03/msg00559.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21199-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Apr 01 08:28:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27818 invoked by alias); 1 Apr 2017 08:28:14 -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 27786 invoked by uid 48); 1 Apr 2017 08:28:13 -0000 From: "vljubovic at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21341] New: C++ vector elements wrongly evaluated with MI2 Date: Sat, 01 Apr 2017 08:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vljubovic at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00000.txt.bz2 Content-length: 4902 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21341 Bug ID: 21341 Summary: C++ vector elements wrongly evaluated with MI2 Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: vljubovic at gmail dot com Target Milestone: --- While debugging C++ programs, when options -q --interpreter=3Dmi2 gdb will = return wrong values while inspecting vector elements. Consider the following simple C++ program (bugdemo.cpp): #include #include int main() {=20=20 std::vector v{1,2,3,4}; // test int x; std::cin>>x; std::cout<<"Value of " << x << "-th element is "< This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from bugdemo...done. (gdb) break 7 Breakpoint 1 at 0x400bc1: file main.cpp, line 7. (gdb) run Starting program: /rhome/t/test/workspace/TP/T1/Z1/bugdemo=20 3 Breakpoint 1, main () at main.cpp:7 7 std::cout<<"Value of " << x << "-th element is "< >::value_type &) @0x6= 03014: 2 (gdb) q A debugging session is active. Inferior 1 [process 10116] will be killed. Quit anyway? (y or n) y So far soo good, everthing seems to work. Now the same session with command line: gdb -q --interpreter=3Dmi2 bugdemo =3Dthread-group-added,id=3D"i1" ~"Reading symbols from bugdemo..." ~"done.\n" (gdb)=20 -break-insert 8 ^done,bkpt=3D{number=3D"1",type=3D"breakpoint",disp=3D"keep",enabled=3D"y",= addr=3D"0x0000000000400c1a",func=3D"main()",file=3D"main.cpp",fullname=3D"/= rhome/t/test/workspace/TP/T1/Z1/main.cpp",line=3D"8",thread-groups=3D["i1"]= ,times=3D"0",original-location=3D"/rhome/t/test/workspace/TP/T1/Z1/main.cpp= :8"} (gdb)=20 -exec-run =3Dthread-group-started,id=3D"i1",pid=3D"10574" =3Dthread-created,id=3D"1",group-id=3D"i1" =3Dlibrary-loaded,id=3D"/lib64/ld-linux-x86-64.so.2",target-name=3D"/lib64/= ld-linux-x86-64.so.2",host-name=3D"/lib64/ld-linux-x86-64.so.2",symbols-loa= ded=3D"0",thread-group=3D"i1" ^running *running,thread-id=3D"all" (gdb)=20 =3Dlibrary-loaded,id=3D"/usr/lib/x86_64-linux-gnu/libstdc++.so.6",target-na= me=3D"/usr/lib/x86_64-linux-gnu/libstdc++.so.6",host-name=3D"/usr/lib/x86_6= 4-linux-gnu/libstdc++.so.6",symbols-loaded=3D"0",thread-group=3D"i1" =3Dlibrary-loaded,id=3D"/lib/x86_64-linux-gnu/libgcc_s.so.1",target-name=3D= "/lib/x86_64-linux-gnu/libgcc_s.so.1",host-name=3D"/lib/x86_64-linux-gnu/li= bgcc_s.so.1",symbols-loaded=3D"0",thread-group=3D"i1" =3Dlibrary-loaded,id=3D"/lib/x86_64-linux-gnu/libc.so.6",target-name=3D"/li= b/x86_64-linux-gnu/libc.so.6",host-name=3D"/lib/x86_64-linux-gnu/libc.so.6"= ,symbols-loaded=3D"0",thread-group=3D"i1" =3Dlibrary-loaded,id=3D"/lib/x86_64-linux-gnu/libm.so.6",target-name=3D"/li= b/x86_64-linux-gnu/libm.so.6",host-name=3D"/lib/x86_64-linux-gnu/libm.so.6"= ,symbols-loaded=3D"0",thread-group=3D"i1" 3 Value of 3-th element is 4 =3Dbreakpoint-modified,bkpt=3D{number=3D"1",type=3D"breakpoint",disp=3D"kee= p",enabled=3D"y",addr=3D"0x0000000000400c1a",func=3D"main()",file=3D"main.c= pp",fullname=3D"/rhome/t/test/workspace/TP/T1/Z1/main.cpp",line=3D"8",threa= d-groups=3D["i1"],times=3D"1",original-location=3D"/rhome/t/test/workspace/= TP/T1/Z1/main.cpp:8"} ~"\n" ~"Breakpoint 1, main () at main.cpp:8\n" ~"8\t return 0;\n" *stopped,reason=3D"breakpoint-hit",disp=3D"keep",bkptno=3D"1",frame=3D{addr= =3D"0x0000000000400c1a",func=3D"main",args=3D[],file=3D"main.cpp",fullname= =3D"/rhome/t/test/workspace/TP/T1/Z1/main.cpp",line=3D"8"},thread-id=3D"1",= stopped-threads=3D"all",core=3D"1" (gdb)=20 -data-evaluate-expression v[1] ^done,value=3D"@0x603014" (gdb)=20 q &"q\n" =3Dthread-exited,id=3D"1",group-id=3D"i1" =3Dthread-group-exited,id=3D"i1" Notice the line: ^done,value=3D"@0x603014" expected result should be: ^done,value=3D"2" --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21200-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 04 00:09:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 12638 invoked by alias); 4 Apr 2017 00:09:14 -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 12607 invoked by uid 48); 4 Apr 2017 00:09:13 -0000 From: "macro@linux-mips.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21337] [mips] segfault when re-reading symbols with remote debugging. Date: Tue, 04 Apr 2017 00:09: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: macro@linux-mips.org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00001.txt.bz2 Content-length: 390 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21337 Maciej W. Rozycki changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |macro@linux-mips.org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21201-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 04 04:07:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3069 invoked by alias); 4 Apr 2017 04:07:12 -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 3041 invoked by uid 48); 4 Apr 2017 04:07:10 -0000 From: "oshin.khandelwal at amdocs dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21350] New: ptrace: No such process Date: Tue, 04 Apr 2017 04:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: oshin.khandelwal at amdocs dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00002.txt.bz2 Content-length: 1072 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 Bug ID: 21350 Summary: ptrace: No such process Product: gdb Version: 7.2 Status: UNCONFIRMED Severity: critical Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: oshin.khandelwal at amdocs dot com Target Milestone: --- > gdb -p GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: . Attaching to process 13384 ptrace: No such process. (gdb) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21202-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 04 09:24:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 29742 invoked by alias); 4 Apr 2017 09:24:28 -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 29524 invoked by uid 48); 4 Apr 2017 09:24:10 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21350] ptrace: No such process Date: Tue, 04 Apr 2017 09:24: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.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00003.txt.bz2 Content-length: 527 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- What's the bug that you're reporting? What were you expecting to see? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21203-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 04 09:31:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 39041 invoked by alias); 4 Apr 2017 09:31:15 -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 38999 invoked by uid 55); 4 Apr 2017 09:31:14 -0000 From: "oshin.khandelwal at amdocs dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21350] ptrace: No such process Date: Tue, 04 Apr 2017 09:31: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.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: oshin.khandelwal at amdocs dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00004.txt.bz2 Content-length: 1768 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 --- Comment #2 from oshin.khandelwal at amdocs dot com --- HI Pedro, When executing gdb command with process id, the command terminates with " ptrace: No such process". We expect to see the details related to the PID mapped in command argument. OS Version : Red Hat Enterprise Linux Server release 6.4 (Santiago) GLIBC Version on server are as below, #rpm -qa | grep -i glibc glibc-headers-2.12-1.107.el6.x86_64 glibc-devel-2.12-1.107.el6.x86_64 glibc-devel-2.12-1.107.el6.i686 glibc-common-2.12-1.107.el6.x86_64 glibc-2.12-1.107.el6.i686 glibc-2.12-1.107.el6.x86_64 Regards, Oshin Khandelwal Global SE&O IT, Business Technologies Group Contact : +91-9764073624 Desk: 2091-58406 -----Original Message----- From: palves at redhat dot com [mailto:sourceware-bugzilla@sourceware.org]= =20 Sent: Tuesday, April 04, 2017 2:54 PM To: Oshin Khandelwal Subject: [Bug gdb/21350] ptrace: No such process https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- What's the b= ug that you're reporting? What were you expecting to see? -- You are receiving this mail because: You reported the bug. This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21204-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 04 09:32:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 40848 invoked by alias); 4 Apr 2017 09:32:49 -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 40822 invoked by uid 48); 4 Apr 2017 09:32:48 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21350] ptrace: No such process Date: Tue, 04 Apr 2017 09:32: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.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00005.txt.bz2 Content-length: 241 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 --- Comment #3 from Pedro Alves --- But does the process with that ID exist? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21205-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 04 09:37:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4070 invoked by alias); 4 Apr 2017 09:37:20 -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 1992 invoked by uid 55); 4 Apr 2017 09:37:19 -0000 From: "oshin.khandelwal at amdocs dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21350] ptrace: No such process Date: Tue, 04 Apr 2017 09:37: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.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: oshin.khandelwal at amdocs dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00006.txt.bz2 Content-length: 1775 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 --- Comment #4 from oshin.khandelwal at amdocs dot com --- Hi, Please refer the below output. [user]@> psu | grep BL1BTLSOR [user] 13384 1 1 22:22 ? 00:00:13 bl1BTLServer -n BL1BTLSOR -f REGULAR [user] 31135 12301 0 22:37 pts/0 00:00:00 grep BL1BTLSOR [user]@> gdb -p 13384 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: . Attaching to process 13384 ptrace: No such process. (gdb) Regards, Oshin Khandelwal Global SE&O IT, Business Technologies Group Contact : +91-9764073624 Desk: 2091-58406 -----Original Message----- From: palves at redhat dot com [mailto:sourceware-bugzilla@sourceware.org]= =20 Sent: Tuesday, April 04, 2017 9:33 AM To: Oshin Khandelwal Subject: [Bug gdb/21350] ptrace: No such process https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 --- Comment #3 from Pedro Alves --- But does the process with that ID exist? -- You are receiving this mail because: You reported the bug. This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21206-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 04 09:43:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35786 invoked by alias); 4 Apr 2017 09:43:58 -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 35761 invoked by uid 48); 4 Apr 2017 09:43:57 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21350] ptrace: No such process Date: Tue, 04 Apr 2017 09:43: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.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q2/txt/msg00007.txt.bz2 Content-length: 962 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Pedro Alves --- (In reply to oshin.khandelwal from comment #4) > Hi, >=20 > Please refer the below output. >=20 > [user]@> psu | grep BL1BTLSOR > [user] 13384 1 1 22:22 ? 00:00:13 bl1BTLServer -n BL1BTLSOR = -f > REGULAR Looks like the process is zombie. "cat /proc/13384/status" would probably show it. More recent GDBs give a clearer message in this case: process 13384 is a zombie - the process has already terminated Tentatively closing. Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21207-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 04 10:29:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 90913 invoked by alias); 4 Apr 2017 10:29:03 -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 90866 invoked by uid 55); 4 Apr 2017 10:29:03 -0000 From: "oshin.khandelwal at amdocs dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21350] ptrace: No such process Date: Tue, 04 Apr 2017 10:29: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.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: oshin.khandelwal at amdocs dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME 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: 2017-q2/txt/msg00008.txt.bz2 Content-length: 1758 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 --- Comment #6 from oshin.khandelwal at amdocs dot com --- Hi, Do we expect the same output for sleeping processes as well ? Regards, Oshin Khandelwal Global SE&O IT, Business Technologies Group Contact : +91-9764073624 Desk: 2091-58406 -----Original Message----- From: palves at redhat dot com [mailto:sourceware-bugzilla@sourceware.org]= =20 Sent: Tuesday, April 04, 2017 3:14 PM To: Oshin Khandelwal Subject: [Bug gdb/21350] ptrace: No such process https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Pedro Alves --- (In reply to oshin.khandelwal from comment #4) > Hi, >=20 > Please refer the below output. >=20 > [user]@> psu | grep BL1BTLSOR > [user] 13384 1 1 22:22 ? 00:00:13 bl1BTLServer -n BL1BTLSOR = -f > REGULAR Looks like the process is zombie. "cat /proc/13384/status" would probably show it. More recent GDBs give a clearer message in this case: process 13384 is a zombie - the process has already terminated Tentatively closing. Thanks. -- You are receiving this mail because: You reported the bug. This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21208-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 04 10:44:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41160 invoked by alias); 4 Apr 2017 10:44:58 -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 41130 invoked by uid 55); 4 Apr 2017 10:44:58 -0000 From: "oshin.khandelwal at amdocs dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21350] ptrace: No such process Date: Tue, 04 Apr 2017 10:44: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.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: oshin.khandelwal at amdocs dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME 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: 2017-q2/txt/msg00009.txt.bz2 Content-length: 2133 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 --- Comment #7 from oshin.khandelwal at amdocs dot com --- Hi Pedro, Need an update on this on priority. Regards, Oshin Khandelwal Global SE&O IT, Business Technologies Group Contact : +91-9764073624 Desk: 2091-58406 -----Original Message----- From: Oshin Khandelwal=20 Sent: Tuesday, April 04, 2017 3:57 PM To: 'palves at redhat dot com' Subject: RE: [Bug gdb/21350] ptrace: No such process Hi, Do we expect the same output for sleeping processes as well ? Regards, Oshin Khandelwal Global SE&O IT, Business Technologies Group Contact : +91-9764073624 Desk: 2091-58406 -----Original Message----- From: palves at redhat dot com [mailto:sourceware-bugzilla@sourceware.org]= =20 Sent: Tuesday, April 04, 2017 3:14 PM To: Oshin Khandelwal Subject: [Bug gdb/21350] ptrace: No such process https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Pedro Alves --- (In reply to oshin.khandelwal from comment #4) > Hi, >=20 > Please refer the below output. >=20 > [user]@> psu | grep BL1BTLSOR > [user] 13384 1 1 22:22 ? 00:00:13 bl1BTLServer -n BL1BTLSOR = -f > REGULAR Looks like the process is zombie. "cat /proc/13384/status" would probably show it. More recent GDBs give a clearer message in this case: process 13384 is a zombie - the process has already terminated Tentatively closing. Thanks. -- You are receiving this mail because: You reported the bug. This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21209-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 04 10:57:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 113556 invoked by alias); 4 Apr 2017 10:57:18 -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 113531 invoked by uid 48); 4 Apr 2017 10:57:18 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21350] ptrace: No such process Date: Tue, 04 Apr 2017 10:57: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.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME 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: 2017-q2/txt/msg00010.txt.bz2 Content-length: 536 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 --- Comment #8 from Pedro Alves --- > Need an update on this on priority. Please note this is an upstream tracker monitored on a volunteering basis, = and as such priority requests don't mean much here. If you need priority handl= ing, please file a bug with your vendor (RHEL/Red Hat) in this case. > Do we expect the same output for sleeping processes as well ? No. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21210-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 04 16:11:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 16033 invoked by alias); 4 Apr 2017 16:11:29 -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 16008 invoked by uid 48); 4 Apr 2017 16:11:29 -0000 From: "jcarriere@ausy-group.com" To: gdb-prs@sourceware.org Subject: [Bug c++/21352] New: Command tsave does not support -r argument Date: Tue, 04 Apr 2017 16:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jcarriere@ausy-group.com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00011.txt.bz2 Content-length: 1445 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21352 Bug ID: 21352 Summary: Command tsave does not support -r argument Product: gdb Version: 7.11 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: jcarriere@ausy-group.com Target Milestone: --- The command tsave, for saving tracepoints to a file, refuses the -r option, claiming it is not a valid option. My personal investigation lead me to trace_save_command (in tracepoint.c or tracefile.c), which has code like this: for (; *argv; ++argv) { if (strcmp (*argv, "-r") =3D=3D 0) target_does_save =3D 1; if (strcmp (*argv, "-ctf") =3D=3D 0) generate_ctf =3D 1; else if (**argv =3D=3D '-') error (_("unknown option `%s'"), *argv); else filename =3D *argv; } I fixed it like this: for (; *argv; ++argv) { if (strcmp (*argv, "-r") =3D=3D 0) target_does_save =3D 1; else if (strcmp (*argv, "-ctf") =3D=3D 0) generate_ctf =3D 1; else if (**argv =3D=3D '-') error (_("unknown option `%s'"), *argv); else filename =3D *argv; } Thank you the GDB team for developing this great piece of software. Jonathan. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21211-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 04 18:47:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 113222 invoked by alias); 4 Apr 2017 18:47:22 -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 113016 invoked by uid 48); 4 Apr 2017 18:47:21 -0000 From: "eyck@it-jw.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/13519] [avr][Regression 7.1/7.2/7.3/7.4] disassemble command attempts to disassemble SRAM rather than program memory Date: Tue, 04 Apr 2017 18:47: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.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: eyck@it-jw.com 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: cc 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: 2017-q2/txt/msg00012.txt.bz2 Content-length: 576 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13519 Eyck Jentzsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eyck@it-jw.com --- Comment #20 from Eyck Jentzsch --- Hi, the submission of the patch to gdb-patches is more than a year old. Is there any estimate when this patch will become part of the main line? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21212-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 05 11:37:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 77358 invoked by alias); 5 Apr 2017 11:37:48 -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 76593 invoked by uid 55); 5 Apr 2017 11:37:47 -0000 From: "oshin.khandelwal at amdocs dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21350] ptrace: No such process Date: Wed, 05 Apr 2017 11:37: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.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: oshin.khandelwal at amdocs dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME 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: 2017-q2/txt/msg00013.txt.bz2 Content-length: 2295 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 --- Comment #9 from oshin.khandelwal at amdocs dot com --- Hi, [root@ ~]# ps -ef | grep -i bl1BTLServer [user] 4613 1 0 Apr04 ? 00:00:41 bl1BTLServer -n BL1BTLSOR -f REGULAR [user] 10414 1 0 Apr04 ? 00:00:19 bl1BTLServer -n BTLQUOTE -f REGULAR root 26465 20983 0 17:05 pts/4 00:00:00 grep -i bl1BTLServer [root@ ~]# cat /proc/4613/status | grep -i state State: S (sleeping) [root@ ~]# cat /proc/10414/status | grep -i state State: S (sleeping) [root@ ~]# gdb -p 10414 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: . Attaching to process 10414 ptrace: No such process. Regards, Oshin Khandelwal Global SE&O IT, Business Technologies Group Contact : +91-9764073624 Desk: 2091-58406 -----Original Message----- From: palves at redhat dot com [mailto:sourceware-bugzilla@sourceware.org]= =20 Sent: Tuesday, April 04, 2017 4:27 PM To: Oshin Khandelwal Subject: [Bug gdb/21350] ptrace: No such process https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 --- Comment #8 from Pedro Alves --- > Need an update on this on priority. Please note this is an upstream tracker monitored on a volunteering basis, = and as such priority requests don't mean much here. If you need priority handl= ing, please file a bug with your vendor (RHEL/Red Hat) in this case. > Do we expect the same output for sleeping processes as well ? No. -- You are receiving this mail because: You reported the bug. This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21213-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 05 16:02:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 105350 invoked by alias); 5 Apr 2017 16:02:02 -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 104291 invoked by uid 48); 5 Apr 2017 16:02:02 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21350] ptrace: No such process Date: Wed, 05 Apr 2017 16:02: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.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q2/txt/msg00014.txt.bz2 Content-length: 779 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21350 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #10 from Sergio Durigan Junior --- I recommend that you open this bug on Red Hat's bugzilla (https://bugzilla.redhat.com/enter_bug.cgi?product=3DRed%20Hat%20Enterprise= %20Linux%206) as this is happening with a GDB that is shipped by RHEL-6.4. This bug cann= ot be reproduced by using the latest version of GDB upstream. Thanks, --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21214-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 05 16:04:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68208 invoked by alias); 5 Apr 2017 16:04:35 -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 66434 invoked by uid 48); 5 Apr 2017 16:04:34 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21352] Command tsave does not support -r argument Date: Wed, 05 Apr 2017 16:04: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: 7.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00015.txt.bz2 Content-length: 603 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21352 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #1 from Sergio Durigan Junior --- Hi Jonathan, Thanks for the report. Yeah, this is clearly a thinko. I'll push an obvious commit fixing this. Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21215-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 05 16:21:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 62751 invoked by alias); 5 Apr 2017 16:21:14 -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 62715 invoked by uid 48); 5 Apr 2017 16:21:13 -0000 From: "andrew at ugh dot net.au" To: gdb-prs@sourceware.org Subject: [Bug d/21354] New: can't index a dynamic array Date: Wed, 05 Apr 2017 16:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: d X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: andrew at ugh dot net.au X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00016.txt.bz2 Content-length: 848 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21354 Bug ID: 21354 Summary: can't index a dynamic array Product: gdb Version: HEAD Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: d Assignee: unassigned at sourceware dot org Reporter: andrew at ugh dot net.au Target Milestone: --- With a declaration like: char[] string =3D "hello"; I can print it: (gdb) p string $1 =3D "hello" But can't access individual elements: (gdb) p string[0] Invalid binary operation specified. However using .ptr works: (gdb) p string.ptr[0] $2 =3D 104 'h' I'm compiling using dmd v1.079.0 and using gdb as of 4ac40124eef08045bf99ad9f4fcc277961953109. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21216-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 05 16:23:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64960 invoked by alias); 5 Apr 2017 16:23:16 -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 64936 invoked by uid 48); 5 Apr 2017 16:23:15 -0000 From: "andrew at ugh dot net.au" To: gdb-prs@sourceware.org Subject: [Bug d/21355] New: can't slice a dynamic array Date: Wed, 05 Apr 2017 16:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: d X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: andrew at ugh dot net.au X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00017.txt.bz2 Content-length: 765 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21355 Bug ID: 21355 Summary: can't slice a dynamic array Product: gdb Version: HEAD Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: d Assignee: unassigned at sourceware dot org Reporter: andrew at ugh dot net.au Target Milestone: --- With a declaration like: char[] string =3D "hello"; I can print it: (gdb) p string $1 =3D "hello" But can't slice it: (gdb) p string[0 .. 3] cannot take slice of non-array I'm compiling using dmd v1.079.0 and using gdb as of 4ac40124eef08045bf99ad9f4fcc277961953109. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21217-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 05 16:27:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 69504 invoked by alias); 5 Apr 2017 16:27: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 69473 invoked by uid 48); 5 Apr 2017 16:27:51 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21352] Command tsave does not support -r argument Date: Wed, 05 Apr 2017 16:27: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.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: component 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: 2017-q2/txt/msg00018.txt.bz2 Content-length: 383 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21352 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Component|c++ |gdb --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21218-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 05 16:32:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 15088 invoked by alias); 5 Apr 2017 16:32:20 -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 15063 invoked by uid 55); 5 Apr 2017 16:32:20 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21352] Command tsave does not support -r argument Date: Wed, 05 Apr 2017 16:32: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.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00019.txt.bz2 Content-length: 1007 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21352 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D4a596fe20e93= 109300e841a3d0ee5f198146ab6d commit 4a596fe20e93109300e841a3d0ee5f198146ab6d Author: Sergio Durigan Junior Date: Wed Apr 5 12:28:30 2017 -0400 Fix PR 21352: Command tsave does not support -r argument This is an obvious fix for PR 21352. The problem is that the argument parsing loop is not using an "else if" where it should, and therefore the '-r' option ends up unrecognized by GDB. gdb/ChangeLog: 2017-04-05 Sergio Durigan Junior PR gdb/21352 * tracefile.c (tsave_command): Fix argument parsing for '-r' option. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21219-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 05 16:32:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 16479 invoked by alias); 5 Apr 2017 16:32:51 -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 16391 invoked by uid 48); 5 Apr 2017 16:32:51 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21352] Command tsave does not support -r argument Date: Wed, 05 Apr 2017 16:32: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.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q2/txt/msg00020.txt.bz2 Content-length: 587 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21352 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Sergio Durigan Junior --- Fixed. https://sourceware.org/ml/gdb-patches/2017-04/msg00117.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21220-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 05 16:40:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27623 invoked by alias); 5 Apr 2017 16:40:34 -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 27585 invoked by uid 48); 5 Apr 2017 16:40:33 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Wed, 05 Apr 2017 16:40: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00021.txt.bz2 Content-length: 588 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org --- Comment #5 from Yao Qi --- If you start gdb, type "abc" and enter. Does GDB crash? Can you run gdb in gdb or other debugger, and capture the stack backtrace on crash? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21221-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 05 16:45:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 77379 invoked by alias); 5 Apr 2017 16:45:46 -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 75430 invoked by uid 55); 5 Apr 2017 16:45:40 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21352] Command tsave does not support -r argument Date: Wed, 05 Apr 2017 16:45: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.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 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: 2017-q2/txt/msg00022.txt.bz2 Content-length: 831 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21352 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D0ad9d8c73486= e60c5a4963c1b7a0ea7063d69cd2 commit 0ad9d8c73486e60c5a4963c1b7a0ea7063d69cd2 Author: Sergio Durigan Junior Date: Wed Apr 5 12:43:52 2017 -0400 PR 21352: Add testsuite for "tsave -r" command This commit adds a test for the fix of PR 21352. gdb/testsuite/ChangeLog: 2017-04-05 Sergio Durigan Junior PR gdb/21352 * gdb.trace/tsv.exp: Add test for "tsave -r". --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21222-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 05 17:19:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 48024 invoked by alias); 5 Apr 2017 17:19:25 -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 47888 invoked by uid 48); 5 Apr 2017 17:19:15 -0000 From: "tcurdt at vafer dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Wed, 05 Apr 2017 17:19: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tcurdt at vafer dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00023.txt.bz2 Content-length: 5709 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 --- Comment #6 from tcurdt at vafer dot org --- Yes, that also crashes: $ arm-none-eabi-gdb GNU gdb (GNU Tools for ARM Embedded Processors) 7.12.0.20161204-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copyi= ng" and "show warranty" for details. This GDB was configured as "--host=3Dx86_64-apple-darwin10 --target=3Darm-none-eabi". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) abc Abort trap: 6 Here is the stacktrace: $ lldb arm-none-eabi-gdb (lldb) target create "arm-none-eabi-gdb" Traceback (most recent call last): File "", line 1, in File "/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources= /Python/lldb/__init__.py", line 98, in import six ImportError: No module named six Traceback (most recent call last): ... many of these ... Traceback (most recent call last): File "", line 1, in NameError: name 'run_one_line' is not defined ... Current executable set to 'arm-none-eabi-gdb' (x86_64). (lldb) r Process 53435 launched: '/usr/local/bin/arm-none-eabi-gdb' (x86_64) GNU gdb (GNU Tools for ARM Embedded Processors) 7.12.0.20161204-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=3Dx86_64-apple-darwin10 --target=3Darm-none-eabi". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) abc Process 53435 stopped * thread #1, queue =3D 'com.apple.main-thread', stop reason =3D signal SI= GABRT frame #0: 0x00007fffc65cbd42 libsystem_kernel.dylib`__pthread_kill + = 10 libsystem_kernel.dylib`__pthread_kill: -> 0x7fffc65cbd42 <+10>: jae 0x7fffc65cbd4c ; <+20> 0x7fffc65cbd44 <+12>: movq %rax, %rdi 0x7fffc65cbd47 <+15>: jmp 0x7fffc65c4caf ; cerror_nocan= cel 0x7fffc65cbd4c <+20>: retq=20=20=20 (lldb) bt all * thread #1, queue =3D 'com.apple.main-thread', stop reason =3D signal SI= GABRT * frame #0: 0x00007fffc65cbd42 libsystem_kernel.dylib`__pthread_kill + = 10 frame #1: 0x00007fffc66b95bf libsystem_pthread.dylib`pthread_kill + 90 frame #2: 0x00007fffc6531420 libsystem_c.dylib`abort + 129 frame #3: 0x00000001003310a1 arm-none-eabi-gdb`uw_init_context_1 + 88 frame #4: 0x0000000100331498 arm-none-eabi-gdb`_Unwind_RaiseException= + 62 frame #5: 0x000000010032f868 arm-none-eabi-gdb`__cxa_throw + 90 frame #6: 0x0000000100231ae5 arm-none-eabi-gdb`throw_exception_cxx(gdb_exception) + 117 frame #7: 0x0000000100231b75 arm-none-eabi-gdb`throw_it(return_reason, errors, char const*, __va_list_tag*) + 101 frame #8: 0x0000000100231da6 arm-none-eabi-gdb`throw_verror(errors, c= har const*, __va_list_tag*) + 22 frame #9: 0x00000001001f4c24 arm-none-eabi-gdb`verror(char const*, __va_list_tag*) + 20 frame #10: 0x000000010023172c arm-none-eabi-gdb`error(char const*, ..= .) + 140 frame #11: 0x0000000100333d46 arm-none-eabi-gdb`undef_cmd_error(char const*, char const*) + 67 frame #12: 0x000000010004454a arm-none-eabi-gdb`lookup_cmd(char const= **, cmd_list_element*, char*, int, int) + 522 frame #13: 0x00000001001f28ef arm-none-eabi-gdb`execute_command(char*, int) + 175 frame #14: 0x000000010012566c arm-none-eabi-gdb`command_handler(char*= ) + 108 frame #15: 0x000000010012595a arm-none-eabi-gdb`command_line_handler(char*) + 58 frame #16: 0x0000000100124bd7 arm-none-eabi-gdb`gdb_rl_callback_handler(char*) + 55 frame #17: 0x0000000100250fa8 arm-none-eabi-gdb`rl_callback_read_char= + 328 frame #18: 0x0000000100124b2e arm-none-eabi-gdb`gdb_rl_callback_read_char_wrapper(void*) + 78 frame #19: 0x00000001001250d0 arm-none-eabi-gdb`stdin_event_handler(i= nt, void*) + 80 frame #20: 0x0000000100123ef5 arm-none-eabi-gdb`gdb_wait_for_event(in= t) + 1285 frame #21: 0x0000000100124052 arm-none-eabi-gdb`gdb_do_one_event() (.part.2) + 114 frame #22: 0x00000001001241c5 arm-none-eabi-gdb`start_event_loop() + = 21 frame #23: 0x000000010011dcbb arm-none-eabi-gdb`captured_command_loop(void*) + 43 frame #24: 0x000000010011af6f arm-none-eabi-gdb`catch_errors(int (*)(void*), void*, char*, return_mask) + 79 frame #25: 0x000000010011ee2a arm-none-eabi-gdb`gdb_main(captured_main_args*) + 3194 frame #26: 0x0000000100332e78 arm-none-eabi-gdb`main + 40 frame #27: 0x0000000100000cf4 arm-none-eabi-gdb`start + 52 (lldb) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21223-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 05 19:21:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 85362 invoked by alias); 5 Apr 2017 19:21:34 -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 85336 invoked by uid 48); 5 Apr 2017 19:21:33 -0000 From: "steve.merritt at intel dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21356] New: value.c:828: internal-error: int value_contents_bits_eq(const value*, int, const value*, int, int): Assertion `offset1 + length <= TYPE_LENGTH (val1->enclosing_type) * TARGET_CHAR_BIT' failed Date: Wed, 05 Apr 2017 19:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: steve.merritt at intel dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00024.txt.bz2 Content-length: 2204 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21356 Bug ID: 21356 Summary: value.c:828: internal-error: int value_contents_bits_eq(const value*, int, const value*, int, int): Assertion `offset1 + length <=3D TYPE_LENGTH (val1->enclosing_type) * TARGET_CHAR_BIT' failed Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: steve.merritt at intel dot com Target Milestone: --- gdb will assert when printing "container_object2" in the attached sample. value.c:828: internal-error: int value_contents_bits_eq(const value*, int, const value*, int, int): Assertion `offset1 + length <=3D TYPE_LENGTH (val1->enclosing_type) * TARGET_CHAR_BIT' failed. The use of a typedef in the declaration of one of the fields of the struct container_struct2 is triggering the issue. In the attached sample, there are two nearly identical structs, container_struct1 and container_struct2. The only difference between the t= wo is the use of a typedef in container_struct2 when declaring one of the fiel= ds.=20 The field (_vla_struct_object2) is a variable length struct. To reproduce: > gcc -g vls_assert.c > gdb a.out (gdb) b 49 Breakpoint 1 at 0x40095a: file vls_assert.c, line 49. (gdb) r Breakpoint 1, vls_factory (n=3D5) at vls_assert.c:50 50 return; (gdb) p container_object1 $1 =3D {_container_member1 =3D 5, _vla_struct_object1 =3D {_some_member = =3D 10,=20 _vla_field =3D {0, 2, 4, 6, 8}}} (gdb) p container_object2 $2 =3D {_container_member2 =3D 15, _vla_struct_object2 =3D {_some_member= =3D 0,=20 _vla_field =3D { value.c:828: internal-error: int value_contents_bits_eq(const value*,=20 int, const value*, int, int): Assertion `offset1 + length <=3D TYPE_LENG= TH (val1->enclosing_type) * TARGET_CHAR_BIT' failed. I reproduced the issue with gcc 4.8.3 and gcc 6.3.0 on EL7.0. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21224-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 05 19:22:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 86291 invoked by alias); 5 Apr 2017 19:22:28 -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 86263 invoked by uid 48); 5 Apr 2017 19:22:27 -0000 From: "steve.merritt at intel dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21356] value.c:828: internal-error: int value_contents_bits_eq(const value*, int, const value*, int, int): Assertion `offset1 + length <= TYPE_LENGTH (val1->enclosing_type) * TARGET_CHAR_BIT' failed Date: Wed, 05 Apr 2017 19:22: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: steve.merritt at intel dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00025.txt.bz2 Content-length: 330 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21356 --- Comment #1 from Steve Merritt --- Created attachment 9974 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9974&action=3Dedit assertion reproducer --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21225-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 07 10:07:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 101176 invoked by alias); 7 Apr 2017 10:07:54 -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 101139 invoked by uid 48); 7 Apr 2017 10:07:53 -0000 From: "jwakely.gcc at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21358] New: Can't list or set breakpoints in current source file if it is a symlink Date: Fri, 07 Apr 2017 10:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jwakely.gcc at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00026.txt.bz2 Content-length: 4251 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21358 Bug ID: 21358 Summary: Can't list or set breakpoints in current source file if it is a symlink Product: gdb Version: 7.11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: jwakely.gcc at gmail dot com Target Milestone: --- ~$ cd /tmp tmp$ cat > test.cc #include void f() { puts("printy printy printy"); }=20 int main() { f(); } tmp$ ln -s test.cc link.cc tmp$ g++ -g link.cc tmp$ /home/jwakely/gcc/gdb/7.12.1/bin/gdb -nx -ex start -ex "br 5" a.out GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from a.out...done. Temporary breakpoint 1 at 0x4005fb: file link.cc, line 10. Starting program: /tmp/a.out=20 Temporary breakpoint 1, main () at link.cc:10 10 f(); No line 5 in the current file. Make breakpoint pending on future shared library load? (y or [n]) n (gdb) br 5 No line 5 in the current file. Make breakpoint pending on future shared library load? (y or [n]) n (gdb) step f () at link.cc:5 5 puts("printy printy printy"); (gdb) bt #0 f () at link.cc:5 #1 0x0000000000400600 in main () at link.cc:10 (gdb) br Breakpoint 2 at 0x4005ea: file link.cc, line 5. (gdb) l 5 No line 5 in the current file. (gdb) l link.cc:5 1 #include 2 3 void f() 4 { 5 puts("printy printy printy"); 6 } 7 8 int main() 9 { 10 f(); (gdb) l test.cc:5 No source file named test.cc. (gdb)=20 The backtrace shows the "correct" filename (i.e. the symlink) and setting a breakpoint on the current line shows "file link.cc, line 5", and setting a breakpoint at "link.cc:5" works. But "br 5" and "list 5" don't. (gdb) maint info line-table objfile: /tmp/a.out ((struct objfile *) 0x2606bb0) compunit_symtab: ((struct compunit_symtab *) 0x2611c40) symtab: /tmp/test.cc ((struct symtab *) 0x2611cc0) linetable: ((struct linetable *) 0x265f140): INDEX LINE ADDRESS 0 4 0x00000000004005e6 1 5 0x00000000004005ea 2 6 0x00000000004005f4 3 9 0x00000000004005f7 4 10 0x00000000004005fb 5 11 0x0000000000400600 6 0 0x0000000000400607 objfile: /tmp/a.out ((struct objfile *) 0x2606bb0) compunit_symtab: ((struct compunit_symtab *) 0x2611c40) symtab: /usr/lib/gcc/x86_64-redhat-linux/6.3.1/include/stddef.h ((struct sy= mtab *) 0x2611d00) linetable: ((struct linetable *) 0x0): No line table. objfile: /tmp/a.out ((struct objfile *) 0x2606bb0) compunit_symtab: ((struct compunit_symtab *) 0x2611c40) symtab: /usr/include/bits/types.h ((struct symtab *) 0x2611d40) linetable: ((struct linetable *) 0x0): No line table. objfile: /tmp/a.out ((struct objfile *) 0x2606bb0) compunit_symtab: ((struct compunit_symtab *) 0x2611c40) symtab: /usr/include/libio.h ((struct symtab *) 0x2611d80) linetable: ((struct linetable *) 0x0): No line table. objfile: /tmp/a.out ((struct objfile *) 0x2606bb0) compunit_symtab: ((struct compunit_symtab *) 0x2611c40) symtab: /usr/include/stdio.h ((struct symtab *) 0x2611dc0) linetable: ((struct linetable *) 0x0): No line table. objfile: /tmp/a.out ((struct objfile *) 0x2606bb0) compunit_symtab: ((struct compunit_symtab *) 0x2611c40) symtab: /usr/include/bits/sys_errlist.h ((struct symtab *) 0x2611e00) linetable: ((struct linetable *) 0x0): No line table. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21226-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 07 10:08:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 103978 invoked by alias); 7 Apr 2017 10:08:05 -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 103947 invoked by uid 48); 7 Apr 2017 10:08:04 -0000 From: "jwakely.gcc at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21358] Can't list or set breakpoints in current source file if it is a symlink Date: Fri, 07 Apr 2017 10:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jwakely.gcc at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: version 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: 2017-q2/txt/msg00027.txt.bz2 Content-length: 382 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21358 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Version|7.11.1 |7.12.1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21227-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 07 11:31:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 30883 invoked by alias); 7 Apr 2017 11:31:33 -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 29752 invoked by uid 48); 7 Apr 2017 11:31:32 -0000 From: "jwakely.gcc at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21358] Can't list or set breakpoints in current source file if it is a symlink Date: Fri, 07 Apr 2017 11:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jwakely.gcc at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00028.txt.bz2 Content-length: 736 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21358 --- Comment #1 from Jonathan Wakely --- Pedro suggested this is related to "set basenames-may-differ" and so might = be by design. I would argue that the user experience is quite poor in that case though. Most commands seem pretty clear about what the current file name is: (gdb) step f () at link.cc:5 5 puts("printy printy printy"); (gdb) bt #0 f () at link.cc:5 #1 0x0000000000400600 in main () at link.cc:10 (gdb) br Breakpoint 2 at 0x4005ea: file link.cc, line 5. But then suddenly it's no longer that file: (gdb) l 5 No line 5 in the current file. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21228-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 07 13:42:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53129 invoked by alias); 7 Apr 2017 13:42: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 53054 invoked by uid 48); 7 Apr 2017 13:42:52 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Fri, 07 Apr 2017 13:42: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00029.txt.bz2 Content-length: 1810 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 --- Comment #7 from Yao Qi --- Reproduced on GDB mainline as well. (gdb) abc Process 40992 stopped * thread #1: tid =3D 0x1f03, 0x00007fff8b71382a libsystem_kernel.dylib`__ki= ll + 10, stop reason =3D signal SIGABRT frame #0: 0x00007fff8b71382a libsystem_kernel.dylib`__kill + 10 libsystem_kernel.dylib`__kill + 10: -> 0x7fff8b71382a: jae 0x00007fff8b713831 ; __kill + 17 0x7fff8b71382c: jmpq 0x00007fff8b714ffc ; cerror 0x7fff8b713831: ret=20=20=20=20 0x7fff8b713832: nop=20=20=20=20 (lldb) bt=20 * thread #1: tid =3D 0x1f03, 0x00007fff8b71382a libsystem_kernel.dylib`__ki= ll + 10, stop reason =3D signal SIGABRT frame #0: 0x00007fff8b71382a libsystem_kernel.dylib`__kill + 10 frame #1: 0x00007fff8ac4ba9c libsystem_c.dylib`abort + 177 frame #2: 0x00000001003774e1 gdb`uw_init_context_1 + 88 at unwind-dw2.c:1563 frame #3: 0x00000001003778d8 gdb`_Unwind_RaiseException + 62 at unwind.inc:88 frame #4: 0x000000010033119f gdb`__cxa_throw + 90 at eh_throw.cc:82 frame #5: 0x0000000100124e7d gdb`throw_exception_cxx + 125 at common-exceptions.c:303 frame #6: 0x0000000100124f15 gdb`throw_it + 101 at common-exceptions.c:= 317 frame #7: 0x0000000100125156 gdb`throw_verror(errors, char const*, __va_list_tag*) + 22 at common-exceptions.c:379 frame #8: 0x00000001002633d4 gdb`verror(char const*, __va_list_tag*) + = 20 at utils.c:432 frame #9: 0x000000010017594c gdb`error(char const*, ...) + 140 at errors.c:43 frame #10: 0x000000010037a178 gdb`undef_cmd_error + 86 at cli-decode.c:= 1464 However, if I remove -static-libgcc from LDFLAGS in GDB build, GDB works fi= ne. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21229-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 07 13:56:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 115369 invoked by alias); 7 Apr 2017 13:56:44 -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 115337 invoked by uid 48); 7 Apr 2017 13:56:44 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Fri, 07 Apr 2017 13:56: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00030.txt.bz2 Content-length: 815 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 --- Comment #8 from Yao Qi --- It turns out a libgcc issue. If C++ program is linked with -static-libgcc = and throws exception, it won't be caught. $ cat test.cpp=20 int main() { try { throw 0; } catch (...) { } return 0; } $ /opt/local/bin/g++ -static-libgcc test.cpp -o test.exe $ ./test.exe=20 Abort trap: 6 $ /opt/local/bin/g++ --version g++ (MacPorts gcc5 5.4.0_0) 5.4.0 Copyright (C) 2015 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21230-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 07 14:06:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 2938 invoked by alias); 7 Apr 2017 14:06:24 -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 2890 invoked by uid 48); 7 Apr 2017 14:06:23 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Fri, 07 Apr 2017 14:06: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: cc cf_gcchost 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: 2017-q2/txt/msg00031.txt.bz2 Content-length: 622 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gingold at adacore dot com Host| |x86_64-apple-darwin10 --- Comment #9 from Yao Qi --- It is not a GDB bug, but GDB on darwin host is broken. Tristan, do you have some ideas on this issue? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21231-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 07 16:08:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 113782 invoked by alias); 7 Apr 2017 16:08:16 -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 113734 invoked by uid 48); 7 Apr 2017 16:08:15 -0000 From: "ibuclaw at gdcproject dot org" To: gdb-prs@sourceware.org Subject: [Bug d/20806] Error during debug startup Date: Fri, 07 Apr 2017 16:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: d X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ibuclaw at gdcproject dot org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00032.txt.bz2 Content-length: 585 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20806 Iain Buclaw changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ibuclaw at gdcproject dot = org --- Comment #2 from Iain Buclaw --- I would avoid using -gc, as that tells gdb the program is C code, and so not managed by the D language support. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21232-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 07 16:16:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 11006 invoked by alias); 7 Apr 2017 16:16:11 -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 10962 invoked by uid 48); 7 Apr 2017 16:16:10 -0000 From: "ibuclaw at gdcproject dot org" To: gdb-prs@sourceware.org Subject: [Bug d/21354] can't index a dynamic array Date: Fri, 07 Apr 2017 16:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: d X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: ibuclaw at gdcproject dot org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00033.txt.bz2 Content-length: 404 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21354 Iain Buclaw changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ibuclaw at gdcproject dot = org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21233-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 07 16:16:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 11264 invoked by alias); 7 Apr 2017 16:16:13 -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 11230 invoked by uid 48); 7 Apr 2017 16:16:13 -0000 From: "ibuclaw at gdcproject dot org" To: gdb-prs@sourceware.org Subject: [Bug d/21355] can't slice a dynamic array Date: Fri, 07 Apr 2017 16:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: d X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: ibuclaw at gdcproject dot org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00034.txt.bz2 Content-length: 404 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21355 Iain Buclaw changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ibuclaw at gdcproject dot = org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21234-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Apr 09 00:20:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3690 invoked by alias); 9 Apr 2017 00:20:42 -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 3654 invoked by uid 48); 9 Apr 2017 00:20:41 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/20367] add further Rust demangling Date: Sun, 09 Apr 2017 00:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q2/txt/msg00035.txt.bz2 Content-length: 1015 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20367 --- Comment #5 from Tom Tromey --- I have a patch for this but I haven't been able to find a situation where it helps. It doesn't help minimal symbols, because gdb thinks those are always C++ symbols. There was a gdb bug on file for this, for Java, for a long time; but it's difficult to argue that it is really a gdb bug as any fix would seem to involve using debug symbols to interpret minimal symbol names, which seems like an inversion at least. (IMO Rust should not use a mangling that is close to C++, but that's how it is for now.) On the other hand, for DWARF symbols, the ones that are likely to be affected are all emitted in a funny way, with names like "{{impl}}" embedded. E.g.: <54> DW_AT_linkage_name: (indirect string, offset: 0x84): _ZN2bc8{{impl}}4what15__STATIC_FMTSTRE There's a Rust compiler bug on file for this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21235-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Apr 09 00:22:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 5840 invoked by alias); 9 Apr 2017 00:22:21 -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 5794 invoked by uid 48); 9 Apr 2017 00:22:20 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/20367] add further Rust demangling Date: Sun, 09 Apr 2017 00:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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: 2017-q2/txt/msg00036.txt.bz2 Content-length: 344 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20367 --- Comment #6 from Tom Tromey --- Created attachment 9978 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9978&action=3Dedit the patch the patch; needs a test case --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21236-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Apr 09 09:33:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 85748 invoked by alias); 9 Apr 2017 09:33:47 -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 85671 invoked by uid 48); 9 Apr 2017 09:33:46 -0000 From: "mark at klomp dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/20367] add further Rust demangling Date: Sun, 09 Apr 2017 09:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at klomp dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q2/txt/msg00037.txt.bz2 Content-length: 1532 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20367 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mark at klomp dot org --- Comment #7 from Mark Wielaard --- I think in rust_sniff_from_mangled_name () you need to use the new rust_is_mangled () or rust_demangle () from libiberty. See the documentatio= n in demangle.h: /* Returns non-zero iff MANGLED is a rust mangled symbol. MANGLED must already have been demangled through cplus_demangle_v3. If this function returns non-zero then MANGLED can be demangled (in-place) using RUST_DEMANGLE_SYM. */ extern int rust_is_mangled (const char *mangled); /* Demangles SYM (in-place) if RUST_IS_MANGLED returned non-zero for SYM. If RUST_IS_MANGLED returned zero for SYM then RUST_DEMANGLE_SYM might replace characters that cannot be demangled with '?' and might truncate SYM. After calling RUST_DEMANGLE_SYM SYM might be shorter, but never larger. */ extern void rust_demangle_sym (char *sym); /* Demangles MANGLED if it was GNU_V3 and then RUST mangled, otherwise returns NULL. Uses CPLUS_DEMANGLE_V3, RUST_IS_MANGLED and RUST_DEMANGLE_SYM. Returns a new string that is owned by the caller. */ extern char * rust_demangle (const char *mangled, int options); --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21237-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Apr 09 13:35:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63850 invoked by alias); 9 Apr 2017 13:35:40 -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 63813 invoked by uid 48); 9 Apr 2017 13:35:39 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/20367] add further Rust demangling Date: Sun, 09 Apr 2017 13:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q2/txt/msg00038.txt.bz2 Content-length: 278 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20367 --- Comment #8 from Tom Tromey --- Wow, thanks Mark. I'm glad you pointed that out, I had totally missed it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21238-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Apr 09 18:55:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 57077 invoked by alias); 9 Apr 2017 18:55:02 -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 55883 invoked by uid 48); 9 Apr 2017 18:55:01 -0000 From: "HBBroeker@T-Online.de" To: gdb-prs@sourceware.org Subject: [Bug win32/21365] New: windows-nat.c compilation fails: no constructor for ptid_t Date: Sun, 09 Apr 2017 18:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: win32 X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: HBBroeker@T-Online.de X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00039.txt.bz2 Content-length: 1222 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21365 Bug ID: 21365 Summary: windows-nat.c compilation fails: no constructor for ptid_t Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32 Assignee: unassigned at sourceware dot org Reporter: HBBroeker@T-Online.de Target Milestone: --- This commit: commit 436252de3e9de546001c4312d0863ce7e10aa200 Author: Simon Marchi Date: Thu Apr 6 23:29:53 2017 -0400 Class-ify ptid_t breaks the compilation on Cygwin64 / GCC 5.4.0: ../../binutils-gdb/gdb/windows-nat.c: In Funktion =C2=BBvoid windows_detach(target_ops*, const char*, int)=C2=AB: ../../binutils-gdb/gdb/windows-nat.c:1915:20: Fehler: Umwandlung in =C2=BBp= tid_t=C2=AB von Initialisierungsliste w=C3=BCrde expliziten Konstruktor =C2=BBconstexpr ptid_t::ptid_t(int, long int, long int)=C2=AB verwenden ptid_t ptid =3D {-1}; [Sorry about the messages in German: they're saying that {-1} is not a valid initializer for ptid_t] --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21239-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Apr 09 19:53:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 18922 invoked by alias); 9 Apr 2017 19:53:43 -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 18860 invoked by uid 48); 9 Apr 2017 19:53:42 -0000 From: "dwjbosman at yahoo dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21366] New: Python script causes GDB core dump Date: Sun, 09 Apr 2017 19:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dwjbosman at yahoo dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00040.txt.bz2 Content-length: 2174 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21366 Bug ID: 21366 Summary: Python script causes GDB core dump Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: dwjbosman at yahoo dot com Target Milestone: --- When I run the following script in GDB: 
import sys
import os
import zmq
c =3D zmq.Context.instance()
s =3D c.socket(zmq.ROUTER)
print(s)
s.bind_to_random_port("tcp://127.0.0.1")
print("works")
sys.exit(0)
with arm-none-eabi-gdb --command test.py GDB crashes with a core dump: I cloned the Git repository: commit 5e8bf44f4c94d430ac21257a1a953cfccd2ce79b crashes I have done a binary search over the git repository:=20 commit 5809899dad253e2fefcb6f7ae57a6f43cfa4e3c5 and onwards crashes commit 3e25a500a1ba05587389737e7c617e5ae6dd2bcf and before work gdb was configured as follows: This GDB was configured as follows: configure --host=3Dx86_64-pc-linux-gnu --target=3Darm-none-eabi --with-auto-load-dir=3D$debugdir:$datadir/auto-load --with-auto-load-safe-path=3D$debugdir:$datadir/auto-load --with-expat --with-gdb-datadir=3D/usr/special/tmp/share/gdb (relocatable) --with-jit-reader-dir=3D/usr/special/tmp/lib/gdb (relocatable) --without-libunwind-ia64 --with-lzma --with-python=3D/opt/conda/envs/gdb_ipykernel --without-guile --with-separate-debug-dir=3D/usr/special/tmp/lib/debug (reloca= table) --without-babeltrace My build command: cd binutils-gdb && export LDFLAGS=3D-L/opt/conda/envs/gdb_ipykernel/lib/ && ./configure --target=3Darm-none-eabi --prefix=3D/usr/special/tmp --with-python=3D/opt/conda/envs/gdb_ipykernel/bin/ python && make && make tooldir=3D/usr/special/tmp install python version is python 3.5.2 ZMQ: python -c 'import zmq; print(zmq.zmq_version(), zmq.__version__)' 4.1.6 16.0.2 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21240-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Apr 09 19:55:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 21731 invoked by alias); 9 Apr 2017 19:55:48 -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 21699 invoked by uid 48); 9 Apr 2017 19:55:47 -0000 From: "dwjbosman at yahoo dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21366] Python script causes GDB core dump Date: Sun, 09 Apr 2017 19:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dwjbosman at yahoo dot com X-Bugzilla-Status: UNCONFIRMED 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: cf_gcctarget cc cf_gcchost 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: 2017-q2/txt/msg00041.txt.bz2 Content-length: 529 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21366 Dinne Bosman changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |arm-none-eabi CC| |dwjbosman at yahoo dot com Host| |x86_64-pc-linux-gnu --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21241-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Apr 10 11:10:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63563 invoked by alias); 10 Apr 2017 11:10:33 -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 63527 invoked by uid 48); 10 Apr 2017 11:10:31 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21226] DW_OP_stack_value pieces yield wrong data on big-endian targets Date: Mon, 10 Apr 2017 11:10: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: arnez at linux dot vnet.ibm.com 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: 2017-q2/txt/msg00042.txt.bz2 Content-length: 358 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21226 --- Comment #3 from Andreas Arnez --- I've posted an updated version of the fix among some other DWARF piece hand= ling fixes: https://sourceware.org/ml/gdb-patches/2017-04/msg00180.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21242-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Apr 10 13:33:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63390 invoked by alias); 10 Apr 2017 13:32:59 -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 63358 invoked by uid 48); 10 Apr 2017 13:32:59 -0000 From: "schwab@linux-m68k.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21364] Dead code due to an unreachable condition in osdata.c Date: Mon, 10 Apr 2017 13:32: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: schwab@linux-m68k.org X-Bugzilla-Status: UNCONFIRMED 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: bug_status component version resolution product 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: 2017-q2/txt/msg00043.txt.bz2 Content-length: 671 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21364 Andreas Schwab changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Component|binutils |gdb Version|2.29 (HEAD) |HEAD Resolution|WONTFIX |--- Product|binutils |gdb --- Comment #2 from Andreas Schwab --- Moving to gdb. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21243-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Apr 10 13:41:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109294 invoked by alias); 10 Apr 2017 13:41:30 -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 109238 invoked by uid 55); 10 Apr 2017 13:41:28 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug threads/19942] AddressSanitizer: heap-use-after-free in thread_apply_all_command Date: Mon, 10 Apr 2017 13:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q2/txt/msg00044.txt.bz2 Content-length: 5227 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19942 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Yao Qi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D803bdfe43083= 475c7df3db38dc96f4e20d05457d commit 803bdfe43083475c7df3db38dc96f4e20d05457d Author: Yao Qi Date: Mon Apr 10 14:39:41 2017 +0100 Don't delete thread_info if refcount isn't zero I build GDB with asan, and run test case hook-stop.exp, and threadapply.exp, I got the following asan error, =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D^M ^[[1m^[[31m=3D=3D2291=3D=3DERROR: AddressSanitizer: heap-use-after-free= on address 0x6160000999c4 at pc 0x000000826022 bp 0x7ffd28a8ff70 sp 0x7ffd28a8ff60^M ^[[1m^[[0m^[[1m^[[34mREAD of size 4 at 0x6160000999c4 thread T0^[[1m^[[= 0m^M #0 0x826021 in release_stop_context_cleanup ../../binutils-gdb/gdb/infrun.c:8203^M #1 0x72798a in do_my_cleanups ../../binutils-gdb/gdb/common/cleanups.c:154^M #2 0x727a32 in do_cleanups(cleanup*) ../../binutils-gdb/gdb/common/cleanups.c:176^M #3 0x826895 in normal_stop() ../../binutils-gdb/gdb/infrun.c:8381^M #4 0x815208 in fetch_inferior_event(void*) ../../binutils-gdb/gdb/infrun.c:4011^M #5 0x868aca in inferior_event_handler(inferior_event_type, void*) ../../binutils-gdb/gdb/inf-loop.c:44^M .... ^[[1m^[[32m0x6160000999c4 is located 68 bytes inside of 568-byte region [0x616000099980,0x616000099bb8)^M ^[[1m^[[0m^[[1m^[[35mfreed by thread T0 here:^[[1m^[[0m^M #0 0x7fb0bc1312ca in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x982ca)^M #1 0xb8c62f in xfree(void*) ../../binutils-gdb/gdb/common/common-utils.c:100^M #2 0x83df67 in free_thread ../../binutils-gdb/gdb/thread.c:207^M #3 0x83dfd2 in init_thread_list() ../../binutils-gdb/gdb/thread.c:2= 23^M #4 0x805494 in kill_command ../../binutils-gdb/gdb/infcmd.c:2595^M .... Detaching from program: /home/yao.qi/SourceCode/gnu/build-with-asan/gdb/testsuite/outputs/gdb.threa= ds/threadapply/threadapply, process 2399^M =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D^M ^[[1m^[[31m=3D=3D2387=3D=3DERROR: AddressSanitizer: heap-use-after-free= on address 0x6160000a98c0 at pc 0x00000083fd28 bp 0x7ffd401c3110 sp 0x7ffd401c3100^M ^[[1m^[[0m^[[1m^[[34mREAD of size 4 at 0x6160000a98c0 thread T0^[[1m^[[= 0m^M #0 0x83fd27 in thread_alive ../../binutils-gdb/gdb/thread.c:741^M #1 0x844277 in thread_apply_all_command ../../binutils-gdb/gdb/thread.c:1804^M .... ^M ^[[1m^[[32m0x6160000a98c0 is located 64 bytes inside of 568-byte region [0x6160000a9880,0x6160000a9ab8)^M ^[[1m^[[0m^[[1m^[[35mfreed by thread T0 here:^[[1m^[[0m^M #0 0x7f59a7e322ca in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x982ca)^M #1 0xb8c62f in xfree(void*) ../../binutils-gdb/gdb/common/common-utils.c:100^M #2 0x83df67 in free_thread ../../binutils-gdb/gdb/thread.c:207^M #3 0x83dfd2 in init_thread_list() ../../binutils-gdb/gdb/thread.c:2= 23^M This patch fixes the issue by deleting thread_info object if it is deletable, otherwise, mark it as exited (by set_thread_exited). Function set_thread_exited is shared from delete_thread_1. This patch also moves field "refcount" to private and methods incref and decref. Additionally, we stop using "ptid_t" in "struct current_thread_cleanup" to reference threads, instead we use "thread_info" directly. Due to this change, we don't need restore_current_thread_ptid_changed anymore. gdb: 2017-04-10 Yao Qi PR gdb/19942 * gdbthread.h (thread_info::deletable): New method. (thread_info::incref): New method. (thread_info::decref): New method. (thread_info::refcount): Move it to private. * infrun.c (save_stop_context): Call inc_refcount. (release_stop_context_cleanup): Likewise. * thread.c (set_thread_exited): New function. (init_thread_list): Delete "tp" only it is deletable, otherwise call set_thread_exited. (delete_thread_1): Call set_thread_exited. (current_thread_cleanup) : Remove. : New field. (restore_current_thread_ptid_changed): Removed. (do_restore_current_thread_cleanup): Adjust. (restore_current_thread_cleanup_dtor): Don't call find_thread_ptid. (set_thread_refcount): Use dec_refcount. (make_cleanup_restore_current_thread): Adjust. (thread_apply_all_command): Call inc_refcount. (_initialize_thread): Don't call observer_attach_thread_ptid_changed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21244-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Apr 10 14:06:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 104244 invoked by alias); 10 Apr 2017 14:06:29 -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 103278 invoked by uid 48); 10 Apr 2017 14:06:28 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug threads/19942] AddressSanitizer: heap-use-after-free in thread_apply_all_command Date: Mon, 10 Apr 2017 14:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution assigned_to target_milestone 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: 2017-q2/txt/msg00045.txt.bz2 Content-length: 628 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19942 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Assignee|unassigned at sourceware dot org |qiyao at gcc dot gn= u.org Target Milestone|--- |8.0 --- Comment #2 from Yao Qi --- Close. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21245-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Apr 10 16:46:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 56391 invoked by alias); 10 Apr 2017 16:46:40 -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 55936 invoked by uid 55); 10 Apr 2017 16:46:39 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21364] Dead code due to an unreachable condition in osdata.c Date: Mon, 10 Apr 2017 16:46: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00046.txt.bz2 Content-length: 1136 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21364 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Da5bef50fdbfa= dbc6b8911b458580ee91cbfcdafd commit a5bef50fdbfadbc6b8911b458580ee91cbfcdafd Author: Sergio Durigan Junior Date: Mon Apr 10 12:43:44 2017 -0400 Fix PR gdb/21364: Dead code due to an unreachable condition in osdata.c Pedro's recent commits enabling -Wwrite-strings has changed a bit the logic of info_osdata. Now, 'type' is always non-NULL, so we have to check if it's an empty string instead of NULL. One of the checks was fixed, but there is another that was left behind. This commit fixes it. gdb/ChangeLog: 2017-04-10 Sergio Durigan Junior PR gdb/21364 * osdata.c (info_osdata): Check if 'type' is an empty string instead of NULL. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21246-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Apr 10 16:47:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79705 invoked by alias); 10 Apr 2017 16:47:25 -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 79093 invoked by uid 48); 10 Apr 2017 16:47:25 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21364] Dead code due to an unreachable condition in osdata.c Date: Mon, 10 Apr 2017 16:47: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat 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 cc resolution 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: 2017-q2/txt/msg00047.txt.bz2 Content-length: 610 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21364 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |sergiodj at redhat dot com Resolution|--- |FIXED --- Comment #4 from Sergio Durigan Junior --- Fixed, thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21247-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Apr 10 20:57:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 67736 invoked by alias); 10 Apr 2017 20:57:38 -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 67702 invoked by uid 48); 10 Apr 2017 20:57:37 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21366] Python script causes GDB core dump Date: Mon, 10 Apr 2017 20:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: WAITING 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: bug_status cf_reconfirmed_on cc everconfirmed 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: 2017-q2/txt/msg00048.txt.bz2 Content-length: 860 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21366 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2017-04-10 CC| |sergiodj at redhat dot com Ever confirmed|0 |1 --- Comment #1 from Sergio Durigan Junior --- Thanks for the bug report. Could you please recompile GDB using '-O0 -g3' as CFLAGS/CXXFLAGS, and then= let us know more information about the core dump being generated? A backtrace would be really helpful. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21248-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Apr 10 21:24:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41473 invoked by alias); 10 Apr 2017 21:24:43 -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 41224 invoked by uid 48); 10 Apr 2017 21:24:37 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug win32/21365] windows-nat.c compilation fails: no constructor for ptid_t Date: Mon, 10 Apr 2017 21:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: win32 X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: WAITING 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: bug_status cf_reconfirmed_on cc everconfirmed 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: 2017-q2/txt/msg00049.txt.bz2 Content-length: 855 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21365 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2017-04-10 CC| |sergiodj at redhat dot com Ever confirmed|0 |1 --- Comment #1 from Sergio Durigan Junior --- I can't reproduce this bug when compiling with a MingW compiler. Also, you= 're using a somewhat older compiler; could you try updating your GCC to a newer version? My guess is that this is the problem. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21249-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Apr 10 22:01:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 34272 invoked by alias); 10 Apr 2017 22:01:13 -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 34246 invoked by uid 48); 10 Apr 2017 22:01:12 -0000 From: "HBBroeker@T-Online.de" To: gdb-prs@sourceware.org Subject: [Bug win32/21365] windows-nat.c compilation fails: no constructor for ptid_t Date: Mon, 10 Apr 2017 22:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: win32 X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: HBBroeker@T-Online.de X-Bugzilla-Status: WAITING 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: 2017-q2/txt/msg00050.txt.bz2 Content-length: 588 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21365 --- Comment #2 from HBBroeker@T-Online.de --- (In reply to Sergio Durigan Junior from comment #1) > I can't reproduce this bug when compiling with a MingW compiler. Also, > you're using a somewhat older compiler; could you try updating your GCC t= o a > newer version? My guess is that this is the problem. Well, looks like someone else could reproduce it on MingW32. Simon Marchi addressed this by commit 8473b4472dce9ce87aaad35ff8e975e1487f914e --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21250-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 11 00:35:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 51432 invoked by alias); 11 Apr 2017 00:35:20 -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 51398 invoked by uid 48); 11 Apr 2017 00:35:19 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug win32/21365] windows-nat.c compilation fails: no constructor for ptid_t Date: Tue, 11 Apr 2017 00:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: win32 X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q2/txt/msg00051.txt.bz2 Content-length: 640 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21365 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |FIXED --- Comment #3 from Sergio Durigan Junior --- Oh, so that's why I wasn't able to reproduce: I was already using the latest GDB. Anyway, I'm closing this report then. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21251-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 11 09:58:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122638 invoked by alias); 11 Apr 2017 09:58:00 -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 122572 invoked by uid 48); 11 Apr 2017 09:57:59 -0000 From: "dwjbosman at yahoo dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21366] Python script causes GDB core dump Date: Tue, 11 Apr 2017 09:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dwjbosman at yahoo dot com X-Bugzilla-Status: WAITING 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: 2017-q2/txt/msg00052.txt.bz2 Content-length: 6794 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21366 --- Comment #2 from Dinne Bosman --- Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/special/tmp/bin/arm-none-eabi-gdb --command test_error.py'. (test_error.py is the following program: import sys import os import zmq c =3D zmq.Context.instance() s =3D c.socket(zmq.ROUTER) print(s) s.bind_to_random_port("tcp://127.0.0.1") print("works") sys.exit(0) ) Program terminated with signal SIGABRT, Aborted. The backtrace of commit 5809899dad253e2fefcb6f7ae57a6f43cfa4e3c5: #0 0x00007f3d64eeb067 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f3d64eec448 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007f3d6349ef78 in _Unwind_SetGR (context=3D, index=3D, val=3D) at /gcc-build/libgcc/unwind-dw2.c:271 #3 0x00007f3d63734c62 in __gxx_personality_v0 () from /opt/conda/envs/gdb_ipykernel/lib/libstdc++.so.6 #4 0x00000000008bd653 in _Unwind_RaiseException_Phase2 () #5 0x00000000008bde97 in _Unwind_Resume () #6 0x0000000000892b0a in std::ostreambuf_iterator > std::num_put > >::_M_insert_int(std::ostreambuf_iterator >, std::ios_base&, char, unsigned long) const () #7 0x0000000000892b1d in std::num_put > >::do_put(std::ostreambuf_iterator >, std::ios_base&, char, unsigned long) const () #8 0x00007f3d637b18ea in std::ostream& std::ostream::_M_insert(unsigned long) () from /opt/conda/envs/gdb_ipykernel/lib/libstdc++.so= .6 #9 0x00007f3d63aab1e9 in operator<< (__n=3D0, this=3D) at /usr/include/c++/4.9/ostream:185 #10 zmq::tcp_address_t::to_string (this=3Dthis@entry=3D0x16b5f60, addr_=3D.= ..) at src/tcp_address.cpp:523 #11 0x00007f3d63aae04d in zmq::tcp_listener_t::set_address (this=3Dthis@entry=3D0x16b5c20, addr_=3D) at src/tcp_listene= r.cpp:222 #12 0x00007f3d63aa0680 in zmq::socket_base_t::bind (this=3D0x16b55b0, addr_=3Daddr_@entry=3D0x7f3d64ab13d0 "tcp://127.0.0.1:*") at src/socket_base.cpp:407 #13 0x00007f3d63ab34c9 in zmq_bind (s_=3D, addr_=3Daddr_@entry=3D0x7f3d64ab13d0 "tcp://127.0.0.1:*") at src/zmq.cpp:305 #14 0x00007f3d62c4e864 in __pyx_pf_3zmq_7backend_6cython_6socket_6Socket_12= bind (__pyx_v_addr=3D0x7f3d64ab13b0, __pyx_v_self=3D0x7f3d62c0ffa8) at zmq/backend/cython/socket.c:5433 #15 __pyx_pw_3zmq_7backend_6cython_6socket_6Socket_13bind (__pyx_v_self=3D0x7f3d62c0ffa8, __pyx_v_addr=3D) at zmq/backend/cython/socket.c:5294 #16 0x00007f3d6328d696 in __Pyx_CyFunction_CallMethod (kw=3D, arg=3D0x7f3d64d10c18, self=3D0x7f3d62c0ffa8, func=3D0x7f3d649ebb10) at zmq/backend/cython/error.c:1965 #17 __Pyx_CyFunction_CallAsMethod (func=3D0x7f3d649ebb10, args=3D, kw=3D) at zmq/backend/cython/error.c:2004 #18 0x00007f3d65a04236 in PyObject_Call (func=3D0x7f3d649ebb10, arg=3D, kw=3D) at Objects/abstract.c:2165 #19 0x00007f3d65ade314 in do_call (nk=3D, na=3D2, pp_stack=3D0x7ffcbc5fe2e8, func=3D0x7f3d649ebb10) at Python/ceval.c:4936 #20 call_function (oparg=3D, pp_stack=3D0x7ffcbc5fe2e8) at Python/ceval.c:4732 #21 PyEval_EvalFrameEx (f=3D, throwflag=3D) at Python/ceval.c:3236 #22 0x00007f3d65ae1b49 in _PyEval_EvalCodeWithName (_co=3D, globals=3D, locals=3D, args=3D, argcount=3D2, kws=3D0x7f3d64db6ba8, kwcount=3D0, defs=3D0x7f3d62c394e0, def= count=3D3, kwdefs=3D0x0, closure=3D0x0, name=3D0x7f3d64a5d348, qualname=3D0x7f3d62c29d= f0) at Python/ceval.c:4018 #23 0x00007f3d65ae0df5 in fast_function (nk=3D, na=3D2, n=3D= , pp_stack=3D0x7ffcbc5fe508, func=3D0x7f3d62c3c0d0) at Python/ceval.c:4= 813 #24 call_function (oparg=3D, pp_stack=3D0x7ffcbc5fe508) at Python/ceval.c:4730 #25 PyEval_EvalFrameEx (f=3D, throwflag=3D) at Python/ceval.c:3236 #26 0x00007f3d65ae1b49 in _PyEval_EvalCodeWithName (_co=3D, globals=3D, locals=3D, args=3D, argcount=3D0, kws=3D0x0, kwcount=3D0, defs=3D0x0, defcount=3D0, kwdefs=3D0x= 0, closure=3D0x0, name=3D0x0, qualname=3D0x0) at Python/ceval.c:4018 #27 0x00007f3d65ae1cd8 in PyEval_EvalCodeEx (_co=3D, globals=3D, locals=3D, args=3D, argcount=3D, kws=3D, kwcount=3D0, defs=3D0x0,= defcount=3D0, kwdefs=3D0x0, closure=3D0x0) at Python/ceval.c:4039 #28 0x00007f3d65ae1d1b in PyEval_EvalCode (co=3D, globals=3D, locals=3D) at Python/ceval.c:777 #29 0x00007f3d65b07020 in run_mod (arena=3D0x15bcfb0, flags=3D0x0, locals=3D0x7f3d64e63248, globals=3D0x7f3d64e63248, filename=3D0x7f3d6499b3b= 0, mod=3D0x15f73f0) at Python/pythonrun.c:976 #30 PyRun_FileExFlags (fp=3D0x15bcd10, filename_str=3D, start=3D, globals=3D0x7f3d64e63248, locals=3D0x7f3d64e63248, closeit=3D, flags=3D0x0) at Python/pythonrun.c:929 #31 0x00007f3d65b08623 in PyRun_SimpleFileExFlags (fp=3D0x15bcd10, filename=3D, closeit=3D0, flags=3D0x0) at Python/pythonrun.c= :396 #32 0x000000000049192e in python_run_simple_file (file=3D0x15bcd10, filename=3D0x7ffcbc60090e "test_error.py") at ./python/python.c:379 #33 0x0000000000492b50 in gdbpy_source_script (extlang=3D0x8df9c0 , file=3D0x15bcd10, filename=3D0x7ffcbc60090e "test_error.py") at ./python/python.c:911 #34 0x000000000046d5f5 in source_script_from_stream (stream=3D0x15bcd10, file=3D0x7ffcbc60090e "test_error.py", file_to_open=3D0x7ffcbc60090e "test_error.py") at ./cli/cli-cmds.c:577 #35 0x000000000046d6e8 in source_script_with_search (file=3D0x7ffcbc60090e "test_error.py", from_tty=3D1, search_path=3D0) at ./cli/cli-cmds.c:630 #36 0x000000000046d71b in source_script (file=3D0x7ffcbc60090e "test_error.= py", from_tty=3D1) at ./cli/cli-cmds.c:640 #37 0x00000000005a9de5 in catch_command_errors_const (command=3D0x46d6f6 , arg=3D0x7ffcbc60090e "test_error.py", from_tty=3D1) at main.c:402 #38 0x00000000005ab142 in captured_main (data=3D0x7ffcbc5feaa0) at main.c:1= 124 #39 0x00000000005ab206 in gdb_main (args=3D0x7ffcbc5feaa0) at main.c:1161 #40 0x000000000040d43d in main (argc=3D3, argv=3D0x7ffcbc5feba8) at gdb.c:32 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21252-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 11 10:03:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 5679 invoked by alias); 11 Apr 2017 10:03:59 -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 4482 invoked by uid 48); 11 Apr 2017 10:03:59 -0000 From: "dwjbosman at yahoo dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21366] Python script causes GDB core dump Date: Tue, 11 Apr 2017 10:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dwjbosman at yahoo dot com X-Bugzilla-Status: WAITING 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: 2017-q2/txt/msg00053.txt.bz2 Content-length: 2346 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21366 --- Comment #3 from Dinne Bosman --- The diff between the working and next non working commit: git diff 3e25a500a1ba05587389737e7c617e5ae6dd2bcf..5809899dad253e2fefcb6f7ae57a6f43c= fa4e3c5 diff --git a/gdb/ChangeLog b/gdb/ChangeLog index fe3ea42..8c8b18a 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,5 +1,10 @@ 2016-09-23 Tom Tromey + * break-catch-sig.c: Include . + (signal_catchpoint_print_one): Use std::string. + +2016-09-23 Tom Tromey + * utils.c (struct restore_ui_out_closure): Remove. * objfiles.h (terminate_minimal_symbol_table): Don't declare. diff --git a/gdb/break-catch-sig.c b/gdb/break-catch-sig.c index 06ee44c..296f900 100644 --- a/gdb/break-catch-sig.c +++ b/gdb/break-catch-sig.c @@ -28,7 +28,8 @@ #include "valprint.h" #include "cli/cli-utils.h" #include "completer.h" -#include "gdb_obstack.h" + +#include #define INTERNAL_SIGNAL(x) ((x) =3D=3D GDB_SIGNAL_TRAP || (x) =3D=3D GDB_S= IGNAL_INT) @@ -265,11 +266,7 @@ signal_catchpoint_print_one (struct breakpoint *b, { int i; gdb_signal_type iter; - struct obstack text; - struct cleanup *cleanup; - - obstack_init (&text); - cleanup =3D make_cleanup_obstack_free (&text); + std::string text; for (i =3D 0; VEC_iterate (gdb_signal_type, c->signals_to_be_caught, i, iter); @@ -278,12 +275,10 @@ signal_catchpoint_print_one (struct breakpoint *b, const char *name =3D signal_to_name_or_int (iter); if (i > 0) - obstack_grow (&text, " ", 1); - obstack_grow (&text, name, strlen (name)); + text +=3D " "; + text +=3D name; } - obstack_grow (&text, "", 1); - do_cleanups (cleanup);iout, "what", (const char *) obstack_base (&text));--More-- + ui_out_field_string (uiout, "what", text.c_str ()); } else ui_out_field_string (uiout, "what", The changes seem minor. So in the non working version I started undoing cha= nges to see if the modified GDB would work. At the end the change that made the difference is just the declaration of std::string text; --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21253-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 11 15:14:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 32186 invoked by alias); 11 Apr 2017 15:14:01 -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 31203 invoked by uid 48); 11 Apr 2017 15:14:00 -0000 From: "roman.mescheryakov at gmail dot com" To: gdb-prs@sourceware.org Subject: =?UTF-8?B?W0J1ZyBicmVha3BvaW50cy8yMTM3Ml0gTmV3OiDigJxDYW5ub3QgYWNjZXNz?= =?UTF-8?B?IG1lbW9yeSBhdCBhZGRyZXNz4oCdIGFmdGVyIGNhdGNoIHN5c2NhbGwgb24g?= =?UTF-8?B?UmFzcGJpYW4=?= Date: Tue, 11 Apr 2017 15:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: roman.mescheryakov at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q2/txt/msg00054.txt.bz2 Content-length: 5124 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21372 Bug ID: 21372 Summary: =E2=80=9CCannot access memory at address=E2=80=9D after= catch syscall on Raspbian Product: gdb Version: 7.12 Status: UNCONFIRMED Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: roman.mescheryakov at gmail dot com Target Milestone: --- Created attachment 9983 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9983&action=3Dedit gdb_slave_player-7.7.1.typescript I=E2=80=99m new to gdb and Linux, so please excuse me if my situation will = appear to be not a bug. I=E2=80=99m investigating a performance issue with my Python script on a Ra= spberry Pi 3. It runs official Raspbian operating system that is adaptation of Debian = for Raspberry Pi mini-PC. I need to set catchpoint on a certain system call (gettimeofday, also tried futex), so the need arises in using gdb and not t= he Python debugger. I installed python2.7-dbg package in order to have Python extensions for gd= b: sudo apt-get install python2.7-dbg After that I run my script under gdb and issue =E2=80=9Ccatch syscall getti= meofday=E2=80=9D, see gdb_slave_player-7.7.1.typescript file attached. After 1st breakpoint h= it and issuing the =E2=80=9Ccontinue=E2=80=9D command 2 times, the following e= rror message appears: Cannot access memory at address 0x76e3b964 If I examine the /proc//maps file, I see that this address is indeed n= ot a part of my Python=E2=80=99s process address space. After this error I see that my application is not running. If I issue =E2=80=9Ccontinue=E2=80=9D to gdb again, the following message is displayed: Cannot execute this command while the selected thread is running. And my script is still not running. If I run that Python script under gdb without issuing =E2=80=9Ccatch syscal= l=E2=80=9D, the program works well and gdb doesn=E2=80=99t output any errors. I suppose this =E2=80=9CCannot access memory at address 0x76e3b964=E2=80=9D= error is a bug. My expectation is that after =E2=80=9Ccatch syscall=E2=80=9D Python process ru= ns without errors and breakpoint is hit when corresponding system function is called. Additional information: GDB version: GNU gdb (Raspbian 7.7.1+dfsg-5+rpi1) 7.7.1 GDB configuration: This GDB was configured as follows: configure --host=3Darm-linux-gnueabihf --target=3Darm-linux-gnueabihf --with-auto-load-dir=3D$debugdir:$datadir/auto-load --with-auto-load-safe-path=3D$debugdir:$datadir/auto-load --with-expat --with-gdb-datadir=3D/usr/share/gdb (relocatable) --with-jit-reader-dir=3D/usr/lib/gdb (relocatable) --without-libunwind-ia64 --with-lzma --with-python=3D/usr (relocatable) --with-separate-debug-dir=3D/usr/lib/debug (relocatable) --with-system-gdbinit=3D/etc/gdb/gdbinit --with-zlib --without-babeltrace ("Relocatable" means the directory can be moved with the GDB installation tree, and GDB will still find it.) =E2=80=9CWhat compiler (and its version) was used to compile GDB=E2=80=9D -= I don=E2=80=99t know, I use GDB preinstalled in Raspbian. uname -a: Linux s21volnaya5 4.4.50-v7+ #970 SMP Mon Feb 20 19:18:29 GMT 2017 armv7l GNU/Linux After searching in Internet I found the "Raspbian GDB broken" (https://www.raspberrypi.org/forums/viewtopic.php?f=3D33&t=3D104827&p=3D114= 6299#p1146299) forum post with instructions on how to compile and build newer GDB version = on Raspbian. I tried these steps and succeeded with new GDB version compiling = and installation, but the problem remained the same. See gdb_slave_player-7.12.typescript file attached. GDB version: GNU gdb (GDB) 7.12 GDB configuration: This GDB was configured as follows: configure --host=3Darmv7l-unknown-linux-gnueabihf --target=3Darmv7l-unknown-linux-gnueabihf --with-auto-load-dir=3D$debugdir:$datadir/auto-load --with-auto-load-safe-path=3D$debugdir:$datadir/auto-load --with-expat --with-gdb-datadir=3D/usr/share/gdb (relocatable) --with-jit-reader-dir=3D/usr/lib/gdb (relocatable) --without-libunwind-ia64 --without-lzma --with-python=3D/usr (relocatable) --without-guile --with-separate-debug-dir=3D/usr/lib/debug (relocatable) --without-babeltrace ("Relocatable" means the directory can be moved with the GDB installation tree, and GDB will still find it.) =E2=80=9CWhat compiler (and its version) was used to compile GDB=E2=80=9D -= My GCC version is: gcc (Raspbian 4.9.2-10) 4.9.2 I tried reporting this problem to Raspbian developers, see https://github.com/raspberrypi/linux/issues/1956, but I was told the issue should be reported to GDB developers. So I report this issue here. Please h= elp! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21254-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 11 15:15:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 124837 invoked by alias); 11 Apr 2017 15:15:00 -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 124008 invoked by uid 48); 11 Apr 2017 15:15:00 -0000 From: "roman.mescheryakov at gmail dot com" To: gdb-prs@sourceware.org Subject: =?UTF-8?B?W0J1ZyBicmVha3BvaW50cy8yMTM3Ml0g4oCcQ2Fubm90IGFjY2VzcyBtZW1v?= =?UTF-8?B?cnkgYXQgYWRkcmVzc+KAnSBhZnRlciBjYXRjaCBzeXNjYWxsIG9uIFJhc3Bi?= =?UTF-8?B?aWFu?= Date: Tue, 11 Apr 2017 15:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: roman.mescheryakov at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00055.txt.bz2 Content-length: 341 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21372 --- Comment #1 from Roman M --- Created attachment 9984 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9984&action=3Dedit gdb_slave_player-7.12.typescript --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21255-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 12 09:09:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 21939 invoked by alias); 12 Apr 2017 09:09:10 -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 21891 invoked by uid 48); 12 Apr 2017 09:09:09 -0000 From: "roman.mescheryakov at gmail dot com" To: gdb-prs@sourceware.org Subject: =?UTF-8?B?W0J1ZyBicmVha3BvaW50cy8yMTM3Ml0g4oCcQ2Fubm90IGFjY2VzcyBtZW1v?= =?UTF-8?B?cnkgYXQgYWRkcmVzc+KAnSBhZnRlciBjYXRjaCBzeXNjYWxsIG9uIFJhc3Bi?= =?UTF-8?B?aWFu?= Date: Wed, 12 Apr 2017 09:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: roman.mescheryakov at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.isobsolete attachments.created 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: 2017-q2/txt/msg00056.txt.bz2 Content-length: 742 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21372 Roman M changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #9984|0 |1 is obsolete| | --- Comment #2 from Roman M --- Created attachment 9987 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9987&action=3Dedit gdb_slave_player-7.12.typescript (now the full one) Previously uploaded gdb_slave_player-7.12.typescript was incomplete, upload= ed a full one --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21256-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 12 13:10:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 59426 invoked by alias); 12 Apr 2017 13:10:01 -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 58960 invoked by uid 55); 12 Apr 2017 13:10:00 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug c++/21323] GDB thinks char16_t and char32_t are signed in C++ Date: Wed, 12 Apr 2017 13:10: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00057.txt.bz2 Content-length: 3287 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21323 --- Comment #7 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D53e710acd249= e1861029b19b7a3d8195e7f28929 commit 53e710acd249e1861029b19b7a3d8195e7f28929 Author: Pedro Alves Date: Wed Apr 12 14:00:49 2017 +0100 Fix PR c++/21323: GDB thinks char16_t and char32_t are signed in C++ While the C++ standard says that char16_t and char32_t are unsigned typ= es: Types char16_t and char32_t denote distinct types with the same size, signedness, and alignment as uint_least16_t and uint_least32_t, respectively, in , called the underlying types. ... gdb treats them as signed currently: (gdb) p (char16_t)-1 $1 =3D -1 u'\xffff' There are actually two places in gdb that hardcode these types: - gdbtypes.c:gdbtypes_post_init, when creating the built-in types, seemingly used by the "x /s" command (judging from commit 9a22f0d0). - dwarf2read.c, when reading base types with DW_ATE_UTF encoding (which is what is used for these types, when compiling for C++11 and up). Despite the comment, the type created does end up used. Both places need fixing. But since I couldn't tell why dwarf2read.c needs to create a new type, I've made it use the per-arch built-in types instead, so that the types are only created once per arch instead of once per objfile. That seems to work fine. While writting the test, I noticed that the C++ language parser isn't actually aware of these built-in types, so if you try to use them without a program that uses them, you get: (gdb) set language c++ (gdb) ptype char16_t No symbol table is loaded. Use the "file" command. (gdb) ptype u"hello" No type named char16_t. (gdb) p u"hello" No type named char16_t. That's fixed by simply adding a couple entries to C++'s built-in types array in c-lang.c. With that, we get the expected: (gdb) ptype char16_t type =3D char16_t (gdb) ptype u"hello" type =3D char16_t [6] (gdb) p u"hello" $1 =3D u"hello" gdb/ChangeLog: 2017-04-12 Pedro Alves PR c++/21323 * c-lang.c (cplus_primitive_types) : New enum values. (cplus_language_arch_info): Register cplus_primitive_type_char16_t and cplus_primitive_type_char32_t. * dwarf2read.c (read_base_type) : If bit size is 16 or 32, use the archtecture's built-in type for char16_t and char32_t, respectively. Otherwise, fallback to init_integer_type as before, but make the type unsigned, and issue a complaint. * gdbtypes.c (gdbtypes_post_init): Make char16_t and char32_t unsig= ned. gdb/testsuite/ChangeLog: 2017-04-12 Pedro Alves PR c++/21323 * gdb.cp/wide_char_types.c: New file. * gdb.cp/wide_char_types.exp: New file. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21257-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 12 13:10:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 61528 invoked by alias); 12 Apr 2017 13:10:05 -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 61304 invoked by uid 55); 12 Apr 2017 13:10:05 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug c++/21323] GDB thinks char16_t and char32_t are signed in C++ Date: Wed, 12 Apr 2017 13:10: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00058.txt.bz2 Content-length: 3606 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21323 --- Comment #8 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D53375380e934= 928af133bca69c1e1912c35e9c73 commit 53375380e934928af133bca69c1e1912c35e9c73 Author: Pedro Alves Date: Wed Apr 12 14:00:49 2017 +0100 Teach GDB that wchar_t is a built-in type in C++ mode GDB is currently not aware that wchar_t is a built-in type in C++ mode. This is usually not a problem because the debug info describes the type, so when you have a program loaded, you don't notice this. However, if you try expressions involving wchar_t before a program is loaded, gdb errors out: (gdb) p (wchar_t)-1 No symbol table is loaded. Use the "file" command. (gdb) p L"hello" No type named wchar_t. (gdb) ptype L"hello" No type named wchar_t. This commit teaches gdb about the type. After: (gdb) p (wchar_t)-1 $1 =3D -1 L'\xffffffff' (gdb) p L"hello" $2 =3D L"hello" (gdb) ptype L"hello" type =3D wchar_t [6] Unlike char16_t/char32_t, unfortunately, the underlying type of wchar_t is implementation dependent, both size and signness. So this requires adding a couple new gdbarch hooks. I grepped the GCC code base for WCHAR_TYPE and WCHAR_TYPE_SIZE, and it seems to me that the majority of the ABIs have a 4-byte signed wchar_t, so that's what I made the default for GDB too. And then I looked for which ports have a 16-bit and/or unsigned wchar_t, and made GDB follow suit. gdb/ChangeLog: 2017-04-12 Pedro Alves PR gdb/21323 * c-lang.c (cplus_primitive_types) : New enum value. (cplus_language_arch_info): Register cplus_primitive_type_wchar_t. * gdbtypes.h (struct builtin_type) : New field. * gdbtypes.c (gdbtypes_post_init): Create the "wchar_t" type. * gdbarch.sh (wchar_bit, wchar_signed): New per-arch values. * gdbarch.h, gdbarch.c: Regenerate. * aarch64-tdep.c (aarch64_gdbarch_init): Override gdbarch_wchar_bit and gdbarch_wchar_signed. * alpha-tdep.c (alpha_gdbarch_init): Likewise. * arm-tdep.c (arm_gdbarch_init): Likewise. * avr-tdep.c (avr_gdbarch_init): Likewise. * h8300-tdep.c (h8300_gdbarch_init): Likewise. * i386-nto-tdep.c (i386nto_init_abi): Likewise. * i386-tdep.c (i386_go32_init_abi): Likewise. * m32r-tdep.c (m32r_gdbarch_init): Likewise. * moxie-tdep.c (moxie_gdbarch_init): Likewise. * nds32-tdep.c (nds32_gdbarch_init): Likewise. * rs6000-aix-tdep.c (rs6000_aix_init_osabi): Likewise. * sh-tdep.c (sh_gdbarch_init): Likewise. * sparc-tdep.c (sparc32_gdbarch_init): Likewise. * sparc64-tdep.c (sparc64_init_abi): Likewise. * windows-tdep.c (windows_init_abi): Likewise. * xstormy16-tdep.c (xstormy16_gdbarch_init): Likewise. gdb/testsuite/ChangeLog: 2017-04-12 Pedro Alves PR gdb/21323 * gdb.cp/wide_char_types.c: Include . (wchar): New global. * gdb.cp/wide_char_types.exp (wide_char_types_program) (do_test_wide_char, wide_char_types_no_program, top level): Add wchar_t testing. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21258-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 12 13:12:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 70237 invoked by alias); 12 Apr 2017 13:12:02 -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 70180 invoked by uid 48); 12 Apr 2017 13:12:00 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21323] GDB thinks char16_t and char32_t are signed in C++ Date: Wed, 12 Apr 2017 13:12: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution assigned_to target_milestone 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: 2017-q2/txt/msg00059.txt.bz2 Content-length: 675 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21323 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Assignee|unassigned at sourceware dot org |palves at redhat do= t com Target Milestone|--- |8.0 --- Comment #9 from Pedro Alves --- Fixes pushed to master. They'll be in 8.0. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21259-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 12 14:04:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89403 invoked by alias); 12 Apr 2017 14:04:47 -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 88715 invoked by uid 48); 12 Apr 2017 14:04:46 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21078] gdb compiled with mingw32 crashes on Windows7 when entering any invalid command Date: Wed, 12 Apr 2017 14:04: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00060.txt.bz2 Content-length: 615 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21078 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brobecker at gnat dot com --- Comment #4 from Joel Brobecker --- I just built using the current master, using GCC 6.3.1, and it worked fine = for me: (top-gdb) help foobar Undefined command: "foobar". Try "help". --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21260-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 12 15:37:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 101592 invoked by alias); 12 Apr 2017 15:37:33 -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 101172 invoked by uid 48); 12 Apr 2017 15:37:33 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Wed, 12 Apr 2017 15:37: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00061.txt.bz2 Content-length: 758 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brobecker at gnat dot com --- Comment #10 from Joel Brobecker --- FTR: I tried on Yosemite and El Capitan, using GCC 6.3.1, and had no proble= ms with exception handling. For instance: (gdb) help error Undefined command: "error". Try "help". (gdb) tar ext :4242 :4242: Operation timed out. Looks like you just need to find or build a functional compiler? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21261-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 12 16:15:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79747 invoked by alias); 12 Apr 2017 16:15:55 -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 78019 invoked by uid 48); 12 Apr 2017 16:15:54 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Wed, 12 Apr 2017 16:15: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00062.txt.bz2 Content-length: 632 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 --- Comment #11 from Yao Qi --- (In reply to Joel Brobecker from comment #10) > FTR: I tried on Yosemite and El Capitan, using GCC 6.3.1, and had no > problems with exception handling. For instance: >=20 > (gdb) help error > Undefined command: "error". Try "help". > (gdb) tar ext :4242 > :4242: Operation timed out. >=20 > Looks like you just need to find or build a functional compiler? My Mac is 10.7 Lion. Is the GCC you get from MacPort, or built by yourself? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21262-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 12 16:24:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 2049 invoked by alias); 12 Apr 2017 16:24:44 -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 1992 invoked by uid 48); 12 Apr 2017 16:24:40 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Wed, 12 Apr 2017 16:24: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00063.txt.bz2 Content-length: 252 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 --- Comment #12 from Joel Brobecker --- It's a version of GCC that we build ourselves. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21263-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 12 16:29:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27749 invoked by alias); 12 Apr 2017 16:29:17 -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 26968 invoked by uid 48); 12 Apr 2017 16:29:16 -0000 From: "tcurdt at vafer dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21240] arm-none-eabi-gdb crashes on start Date: Wed, 12 Apr 2017 16:29: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tcurdt at vafer dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00064.txt.bz2 Content-length: 1443 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21240 --- Comment #13 from tcurdt at vafer dot org --- FTR: $ cat > test.cpp int main() { try { throw 0; } catch (...) { } return 0; } ^C $ g++-6 -static-libgcc test.cpp -o foo $ ./foo=20 Abort trap: 6 $ g++-6 -v Using built-in specs. COLLECT_GCC=3Dg++-6 COLLECT_LTO_WRAPPER=3D/usr/local/Cellar/gcc/6.3.0_1/libexec/gcc/x86_64-appl= e-darwin16.4.0/6.3.0/lto-wrapper Target: x86_64-apple-darwin16.4.0 Configured with: ../configure --build=3Dx86_64-apple-darwin16.4.0 --prefix=3D/usr/local/Cellar/gcc/6.3.0_1 --libdir=3D/usr/local/Cellar/gcc/6.3.0_1/lib/gcc/6 --enable-languages=3Dc,c++,objc,obj-c++,fortran --program-suffix=3D-6 --with-gmp=3D/usr/local/opt/gmp --with-mpfr=3D/usr/local/opt/mpfr --with-mpc=3D/usr/local/opt/libmpc --with-isl=3D/usr/local/opt/isl --with-system-zlib --enable-stage1-checking --enable-checking=3Drelease --enable-lto --with-build-config=3Dbootstrap-debug --disable-werror --with-pkgversion=3D'Homebrew GCC 6.3.0_1' --with-bugurl=3Dhttps://github.com/Homebrew/homebrew-core/issues --disable-= nls --enable-multilib --with-native-system-header-dir=3D/usr/include --with-sysroot=3D/Applications/Xcode.app/Contents/Developer/Platforms/MacOS= X.platform/Developer/SDKs/MacOSX10.12.sdk Thread model: posix gcc version 6.3.0 (Homebrew GCC 6.3.0_1)=20 on macOS 10.12.4 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21264-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 12 20:49:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 1294 invoked by alias); 12 Apr 2017 20:49:19 -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 1266 invoked by uid 48); 12 Apr 2017 20:49:18 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/21381] New: Invalid -var-info-path-expression result with anonymous union in std::string Date: Wed, 12 Apr 2017 20:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00065.txt.bz2 Content-length: 1441 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21381 Bug ID: 21381 Summary: Invalid -var-info-path-expression result with anonymous union in std::string Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: mi Assignee: unassigned at sourceware dot org Reporter: simon.marchi at ericsson dot com Target Milestone: --- This is rather specific, but it's probably possible to create a smaller test case. Test source: ---- 8< ---- #include int main () { std::string s; s =3D "foo"; return 0; } ---- >8 ---- compilation line: g++ test.cpp -g3 -O0 -o test gdb command line: gdb -i mi -nx test MI commands used: start -var-create - * s -var-list-children var1 -var-list-children var1.private -var-list-children var1.private.2_anonymous -var-list-children var1.private.2_anonymous.public -var-list-children var1.private.2_anonymous.public._M_local_buf So far everything is fine, it just creates all the variable object children= .=20 Now we try to use -var-info-path-expression on the last one: -var-info-path-expression var1.private.2_anonymous.public._M_local_buf ^done,path_expr=3D"(()._M_local_buf)" The returned expression is not valid. It should have been "((s)._M_local_buf)". --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21265-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 12 20:51:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 51686 invoked by alias); 12 Apr 2017 20:51:19 -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 51035 invoked by uid 48); 12 Apr 2017 20:51:19 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/21381] Invalid -var-info-path-expression result with anonymous union in std::string Date: Wed, 12 Apr 2017 20:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: 2017-q2/txt/msg00066.txt.bz2 Content-length: 284 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21381 --- Comment #1 from Simon Marchi --- Versions used: GNU gdb (GDB) 7.12.50.20170121-git gcc (GCC) 6.3.1 20170306 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21266-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 12 20:51:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 62287 invoked by alias); 12 Apr 2017 20:51:30 -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 61869 invoked by uid 48); 12 Apr 2017 20:51:29 -0000 From: "malaperle at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/21381] Invalid -var-info-path-expression result with anonymous union in std::string Date: Wed, 12 Apr 2017 20:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: malaperle at gmail dot com 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: cc 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: 2017-q2/txt/msg00067.txt.bz2 Content-length: 403 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21381 Marc-Andre Laperle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |malaperle at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21267-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Apr 13 11:30:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 123854 invoked by alias); 13 Apr 2017 11:30:51 -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 123809 invoked by uid 48); 13 Apr 2017 11:30:50 -0000 From: "erik.m.bray+sourceware at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21057] GDB build failure with flex 2.6.3 Date: Thu, 13 Apr 2017 11:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: erik.m.bray+sourceware at gmail dot com 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: cc 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: 2017-q2/txt/msg00068.txt.bz2 Content-length: 662 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21057 Erik Bray changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erik.m.bray+sourceware@gmai | |l.com --- Comment #4 from Erik Bray --- For what it's worth, one small merge conflict aside, this patch solved the issue for me as well, bison-specificity aside. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21268-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Apr 13 15:20:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 114555 invoked by alias); 13 Apr 2017 15:20:14 -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 114100 invoked by uid 55); 13 Apr 2017 15:20:10 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug threads/13217] thread apply all detach throws a SEGFAULT Date: Thu, 13 Apr 2017 15:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 7.7 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: 2017-q2/txt/msg00069.txt.bz2 Content-length: 992 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13217 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D5fd69d0ab2c4= 2d2be0781bf3a5d60e1d5b8d05dc commit 5fd69d0ab2c42d2be0781bf3a5d60e1d5b8d05dc Author: Pedro Alves Date: Thu Apr 13 16:15:34 2017 +0100 Improve coverage of the PR threads/13217 regression test - Make sure we end up with no thread selected after the detach. - Test both "thread apply all" and "thread apply $some_threads", for completeness. gdb/ChangeLog: 2017-04-13 Pedro Alves PR threads/13217 * gdb.threads/threadapply.exp (thr_apply_detach): New procedure. (top level): Call it twice, with different thread sets. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21269-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Apr 13 17:20:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 29468 invoked by alias); 13 Apr 2017 17:20:42 -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 29425 invoked by uid 48); 13 Apr 2017 17:20:41 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21057] GDB build failure with flex 2.6.3 Date: Thu, 13 Apr 2017 17:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: cc 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: 2017-q2/txt/msg00070.txt.bz2 Content-length: 993 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21057 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #5 from Pedro Alves --- I couldn't reproduce this with current flex master: $ flex --version flex 2.6.4 Looking at the git log, it sound like it was fixed with this: commit 078b46c69d063aef1715b11348a2871d6036f253 Author: Christos Zoulas AuthorDate: Sun Jan 22 18:34:30 2017 +0100 Commit: Will Estes CommitDate: Mon Jan 23 13:39:49 2017 -0500 Add more defines in the non-reentrant part. Fix the reentrant part; don't "#define yyfoo yyfoo" because it breaks code that does #ifndef yywrap .. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21270-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Apr 13 17:34:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27842 invoked by alias); 13 Apr 2017 17:34:20 -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 27796 invoked by uid 48); 13 Apr 2017 17:34:19 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21057] GDB build failure with flex 2.6.3 Date: Thu, 13 Apr 2017 17:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q2/txt/msg00071.txt.bz2 Content-length: 384 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21057 --- Comment #6 from Pedro Alves --- Confirmed, that commit fixes it. AFAICS, there's no official 2.6.4 yet, so looks like the simplest for now is to just avoid 2.6.3. (Maybe get distros= to backport that flex patch.) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21271-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Apr 13 17:36:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 30111 invoked by alias); 13 Apr 2017 17:36:35 -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 30049 invoked by uid 48); 13 Apr 2017 17:36:34 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21057] GDB build failure with flex 2.6.3 Date: Thu, 13 Apr 2017 17:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q2/txt/msg00072.txt.bz2 Content-length: 386 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21057 --- Comment #7 from Pedro Alves --- For GDB, switching to -p sounds like a viable option going forward. Also, = we probably need to switch to C++ mode, to avoid ODR violations around the parsers... Need volunteers. :-) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21272-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Apr 13 23:24:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 113669 invoked by alias); 13 Apr 2017 23:24:30 -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 113505 invoked by uid 48); 13 Apr 2017 23:24:22 -0000 From: "HBBroeker@T-Online.de" To: gdb-prs@sourceware.org Subject: [Bug build/21385] New: windows-nat.c compilation fails: no declaration for allargs Date: Thu, 13 Apr 2017 23:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: HBBroeker@T-Online.de X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00073.txt.bz2 Content-length: 1143 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21385 Bug ID: 21385 Summary: windows-nat.c compilation fails: no declaration for allargs Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: HBBroeker@T-Online.de Target Milestone: --- As of commit 7c5ded6a00c4817d56cdf04fbc1969bc33b2a930, windows-nat.c again = does not compile on Cygwin64 (current, GCC-5.4): ../../binutils-gdb/gdb/windows-nat.c: In function 'void windows_create_inferior(target_ops*, const char*, const string&, char**, in= t)': ../../binutils-gdb/gdb/windows-nat.c:2478:29: error: 'allargs' was not decl= ared in this scope len =3D mbstowcs (NULL, allargs, 0) + 1; ^ ../../binutils-gdb/gdb/windows-nat.c:2496:24: error: 'allargs' was not decl= ared in this scope + mbstowcs (NULL, allargs, 0) + 2; ^ --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21273-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 14 01:04:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78941 invoked by alias); 14 Apr 2017 01:04: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 78917 invoked by uid 55); 14 Apr 2017 01:04:23 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug build/21385] windows-nat.c compilation fails: no declaration for allargs Date: Fri, 14 Apr 2017 01:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00074.txt.bz2 Content-length: 1009 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21385 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D096c92ddb3a5= a959bc638cff3c4ffa0f48a737d7 commit 096c92ddb3a5a959bc638cff3c4ffa0f48a737d7 Author: Sergio Durigan Junior Date: Thu Apr 13 21:01:53 2017 -0400 Fix build breakage on Cygwin (PR gdb/21385) On gdb/windows-nat.c:windows_create_inferior, ALLARGS needs to be declared independently of the host that we're building for. This fixes a build breakage on Cygwin. 2017-04-13 Sergio Durigan Junior PR gdb/21385 * windows-nat.c (windows_create_inferior): Declare 'allargs' independently of the host, and fix build breakage on Cygwin. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21274-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 14 01:05:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 80655 invoked by alias); 14 Apr 2017 01:05:22 -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 80620 invoked by uid 48); 14 Apr 2017 01:05:22 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21385] windows-nat.c compilation fails: no declaration for allargs Date: Fri, 14 Apr 2017 01:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat 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 cc resolution 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: 2017-q2/txt/msg00075.txt.bz2 Content-length: 610 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21385 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |sergiodj at redhat dot com Resolution|--- |FIXED --- Comment #2 from Sergio Durigan Junior --- Fixed, thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21275-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 14 18:08:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 8051 invoked by alias); 14 Apr 2017 18:08:37 -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 8021 invoked by uid 48); 14 Apr 2017 18:08:36 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/21388] New: Sourcing a file that contains an "interpreter-exec mi" command screws up the CLI Date: Fri, 14 Apr 2017 18:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00076.txt.bz2 Content-length: 704 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21388 Bug ID: 21388 Summary: Sourcing a file that contains an "interpreter-exec mi" command screws up the CLI Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: cli Assignee: unassigned at sourceware dot org Reporter: simon.marchi at ericsson dot com Target Milestone: --- Put this in blah.gdb: interpreter-exec mi "show non-stop" Then do (gdb) source blah.gdb The CLI is screwed up, it's not possible to type. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21276-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 14 19:29:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 119224 invoked by alias); 14 Apr 2017 19:29:08 -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 119194 invoked by uid 48); 14 Apr 2017 19:29:07 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/21381] Invalid -var-info-path-expression result with anonymous union in std::string Date: Fri, 14 Apr 2017 19:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: attachments.created 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: 2017-q2/txt/msg00077.txt.bz2 Content-length: 325 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21381 --- Comment #2 from Simon Marchi --- Created attachment 9994 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9994&action=3Dedit proposed patch --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21277-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 14 19:43:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 6975 invoked by alias); 14 Apr 2017 19:43:39 -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 6947 invoked by uid 48); 14 Apr 2017 19:43:38 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/21381] Invalid -var-info-path-expression result with anonymous union in std::string Date: Fri, 14 Apr 2017 19:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: 2017-q2/txt/msg00078.txt.bz2 Content-length: 1705 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21381 --- Comment #3 from Simon Marchi --- I think I identified the problem. In c_is_path_expr_parent, we are doing t= his: field_name =3D TYPE_FIELD_NAME (parent_type, var->index); var->index is the index of the current varobj (a class field) in its parent= .=20 The problem is that the varobj index in its parent doesn't translate direct= ly to an index in the array of fields of the type of its parent, which is assu= med by the statement above. That's because while the fields array of the class type looks like this: [0] public field npos [1] private field _M_dataplus [2] private field _M_string_length [3] private field ... the varobj tree looks like: string public npos private _M_dataplus _M_string_length 2_anonymous (name given to the anonymous union by gdb) When calling c_is_path_expr_parent with var =3D 2_anonymous, var->index is 2 (it's the index in its varobj parent). This index is used to lookup the fi= eld type in the parent's type's field table, which erroneously ends up referrin= g to _M_string_length. It returns true instead of false, which ends up in an em= pty string being used as a path instead of searching higher in the varobj tree = for something that really is a path expression parent. So, like in cplus_describe_child, we have to iterate on the parent's type's field table to find the 3rd private field (as in the proposed patch). That will find the right field. In cplus_describe_child, we could probably assert that parent_expression is= not empty. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21278-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Apr 17 16:38:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31711 invoked by alias); 17 Apr 2017 16:38:51 -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 31653 invoked by uid 48); 17 Apr 2017 16:38:49 -0000 From: "malaperle at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/21381] Invalid -var-info-path-expression result with anonymous union in std::string Date: Mon, 17 Apr 2017 16:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: malaperle at gmail dot com 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: 2017-q2/txt/msg00079.txt.bz2 Content-length: 347 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21381 --- Comment #4 from Marc-Andre Laperle --- (In reply to Simon Marchi from comment #2) > Created attachment 9994 [details] > proposed patch I tested it and the patch seems to work! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21279-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Apr 17 17:56:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 61100 invoked by alias); 17 Apr 2017 17:56:43 -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 60397 invoked by uid 48); 17 Apr 2017 17:56:42 -0000 From: "robmaher3075 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug server/21392] New: gdbserver unable to interrupt execution of daemonized processes starting at 7.9 Date: Mon, 17 Apr 2017 17:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.9 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: robmaher3075 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q2/txt/msg00080.txt.bz2 Content-length: 2253 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21392 Bug ID: 21392 Summary: gdbserver unable to interrupt execution of daemonized processes starting at 7.9 Product: gdb Version: 7.9 Status: UNCONFIRMED Severity: normal Priority: P2 Component: server Assignee: unassigned at sourceware dot org Reporter: robmaher3075 at gmail dot com Target Milestone: --- Created attachment 9996 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D9996&action=3Dedit Vagrant Ubuntu 16.04 (ubuntu/xenial64) with gdb 7.11.1 can't halt process I've been having problems debugging daemonized processes on x86_64 when usi= ng a remote target with gdb -> gdbserver -> [daemon process]. The same setup/de= bug procedure works up to and including GDB 7.8.2. Once I jump to any more rec= ent version (tried 7.9, 7.9.1, 7.10.1, or 7.12.1) gdbserver successfully starts= up and it appears that gdb is initially able to attach to the process, however once the process is resumed I am no longer able to interrupt its execution = with CTRL-C. After a second CTRL-C gdb responds with "^C^CThe target is not responding to interrupt requests. Stop debugging it? (y or n)" and the debug session is no longer useable. While I've been testing this in our Yocto-based development environment I h= ave also been able to reproduce this issue when switching between Vagrant Ubuntu VMs for 14.04 (gdb version 7.7.1) and Ubuntu 16.04 (gdb version 7.11.1). Steps to reproduce as shown in attached log: 1) start-stop-daemon --start --background --exec /bin/sleep -- 300 2) sudo gdbserver --debug --attach 127.0.0.1:34115 `pidof sleep` 3) gdb 3.1) target remote 127.0.0.1:34115 3.2) c (continue) 3.3) CTRL-C (target fails to halt) 3.4) CTRL-C (target not responding message) Also I've noticed that some daemons don't seem to be affected by this issue= .=20 After looking at their source it seems that those daemons who fork() once, setsid(), and continue don't seem to be affected while those that fork(), setsid(), fork(), and continue will not interrupt as expected. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21280-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Apr 17 17:57:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107676 invoked by alias); 17 Apr 2017 17:57:16 -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 106809 invoked by uid 48); 17 Apr 2017 17:57:16 -0000 From: "robmaher3075 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug server/21392] gdbserver unable to interrupt execution of daemonized processes starting at 7.9 Date: Mon, 17 Apr 2017 17:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.9 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: robmaher3075 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00081.txt.bz2 Content-length: 401 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21392 robmaher changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robmaher3075 at gmail dot = com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21281-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 18 16:50:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 117853 invoked by alias); 18 Apr 2017 16:50:03 -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 117167 invoked by uid 55); 18 Apr 2017 16:50:02 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug threads/20743] can't usefully "continue" due to "ptrace: No such process" after gdb switches thread (gdb7.11.1 on FreeBSD 11) Date: Tue, 18 Apr 2017 16:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00082.txt.bz2 Content-length: 985 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20743 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by John Baldwin : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dd56060f08aa4= ed5786042a066f62aa8e474cc0fd commit d56060f08aa4ed5786042a066f62aa8e474cc0fd Author: John Baldwin Date: Tue Apr 18 09:44:32 2017 -0700 PR threads/20743: Don't attempt to suspend or resume exited threads. When resuming a native FreeBSD process, ignore exited threads when suspending/resuming individual threads prior to continuing the process. gdb/ChangeLog: PR threads/20743 * fbsd-nat.c (resume_one_thread_cb): Remove. (resume_all_threads_cb): Remove. (fbsd_resume): Use ALL_NON_EXITED_THREADS instead of iterate_over_threads. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21282-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 18 16:53:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 129522 invoked by alias); 18 Apr 2017 16:53:43 -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 129409 invoked by uid 55); 18 Apr 2017 16:53:42 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug threads/20743] can't usefully "continue" due to "ptrace: No such process" after gdb switches thread (gdb7.11.1 on FreeBSD 11) Date: Tue, 18 Apr 2017 16:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00083.txt.bz2 Content-length: 993 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20743 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The gdb-8.0-branch branch has been updated by John Baldwin : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D24b03ea86442= 4cf8482ba07fb074389aa759e592 commit 24b03ea864424cf8482ba07fb074389aa759e592 Author: John Baldwin Date: Tue Apr 18 09:44:32 2017 -0700 PR threads/20743: Don't attempt to suspend or resume exited threads. When resuming a native FreeBSD process, ignore exited threads when suspending/resuming individual threads prior to continuing the process. gdb/ChangeLog: PR threads/20743 * fbsd-nat.c (resume_one_thread_cb): Remove. (resume_all_threads_cb): Remove. (fbsd_resume): Use ALL_NON_EXITED_THREADS instead of iterate_over_threads. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21283-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 18 16:54:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 404 invoked by alias); 18 Apr 2017 16:54:27 -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 364 invoked by uid 48); 18 Apr 2017 16:54:26 -0000 From: "raajeshdasari at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug corefiles/21395] New: thread.c:1010 internal-error: int is_executing(ptid_t): Assertion `tp' failed. Date: Tue, 18 Apr 2017 16:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: raajeshdasari at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00084.txt.bz2 Content-length: 8581 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21395 Bug ID: 21395 Summary: thread.c:1010 internal-error: int is_executing(ptid_t): Assertion `tp' failed. Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: critical Priority: P2 Component: corefiles Assignee: unassigned at sourceware dot org Reporter: raajeshdasari at gmail dot com Target Milestone: --- When i tried to attach and detach a multi threaded application on mips64 ba= sed environment, I am noticing gdb crash. when trying to attach "Couldn't write debug register: No such process." err= os is seen and also after attaching the process, corrupt stack error is notice= d in 'bt' command output. (gdb) bt #0 0xe7a2046c in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) when trying to detach gdb crash is observed. gdb -p 13124 GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "mips64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". Attaching to process 13124 Couldn't write debug register: No such process. (gdb) quit A debugging session is active. Inferior 1 [process 13124] will be detached. Quit anyway? (y or n) y /root/distro/work/shared/gdb-7.12.1/gdb/thread.c:1010: internal-error: int is_executing(ptid_t): Assertion `tp' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y This is a bug, please report it. For instructions, see: . /root/distro/work/shared/gdb-7.12.1/gdb/thread.c:1010: internal-error: int is_executing(ptid_t): Assertion `tp' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) y Aborted (core dumped) [1]+ Stopped ./test file /usr/bin/gdb /usr/bin/gdb: ELF 64-bit MSB executable, MIPS, MIPS64 version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, not stripped here is the backtrace of the core file. GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "mips64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/gdb...done. [New LWP 13272] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `gdb -p 13124'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=3D) at ../sysdeps/unix/sysv/linux/raise.= c:58 58 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 __GI_raise (sig=3D) at ../sysdeps/unix/sysv/linux/raise.= c:58 #1 0x000000ffefdadb2c in __GI_abort () at abort.c:89 #2 0x0000000120301e68 in dump_core () at /root/distro/work/shared/gdb-7.12.1/gdb/utils.c:561 #3 0x0000000120304ee8 in internal_vproblem (problem=3Dproblem@entry=3D0x12= 07a3680 , file=3D, line=3D,=20 fmt=3D, ap=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/utils.c:772 #4 0x0000000120304fc0 in internal_verror (file=3D, line=3D, fmt=3D, ap=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/utils.c:798 #5 0x00000001203527c0 in internal_error (file=3D, line=3D, fmt=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/common/errors.c:55 #6 0x00000001201ebc50 in is_executing (ptid=3D...) at /root/distro/work/shared/gdb-7.12.1/gdb/thread.c:1010 #7 0x0000000120097010 in get_detach_signal (lp=3Dlp@entry=3D0x120894650) at /root/distro/work/shared/gdb-7.12.1/gdb/linux-nat.c:1334 #8 0x000000012009847c in detach_one_lwp (lp=3Dlp@entry=3D0x120894650, signo_p=3Dsigno_p@entry=3D0x0) at /root/distro/work/shared/gdb-7.12.1/gdb/linux-nat.c:1420 #9 0x0000000120098640 in detach_callback (lp=3Dlp@entry=3D0x120894650, data=3Ddata@entry=3D0x0) at /root/distro/work/shared/gdb-7.12.1/gdb/linux-nat.c:1489 #10 0x000000012009b590 in iterate_over_lwps (filter=3D..., callback=3Dcallback@entry=3D0x1200985d8 , data=3Ddata@entry=3D0x0) at /root/distro/work/shared/gdb-7.12.1/gdb/linux-nat.c:984 #11 0x000000012009bbfc in linux_nat_detach (ops=3D0x120801430, args=3D0x0, from_tty=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/linux-nat.c:1511 #12 0x00000001202fe138 in kill_or_detach (inf=3Dinf@entry=3D0x120884040, args=3Dargs@entry=3D0xffffe3ebb0) at /root/distro/work/shared/gdb-7.12.1/gdb/top.c:1540 #13 0x0000000120333134 in iterate_over_inferiors (callback=3D0x1202fe080 , data=3D0xffffe3ebb0) at /root/distro/work/shared/gdb-7.12.1/gdb/inferior.c:397 #14 0x00000001202ffda8 in quit_force (args=3D, from_tty=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/top.c:1655 #15 0x00000001200e61c0 in quit_command (args=3D0x0, from_tty=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/cli/cli-cmds.c:351 #16 0x00000001200e2ca4 in cmd_func (cmd=3D0x12087ade0, args=3D0x0, from_tty=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/cli/cli-decode.c:1913 #17 0x00000001202feb30 in execute_command (p=3D, from_tty=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/top.= c:674 #18 0x00000001201fe7d8 in command_line_handler (rl=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/event-top.c:822 #19 0x00000001201fd1f0 in gdb_rl_callback_handler (rl=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/event-top.c:213 #20 0x0000000120404478 in rl_callback_read_char () at /root/distro/work/shared/gdb-7.12.1/readline/callback.c:220 #21 0x00000001201fd0a8 in gdb_rl_callback_read_char_wrapper_noexcept () at /root/distro/work/shared/gdb-7.12.1/gdb/event-top.c:175 #22 0x00000001201fd160 in gdb_rl_callback_read_char_wrapper (client_data=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/event-top.c:192 #23 0x00000001201fdb00 in stdin_event_handler (error=3D, client_data=3D0x1207e60f0) at /root/distro/work/shared/gdb-7.12.1/gdb/event-top.c:568 #24 0x00000001201fbb04 in gdb_wait_for_event (block=3Dblock@entry=3D1) at /root/distro/work/shared/gdb-7.12.1/gdb/event-loop.c:859 #25 0x00000001201fc0b0 in gdb_do_one_event () at /root/distro/work/shared/gdb-7.12.1/gdb/event-loop.c:347 #26 0x00000001201fc204 in start_event_loop () at /root/distro/work/shared/gdb-7.12.1/gdb/event-loop.c:371 #27 0x00000001201f4048 in captured_command_loop (data=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/main.c:324 #28 0x00000001201ef47c in catch_errors (func=3D0x1201f3ff0 , func_args=3D, errstring=3D0x12056f900 "", mask=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/exceptions.c:236 #29 0x00000001201f57ec in captured_main (data=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/main.c:1149 #30 gdb_main (args=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/main.c:1159 #31 0x0000000120069a5c in main (argc=3D, argv=3D) at /root/distro/work/shared/gdb-7.12.1/gdb/gdb.c:32 (gdb) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21284-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 18 16:54:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 1072 invoked by alias); 18 Apr 2017 16:54:50 -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 1047 invoked by uid 48); 18 Apr 2017 16:54:50 -0000 From: "raajeshdasari at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug corefiles/21395] thread.c:1010 internal-error: int is_executing(ptid_t): Assertion `tp' failed. Date: Tue, 18 Apr 2017 16:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: raajeshdasari at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00085.txt.bz2 Content-length: 425 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21395 raajeshdasari at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |raajeshdasari at gmail dot= com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21285-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 18 16:55:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 2734 invoked by alias); 18 Apr 2017 16:55:21 -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 2583 invoked by uid 48); 18 Apr 2017 16:55:20 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug threads/20743] can't usefully "continue" due to "ptrace: No such process" after gdb switches thread (gdb7.11.1 on FreeBSD 11) Date: Tue, 18 Apr 2017 16:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jhb at FreeBSD dot org 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q2/txt/msg00086.txt.bz2 Content-length: 538 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20743 jhb at FreeBSD dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from jhb at FreeBSD dot org --- Fix committed to master and the 8.0 branch and will appear in 8.0 release. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21286-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Apr 20 10:51:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 2233 invoked by alias); 20 Apr 2017 10:51:06 -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 2172 invoked by uid 48); 20 Apr 2017 10:51:04 -0000 From: "raajeshdasari at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug corefiles/21395] thread.c:1010 internal-error: int is_executing(ptid_t): Assertion `tp' failed. Date: Thu, 20 Apr 2017 10:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: raajeshdasari at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00087.txt.bz2 Content-length: 829 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21395 --- Comment #1 from raajeshdasari at gmail dot com --- I have added few log messages in mips_linux_new_thread function in mips-linux-nat.c file . Added log message inside this "if" block. if (ptrace (PTRACE_SET_WATCH_REGS, tid, &watch_mirror, NULL) =3D=3D -1) perror_with_name (_("Couldn't write debug register")); I see that ptrace call() for one thread is failed and hence "Couldn't write debug register: No such process" error is seen while trying to attach a mul= ti threaded application. I also checked the ERROR code in the failure scenario, error code is ESRCH. Could someone please look into this and provide some inputs. Regards, Rajesh. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21287-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Apr 20 11:01:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 114098 invoked by alias); 20 Apr 2017 11:01:24 -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 113169 invoked by uid 48); 20 Apr 2017 11:01:19 -0000 From: "raajeshdasari at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug corefiles/21395] thread.c:1010 internal-error: int is_executing(ptid_t): Assertion `tp' failed. Date: Thu, 20 Apr 2017 11:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: raajeshdasari at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: priority 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: 2017-q2/txt/msg00088.txt.bz2 Content-length: 1088 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21395 raajeshdasari at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P1 --- Comment #2 from raajeshdasari at gmail dot com --- I have added few log messages in mips_linux_new_thread function in mips-linux-nat.c file . Added log message inside this "if" block. if (ptrace (PTRACE_SET_WATCH_REGS, tid, &watch_mirror, NULL) =3D=3D -1) perror_with_name (_("Couldn't write debug register")); I see that ptrace call() for one thread is failed and hence "Couldn't write debug register: No such process" error is seen while trying to attach a mul= ti threaded application. I also checked the ERROR code in the failure scenario, error code is ESRCH. Could someone please look into this and provide some inputs. Regards, Rajesh. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21288-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Apr 20 17:07:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 52995 invoked by alias); 20 Apr 2017 17:07:39 -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 52884 invoked by uid 48); 20 Apr 2017 17:07:38 -0000 From: "ldalessandro at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21405] New: thread.c:100: internal-error: thread_info* inferior_thread(): Assertion `tp' failed. Date: Thu, 20 Apr 2017 17:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ldalessandro at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q2/txt/msg00089.txt.bz2 Content-length: 10622 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21405 Bug ID: 21405 Summary: thread.c:100: internal-error: thread_info* inferior_thread(): Assertion `tp' failed. Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: ldalessandro at gmail dot com Target Milestone: --- Created attachment 10001 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10001&action=3Ded= it test case I'm running into the assertion at: thread.c:100: internal-error: thread_info* inferior_thread(): Assertion `tp' failed. I'm using: 1. gcc-6.3 2. valgrind-svn (r16308) 3. gdb-8.0.50.20170420-git To reproduce: 1. compile the attached testcase 2. run under valgrind with --vgdb-error=3D0 3. (in a different shell) launch gdb 4. attach to valgrind as a remote target 5. continue Trace: $ cat hello.cpp=20 #include #include using namespace std; int main() { thread([](){ cout << "hello world\n"; }).join(); return 0; } $ g++ -pthread -o hello hello.cpp=20 $ ./hello=20 hello world $ valgrind --vgdb-error=3D0 ./hello =3D=3D22111=3D=3D Memcheck, a memory error detector =3D=3D22111=3D=3D Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward = et al. =3D=3D22111=3D=3D Using Valgrind-3.13.0.SVN and LibVEX; rerun with -h for c= opyright info =3D=3D22111=3D=3D Command: ./hello =3D=3D22111=3D=3D=20 =3D=3D22111=3D=3D (action at startup) vgdb me ...=20 =3D=3D22111=3D=3D=20 =3D=3D22111=3D=3D TO DEBUG THIS PROCESS USING GDB: start GDB like this =3D=3D22111=3D=3D /path/to/gdb ./hello =3D=3D22111=3D=3D and then give GDB the following command =3D=3D22111=3D=3D target remote | /u/ldalessa/.local/modules/valgrind/HEAD/lib/valgrind/../../bin/vgdb --pid=3D22111 =3D=3D22111=3D=3D --pid is optional if only one valgrind process is running =3D=3D22111=3D=3D=20 $ gdb ./hello=20 GNU gdb (GDB) 8.0.50.20170420-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./hello...(no debugging symbols found)...done. (gdb) target remote | /u/ldalessa/.local/modules/valgrind/HEAD/lib/valgrind/../../bin/vgdb --pid=3D22111 Remote debugging using | /u/ldalessa/.local/modules/valgrind/HEAD/lib/valgrind/../../bin/vgdb --pid=3D22111 relaying data between gdb and process 22111 warning: remote target does not support file transfer, attempting to access files from local filesystem. Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/ld-2.19.so...done. done. 0x00000000040012d0 in _start () from /lib64/ld-linux-x86-64.so.2 (gdb) c Continuing. thread.c:100: internal-error: thread_info* inferior_thread(): Assertion `tp' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y This is a bug, please report it. For instructions, see: . thread.c:100: internal-error: thread_info* inferior_thread(): Assertion `tp' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) y Aborted (core dumped) GDB backtrace: $ gdb `which gdb` core GNU gdb (GDB) 8.0.50.20170420-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /u/ldalessa/.local/binutils/git/bin/gdb...done. [New LWP 9856] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `gdb ./hello'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f1022398c37 in __GI_raise (sig=3Dsig@entry=3D6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007f1022398c37 in __GI_raise (sig=3Dsig@entry=3D6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007f102239c028 in __GI_abort () at abort.c:89 #2 0x000000000067b726 in dump_core () at utils.c:465 #3 0x000000000067da88 in internal_vproblem(internal_problem *, const char = *, int, const char *, typedef __va_list_tag __va_list_tag *) (problem=3Dproblem@entry=3D0xd21160 , file=3D,=20 line=3D, fmt=3D, ap=3Dap@entry=3D0x7fff1f= d87608) at utils.c:676 #4 0x000000000067db49 in internal_verror (file=3D, line=3D, fmt=3D, ap=3Dap@entry=3D0x7fff1fd876= 08) at utils.c:702 #5 0x000000000059ab52 in internal_error (file=3Dfile@entry=3D0x8db4f7 "thr= ead.c", line=3Dline@entry=3D100, fmt=3D) at common/errors.c:55 #6 0x0000000000670415 in inferior_thread () at thread.c:100 #7 0x00000000004aed4c in tui_on_normal_stop (bs=3D, print_frame=3D) at tui/tui-interp.c:97 #8 0x0000000000609415 in generic_observer_notify (args=3D0x7fff1fd87720, subject=3D) at observer.c:167 #9 observer_notify_normal_stop (bs=3Dbs@entry=3D0x0, print_frame=3D) at observer.inc:61 #10 0x00000000005da1dd in normal_stop () at infrun.c:8373 #11 0x000000000054ab96 in do_my_cleanups (pmy_chain=3Dpmy_chain@entry=3D0xd= 1fc80 , old_chain=3D0x874380 ) at common/cleanups.c:154 #12 0x000000000054ad1d in do_cleanups (old_chain=3D) at common/cleanups.c:176 #13 0x000000000054ffae in throw_exception_cxx (exception=3D...) at common/common-exceptions.c:289 #14 0x0000000000550094 in throw_exception (exception=3D...) at common/common-exceptions.c:317 #15 throw_it(return_reason, errors, const char *, typedef __va_list_tag __va_list_tag *) (reason=3Dreason@entry=3DRETURN_ERROR, error=3D, fmt=3D, ap=3Dap@entry=3D0x7fff1fd87848) at common/common-exceptions.c:373 #16 0x00000000005502c6 in throw_verror (error=3D, fmt=3D, ap=3Dap@entry=3D0x7fff1fd87848) at common/common-exceptions.c:379 #17 0x0000000000550377 in throw_error (error=3Derror@entry=3DTARGET_CLOSE_E= RROR, fmt=3D) at common/common-exceptions.c:394 #18 0x0000000000474a33 in readchar (timeout=3D) at remote.c:= 8614 #19 0x000000000047544f in getpkt_or_notif_sane_1 (buf=3Dbuf@entry=3D0x19b60= 40, sizeof_buf=3Dsizeof_buf@entry=3D0x19b6048, forever=3Dforever@entry=3D0, expecting_notif=3Dexpecting_notif@entry=3D0, is_notif=3Dis_notif@entry=3D0x= 0) at remote.c:9157 #20 0x000000000047e950 in getpkt_sane (forever=3D0, sizeof_buf=3D0x19b6048, buf=3D0x19b6040) at remote.c:9259 #21 getpkt (forever=3D0, sizeof_buf=3D0x19b6048, buf=3D0x19b6040) at remote= .c:9097 #22 remote_pass_signals (numsigs=3D, pass_signals=3D0x19feaf= 0 "", self=3D) at remote.c:2036 #23 0x00000000005d61af in do_target_resume (resume_ptid=3D..., step=3D0, sig=3DGDB_SIGNAL_0) at infrun.c:2369 #24 0x00000000005db87a in resume (sig=3DGDB_SIGNAL_0) at infrun.c:2760 #25 0x00000000005dc7e3 in keep_going_pass_signal (ecs=3Decs@entry=3D0x7fff1= fd87c30) at infrun.c:7829 #26 0x00000000005dd29b in proceed (addr=3D, siggnal=3D) at infrun.c:3196 #27 0x00000000005d27f7 in continue_command (args=3D, from_tt= y=3D1) at infcmd.c:862 #28 0x00000000004986b9 in cmd_func (cmd=3D, args=3D, from_tty=3D) at cli/cli-decode.c:1887 #29 0x0000000000676003 in execute_command (p=3D, p@entry=3D0= x1bb1b30 "c", from_tty=3D1) at top.c:674 #30 0x00000000005a2ecc in command_handler (command=3D0x1bb1b30 "c") at event-top.c:590 #31 0x00000000005a3198 in command_line_handler (rl=3D) at event-top.c:780 #32 0x00000000005a250c in gdb_rl_callback_handler (rl=3D0x1af9620 "") at event-top.c:213 #33 0x00000000006b7333 in rl_callback_read_char () at callback.c:220 #34 0x00000000005a244e in gdb_rl_callback_read_char_wrapper_noexcept () at event-top.c:175 #35 0x00000000005a24b9 in gdb_rl_callback_read_char_wrapper (client_data=3D) at event-top.c:192 #36 0x00000000005a29e0 in stdin_event_handler (error=3D, client_data=3D0x1920c30) at event-top.c:518 #37 0x00000000005a185d in gdb_wait_for_event (block=3Dblock@entry=3D1) at event-loop.c:859 #38 0x00000000005a19c4 in gdb_do_one_event () at event-loop.c:347 #39 0x00000000005a1b35 in gdb_do_one_event () at ./common/common-exceptions.h:221 #40 start_event_loop () at event-loop.c:371 #41 0x00000000005f4d88 in captured_command_loop (data=3Ddata@entry=3D0x0) at main.c:325 #42 0x00000000005a3aa3 in catch_errors (func=3Dfunc@entry=3D0x5f4d60 , func_args=3Dfunc_args@entry=3D0x0, errstring=3Derrstring@entry=3D0x8200e2 "", mask=3Dmask@entry=3DRETURN_MASK_= ALL) at exceptions.c:236 #43 0x00000000005f5cb6 in captured_main (data=3D0x7fff1fd88000) at main.c:1= 150 #44 gdb_main (args=3Dargs@entry=3D0x7fff1fd88130) at main.c:1160 #45 0x000000000040e305 in main (argc=3D, argv=3D) at gdb.c:32 (gdb)=20 ref: https://sourceware.org/ml/gdb/2017-04/msg00028.html ref: https://sourceware.org/bugzilla/show_bug.cgi?id=3D11362 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21289-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Apr 20 17:24:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 18462 invoked by alias); 20 Apr 2017 17:24:47 -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 17898 invoked by uid 48); 20 Apr 2017 17:24:31 -0000 From: "ldalessandro at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21405] thread.c:100: internal-error: thread_info* inferior_thread(): Assertion `tp' failed. Date: Thu, 20 Apr 2017 17:24: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ldalessandro at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00090.txt.bz2 Content-length: 390 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21405 ldalessandro at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ldalessandro at gmail dot = com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21290-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Apr 20 18:46:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 22449 invoked by alias); 20 Apr 2017 18:46:35 -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 22425 invoked by uid 48); 20 Apr 2017 18:46:34 -0000 From: "dilyan.palauzov at aegee dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21406] New: gdb/ada-lex.l: %option noyywrap Date: Thu, 20 Apr 2017 18:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dilyan.palauzov at aegee dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00091.txt.bz2 Content-length: 1486 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21406 Bug ID: 21406 Summary: gdb/ada-lex.l: %option noyywrap Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: dilyan.palauzov at aegee dot org Target Milestone: --- As it was done in the other .l files, please replace int yywrap() in ada-le= x.l with %option noyywrap . diff --git a/gdb/ada-lex.l b/gdb/ada-lex.l --- a/gdb/ada-lex.l +++ b/gdb/ada-lex.l @@ -78,7 +78,7 @@ static int find_dot_all (const char *); %} -%option case-insensitive interactive nodefault +%option case-insensitive interactive nodefault noyywrap %s BEFORE_QUAL_QUOTE @@ -636,12 +636,6 @@ rewind_to_char (int ch) yyrestart (NULL); } -int -yywrap(void) -{ - return 1; -} - /* Dummy definition to suppress warnings about unused static definitions. = */ typedef void (*dummy_function) (); dummy_function ada_flex_use[] =3D=20 diff --git a/gdb/ada-exp.y b/gdb/ada-exp.y --- a/gdb/ada-exp.y +++ b/gdb/ada-exp.y @@ -721,7 +721,6 @@ primary : '*' primary %prec '.' #define yy_switch_to_buffer ada_yy_switch_to_buffer #define yyrestart ada_yyrestart #define yytext ada_yytext -#define yywrap ada_yywrap static struct obstack temp_parse_space; --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21291-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 21 13:06:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27087 invoked by alias); 21 Apr 2017 13:06:45 -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 27054 invoked by uid 48); 21 Apr 2017 13:06:44 -0000 From: "LpSolit at netscape dot net" To: gdb-prs@sourceware.org Subject: [Bug python/21007] New: Expose breaking with regular expressions on the Python API Date: Fri, 21 Apr 2017 13:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: LpSolit at netscape dot net X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00092.txt.bz2 Content-length: 861 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21007 Bug ID: 21007 Summary: Expose breaking with regular expressions on the Python API Product: gdb Version: 7.11 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: ciro.santilli at gmail dot com Target Milestone: --- Currently you need to shell out: gdb.execute('rbreak {}'.format(regexp)) but it would be cool if there was a boolean `regular_expression` constructor argument to `gdb.Breakpoint`. Looked at docs at: https://sourceware.org/gdb/current/onlinedocs/gdb/Breakpoints-In-Python.htm= l#Breakpoints-In-Python --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21292-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Apr 22 01:49:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 51370 invoked by alias); 22 Apr 2017 01:49:21 -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 51221 invoked by uid 48); 22 Apr 2017 01:49:19 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug build/21057] GDB build failure with flex 2.6.3 Date: Sat, 22 Apr 2017 01:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: cc 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: 2017-q2/txt/msg00093.txt.bz2 Content-length: 900 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21057 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --- Comment #8 from Tom Tromey --- (In reply to Pedro Alves from comment #7) > For GDB, switching to -p sounds like a viable option going forward. Also, > we probably need to switch to C++ mode, to avoid ODR violations around the > parsers... Need volunteers. :-) I tried yacc -p once, and it was trickier than it seemed like it ought to have been. C++ mode is a bison extension AFAIK. I think using it would be very nice, but I wonder whether it's acceptable. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21293-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Apr 22 12:43:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 111318 invoked by alias); 22 Apr 2017 12:43:19 -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 111293 invoked by uid 48); 22 Apr 2017 12:43:18 -0000 From: "vishwanath.patil at pathpartnertech dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21419] New: Unable to list program after loading symbolic table Date: Sat, 22 Apr 2017 12:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: vishwanath.patil at pathpartnertech dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00094.txt.bz2 Content-length: 1633 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21419 Bug ID: 21419 Summary: Unable to list program after loading symbolic table Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: critical Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: vishwanath.patil at pathpartnertech dot com Target Milestone: --- With GDB even after loading symbolic table , gdb unable to list program lin= es. It is able to list only if I specify the source code path , setting via "di= r" command. GDB version 7.8 and 7.12 tried . program compiled with arm-linux-gnueabi-gcc -g main.c arch - armV5. GDB console log GNU gdb (Linaro GDB) 7.8-2014.09 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "arm-linux-gnueabi". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from a.out...done. (gdb) l=20 13 main.c: No such file or directory. (gdb) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21294-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Apr 22 12:46:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 116942 invoked by alias); 22 Apr 2017 12:46:31 -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 116918 invoked by uid 48); 22 Apr 2017 12:46:30 -0000 From: "vishwanath.patil at pathpartnertech dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21419] Unable to list program after loading symbolic table Date: Sat, 22 Apr 2017 12:46: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: vishwanath.patil at pathpartnertech dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00095.txt.bz2 Content-length: 324 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21419 --- Comment #1 from vishwanath --- issue is close to this issue , http://stackoverflow.com/questions/21928876/gdb-can-not-load-source-file --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21295-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Apr 24 08:06:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63205 invoked by alias); 24 Apr 2017 08:06:44 -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 63178 invoked by uid 48); 24 Apr 2017 08:06:43 -0000 From: "jeanmichael.celerier at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21424] New: -gsplit-dwarf: top namespace info seems to be lost in GDB Date: Mon, 24 Apr 2017 08:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jeanmichael.celerier at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00096.txt.bz2 Content-length: 1422 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21424 Bug ID: 21424 Summary: -gsplit-dwarf: top namespace info seems to be lost in GDB Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: jeanmichael.celerier at gmail dot com Target Milestone: --- Originally posted in GCC bug tracker:=20 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D80490 Given the following code:=20 main.cpp:=20 namespace ossia { class foo { public: void f() { } }; namespace net=20 {=20 class bar { public: void g() { } }; } } int main() { auto x =3D new ossia::foo; auto y =3D new ossia::net::bar; x->f(); y->g(); } And the following invocation :=20 g++ -ggdb -O0 -gsplit-dwarf -Wl,--gdb-index -fuse-ld=3Dgold main.cpp Debugging in gdb looks like this :=20 gdb a.out b main > auto x =3D new ossia::foo; p x > $1 =3D ((anonymous namespace)::foo *) 0x414c20 n p y > $2 =3D ((anonymous namespace)::net::bar *) 0x414c40 Doing=20 strings a.out | c++filt seems to yield the correct types, though. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21296-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Apr 24 09:30:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49273 invoked by alias); 24 Apr 2017 09:30:42 -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 48838 invoked by uid 48); 24 Apr 2017 09:30:29 -0000 From: "mark at klomp dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/20367] add further Rust demangling Date: Mon, 24 Apr 2017 09:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at klomp dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q2/txt/msg00097.txt.bz2 Content-length: 374 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20367 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mjw at fedoraproject dot org | --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21297-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 25 03:09:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 69144 invoked by alias); 25 Apr 2017 03:09:12 -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 69095 invoked by uid 48); 25 Apr 2017 03:09:11 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug python/16486] differences between "bt" and "bt no-filters" Date: Tue, 25 Apr 2017 03:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: pmuldoon at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q2/txt/msg00098.txt.bz2 Content-length: 1123 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16486 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --- Comment #3 from Tom Tromey --- FWIW this is still a bit odd. I ran gdb on itself (just "run" then interrupted when the prompt came up); and did a bt using the colorizing frame filter from my gdb-helpers project. With the filter, apparently all one line: #5 0x00000000007d9de8 in catch_errors(int (*)(void*), void*, char const*, return_mask) (func=3D0x84b565 , func_args=3D0= x0, errstring=3D0xf0bafb "", mask=3DRETURN_MASK_ALL) Without: #5 0x00000000007d9de8 in catch_errors ( func=3D0x84b565 , func_args=3D0x0,=20 errstring=3D0xf0bafb "", mask=3DRETURN_MASK_ALL) at ../../binutils-gdb/gdb/exceptions.c:236 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21298-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 25 03:59:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 15000 invoked by alias); 25 Apr 2017 03:59:01 -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 12219 invoked by uid 48); 25 Apr 2017 03:58:59 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug python/16486] differences between "bt" and "bt no-filters" Date: Tue, 25 Apr 2017 03:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: pmuldoon at redhat dot com 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: 2017-q2/txt/msg00099.txt.bz2 Content-length: 330 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16486 --- Comment #4 from Tom Tromey --- Also I suspect that those wrap_here calls should adjust their arguments to account for increased indentation in elided frames. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21299-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 25 20:33:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 10221 invoked by alias); 25 Apr 2017 20:33:00 -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 10155 invoked by uid 48); 25 Apr 2017 20:32:59 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/16486] differences between "bt" and "bt no-filters" Date: Tue, 25 Apr 2017 20:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pmuldoon at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: pmuldoon at redhat dot com 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: 2017-q2/txt/msg00100.txt.bz2 Content-length: 364 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16486 --- Comment #5 from Phil Muldoon --- Good point on the wrap hints. I have some more time allocated now to look at Python. I'll take a look at the wrap hints and see what's going on with the output. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21300-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 25 23:09:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 72912 invoked by alias); 25 Apr 2017 23:09:38 -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 72874 invoked by uid 48); 25 Apr 2017 23:09:38 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug python/16486] differences between "bt" and "bt no-filters" Date: Tue, 25 Apr 2017 23:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: pmuldoon at redhat dot com 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: 2017-q2/txt/msg00101.txt.bz2 Content-length: 488 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16486 --- Comment #6 from Tom Tromey --- (In reply to Phil Muldoon from comment #5) > Good point on the wrap hints. I have some more time allocated now to look= at > Python. I'll take a look at the wrap hints and see what's going on with t= he > output. FWIW my patch series from today has a fix for the one spot I noticed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21301-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 26 04:29:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 38819 invoked by alias); 26 Apr 2017 04:29:01 -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 38768 invoked by uid 48); 26 Apr 2017 04:29:01 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug guile/21104] 7.12.1 does not compile with latest guile (2.1.6) Date: Wed, 26 Apr 2017 04:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: guile X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00102.txt.bz2 Content-length: 411 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21104 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.marchi at ericsson d= ot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21302-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 26 04:31:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 106043 invoked by alias); 26 Apr 2017 04:31:34 -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 105927 invoked by uid 48); 26 Apr 2017 04:31:26 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug guile/21104] 7.12.1 does not compile with latest guile (2.1.6) Date: Wed, 26 Apr 2017 04:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: guile X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00103.txt.bz2 Content-length: 400 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21104 --- Comment #2 from Simon Marchi --- I am not aware of anyone working on this, but contributions are always welc= ome. I don't use Guile myself and am not familiar with the concepts, so it woul= d be difficult for me to do it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21303-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 26 19:24:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 119667 invoked by alias); 26 Apr 2017 19:24:34 -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 119563 invoked by uid 48); 26 Apr 2017 19:24:26 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21225] Which version of gdb should I use for best reliability Date: Wed, 26 Apr 2017 19:24: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.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q2/txt/msg00104.txt.bz2 Content-length: 1019 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21225 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Pedro Alves --- Hi there! I'd like to stress that I'd really appreciate specific suggestions for what sort of issues impact you the most, and learn more about your use cases.=20 Filing a bug for each specific issue with a reproducer would be ideal. But please feel free to send me email offlist too. I'm always interested in hearing from our users. I have thick skin so feel free to say what you're really thinking. :-) As for this bug, I don't think there's anything else we can do here, so I'm closing it. Thanks for your input. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21304-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Apr 26 22:07:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 103959 invoked by alias); 26 Apr 2017 22:07:39 -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 103683 invoked by uid 48); 26 Apr 2017 22:07:39 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug python/21436] New: frame filter should allow duplicated underlying frames Date: Wed, 26 Apr 2017 22:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00105.txt.bz2 Content-length: 1297 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21436 Bug ID: 21436 Summary: frame filter should allow duplicated underlying frames Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- Currently a frame filter must associate each frame it returns with some underlying inferior frame. If multiple decorated frames refer to the same underlying frame, the resulting output from gdb is a bit funny -- it prints the frame number (like "#5") just once, but otherwise prints the entire frame multiple times (at each spot it is referenced). (It's possible this only occurs when the frame is also elided -- I can't recall right now.) This problem came up while writing a frame filter that understands SpiderMonkey interpreter frames. See: https://bugzilla.mozilla.org/show_bug.cgi?id=3D1254297 In SpiderMonkey, a given invocation of the interpreter loop may actually evaluate several interpreted calls, so each such frame would refer to the same underlying C++ frame. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21305-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Apr 27 05:29:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 22915 invoked by alias); 27 Apr 2017 05:29:40 -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 22857 invoked by uid 48); 27 Apr 2017 05:29:39 -0000 From: "raajeshdasari at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug corefiles/21395] thread.c:1010 internal-error: int is_executing(ptid_t): Assertion `tp' failed. Date: Thu, 27 Apr 2017 05:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: raajeshdasari at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 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: 2017-q2/txt/msg00106.txt.bz2 Content-length: 1480 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21395 --- Comment #3 from raajeshdasari at gmail dot com --- I added a sleep after this ptrace call ptrace (PTRACE_SET_WATCH_REGS, tid, &watch_mirror, NULL); and then retried the same call again , Issue is resol= ved for me . diff --git a/gdb/mips-linux-nat.c b/gdb/mips-linux-nat.c index 9d22773..68641f8 100644 --- a/gdb/mips-linux-nat.c +++ b/gdb/mips-linux-nat.c @@ -634,9 +634,20 @@ mips_linux_new_thread (struct lwp_info *lp) &watch_readback_valid, 0)) return; + long r; + r=3D ptrace (PTRACE_SET_WATCH_REGS, tid, &watch_mirror, NULL); tid =3D ptid_get_lwp (lp->ptid); - if (ptrace (PTRACE_SET_WATCH_REGS, tid, &watch_mirror, NULL) =3D=3D -1) - perror_with_name (_("Couldn't write debug register")); + if ( r =3D=3D -1L && errno =3D=3D ESRCH ) + { + /* sleep for a while to eliminate race condition on update to kernel + * task structure with the process state (STOP state of thread). + */ + usleep(10000); + if ( ptrace (PTRACE_SET_WATCH_REGS, tid, &watch_mirror, NULL) =3D=3D = -1 ) + { + perror_with_name (_("Couldn't write debug register")); + } + } } /* Target to_insert_watchpoint implementation. Try to insert a new --=20 2.4.11 could someone please review this and let me know if any comments. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21307-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 28 02:43:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68995 invoked by alias); 28 Apr 2017 02:43:31 -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 67773 invoked by uid 48); 28 Apr 2017 02:43:30 -0000 From: "ggs334 at 163 dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21443] a bug under gas/opcode Date: Fri, 28 Apr 2017 02:43: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ggs334 at 163 dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_severity 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: 2017-q2/txt/msg00108.txt.bz2 Content-length: 372 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21443 gaohusheng changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |critical --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21306-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Apr 28 02:43:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 26777 invoked by alias); 28 Apr 2017 02:43:10 -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 24271 invoked by uid 48); 28 Apr 2017 02:43:09 -0000 From: "ggs334 at 163 dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21443] New: a bug under gas/opcode Date: Fri, 28 Apr 2017 02:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ggs334 at 163 dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00107.txt.bz2 Content-length: 978 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21443 Bug ID: 21443 Summary: a bug under gas/opcode Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: ggs334 at 163 dot com Target Milestone: --- I found a bug under gas/opcode, Assembler messages: Error: internal: bad mips opcode (bits 0x01e00000 doubly defined): mflxc0 t= ,_d4 Error: internal: bad mips opcode (bits 0x01e00000 doubly defined): mflxc0 t,_d4,_S Error: internal: bad mips opcode (bits 0x01e00000 doubly defined): mtlxc0 t= ,_d4 Error: internal: bad mips opcode (bits 0x01e00000 doubly defined): mtlxc0 t,_d4,_S Internal error! Assertion failure in validate_mips_insn at /ssd/shunyen/sdk/gdb-7.12/gas/config/tc-mips.c:3368. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21308-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Apr 29 00:30:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4868 invoked by alias); 29 Apr 2017 00:30:46 -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 4829 invoked by uid 55); 29 Apr 2017 00:30:45 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/8595] environ.exp could run on more platforms Date: Sat, 29 Apr 2017 00:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: 2017-q2/txt/msg00109.txt.bz2 Content-length: 1775 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8595 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D45ce1b47e449= 0993b5c1a04f4a8acb62d9ec5039 commit 45ce1b47e4490993b5c1a04f4a8acb62d9ec5039 Author: Sergio Durigan Junior Date: Fri Mar 31 13:24:36 2017 -0400 Make environ.exp run on all platforms (and create info-program.exp) This has been on my TODO list for a while. There's a really old bug about this (PR testsuite/8595), and there was no reason for environ.exp to be specific for hppa* targets. So this patch removes this constraint, modernizes the testcase, and cleans up some things. Most of the tests remained, and some were rewritten (especially the one that checks if "show environment" works, which is something kind of hard to do). As a bonus, I'm adding a separated info-program.exp file containing all the tests related to "info program" that were present on environ.exp. Tested locally, everything still passes. gdb/testsuite/ChangeLog: 2017-04-28 Sergio Durigan Junior PR testsuite/8595 * gdb.base/environ.exp: Make test available in all architectures. Move bits related to "info program" testing to gdb.base/info-program.exp. Rewrite tests to use the two new procedures mentione below. (test_set_show_env_var) New procedure. (test_set_show_env_var_equal): Likewise. * gdb.base/info-program.exp: New file. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21309-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Apr 29 00:32:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 7591 invoked by alias); 29 Apr 2017 00:32:28 -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 7557 invoked by uid 48); 29 Apr 2017 00:32:27 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug testsuite/8595] environ.exp could run on more platforms Date: Sat, 29 Apr 2017 00:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q2/txt/msg00110.txt.bz2 Content-length: 537 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8595 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Sergio Durigan Junior --- Finally fixed :-). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21310-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Apr 29 19:56:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 42834 invoked by alias); 29 Apr 2017 19:56:21 -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 42803 invoked by uid 48); 29 Apr 2017 19:56:20 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug record/21447] New: "Assertion `tp != NULL' failed" when trying to "record btrace" a multithreaded program Date: Sat, 29 Apr 2017 19:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q2/txt/msg00111.txt.bz2 Content-length: 1796 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21447 Bug ID: 21447 Summary: "Assertion `tp !=3D NULL' failed" when trying to "record btrace" a multithreaded program Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: record Assignee: unassigned at sourceware dot org Reporter: b7.10110111 at gmail dot com Target Milestone: --- Created attachment 10034 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10034&action=3Ded= it Backtrace Here's a test C++ program: #include #include int bar() { char buf[10]; memset(buf, 0, sizeof(buf)); memset(buf, 'A', 100); // overflow } int foo() { return bar(); } void mythread() { for(volatile int x=3D0;x!=3D1;); } int main() { std::thread thr(mythread); foo(); } I compile it like follows on a 32-bit x86 gcc 4.5: g++ test.cpp -o test -std=3Dc++0x -pthread -g -fno-stack-protector Then I run GDB as gdb -q ./test -ex start -ex 'record btrace' -ex c And get this output: Temporary breakpoint 1, main () at test.cpp:19 19 std::thread thr(mythread); Continuing. record-btrace.c:1415: internal-error: void record_btrace_fetch_registers(target_ops*, regcache*, int): Assertion `tp != =3D NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Attached is a backtrace from the core generated by GDB for itself. I was testing * 32-bit x86 GDB 8.0.50.20170429-git and 7.10.50.20151205-cvs on LFS * 64-bit x86_64 GDB 7.10.50.20151205-cvs on CLFS 1.2.0 CPU is Intel Core i7-4765T Linux 3.12.18 64-bit --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21311-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Apr 29 19:56:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 43400 invoked by alias); 29 Apr 2017 19:56:49 -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 43380 invoked by uid 48); 29 Apr 2017 19:56:49 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug record/21447] "Assertion `tp != NULL' failed" when trying to "record btrace" a multithreaded program Date: Sat, 29 Apr 2017 19:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00112.txt.bz2 Content-length: 258 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21447 --- Comment #1 from Ruslan --- If I comment out std::thread line, the bug doesn't happen. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21312-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon May 01 02:13:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 47512 invoked by alias); 1 May 2017 02:13:07 -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 47405 invoked by uid 48); 1 May 2017 02:13:05 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/8150] Gdb crashes when doing -data-list-register-values Date: Mon, 01 May 2017 02:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: simon.marchi at ericsson dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: OBSOLETE X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution 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: 2017-q2/txt/msg00113.txt.bz2 Content-length: 667 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8150 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |simon.marchi at ericsson d= ot com Resolution|--- |OBSOLETE --- Comment #3 from Simon Marchi --- Spring cleanup, if this isn't actually obsolete, please re-open it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21313-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon May 01 06:04:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 126488 invoked by alias); 1 May 2017 06:04:50 -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 126401 invoked by uid 48); 1 May 2017 06:04:49 -0000 From: "grassfedcode at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21449] New: segfault when running -data-list-register-values x on rust executable Date: Mon, 01 May 2017 06:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: grassfedcode at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q2/txt/msg00114.txt.bz2 Content-length: 1663 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21449 Bug ID: 21449 Summary: segfault when running -data-list-register-values x on rust executable Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: grassfedcode at gmail dot com Target Milestone: --- Created attachment 10035 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10035&action=3Ded= it strace of the gdb session and eventual segfault A segfault occurs in `-data-list-register-values x` when stopped in a rust executable. See https://github.com/cs01/gdbgui/issues/64. This was confirme= d by o11c and simark in the #gdb irc channel. MI transcript:=20 -file-exec-and-symbols /home/chad/git/gdbgui/examples/rust.a\n-break-insert /home/chad/git/gdbgui/examples/hello.rs:15\n-exec-run\n-data-list-register-= values x\n Rust source file: https://raw.githubusercontent.com/cs01/gdbgui/master/examples/hello.rs makefile: https://github.com/cs01/gdbgui/blob/master/examples/makefile The kernel log reports [ 4467.187888] gdb[13609]: segfault at 0 ip 00000000006489ed sp 00007ffc0a0ce260 error 4 in gdb[400000+617000] The bug was fixed in gdb's git repository, commit b96645f1a1e608 "Add suppo= rt for untagged unions in Rust", but is present in version 7.12 and 7.12.1.=20 Seems similar to a bug #8150, which is old and is likely not related since = this occurs only on Rust executables. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21314-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon May 01 06:04:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 126499 invoked by alias); 1 May 2017 06:04:51 -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 126398 invoked by uid 48); 1 May 2017 06:04:49 -0000 From: "grassfedcode at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21450] New: segfault when running -data-list-register-values x on rust executable Date: Mon, 01 May 2017 06:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: grassfedcode at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00115.txt.bz2 Content-length: 1509 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21450 Bug ID: 21450 Summary: segfault when running -data-list-register-values x on rust executable Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: grassfedcode at gmail dot com Target Milestone: --- A segfault occurs in `-data-list-register-values x` when stopped in a rust executable. See https://github.com/cs01/gdbgui/issues/64. This was confirme= d by o11c and simark in the #gdb irc channel. MI transcript:=20 -file-exec-and-symbols /home/chad/git/gdbgui/examples/rust.a\n-break-insert /home/chad/git/gdbgui/examples/hello.rs:15\n-exec-run\n-data-list-register-= values x\n Rust source file: https://raw.githubusercontent.com/cs01/gdbgui/master/examples/hello.rs makefile: https://github.com/cs01/gdbgui/blob/master/examples/makefile The kernel log reports [ 4467.187888] gdb[13609]: segfault at 0 ip 00000000006489ed sp 00007ffc0a0ce260 error 4 in gdb[400000+617000] The bug was fixed in gdb's git repository, commit b96645f1a1e608 "Add suppo= rt for untagged unions in Rust", but is present in version 7.12 and 7.12.1.=20 Seems similar to a bug #8150, which is old and is likely not related since = this occurs only on Rust executables. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21315-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon May 01 19:39:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 119636 invoked by alias); 1 May 2017 19:39:17 -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 119597 invoked by uid 48); 1 May 2017 19:39:16 -0000 From: "grassfedcode at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/21451] New: gdb mi's -data-disassemble command only outputs lines starting from the closest function Date: Mon, 01 May 2017 19:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: grassfedcode at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00116.txt.bz2 Content-length: 1659 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21451 Bug ID: 21451 Summary: gdb mi's -data-disassemble command only outputs lines starting from the closest function Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: mi Assignee: unassigned at sourceware dot org Reporter: grassfedcode at gmail dot com Target Milestone: --- When running gdb v7.6 up to current HEAD (ee7e95efb9) with the mi2 interpre= ter, and trying to view disassembly in mode 4 (mixed source and disassembly), the line number argument is being ignored.=20 for example ``` -file-exec-and-symbols /home/csmith/git/pygdbmi/pygdbmi/tests/sample_c_app/a.out -data-disassemble -f /home/csmith/git/pygdbmi/pygdbmi/tests/sample_c_app/hello.c -l 16 -n 1 4\n ^done,asm_insns=3D[src_and_asm_line=3D{line=3D"16",file=3D"hello.c",fullnam= e=3D"/home/csmith/git/pygdbmi/pygdbmi/tests/sample_c_app/hello.c",line_asm_= insn=3D[{address=3D"0x000000000040057d",func-name=3D"main",offset=3D"0",ins= t=3D"push %rbp"}]}] ``` but when I try to look at the next line (17), it outputs the same line (16): ``` -data-disassemble -f /home/csmith/git/pygdbmi/pygdbmi/tests/sample_c_app/hello.c -l 17 -n 1 4 ^done,asm_insns=3D[src_and_asm_line=3D{line=3D"16",file=3D"hello.c",fullnam= e=3D"/home/csmith/git/pygdbmi/pygdbmi/tests/sample_c_app/hello.c",line_asm_= insn=3D[{address=3D"0x000000000040057d",func-name=3D"main",offset=3D"0",ins= t=3D"push %rbp"}]}] ``` --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21316-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon May 01 19:44:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3838 invoked by alias); 1 May 2017 19:44:25 -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 3719 invoked by uid 48); 1 May 2017 19:44:24 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/21451] gdb mi's -data-disassemble command only outputs lines starting from the closest function Date: Mon, 01 May 2017 19:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00117.txt.bz2 Content-length: 411 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21451 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.marchi at ericsson d= ot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21317-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue May 02 21:24:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109168 invoked by alias); 2 May 2017 21:24:01 -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 109125 invoked by uid 48); 2 May 2017 21:24:00 -0000 From: "freddie_chopin at op dot pl" To: gdb-prs@sourceware.org Subject: [Bug guile/21104] 7.12.1 does not compile with latest guile (2.1.6) Date: Tue, 02 May 2017 21:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: guile X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: freddie_chopin at op dot pl X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00118.txt.bz2 Content-length: 582 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21104 Freddie Chopin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freddie_chopin at op dot pl --- Comment #3 from Freddie Chopin --- For me a "workaround" is to explicitly disable guile by passing `--with-guile=3Dno` to GDB's configure script. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21318-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue May 02 23:14:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 25730 invoked by alias); 2 May 2017 23:14:45 -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 25700 invoked by uid 48); 2 May 2017 23:14:44 -0000 From: "b.r.longbons at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/12228] thread.c:598: internal-error: is_thread_state: Assertion `tp' failed. Date: Tue, 02 May 2017 23:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 7.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b.r.longbons at gmail dot com 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: cc 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: 2017-q2/txt/msg00119.txt.bz2 Content-length: 2665 https://sourceware.org/bugzilla/show_bug.cgi?id=3D12228 Ben Longbons changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |b.r.longbons at gmail dot = com --- Comment #2 from Ben Longbons --- I hit this with a minimal example while filing another bug: GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". @(gdb) target extended-remote | gdbserver --multi stdio Remote debugging using | gdbserver --multi stdio Remote debugging using stdio @(gdb) set remote exec-file /bin/true @(gdb) run Starting program:=20=20 Process /bin/true created; pid =3D 679 stdin/stdout redirected Reading /bin/true from remote target... warning: File transfers from remote targets can be slow. Use "set sysroot" = to access files locally instead. Reading /bin/true from remote target... Reading symbols from target:/bin/true...Reading /bin/e82394864538fa7b23b7f87b259ea2a20889c4.debug from remote target... Reading /bin/.debug/e82394864538fa7b23b7f87b259ea2a20889c4.debug from remote target... (no debugging symbols found)...done. /build/gdb-A87voC/gdb-7.12/gdb/thread.c:982: internal-error: int is_thread_state(ptid_t, thread_state): Assertion `tp' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. @Quit this debugging session? (y or n) y This is a bug, please report it. For instructions, see: . /build/gdb-A87voC/gdb-7.12/gdb/thread.c:982: internal-error: int is_thread_state(ptid_t, thread_state): Assertion `tp' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. @Create a core file of GDB? (y or n) y [1] 669 abort (core dumped) gdb For this case, adding `file /bin/true` fixes it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21319-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue May 02 23:20:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 37531 invoked by alias); 2 May 2017 23:20:37 -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 37505 invoked by uid 48); 2 May 2017 23:20:36 -0000 From: "b.r.longbons at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug server/21454] New: `target extended-remote | gdbserver --multi stdio` uses 100% CPU after gdb quits Date: Tue, 02 May 2017 23:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b.r.longbons at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00120.txt.bz2 Content-length: 2058 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21454 Bug ID: 21454 Summary: `target extended-remote | gdbserver --multi stdio` uses 100% CPU after gdb quits Product: gdb Version: 7.12 Status: UNCONFIRMED Severity: normal Priority: P2 Component: server Assignee: unassigned at sourceware dot org Reporter: b.r.longbons at gmail dot com Target Milestone: --- GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". @(gdb) target extended-remote | gdbserver --multi stdio Remote debugging using | gdbserver --multi stdio Remote debugging using stdio @(gdb) set remote exec-file /bin/true @(gdb) file /bin/true Reading symbols from /bin/true...(no debugging symbols found)...done. @(gdb) run Starting program: /bin/true=20 Process /bin/true created; pid =3D 737 stdin/stdout redirected Reading /lib64/ld-linux-x86-64.so.2 from remote target... warning: File transfers from remote targets can be slow. Use "set sysroot" = to access files locally instead. Reading /lib64/ld-linux-x86-64.so.2 from remote target... Reading /lib/x86_64-linux-gnu/libc.so.6 from remote target... [Inferior 1 (process 737) exited normally] @(gdb) quit This does *not* happen with TCP targets. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21320-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 03 11:49:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122602 invoked by alias); 3 May 2017 11:49:01 -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 122558 invoked by uid 48); 3 May 2017 11:49:00 -0000 From: "antoine.tremblay at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug server/21169] GDBServer on ARM can crash the inferior while single stepping Date: Wed, 03 May 2017 11:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: antoine.tremblay at ericsson dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: antoine.tremblay at ericsson dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone 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: 2017-q2/txt/msg00121.txt.bz2 Content-length: 388 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21169 Antoine Tremblay changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|8.0 |--- --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21321-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 03 11:56:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20381 invoked by alias); 3 May 2017 11:56:19 -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 20352 invoked by uid 48); 3 May 2017 11:56:19 -0000 From: "antoine.tremblay at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/21169] GDBServer on ARM can crash the inferior while single stepping Date: Wed, 03 May 2017 11:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: antoine.tremblay at ericsson dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: antoine.tremblay at ericsson dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: component 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: 2017-q2/txt/msg00122.txt.bz2 Content-length: 540 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21169 Antoine Tremblay changed: What |Removed |Added ---------------------------------------------------------------------------- Component|server |tdep --- Comment #2 from Antoine Tremblay = --- GDB is also affected by this, changed component from server to tdep --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21322-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 03 16:55:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 44174 invoked by alias); 3 May 2017 16:55:37 -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 42956 invoked by uid 48); 3 May 2017 16:55:36 -0000 From: "brian at ubuntu dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21324] gdb hangs when 'thread apply all bt full' is used Date: Wed, 03 May 2017 16:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: brian at ubuntu dot com 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: 2017-q2/txt/msg00123.txt.bz2 Content-length: 456 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21324 --- Comment #2 from brian at ubuntu dot com --- Ubuntu was recently updated with a new version of gdb: GNU gdb (Ubuntu 7.99.90.20170502-0ubuntu1) 7.99.90.20170502-git I repeated the same test with the same crash and I'm still observing the sa= me behavior of gdb hanging and using 100% CPU. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21323-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 03 17:40:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 108522 invoked by alias); 3 May 2017 17:40:48 -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 108478 invoked by uid 48); 3 May 2017 17:40:48 -0000 From: "mjfoley at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21456] New: set print pretty on for macro expand Date: Wed, 03 May 2017 17:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: mjfoley at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00124.txt.bz2 Content-length: 702 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21456 Bug ID: 21456 Summary: set print pretty on for macro expand Product: gdb Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: mjfoley at gmail dot com Target Milestone: --- When macro expanding defined functions if print pretty is on, newlines and indentation similar to pretty printing nested structures could be added when encountering '{', '}', or ';' outside '()'. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21324-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 04 22:15:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 99845 invoked by alias); 4 May 2017 22:15:57 -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 99808 invoked by uid 48); 4 May 2017 22:15:56 -0000 From: "bugzilla at thepaul dot org" To: gdb-prs@sourceware.org Subject: [Bug python/21460] New: SIGTERM received under finalize_python() causes segmentation fault Date: Thu, 04 May 2017 22:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bugzilla at thepaul dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q2/txt/msg00125.txt.bz2 Content-length: 2199 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21460 Bug ID: 21460 Summary: SIGTERM received under finalize_python() causes segmentation fault Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: bugzilla at thepaul dot org Target Milestone: --- Created attachment 10038 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10038&action=3Ded= it script to reproduce bug Under the right conditions, if a SIGTERM signal is received by gdb while the embedded Python interpreter is being shut down, gdb can segfault. To be more specific: when gdb gets a SIGTERM and Python is the active exten= sion language, there is a call stack like this: handle_sigterm (15) set_quit_flag () gdbpy_set_quit_flag (active_ext_lang) PyErr_SetInterrupt () But PyErr_SetInterrupt must not be called after Python has turned off signal handling, which happens just *before* the final garbage collection. If it i= s, and Python happens to check for pending signals (among other times, this happens while Python code is being executed), then Python will try to call a handler for that signal, but the handler will be NULL because it's supposed= to be done with signal handling. Calling the NULL function pointer causes to t= he SIGSEGV. I am attaching a shell script which reliably produces the segfault for me o= n, at least, any of: * gdb built from the HEAD of gdb-8.0-branch * gdb built from tags/gdb-7.12.1-release * gdb 7.11.1-0ubuntu1~16.04 as distributed in Ubuntu 16.04 The script runs the gdb-under-test under another gdb instance, in order to issue the SIGTERM at just the right moment. As a fix, I believe gdbpy_set_quit_flag should simply check that Py_IsInitialized() is true before calling PyErr_SetInterrupt(). I'd make a teensy patch, but I don't want anyone to mistakenly think it is a thing that needs copyright protection or copyright assignment forms. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21325-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 05 17:17:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122286 invoked by alias); 5 May 2017 17:17:05 -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 122237 invoked by uid 48); 5 May 2017 17:17:03 -0000 From: "brian at ubuntu dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21324] gdb hangs when 'thread apply all bt full' is used Date: Fri, 05 May 2017 17:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: brian at ubuntu dot com 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: 2017-q2/txt/msg00126.txt.bz2 Content-length: 12841 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21324 --- Comment #3 from brian at ubuntu dot com --- As I mentioned previously the service I manage retraces crashes from any application on Ubuntu systems. I've ran across another crash from kodi on Ubuntu 16.10 that also manages to hang gdb. The behavior is different thou= gh as some information from the thread is displayed: (gdb) thread apply 43 bt full Thread 43 (Thread 0x7fc54c7e8700 (LWP 9950)): #0 0x00007fc61a3e40bd in poll () at ../sysdeps/unix/syscall-template.S:84 No locals. #1 0x00007fc621393247 in poll () at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 No locals. #2 internal_select_ex.isra.0 (writing=3D1, interval=3D30) at ../Modules/socketmodule.c:730 pollfd =3D {fd =3D 55, events =3D 4, revents =3D 0} #3 internal_select () at ../Modules/socketmodule.c:760 No locals. #4 internal_connect (timeoutp=3D, addrlen=3D, addr=3D0x7fc54c7e50d0, s=3D0x7fc59d494ea0) at ../Modules/socketmodule.c:2113 res =3D -1 timeout =3D 0 #5 sock_connect (s=3D, addro=3D) at ../Modules/socketmodule.c:2156 _save =3D 0x7fc5843d16f0 addrbuf =3D {in =3D {sin_family =3D 2, sin_port =3D 20480, sin_addr= =3D {s_addr =3D 2566652611}, sin_zero =3D "\000\000\000\000\000\000\000"}, un =3D {sun_fami= ly =3D 2, sun_path =3D "\000P\303\002\374\230\000\000\000\000\000\000\000\000\004", '\000' , "@\211\017\235\305\177\070\060P\347\034\244\305\177\000\000H\022\034\244\30= 5\177\000\000K9G!\306\177\000\000`Q~L\305\177\000\000 Q~L\305\177\000\000\360\026=3D\204\305\177\000\000\030U\353\365\305\177\000= \000\320hg\244\305\177\000\000\270\061\024\244\305\177"}, nl =3D {nl_family =3D 2, nl_pad =3D 20480, nl_pid =3D 2566652611, nl_groups= =3D 0}, in6 =3D {sin6_family =3D 2, sin6_port =3D 20480, sin6_flowinfo =3D 2566652611, sin6_addr =3D {__in6_u =3D {__u6_= addr8 =3D "\000\000\000\000\000\000\000\000\004\000\000\000\000\000\000", __u6_addr16= =3D {0, 0, 0, 0, 4, 0, 0, 0}, __u6_addr32 =3D {0, 0, 4, 0}}}, sin6_scope_id =3D 0}, storage =3D {ss_family =3D 2, __ss_padding =3D "\000P\303\002\374\230\000\000\000\000\000\000\000\000\004", '\000' , "@\211\017\235\305\177\070\060P\347\034\244\305\177\000\000H\022\034\244\30= 5\177\000\000K9G!\306\177\000\000`Q~L\305\177\000\000 Q~L\305\177\000\000\360\026=3D\204\305\177\000\000\030U\353\365\305\177\000= \000\320hg\244\305\177\000\000\270\061\024\244\305\177\000\000\000\000\000\= 000\000\000\000", __ss_align =3D 140486724472931}, bt_l2 =3D {l2_family =3D 2, l2_psm =3D 204= 80, l2_bdaddr =3D { b =3D "\303\002\374\230\000"}, l2_cid =3D 0, l2_bdaddr_type = =3D 0 '\000'}, bt_rc =3D {rc_family =3D 2, rc_bdaddr =3D { b =3D "\000P\303", }, rc_channe= l =3D 0 '\000'}, bt_sco =3D {sco_family =3D 2, sco_bdaddr =3D { b =3D "\000P\303", }}, bt_hci = =3D {hci_family =3D 2, hci_dev =3D 20480, hci_channel =3D 707}, ll =3D {sll_fam= ily =3D 2, sll_protocol =3D 20480, sll_ifindex =3D -1728314685, sll_hatype= =3D 0, sll_pkttype =3D 0 '\000', sll_halen =3D 0 '\000', sll_addr =3D "\000\000\000\000\004\000\000"}} addrlen =3D 16 timeout =3D #6 0x00007fc6213c77cf in ext_do_call (nk=3D, na=3D0, flags=3D, pp_stack=3D0x7fc54c7e5248, func=3D0x7fc5c4087170) = at ../Python/ceval.c:4661 tstate =3D kwdict =3D nstar =3D callargs =3D stararg =3D 0x7fc5a415b650 result =3D 0x0 #7 PyEval_EvalFrameEx (f=3D0x7fc59d4acd00, throwflag=3D) at ../Python/ceval.c:3026 flags =3D func =3D 0x7fc5c4087170 na =3D 0 nk =3D n =3D pfunc =3D 0x7fc59d4ace90 sp =3D 0x7fc59d4ace98 opcode_targets =3D {0x7fc6213bfc0d , 0x7fc6213c4b37 , 0x7fc6213c4b3c , 0x7fc6213c4b41 , 0x7fc6213c4b4b , 0x7fc6213c4b46 , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213c4adc , 0x7fc6213c4b6c , 0x7fc6213c4b71 , 0x7fc6213c4b76 , 0x7fc6213c4b7b , 0x7fc6213bfc0d , 0x7fc6213c4b80 , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213c4b85 , 0x7fc6213c4b8a , 0x7fc6213c4b8f , 0x7fc6213c4b9e , 0x7fc6213c4ba3 , 0x7fc6213c4ba8 , 0x7fc6213c4bad , 0x7fc6213c4b99 , 0x7fc6213c4b94 , 0x7fc6213c5c4b , 0x7fc6213c5c46 , 0x7fc6213c5c78 , 0x7fc6213c5c88 , 0x7fc6213c5c95 , 0x7fc6213c5ca2 , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213c5cb2 , 0x7fc6213c5cc5 , 0x7fc6213c48f3 , 0x7fc6213c5cd5 , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213c456f , 0x7fc6213c5ce5 , 0x7fc6213c45bd , 0x7fc6213c5cf5 , 0x7fc6213c592a , 0x7fc6213c5c55 , 0x7fc6213c5c5a , 0x7fc6213c5c3c , 0x7fc6213c5c41 , 0x7fc6213c5c50 , 0x7fc6213c5d05 , 0x7fc6213c5d0a , 0x7fc6213c4bb2 , 0x7fc6213c4bb7 , 0x7fc6213c4bbc , 0x7fc6213c4bc1 , 0x7fc6213c5bfa , 0x7fc6213c5c37 , 0x7fc6213c5a47 , 0x7fc6213bfc0d , 0x7fc6213c5d0f , 0x7fc6213bfa98 , 0x7fc6213c0141 , 0x7fc6213bfa86 , 0x7fc6213c012f , 0x7fc6213c5c5f , 0x7fc6213c5c64 , 0x7fc6213c5c69 , 0x7fc6213c5c6e , 0x7fc6213c5c73 , 0x7fc6213c2185 , 0x7fc6213c5afc , 0x7fc6213c7590 , 0x7fc6213c3082 , 0x7fc6213c59a3 , 0x7fc6213c7595 , 0x7fc6213c32f3 , 0x7fc6213c759a , 0x7fc6213c613a , 0x7fc6213c6142 , 0x7fc6213c614c , 0x7fc6213c6169 , 0x7fc6213c6183 , 0x7fc6213c5a4c , 0x7fc6213c5bff , 0x7fc6213c619f , 0x7fc6213c61b8 , 0x7fc6213c61d4 , 0x7fc6213c61f0 , 0x7fc6213c4b50 , 0x7fc6213c4afe , 0x7fc6213c6209 , 0x7fc6213c62af , 0x7fc6213c58d6 , 0x7fc6213c58f3 , 0x7fc6213c590d , 0x7fc6213c5948 , 0x7fc6213c5962 , 0x7fc6213c5984 , 0x7fc6213c59a8 , 0x7fc6213c59c5 , 0x7fc6213c5a15 , 0x7fc6213c5a2e , 0x7fc6213c1f65 , 0x7fc6213c59dd , 0x7fc6213c59f9 , 0x7fc6213c6227 , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213c5a69 , 0x7fc6213c5a85 , 0x7fc6213c5aa4 , 0x7fc6213c5ac3 , 0x7fc6213bfc0d , 0x7fc6213c4ae1 , 0x7fc6213c4b1b , 0x7fc6213c6241 , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213c7572 , 0x7fc6213c2b0f , 0x7fc6213c5ba6 , 0x7fc6213c5be0 , 0x7fc6213c5bc3 , 0x7fc6213c625b , 0x7fc6213c6278 , 0x7fc6213c6292 , 0x7fc6213bfc0d , 0x7fc6213bfc0d , 0x7fc6213c5b04 , 0x7fc6213c5b3c , 0x7fc6213c5b82 , 0x7fc6213c5ae2 , 0x7fc6213bfc0d , 0x7fc6213c2d62 , 0x7fc6213c5c1b , 0x7fc6213c592f , 0x7fc6213bfc0d } stack_pointer =3D next_instr =3D opcode =3D oparg =3D why =3D WHY_NOT err =3D 0 x =3D 0x7fc5a46db850 v =3D w =3D u =3D t =3D stream =3D 0x0 fastlocals =3D 0x7fc59d4ace78 freevars =3D retval =3D tstate =3D co =3D instr_ub =3D instr_lb =3D instr_prev =3D first_instr =3D names =3D consts =3D #8 0x00007fc62151f99c in PyEval_EvalCodeEx (co=3D, globals=3D, locals=3D, args=3D, argcount=3D3, kws=3D0x0, kwcount=3D0, defs=3D0x0, defcount=3D0, closure=3D0x0) at ../Python/ceva= l.c:3582 f =3D 0x7fc59d4acd00 retval =3D 0x0 fastlocals =3D 0x7fc59d4ace78 ---Type to continue, or q to quit--- freevars =3D 0x7fc59d4ace90 tstate =3D 0x7fc5843d16f0 x =3D u =3D #9 0x00007fc6214cd170 in function_call.lto_priv.355 (func=3D0x7fc59d5ba5f0, arg=3D0x7fc5a47c0c80, kw=3D0x0) at ../Objects/funcobject.c:523 result =3D argdefs =3D kwtuple =3D 0x0 d =3D 0x0 k =3D 0x0 nk =3D 0 nd =3D 0 And that was the last bit of output before the hang. Again this was with gdb version: GNU gdb (Ubuntu 7.99.90.20170502-0ubuntu1) 7.99.90.20170502-git --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21327-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 05 20:47:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 115376 invoked by alias); 5 May 2017 20:47: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 115348 invoked by uid 48); 5 May 2017 20:47:22 -0000 From: "smark at datto dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21462] gdb hangs when pretty printing some variables in eclipse cdt Date: Fri, 05 May 2017 20:47: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: smark at datto dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00128.txt.bz2 Content-length: 374 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21462 smark at datto dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |smark at datto dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21326-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 05 20:47:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 114949 invoked by alias); 5 May 2017 20:47:09 -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 114927 invoked by uid 48); 5 May 2017 20:47:08 -0000 From: "smark at datto dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21462] New: gdb hangs when pretty printing some variables in eclipse cdt Date: Fri, 05 May 2017 20:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: smark at datto dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q2/txt/msg00127.txt.bz2 Content-length: 2033 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21462 Bug ID: 21462 Summary: gdb hangs when pretty printing some variables in eclipse cdt Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: smark at datto dot com Target Milestone: --- Created attachment 10039 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10039&action=3Ded= it a list of stack traces from spinning gdb, plus a bit of the eclipse gdb log I wrote up a question here which basically states the problem, and somebody suggested posting to the mailing list, but I didn't see how, so I thought I= 'd open a bug. http://stackoverflow.com/questions/43743703/anybody-have-a-workaround-for-g= db-hanging-while-rendering-pretty-print-in-eclips I've updated to eclipse neon, I svn updated to the latest svn://gcc.gnu.org/svn/gcc/trunk/libstdc++-v3/python, and I've just built gdb 7.12.1, all the latest stuff, doesn't help. I have the pretty printing all working, but every once in a while, trying to update the variables view, gdb will hang. Actually it spins the cpu. I've attached gdb to gdb (because I find the idea amusing) and have gotten a num= ber of stack traces and they're all implying some failure to find a printer and retrying over and over. Anybody ever see this or have a workaround? It's not obvious which printer (if it's a single one) is causing the problem, or I'd just disable it. Suggestions on how to even diagnose what printer to disable? I google and google and nobody complains of this behaviour, but having reinstalled everything, I don't get why it's not happening to anybody else. Last time I ran into the problem I got some more stack traces and it eventu= ally hung in one spot. See the attached text file of stack traces. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21328-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat May 06 05:20:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 11495 invoked by alias); 6 May 2017 05:20:14 -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 10949 invoked by uid 48); 6 May 2017 05:19:24 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21460] SIGTERM received under finalize_python() causes segmentation fault Date: Sat, 06 May 2017 05:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00129.txt.bz2 Content-length: 871 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21460 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #1 from Sergio Durigan Junior --- Thanks for the report and for the investigation. I encourage you to submit the patch to gdb-patches@sourceware.org. From wh= at you described it'll be a very simple patch (probably one or two lines long), and we don't require copyright assignment for those. Worst case scenario, someone can take your patch and build upon it, without requiring you to go through the paperwork. Cheers. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21329-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat May 06 15:47:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 124623 invoked by alias); 6 May 2017 15:47:12 -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 124309 invoked by uid 48); 6 May 2017 15:47:11 -0000 From: "jothiram.s at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20981] Dynamic library debugging on MacOS X 10.12 (Sierra) and dyld 15 is broken Date: Sat, 06 May 2017 15:47: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jothiram.s at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00130.txt.bz2 Content-length: 390 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20981 Joe changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jothiram.s at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21330-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat May 06 15:51:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68001 invoked by alias); 6 May 2017 15:51:24 -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 67741 invoked by uid 48); 6 May 2017 15:51:23 -0000 From: "jothiram.s at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20981] Dynamic library debugging on MacOS X 10.12 (Sierra) and dyld 15 is broken Date: Sat, 06 May 2017 15:51: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jothiram.s at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00131.txt.bz2 Content-length: 435 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20981 --- Comment #2 from Joe --- In my case, the gdb is starting the original program successfully, but=20 gdb) info shared does not show any information. Also, the break points that I had set in the shared library are not detected and the execution does not stop there. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21331-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat May 06 22:42:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63901 invoked by alias); 6 May 2017 22:42:44 -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 63878 invoked by uid 48); 6 May 2017 22:42:43 -0000 From: "dilyan.palauzov at aegee dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21465] New: Installing scripts in auto-load scripts-directory Date: Sat, 06 May 2017 22:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dilyan.palauzov at aegee dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00132.txt.bz2 Content-length: 2421 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21465 Bug ID: 21465 Summary: Installing scripts in auto-load scripts-directory Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: dilyan.palauzov at aegee dot org Target Milestone: --- If an Autotools package wants to install a -gdb.py script under "auto-load scripts-directory" during "make install", what is the procedure to determine the destination path? I wrote this code: AC_CHECK_PROG(gdb, gdb, found) if $gdb =3D found; then GDB_AUTO_LOAD_SCRIPTS_DIRECTORY=3D$(gdb -q -ex "show data-directory" -ex = "show auto-load scripts-directory" -ex quit |sed "1d;2{N;s/\n//g; s/.*\"\(.*\)\".*:\(.*\)./\1 \2/}; /\$datadir/ {s/\(.*\) \$datadir\(.*\)/\1\2/;q}; s/.* \(.\)/\1/") else GDB_AUTO_LOAD_SCRIPTS_DIRECTORY=3D'${datadir}/gdb/auto-load/${libdir}' fi AC_SUBST(GDB_AUTO_LOAD_SCRIPTS_DIRECTORY) which exposes the current "auto-load scripts-directory" to the Makefile Isn't there a better way? show configuration prints: This GDB was configured as follows: configure --host=3Dx86_64-pc-linux-gnu --target=3Dx86_64-pc-linux-gnu --with-auto-load-dir=3D$debugdir:$datadir/auto-load --with-auto-load-safe-path=3D$debugdir:$datadir/auto-load --with-expat --with-gdb-datadir=3D/usr/local/share/gdb (relocatable) --with-jit-reader-dir=3D/usr/local/lib/gdb (relocatable) --without-libunwind-ia64 --with-lzma --with-python=3D/usr/local (relocatable) --with-guile --with-separate-debug-dir=3D/usr/local/lib/debug (relocatable) --without-babeltrace ("Relocatable" means the directory can be moved with the GDB installation tree, and GDB will still find it.) info '(gdb)Data Files': If the data directory is inside GDB's configured binary prefix (set with '--prefix' or '--exec-prefix'), then the default data directory will be upd= ated automatically if the installed GDB is moved to a new location. and my gdb is in /usr/local/bin. Where shall I move gdb, so that 'show configurtion' prints something differ= ent for '--with-gdb-datadir'? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21332-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 07 00:32:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 91343 invoked by alias); 7 May 2017 00:32:26 -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 91295 invoked by uid 48); 7 May 2017 00:32:23 -0000 From: "dilyan.palauzov at aegee dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21465] Installing scripts in auto-load scripts-directory Date: Sun, 07 May 2017 00:32: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dilyan.palauzov at aegee dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00133.txt.bz2 Content-length: 649 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21465 --- Comment #1 from dilyan.palauzov at aegee dot org --- I mean AC_CHECK_PROG(gdb, gdb, found) if $gdb =3D found; then GDB_AUTO_LOAD_SCRIPTS_DIRECTORY=3D$(gdb -q -ex "show data-directory" -ex = "show auto-load scripts-directory" -ex quit |sed "1d;2{N;s/\n//g; s/.*\"\(.*\)\".*:\(.*\)./\1 \2/}; /\$datadir/ {s/\(.*\) \$datadir\(.*\)/\1\2/;q}; s/.* \(.\)/\1/") else GDB_AUTO_LOAD_SCRIPTS_DIRECTORY=3D'${datadir}/gdb/auto-load' fi AC_SUBST(GDB_AUTO_LOAD_SCRIPTS_DIRECTORY) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21333-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 07 00:45:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27484 invoked by alias); 7 May 2017 00:45:33 -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 27238 invoked by uid 48); 7 May 2017 00:45:15 -0000 From: "dilyan.palauzov at aegee dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21465] Installing scripts in auto-load scripts-directory Date: Sun, 07 May 2017 00:45: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dilyan.palauzov at aegee dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00134.txt.bz2 Content-length: 646 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21465 --- Comment #2 from dilyan.palauzov at aegee dot org --- AC_CHECK_PROG(gdb, gdb, found) if test $gdb =3D found; then GDB_AUTO_LOAD_SCRIPTS_DIRECTORY=3D$(gdb -q -ex "show data-directory" -ex = "show auto-load scripts-directory" -ex quit |sed "1d;2{N;s/\n//g; s/.*\"\(.*\)\".*:\(.*\)./\1 \2/}; /\$datadir/ {s/\(.*\) \$datadir\(.*\)/\1\2/;q}; s/.* \(.\)/\1/") else GDB_AUTO_LOAD_SCRIPTS_DIRECTORY=3D'${datadir}/gdb/auto-load' fi AC_SUBST(GDB_AUTO_LOAD_SCRIPTS_DIRECTORY) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21334-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 07 05:31:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4794 invoked by alias); 7 May 2017 05:31:12 -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 4678 invoked by uid 48); 7 May 2017 05:31:06 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21466] New: better printing of unsized types Date: Sun, 07 May 2017 05:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00135.txt.bz2 Content-length: 1221 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21466 Bug ID: 21466 Summary: better printing of unsized types Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- I found this example on reddit (https://www.reddit.com/r/rust/comments/60ywnb/initializing_a_dynamically_s= ized_type/) struct Bar { info: u32, data: T, } type Foo =3D Bar<[u8]>; fn main() { let x: Box> =3D Box::new(Bar { info: 0, data: [1, 2, 3] }); let y: Box =3D x; } I had to add "let z =3D y" to get debuginfo for "y". Then running in gdb I get: (gdb) p *y $2 =3D us::Bar<[u8]> { info: 0, data: 0x7ffff6c1f014 } ... but that doesn't seem very friendly; in fact it seems odd that the array's address is printed. Also the ptype output is a bit off: (gdb) ptype *y type =3D struct us::Bar<[u8]> { info: u32, data: [u8; ], } It ought to print "data: [u8]" there. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21335-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 07 11:06:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 12289 invoked by alias); 7 May 2017 11:06:51 -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 12258 invoked by uid 48); 7 May 2017 11:06:50 -0000 From: "dedeco.balaco at yahoo dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21467] New: Display function shows one less byte when the last one is \000 Date: Sun, 07 May 2017 11:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 7.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: dedeco.balaco at yahoo dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00136.txt.bz2 Content-length: 2456 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21467 Bug ID: 21467 Summary: Display function shows one less byte when the last one is \000 Product: gdb Version: 7.1 Status: UNCONFIRMED Severity: minor Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: dedeco.balaco at yahoo dot com Target Milestone: --- Display function, in GDBTUI, with an @ element, shows one less byte when the last one is \000. Showing this is probably easier for all to see it clearly. I will try to ma= ke a few steps to anyone reproduce this problem. 1. Given the file p.c: =3D=3D #include int main(int c, char **v) { char p[10] =3D {'a','b','c','d','e',0,0,0,0,0}; printf("p =3D \"%s\"\n", p); return 0; } =3D=3D compile it with: gcc -Wall -ggdb p.c 2. Call gdbtui with: gdbtui a.out 3. Inside gdbtui, do these commands: =3D=3D start n n disp p[0]@5 disp p[0]@6 disp p[0]@7 disp p[0]@8 disp p[0]@9 disp p[0]@10 disp =3D=3D Compare the output for each command. The last null byte is not shown. With a counter given (the "@n"), I expect to *see* all the values I asked. For a s= mall number of values, it is easy. But with a few more being shown, we must count all of them to know which is the case: are we seeing the last value or is it zero? After doing the above steps, the output of the last disp is: =3D=3D (gdb) disp 6: p[0]@10 =3D "abcde\000\000\000\000" 5: p[0]@9 =3D "abcde\000\000\000" 4: p[0]@8 =3D "abcde\000\000" 3: p[0]@7 =3D "abcde\000" 2: p[0]@6 =3D "abcde" 1: p[0]@5 =3D "abcde" (gdb)=20 =3D=3D P.S.: A small observation to something that I did not find a proper place, "Environment", as pointed at http://www.gnu.org/software/gdb/bugs/ is that = the output of "gdbtui --version" command is: =3D=3D $ gdbtui --version GNU gdb (GDB) 7.1-ubuntu Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu". For bug reporting instructions, please see: . =3D=3D --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21336-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 07 11:07:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 13965 invoked by alias); 7 May 2017 11:07:45 -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 13859 invoked by uid 48); 7 May 2017 11:07:44 -0000 From: "dedeco.balaco at yahoo dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21468] New: Display function shows one less byte when the last one is \000 Date: Sun, 07 May 2017 11:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 7.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: dedeco.balaco at yahoo dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00137.txt.bz2 Content-length: 2456 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21468 Bug ID: 21468 Summary: Display function shows one less byte when the last one is \000 Product: gdb Version: 7.1 Status: UNCONFIRMED Severity: minor Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: dedeco.balaco at yahoo dot com Target Milestone: --- Display function, in GDBTUI, with an @ element, shows one less byte when the last one is \000. Showing this is probably easier for all to see it clearly. I will try to ma= ke a few steps to anyone reproduce this problem. 1. Given the file p.c: =3D=3D #include int main(int c, char **v) { char p[10] =3D {'a','b','c','d','e',0,0,0,0,0}; printf("p =3D \"%s\"\n", p); return 0; } =3D=3D compile it with: gcc -Wall -ggdb p.c 2. Call gdbtui with: gdbtui a.out 3. Inside gdbtui, do these commands: =3D=3D start n n disp p[0]@5 disp p[0]@6 disp p[0]@7 disp p[0]@8 disp p[0]@9 disp p[0]@10 disp =3D=3D Compare the output for each command. The last null byte is not shown. With a counter given (the "@n"), I expect to *see* all the values I asked. For a s= mall number of values, it is easy. But with a few more being shown, we must count all of them to know which is the case: are we seeing the last value or is it zero? After doing the above steps, the output of the last disp is: =3D=3D (gdb) disp 6: p[0]@10 =3D "abcde\000\000\000\000" 5: p[0]@9 =3D "abcde\000\000\000" 4: p[0]@8 =3D "abcde\000\000" 3: p[0]@7 =3D "abcde\000" 2: p[0]@6 =3D "abcde" 1: p[0]@5 =3D "abcde" (gdb)=20 =3D=3D P.S.: A small observation to something that I did not find a proper place, "Environment", as pointed at http://www.gnu.org/software/gdb/bugs/ is that = the output of "gdbtui --version" command is: =3D=3D $ gdbtui --version GNU gdb (GDB) 7.1-ubuntu Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu". For bug reporting instructions, please see: . =3D=3D --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21337-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 07 15:29:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 73076 invoked by alias); 7 May 2017 15:29:56 -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 73027 invoked by uid 48); 7 May 2017 15:29:55 -0000 From: "dilyan.palauzov at aegee dot org" To: gdb-prs@sourceware.org Subject: [Bug build/10619] gdb - Manual and info pages should present GNU --long options Date: Sun, 07 May 2017 15:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 6.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: dilyan.palauzov at aegee dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 6.8 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q2/txt/msg00138.txt.bz2 Content-length: 1024 https://sourceware.org/bugzilla/show_bug.cgi?id=3D10619 dilyan.palauzov at aegee dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dilyan.palauzov at aegee d= ot org --- Comment #1 from dilyan.palauzov at aegee dot org --- ./gdb -h versus info '(gdb)Mode Options' Info nodes "Choosing modes" and "Startup', write about "-nx" with one dash,= but "gdb -h" speaks about "--nx" with two dashes. Likewise for "-nh"/"--nh". gdb -h does not mention just "-n". In fact 'Choosing modes' mentions every option with one dash, while "gdb -h" states that only single-letter options are with one dash. All of the single-dash/double-dash long-name options I tried do work, but t= his does not justify inconsistent documentation. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21338-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 07 15:39:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 103986 invoked by alias); 7 May 2017 15:39:15 -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 103952 invoked by uid 48); 7 May 2017 15:39:15 -0000 From: "dilyan.palauzov at aegee dot org" To: gdb-prs@sourceware.org Subject: [Bug mi/21469] New: -gdb-show and data-directory Date: Sun, 07 May 2017 15:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dilyan.palauzov at aegee dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00139.txt.bz2 Content-length: 925 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21469 Bug ID: 21469 Summary: -gdb-show and data-directory Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: mi Assignee: unassigned at sourceware dot org Reporter: dilyan.palauzov at aegee dot org Target Milestone: --- echo "-gdb-show data" | gdb --interpreter=3Dmi and echo "-gdb-show data-directory" | gdb --interpreter=3Dmi both print: =3Dthread-group-added,id=3D"i1" (gdb)=20 ^done (gdb)=20 How to get data-directory using mi? This does not work contrary to my expectations: gdb --interpreter=3Dmi -ex "-gdb-show" I think interpreter-exec called from CLI shall always disable pagination, a= s in gdb -ex "interpreter-exec mi -gdb-show" . --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21339-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 07 17:15:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 50961 invoked by alias); 7 May 2017 17:15:54 -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 50935 invoked by uid 48); 7 May 2017 17:15:53 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug symtab/21470] New: gdb producer-sniffs for "clang" Date: Sun, 07 May 2017 17:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00140.txt.bz2 Content-length: 857 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21470 Bug ID: 21470 Summary: gdb producer-sniffs for "clang" Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- It came up on a rust bug (https://github.com/rust-lang/rust/issues/41252) that gdb producer-sniffs for "clang" (e.g. in i386-tdep.c). A simple fix would be to allow "rustc" as well here. There doesn't seem to be a generic way to sniff for "LLVM back end". However, I wonder whether it makes sense now to switch to a producer blacklist rather than a whitelist. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21340-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 07 22:50:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 55822 invoked by alias); 7 May 2017 22:50:50 -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 55196 invoked by uid 48); 7 May 2017 22:50:50 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug symtab/21470] gdb producer-sniffs for "clang" Date: Sun, 07 May 2017 22:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q2/txt/msg00141.txt.bz2 Content-length: 357 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21470 --- Comment #1 from Tom Tromey --- I'm testing a patch for this, that changes gdb to use a blacklist instead. I'm not sure if this will be acceptable, since the initial blacklist is empty. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21341-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon May 08 13:46:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 82980 invoked by alias); 8 May 2017 13:46:13 -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 82063 invoked by uid 48); 8 May 2017 13:46:12 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug symtab/21470] gdb producer-sniffs for "clang" Date: Mon, 08 May 2017 13:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q2/txt/msg00142.txt.bz2 Content-length: 489 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21470 --- Comment #2 from Tom Tromey --- Maybe this was wishful thinking since there are some regressions if I switch to an empty blacklist. I'm still looking into whether maybe there are just certain old versions of gcc (4.x perhaps) that were bad here. Otherwise, I have a different patch that just adds rustc to the check. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21342-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon May 08 18:09:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 103985 invoked by alias); 8 May 2017 18:09: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 103952 invoked by uid 48); 8 May 2017 18:09:51 -0000 From: "eggert at gnu dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21473] New: wrong type info for extern inline function when debugging Emacs Date: Mon, 08 May 2017 18:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: eggert at gnu dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q2/txt/msg00143.txt.bz2 Content-length: 1837 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21473 Bug ID: 21473 Summary: wrong type info for extern inline function when debugging Emacs Product: gdb Version: 7.12.1 Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: eggert at gnu dot org Target Milestone: --- Created attachment 10042 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10042&action=3Ded= it gzipped tarball of three source files illustrating the bug On x86-64, GDB Fedora 7.12.1-48.fc25 has problems decoding debugging information generated by GCC 6.3.1 20161221 (Red Hat 6.3.1-1). The problem = does not occur when I use GCC 4.8.5 20150623 (Red Hat 4.8.5-11) to compile. Alth= ough I originally reported this as a GCC bug , Richard Biener star= ts to believe that it is a GDB bug.=20 I ran into the problem while attempting to debug GNU Emacs, and constructed= a small test case to illustrate it. To reproduce it on Fedora 25 x86-64, extr= act the files lisp.h, t.c and u.c from the attached tarball, and compile them by running the shell command: gcc -g3 -O2 t.c u.c Then use GDB as follows: $ gdb a.out ... (gdb) ptype make_number type =3D int () (gdb) ptype make_natnum type =3D struct { long i; } (long) (gdb) ptype XIL type =3D struct { long i; } (long) (gdb) The reported type of 'make_number' is incorrect: it should be the same type= as that of make_natnum and XIL, but instead is a function returning 'int'. This incorrect type can cause GDB to print incorrect results in expressions involving make_number. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21343-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue May 09 19:07:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 74544 invoked by alias); 9 May 2017 19:07:48 -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 74507 invoked by uid 48); 9 May 2017 19:07:48 -0000 From: "Olivier.Perret at mailbox dot org" To: gdb-prs@sourceware.org Subject: [Bug mi/21477] New: gdb sometimes dies when new-ui pty is closed Date: Tue, 09 May 2017 19:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: Olivier.Perret at mailbox dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00144.txt.bz2 Content-length: 943 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21477 Bug ID: 21477 Summary: gdb sometimes dies when new-ui pty is closed Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: mi Assignee: unassigned at sourceware dot org Reporter: Olivier.Perret at mailbox dot org Target Milestone: --- Reproducer: 1. Start a gdb session somewhere 2. In a terminal (same cwd), run `socat pty,link=3Dpty STDIO,nonblock=3D1`. 3. In the gdb session, run `new-ui mi3 pty`. 4. Ctrl+C the socat process.=20 Repeat steps 2 to 4 until the gdb also exits (about 20% of the time in my case). About 20% of the time, the gdb process also exits.=20 Also reproducible by using a "real" pty such as /dev/pts/*, but my use-case= is with socat. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21344-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue May 09 21:12:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 46211 invoked by alias); 9 May 2017 21:12:07 -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 46182 invoked by uid 48); 9 May 2017 21:12:07 -0000 From: "dilyan.palauzov at aegee dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21478] New: gdb.texinfo: node Index Files: mention gold --gdb-index Date: Tue, 09 May 2017 21:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dilyan.palauzov at aegee dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00145.txt.bz2 Content-length: 1074 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21478 Bug ID: 21478 Summary: gdb.texinfo: node Index Files: mention gold --gdb-index Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: dilyan.palauzov at aegee dot org Target Milestone: --- diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -19240,7 +19240,8 @@ The index is stored as a section in the symbol file= .=20 @value{GDBN} can write the index to a file, then you can put it into the symbol file using @command{objcopy}. -To create an index file, use the @code{save gdb-index} command: +To create an index file, link with @command{ld.gold --gdb-index} or use +the @code{save gdb-index} command: @table @code @item save gdb-index @var{directory} --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21345-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 10 13:27:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 103751 invoked by alias); 10 May 2017 13:27:00 -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 103298 invoked by uid 48); 10 May 2017 13:27:00 -0000 From: "alexandre.nunes at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21480] New: Gdb can't pretty print strings from gcc 7.1/6.3 with -flto Date: Wed, 10 May 2017 13:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: alexandre.nunes at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q2/txt/msg00146.txt.bz2 Content-length: 1414 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21480 Bug ID: 21480 Summary: Gdb can't pretty print strings from gcc 7.1/6.3 with -flto Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: minor Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: alexandre.nunes at gmail dot com Target Milestone: --- Created attachment 10045 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10045&action=3Ded= it testcase With this example, compiled with g++ -ggdb3 -std=3Dgnu++1z -Og and with/wit= hout -flto: #include #include static void print(const std::string &s) { std::cout << s << "\n"; } int main() { std::string s("test"); print(s); } if we set a breakpoint in the print function, run and type "p s": without lto: Breakpoint 1, print (s=3D"test") at test.cpp:4 4 { (gdb) p s $1 =3D "test" (gdb)=20 with -flto: Breakpoint 1, print (s=3D...) at test.cpp:4 4 { (gdb) p s $1 =3D (const string &) @0x7fffffffdfd0: {_M_dataplus =3D {_M_p =3D 0x7ffff= fffdfe0 "test"}, _M_string_length =3D 4, { _M_local_buf =3D "test\000\177\000\000\000\000\000\000\000\000\000", _M_allocated_capacity =3D 139639930447220}} (gdb) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21346-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 10 13:28:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 28245 invoked by alias); 10 May 2017 13:28:13 -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 26828 invoked by uid 48); 10 May 2017 13:28:10 -0000 From: "alexandre.nunes at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21480] Gdb can't pretty print strings from gcc 7.1/6.3 with -flto Date: Wed, 10 May 2017 13:28: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: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: alexandre.nunes at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00147.txt.bz2 Content-length: 271 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21480 --- Comment #1 from alexandre.nunes at gmail dot com --- Arch is x86_64, compilers tested: g++-6.3 & 7.1 from debian and 7.1 vanilla. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21347-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 10 23:53:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 55010 invoked by alias); 10 May 2017 23:53:54 -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 54979 invoked by uid 48); 10 May 2017 23:53:54 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug symtab/21470] gdb producer-sniffs for "clang" Date: Wed, 10 May 2017 23:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q2/txt/msg00148.txt.bz2 Content-length: 1007 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21470 --- Comment #3 from Tom Tromey --- One specific regression is gdb.ada/ref_param.exp, which fails because gdb starts believing the DWARF line table. But I think the line table is correct and the test might be wrong. CU: /home/tromey/gdb/binutils-gdb/gdb/testsuite/gdb.ada/ref_param/pck.adb: File name Line number Starting address pck.adb 18 0x4012be pck.adb 18 0x4012be pck.adb 20 0x4012c6 pck.adb 21 0x4012d7 pck.adb 23 0x4012e5 With my current patch, the breakpoint is set on line 18. Without it, it is set at line 20. Doesn't line 18 seem correct though? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21348-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 11 11:53:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 52700 invoked by alias); 11 May 2017 11:53:47 -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 51636 invoked by uid 48); 11 May 2017 11:53:47 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug build/8379] configure --program-suffix does not work for gdbserver Date: Thu, 11 May 2017 11:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 5.3 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution 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: 2017-q2/txt/msg00149.txt.bz2 Content-length: 617 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8379 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |sergiodj at redhat dot com Resolution|--- |FIXED --- Comment #1 from Sergio Durigan Junior --- Closing as it's fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21349-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 11 11:59:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 43737 invoked by alias); 11 May 2017 11:59:01 -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 43697 invoked by uid 48); 11 May 2017 11:59:00 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug build/9322] linux-low.c: In function `kill_lwp': error: `__NR_tkill' undeclared Date: Thu, 11 May 2017 11:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 6.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution 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: 2017-q2/txt/msg00150.txt.bz2 Content-length: 739 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9322 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |sergiodj at redhat dot com Resolution|--- |FIXED --- Comment #2 from Sergio Durigan Junior --- Old bug report, don't see how to reproduce it. It's probably been fixed a = log time ago. I'm closing it. Feel free to reopen if still valid. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21350-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 11 14:16:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 57242 invoked by alias); 11 May 2017 14:16:01 -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 57150 invoked by uid 48); 11 May 2017 14:16:00 -0000 From: "ro at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tui/21482] New: gdb 8.0 tui doesn't build with native curses on Solaris Date: Thu, 11 May 2017 14:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget Message-ID: 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: 2017-q2/txt/msg00151.txt.bz2 Content-length: 3131 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21482 Bug ID: 21482 Summary: gdb 8.0 tui doesn't build with native curses on Solaris Product: gdb Version: 8.0 Status: NEW Severity: normal Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: ro at gcc dot gnu.org Target Milestone: --- Target: *-*-solaris2.* When trying to build the gdb 8.0 branch with native curses on Solaris 10 (Solaris 11 and 12 include ncurses as well, and it's found by default), I r= an into a couple of issues: * Initially, compilation failed like this: In file included from /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/gdb_curses.h:42: 0, from /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-data.h:2 6, from /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-disasm.c :31: /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-disasm.c: In function =E2= =80=98CORE_A DDR tui_disassemble(gdbarch*, tui_asm_line*, CORE_ADDR, int)=E2=80=99: /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-disasm.c:71:19: error: = =E2=80=98class string_file=E2=80=99 has no member named =E2=80=98wclear=E2=80=99; did you= mean =E2=80=98clear=E2=80=99? gdb_dis_out.clear (); ^ /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-disasm.c:78:19: error: = =E2=80=98class string_file=E2=80=99 has no member named =E2=80=98wclear=E2=80=99; did you= mean =E2=80=98clear=E2=80=99? gdb_dis_out.clear (); ^ make[2]: *** [Makefile:1927: tui-disasm.o] Error 1 It turned out this happens because has #define clear() wclear(stdscr) this can be avoided by defining NOMACROS, however, like make CFLAGS+=3D-DNOMACROS CXXFLAGS+=3D-DNOMACROS * While this gets around the wclear/clear issue above, I ran into another issue: /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-winsource.c: In function =E2=80=98void tui_erase_source_content(tui_win_info*, int)=E2=80=99: /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-winsource.c:257:18: error: invalid conversion from =E2=80=98const char*=E2=80=99 to =E2=80=98char*=E2= =80=99 [-fpermissive] no_src_str); ^ In file included from /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/gdb_curses.h:42:0, from /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-data.h:26, from /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-winsource.c:33: /vol/gcc-7/lib/gcc/sparc-sun-solaris2.10/7.1.0/include-fixed/curses.h:699:1= 2: note: initializing argument 4 of =E2=80=98int mvwaddstr(WINDOW*, int, int= , char*)=E2=80=99 extern int mvwaddstr(WINDOW *, int, int, char *); ^~~~~~~~~ make[2]: *** [Makefile:1927: tui-winsource.o] Error 1 Unlike ncurses, declares=20 extern int mvwaddstr(WINDOW *, int, int, char *); * In the end, I've just avoided the issue by configuring with --disable-tui. Rainer --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21351-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 11 18:04:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 22752 invoked by alias); 11 May 2017 18:04:27 -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 22721 invoked by uid 48); 11 May 2017 18:04:27 -0000 From: "jrmuizel at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21483] New: Rust expression evaluation can be really expensive Date: Thu, 11 May 2017 18:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jrmuizel at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00152.txt.bz2 Content-length: 1499 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21483 Bug ID: 21483 Summary: Rust expression evaluation can be really expensive Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: jrmuizel at gmail dot com Target Milestone: --- STR: $ git clone https://github.com/servo/webrender $ cd webrender/wrench $ cargo build --release $ gdb --args ../target/release/wrench show reftests/text/text.yaml (gdb) rb Renderer::render (gdb) r Thread 1 "wrench" hit Breakpoint 2, webrender::renderer::Renderer::render (self=3D0x7fffffff9298, framebuffer_size=3D...) at /home/jrmuizel/src/webrender/webrender/src/renderer.rs:1251 1251 pub fn render(&mut self, framebuffer_size: DeviceUintSize) { (gdb) c Thread 1 "wrench" hit Breakpoint 2, webrender::renderer::Renderer::render (self=3D0x7fffffff9298, framebuffer_size=3D...) at /home/jrmuizel/src/webrender/webrender/src/renderer.rs:1251 1251 pub fn render(&mut self, framebuffer_size: DeviceUintSize) { (gdb) p self.current_frame.0.frame.0.passes.buf.ptr.pointer.0[0].color_targets.targ= ets.buf.ptr.pointer.0[0].alpha_batcher.tasks.buf.ptr.pointer.0[0].items.buf= .ptr rust_evaluate_subexp is called roughly 760939 times to evaluate this expres= sion --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21352-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 11 18:06:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 25321 invoked by alias); 11 May 2017 18:06:45 -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 25285 invoked by uid 48); 11 May 2017 18:06:45 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21484] New: watch -location does not work with rust Date: Thu, 11 May 2017 18:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00153.txt.bz2 Content-length: 721 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21484 Bug ID: 21484 Summary: watch -location does not work with rust Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- In rust code, watch -location doesn't work: (gdb) watch -location a syntax error in expression, near `) 0x00007fffffffe0f4'. The problem is how watch -location rewrites the expression. This has to be language-dependent. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21353-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 11 18:10:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35414 invoked by alias); 11 May 2017 18:10:17 -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 35378 invoked by uid 48); 11 May 2017 18:10:17 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21484] watch -location does not work with rust Date: Thu, 11 May 2017 18:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: cc 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: 2017-q2/txt/msg00154.txt.bz2 Content-length: 396 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21484 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrmuizel at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21354-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 12 02:04:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 61940 invoked by alias); 12 May 2017 02:04: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 59564 invoked by uid 48); 12 May 2017 02:04:00 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21483] Rust expression evaluation can be really expensive Date: Fri, 12 May 2017 02:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to 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: 2017-q2/txt/msg00155.txt.bz2 Content-length: 880 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21483 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg Assignee|unassigned at sourceware dot org |tromey at sourcewar= e dot org --- Comment #1 from Tom Tromey --- I think the problem is here: /* Field access in structs and untagged unions works like C. */ *pos =3D pc; result =3D evaluate_subexp_standard (expect_type, exp, pos, nos= ide); This re-evaluates the particular subexpression again. This means an explosion when the LHS itself does this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21355-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 12 02:10:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 125938 invoked by alias); 12 May 2017 02:10:03 -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 125577 invoked by uid 48); 12 May 2017 02:10:00 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21483] Rust expression evaluation can be really expensive Date: Fri, 12 May 2017 02:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed 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: 2017-q2/txt/msg00156.txt.bz2 Content-length: 595 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21483 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-05-12 Ever confirmed|0 |1 --- Comment #2 from Tom Tromey --- I have a patch which I'll put in tomorrow. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21356-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 12 11:02:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78792 invoked by alias); 12 May 2017 11:02:04 -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 78756 invoked by uid 48); 12 May 2017 11:02:03 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/10438] "help" completer does not know about "user-defined" Date: Fri, 12 May 2017 11:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 6.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat 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: 6.8 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution 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: 2017-q2/txt/msg00157.txt.bz2 Content-length: 629 https://sourceware.org/bugzilla/show_bug.cgi?id=3D10438 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |sergiodj at redhat dot com Resolution|--- |FIXED --- Comment #1 from Sergio Durigan Junior --- Olb bug. Closing as it is fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21357-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 12 11:04:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 85950 invoked by alias); 12 May 2017 11:04:01 -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 85896 invoked by uid 48); 12 May 2017 11:04:01 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/10498] segfault on "run " when built with gcc 4.3.4 Date: Fri, 12 May 2017 11:04: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: 6.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: OBSOLETE X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 6.8 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution 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: 2017-q2/txt/msg00158.txt.bz2 Content-length: 702 https://sourceware.org/bugzilla/show_bug.cgi?id=3D10498 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |sergiodj at redhat dot com Resolution|--- |OBSOLETE --- Comment #1 from Sergio Durigan Junior --- I'm closing this as OBSOLETE because it's an old report. Feel free to reop= en if this is still a bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21359-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 12 11:05:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 108301 invoked by alias); 12 May 2017 11:05:25 -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 107654 invoked by uid 48); 12 May 2017 11:05:25 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug build/9627] gdb 6.8 doesn't build when environment variable, "U", is set previously by user. Date: Fri, 12 May 2017 11:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 6.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 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: 2017-q2/txt/msg00160.txt.bz2 Content-length: 254 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9627 --- Comment #3 from Sergio Durigan Junior --- BTW, I checked and the bug is still valid. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21358-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 12 11:05:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 96635 invoked by alias); 12 May 2017 11:05:04 -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 96139 invoked by uid 48); 12 May 2017 11:05:03 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug build/9627] gdb 6.8 doesn't build when environment variable, "U", is set previously by user. Date: Fri, 12 May 2017 11:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 6.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution 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: 2017-q2/txt/msg00159.txt.bz2 Content-length: 680 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9627 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |sergiodj at redhat dot com Resolution|--- |INVALID --- Comment #2 from Sergio Durigan Junior --- Closing as INVALID because this is a libiberty bug. Feel free to reopen if needed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21360-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 12 15:05:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 102644 invoked by alias); 12 May 2017 15:05:33 -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 102615 invoked by uid 55); 12 May 2017 15:05:32 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug rust/21483] Rust expression evaluation can be really expensive Date: Fri, 12 May 2017 15:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q2/txt/msg00161.txt.bz2 Content-length: 1230 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21483 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D6830f270e7b6= 676e7a77c1b8080941e35003d918 commit 6830f270e7b6676e7a77c1b8080941e35003d918 Author: Tom Tromey Date: Thu May 11 22:22:36 2017 -0600 Avoid exponential behavior in rust_evaluate_subexp The STRUCTOP_STRUCT case in rust_evaluate_subexp would evaluate its LHS, and then, if it did not need Rust-specific treatment, it would back up and re-evaluate the entire STRUCTOP_STRUCT part of the expression using evaluate_subexp_standard. This yields exponential behavior and causes some expressions to evaluate extremely slowly. The fix is to simply do the needed work inline. This is PR rust/21483. ChangeLog 2017-05-12 Tom Tromey PR rust/21483: * rust-lang.c (rust_evaluate_subexp) : Don't recurse, just call value_struct_elt directly. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21361-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 12 15:06:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 106434 invoked by alias); 12 May 2017 15:06:41 -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 106395 invoked by uid 48); 12 May 2017 15:06:40 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21483] Rust expression evaluation can be really expensive Date: Fri, 12 May 2017 15:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q2/txt/msg00162.txt.bz2 Content-length: 612 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21483 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Tom Tromey --- Fixed. I asked to put it on the 8.0 branch, we'll see. There's no way to set the target milestone to post-8.0. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21362-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 12 15:12:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 12212 invoked by alias); 12 May 2017 15:12:44 -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 11872 invoked by uid 48); 12 May 2017 15:12:43 -0000 From: "schwab@linux-m68k.org" To: gdb-prs@sourceware.org Subject: [Bug build/9627] gdb 6.8 doesn't build when environment variable, "U", is set previously by user. Date: Fri, 12 May 2017 15:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 6.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: schwab@linux-m68k.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 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: 2017-q2/txt/msg00163.txt.bz2 Content-length: 264 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9627 --- Comment #4 from Andreas Schwab --- It's really an autoconf bug, a leftover from the ansi2knr stuff. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21363-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat May 13 17:58:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 97749 invoked by alias); 13 May 2017 17:58:21 -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 97722 invoked by uid 48); 13 May 2017 17:58:20 -0000 From: "anton at samba dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21490] New: gdb/thread.c:1121: internal-error: void finish_thread_state(ptid_t): Assertion `tp' failed. Date: Sat, 13 May 2017 17:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: anton at samba dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00164.txt.bz2 Content-length: 1271 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21490 Bug ID: 21490 Summary: gdb/thread.c:1121: internal-error: void finish_thread_state(ptid_t): Assertion `tp' failed. Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: anton at samba dot org Target Milestone: --- I hit this assert on ppc64le with a build of HEAD from today: gdb/thread.c:1121: internal-error: void finish_thread_state(ptid_t): Assert= ion `tp' failed. To reproduce # cat testcase.S #include #include FUNC_START(_start) li r0,SYS_exit li r3,0 sc FUNC_END(_start) # cat cmds set pagination off break _start run layout reg stepi 5 # gcc -ffreestanding -nostdlib -fno-builtin -static -o testcase testcase.S # gdb -x cmds ./testcase [Inferior 1 (process 88304) exited normally] ../../binutils-gdb/gdb/thread.c:1121: internal-error: void finish_thread_state(ptid_t): Assertion `tp' failed. A problem internal to GDB has been detected, --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21364-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 14 17:10:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 125483 invoked by alias); 14 May 2017 17:10:09 -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 125434 invoked by uid 48); 14 May 2017 17:10:08 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21484] watch -location does not work with rust Date: Sun, 14 May 2017 17:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: 2017-q2/txt/msg00165.txt.bz2 Content-length: 408 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21484 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |tromey at sourcewar= e dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21365-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 14 17:32:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 45457 invoked by alias); 14 May 2017 17:32:06 -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 45429 invoked by uid 48); 14 May 2017 17:32:05 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/20603] gdb fails to properly restart a rust test executable Date: Sun, 14 May 2017 17:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q2/txt/msg00166.txt.bz2 Content-length: 539 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20603 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Tom Tromey --- I can't reproduce this any more. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21366-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon May 15 03:09:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 95093 invoked by alias); 15 May 2017 03:09:29 -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 95062 invoked by uid 48); 15 May 2017 03:09:28 -0000 From: "shahzeb001 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20981] Dynamic library debugging on MacOS X 10.12 (Sierra) and dyld 15 is broken Date: Mon, 15 May 2017 03:09: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: shahzeb001 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00167.txt.bz2 Content-length: 655 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20981 Shahzeb changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |shahzeb001 at gmail dot com --- Comment #3 from Shahzeb --- Any update on this? I've uninstalled and then installed gdb twice (via brew). I've also codesig= ned it. Still get "No shared libraries loaded at this time.". Really frustratin= g. macOS: 10.12.4 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21367-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon May 15 05:02:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64781 invoked by alias); 15 May 2017 05:02:38 -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 64725 invoked by uid 48); 15 May 2017 05:02:37 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21484] watch -location does not work with rust Date: Mon, 15 May 2017 05:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q2/txt/msg00168.txt.bz2 Content-length: 1084 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21484 --- Comment #1 from Tom Tromey --- This bug turns out to be surprisingly hard. Location watchpoints try to set the language to C when the expression is rewritten to *(TYPE*)ADDR. However, this doesn't actually work, because nothing forces the re-parse to be done in C. Making the obvious change there also doesn't work -- it regresses gdb.dlang/watch-loc.exp, which makes sense, because what happens then is that gdb tries to parse a D type using the C parser. My next idea was to change breakpoint.c to create an equivalent expression without using the parser. But here the problem is how to re-parse the type string when resetting breakpoints. There's no existing API (other than the language parser), AFAIK, that can always parse the output of type_to_string. And, if you're going to use the language parser anyway... I guess we might as well just make the rewriter a lang hook. So, that's my current plan. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21368-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue May 16 09:49:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41247 invoked by alias); 16 May 2017 09:49:17 -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 41210 invoked by uid 48); 16 May 2017 09:49:16 -0000 From: "rguenth at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21494] New: segfault in find_partial_die_in_comp_unit Date: Tue, 16 May 2017 09:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00169.txt.bz2 Content-length: 5256 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21494 Bug ID: 21494 Summary: segfault in find_partial_die_in_comp_unit Product: gdb Version: 8.0 Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: rguenth at gcc dot gnu.org Target Milestone: --- I get a segfault in find_partial_die_in_comp_unit because cu->partial_dies = is NULL. #0 find_partial_die_in_comp_unit (sect_off=3D(unknown: 0), cu=3D0xfff0e0) at /space/rguenther/src/binutils-gdb/gdb/dwarf2read.c:16369 #1 0x00000000005f91d7 in find_partial_die (sect_off=3D(unknown: 0),=20 offset_in_dwz=3D0, cu=3D0xfd8b50) at /space/rguenther/src/binutils-gdb/gdb/dwarf2read.c:16419 #2 0x00000000005f955f in fixup_partial_die (part_die=3D0x1023220, cu=3D0xf= d8b50) at /space/rguenther/src/binutils-gdb/gdb/dwarf2read.c:16522 #3 0x00000000005e16f1 in scan_partial_symbols (first_die=3D0x10231c0,=20 lowpc=3D0x7fffffffd330, highpc=3D0x7fffffffd328, set_addrmap=3D0, cu=3D= 0xfd8b50) at /space/rguenther/src/binutils-gdb/gdb/dwarf2read.c:6824 #4 0x00000000005dfe7a in process_psymtab_comp_unit_reader ( reader=3D0x7fffffffd460, info_ptr=3D0x7ffff7fe4de4 "\002",=20 comp_unit_die=3D0xfef980, has_children=3D1, data=3D0x7fffffffd550) at /space/rguenther/src/binutils-gdb/gdb/dwarf2read.c:6183 #5 0x00000000005df125 in init_cutu_and_read_dies (this_cu=3D0xf1e600,=20 abbrev_table=3D0x0, use_existing_cu=3D0, keep=3D0,=20 die_reader_func=3D0x5dfb24 , data=3D0x7fffffffd550) at /space/rguenther/src/binutils-gdb/gdb/dwarf2read.c:5798 #6 0x00000000005e0324 in process_psymtab_comp_unit (this_cu=3D0xf1e600,=20 want_partial_unit=3D0, pretend_language=3Dlanguage_minimal) at /space/rguenther/src/binutils-gdb/gdb/dwarf2read.c:6265 #7 0x00000000005e0f8c in dwarf2_build_psymtabs_hard (objfile=3D0xf1eff0) at /space/rguenther/src/binutils-gdb/gdb/dwarf2read.c:6658 #8 0x00000000005db951 in dwarf2_build_psymtabs (objfile=3D0xf1eff0) at /space/rguenther/src/binutils-gdb/gdb/dwarf2read.c:4407 #9 0x00000000004f0cab in read_psyms (objfile=3D0xf1eff0) at /space/rguenther/src/binutils-gdb/gdb/elfread.c:1290 #10 0x00000000006c7958 in require_partial_symbols (objfile=3D0xf1eff0, verb= ose=3D0) at /space/rguenther/src/binutils-gdb/gdb/psymtab.c:87 #11 0x0000000000704d23 in read_symbols (objfile=3D0xf1eff0, add_flags=3D...) at /space/rguenther/src/binutils-gdb/gdb/symfile.c:883 #12 0x000000000070535a in syms_from_objfile_1 (objfile=3D0xf1eff0,=20 addrs=3D0xf1dc20, add_flags=3D...) at /space/rguenther/src/binutils-gdb/gdb/symfile.c:1062 #13 0x00000000007053b2 in syms_from_objfile (objfile=3D0xf1eff0, addrs=3D0x= 0,=20 add_flags=3D...) at /space/rguenther/src/binutils-gdb/gdb/symfile.c:1078 #14 0x0000000000705753 in symbol_file_add_with_addrs (abfd=3D0xf1edb0,=20 name=3D0x7fffffffe2bf "./simple.exe", add_flags=3D..., addrs=3D0x0, fla= gs=3D...,=20 parent=3D0x0) at /space/rguenther/src/binutils-gdb/gdb/symfile.c:1177 #15 0x0000000000705a48 in symbol_file_add_from_bfd (abfd=3D0xf1edb0,=20 name=3D0x7fffffffe2bf "./simple.exe", add_flags=3D..., addrs=3D0x0, fla= gs=3D...,=20 parent=3D0x0) at /space/rguenther/src/binutils-gdb/gdb/symfile.c:1268 #16 0x0000000000705ac9 in symbol_file_add (name=3D0x7fffffffe2bf "./simple.= exe",=20 add_flags=3D..., addrs=3D0x0, flags=3D...) we come via 16415 if (per_cu->cu =3D=3D NULL || per_cu->cu->partial_dies =3D=3D= NULL) 16416 -> load_partial_comp_unit (per_cu); 16417 16418 per_cu->cu->last_used =3D 0; 16419 pd =3D find_partial_die_in_comp_unit (sect_off, per_cu->cu); but after load_partial_comp_unit the partial_dies hash is not allocated. The reason is likely invalid DWARF: Compilation Unit @ offset 0x15b: Length: 0x786c (32-bit) Version: 4 Abbrev Offset: 0x64 Pointer Size: 8 <0><166>: Abbrev Number: 1 (DW_TAG_compile_unit) <167> DW_AT_producer : (indirect string, offset: 0x4c7): GNU GIMPLE 8.0.0 20170515 (experimental) [trunk revision 221942] -mtune=3Dgeneric -march=3Dx86-64 -mtune=3Dgeneric -march=3Dx86-64 -g -g -O2 -O0 -O2 -O0 -fex= ceptions -fmath-errno -fsigned-zeros -ftrapping-math -fno-trapv -fno-openmp -fno-ope= nacc -fmessage-length=3D0 -fno-show-column -ffunction-sections -fdata-sections -fltrans <16b> DW_AT_language : 4 (C++) <16c> DW_AT_name : (indirect string, offset: 0x2c5): <170> DW_AT_comp_dir : (indirect string, offset: 0x41e): /abuild/rguenther/obj-early-lto-debug-g/x86_64-pc-linux-gnu/libstdc++-v3/te= stsuite <174> DW_AT_ranges : 0x70 <178> DW_AT_low_pc : 0x0 <180> DW_AT_stmt_list : 0xe7 <1><184>: Abbrev Number: 2 (DW_TAG_imported_unit) <185> DW_AT_import : <0x0> [Abbrev Number: 113] where this import references a non-existing unit. sth better than just segfaulting should happen here. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21370-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue May 16 10:06:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 91085 invoked by alias); 16 May 2017 10:06:57 -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 90949 invoked by uid 48); 16 May 2017 10:06:55 -0000 From: "rguenth at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20536] fails to handle DW_AT_upper_bound with DW_AT_constant_value in referenced DIE Date: Tue, 16 May 2017 10:06: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.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org 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: blocked 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: 2017-q2/txt/msg00171.txt.bz2 Content-length: 507 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20536 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |21494 Referenced Bugs: https://sourceware.org/bugzilla/show_bug.cgi?id=3D21494 [Bug 21494] segfault in find_partial_die_in_comp_unit --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21369-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue May 16 10:06:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 90917 invoked by alias); 16 May 2017 10:06:55 -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 90874 invoked by uid 48); 16 May 2017 10:06:54 -0000 From: "rguenth at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21494] segfault in find_partial_die_in_comp_unit Date: Tue, 16 May 2017 10:06: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org 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: dependson 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: 2017-q2/txt/msg00170.txt.bz2 Content-length: 635 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21494 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |20536 --- Comment #1 from Richard Biener --- Caused by bug 20536 :/ Referenced Bugs: https://sourceware.org/bugzilla/show_bug.cgi?id=3D20536 [Bug 20536] fails to handle DW_AT_upper_bound with DW_AT_constant_value in referenced DIE --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21371-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue May 16 10:08:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 97357 invoked by alias); 16 May 2017 10:08:18 -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 97320 invoked by uid 48); 16 May 2017 10:08:17 -0000 From: "rguenth at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21494] segfault in find_partial_die_in_comp_unit Date: Tue, 16 May 2017 10:08: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org 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: dependson 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: 2017-q2/txt/msg00172.txt.bz2 Content-length: 801 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21494 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|20536 |20882 --- Comment #2 from Richard Biener --- Err, 20882, stupid bugzilla defaults. Referenced Bugs: https://sourceware.org/bugzilla/show_bug.cgi?id=3D20536 [Bug 20536] fails to handle DW_AT_upper_bound with DW_AT_constant_value in referenced DIE https://sourceware.org/bugzilla/show_bug.cgi?id=3D20882 [Bug 20882] GNU ld discards sections required by relocations in .debug_info with --gc-sections --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21372-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue May 16 10:08:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 97485 invoked by alias); 16 May 2017 10:08:19 -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 97376 invoked by uid 48); 16 May 2017 10:08:18 -0000 From: "rguenth at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20536] fails to handle DW_AT_upper_bound with DW_AT_constant_value in referenced DIE Date: Tue, 16 May 2017 10:08: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.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org 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: blocked 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: 2017-q2/txt/msg00173.txt.bz2 Content-length: 502 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20536 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|21494 | Referenced Bugs: https://sourceware.org/bugzilla/show_bug.cgi?id=3D21494 [Bug 21494] segfault in find_partial_die_in_comp_unit --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21373-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue May 16 14:22:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66286 invoked by alias); 16 May 2017 14:22:49 -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 64559 invoked by uid 48); 16 May 2017 14:22:48 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tui/21482] gdb 8.0 tui doesn't build with native curses on Solaris Date: Tue, 16 May 2017 14:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: cc 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: 2017-q2/txt/msg00174.txt.bz2 Content-length: 543 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21482 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org --- Comment #1 from Yao Qi --- Close this issue as it is fixed by https://sourceware.org/ml/gdb-patches/2017-05/msg00287.html ? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21374-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue May 16 19:52:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 18178 invoked by alias); 16 May 2017 19:52:48 -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 18111 invoked by uid 48); 16 May 2017 19:52:47 -0000 From: "jules at op59 dot net" To: gdb-prs@sourceware.org Subject: [Bug python/21496] New: Python signal.signal() doesn't restore SIGINT handler correctly. Date: Tue, 16 May 2017 19:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jules at op59 dot net X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00175.txt.bz2 Content-length: 6269 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21496 Bug ID: 21496 Summary: Python signal.signal() doesn't restore SIGINT handler correctly. Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: jules at op59 dot net Target Milestone: --- I've seen a curious problem in gdb where modifying and restoring the handler for SIGINT from within gdb's python, breaks subsequent handling of Ctrl-C in gdb. Specifically it affects Ctrl-C when used to terminate commands that ou= tput lots of text and page with '---Type to continue, or q to quit---'. Here's how to reproduce, using a build of gdb from git. First get/build an executable who's main() is long enough to require scroll= ing when disassembled from within gdb (you may need to reduce the size of your terminal window for this), and load into gdb: > /home/jules/gdb_git_dir/gdb/gdb --data-directory gdb_git_dir/gdb/data-directory a.out GNU gdb (GDB) 8.0.50.20170516-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copyi= ng" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from a.out...done. Do disassemble of a function: (gdb) disassemble main Dump of assembler code for function main: 0x0000000000400546 <+0>: push %rbp 0x0000000000400547 <+1>: mov %rsp,%rbp 0x000000000040054a <+4>: sub $0x10,%rsp 0x000000000040054e <+8>: mov $0x400634,%edi 0x0000000000400553 <+13>: callq 0x400410 0x0000000000400558 <+18>: movl $0x0,-0x4(%rbp) 0x000000000040055f <+25>: jmp 0x40059c 0x0000000000400561 <+27>: mov -0x4(%rbp),%ecx 0x0000000000400564 <+30>: mov $0x55555556,%edx 0x0000000000400569 <+35>: mov %ecx,%eax 0x000000000040056b <+37>: imul %edx 0x000000000040056d <+39>: mov %ecx,%eax 0x000000000040056f <+41>: sar $0x1f,%eax 0x0000000000400572 <+44>: sub %eax,%edx 0x0000000000400574 <+46>: mov %edx,%eax 0x0000000000400576 <+48>: mov %eax,%edx 0x0000000000400578 <+50>: add %edx,%edx 0x000000000040057a <+52>: add %eax,%edx 0x000000000040057c <+54>: mov %ecx,%eax 0x000000000040057e <+56>: sub %edx,%eax 0x0000000000400580 <+58>: test %eax,%eax 0x0000000000400582 <+60>: jne 0x400598 ---Type to continue, or q to quit--- At this point, Ctrl-C correctly interrupts the disassembly: ---Type to continue, or q to quit---^CQuit Now use python to change and restore the handler for SIGINT. We actually do this twice to verify that we restored the original . (gdb) python >import signal >a =3D signal.signal( signal.SIGINT, signal.SIG_IGN) >b =3D signal.signal( signal.SIGINT, a) >c =3D signal.signal( signal.SIGINT, b) >d =3D signal.signal( signal.SIGINT, c) >print a, b, c, d >end 1 1 (gdb)=20 Try disassembling again: (gdb) disassemble main Dump of assembler code for function main: 0x0000000000400546 <+0>: push %rbp 0x0000000000400547 <+1>: mov %rsp,%rbp 0x000000000040054a <+4>: sub $0x10,%rsp 0x000000000040054e <+8>: mov $0x400634,%edi 0x0000000000400553 <+13>: callq 0x400410 0x0000000000400558 <+18>: movl $0x0,-0x4(%rbp) 0x000000000040055f <+25>: jmp 0x40059c 0x0000000000400561 <+27>: mov -0x4(%rbp),%ecx 0x0000000000400564 <+30>: mov $0x55555556,%edx 0x0000000000400569 <+35>: mov %ecx,%eax 0x000000000040056b <+37>: imul %edx 0x000000000040056d <+39>: mov %ecx,%eax 0x000000000040056f <+41>: sar $0x1f,%eax 0x0000000000400572 <+44>: sub %eax,%edx 0x0000000000400574 <+46>: mov %edx,%eax 0x0000000000400576 <+48>: mov %eax,%edx 0x0000000000400578 <+50>: add %edx,%edx 0x000000000040057a <+52>: add %eax,%edx 0x000000000040057c <+54>: mov %ecx,%eax 0x000000000040057e <+56>: sub %edx,%eax 0x0000000000400580 <+58>: test %eax,%eax 0x0000000000400582 <+60>: jne 0x400598 ---Type to continue, or q to quit--- This time pressing Ctrl-C doesn't interrupt; instead it gives: ---Type to continue, or q to quit---^C At this point, entering any other key ('o' in this example) actually interr= upts the disassembly, and appears to insert the key into the next line: ---Type to continue, or q to quit---^CQuit (gdb) o So it looks like the behaviour of Ctrl-C has been subtly changed by the change+restore of gdb's SIGINT handler. With gdb-7.7, the behaviour is slightly worse - entering Ctrl-C has no affe= ct at all; the only way to terminate the disassembly is to enter q. This is perhaps a minor issue for interactive sessions, but it causes probl= ems when using gdb from scripts, e.g. as part of a test suite. Thanks for any information about what could be going wrong here. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21375-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue May 16 21:22:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63128 invoked by alias); 16 May 2017 21:22:37 -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 63094 invoked by uid 48); 16 May 2017 21:22:37 -0000 From: "jlott1 at yahoo dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21497] New: FreeBSD: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed Date: Tue, 16 May 2017 21:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jlott1 at yahoo dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone attachments.created Message-ID: 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: 2017-q2/txt/msg00176.txt.bz2 Content-length: 4207 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21497 Bug ID: 21497 Summary: FreeBSD: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: jlott1 at yahoo dot com CC: jhb at FreeBSD dot org Target Milestone: --- Created attachment 10053 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10053&action=3Ded= it Debug log of the failed continue I'm using gdb7121 from FreeBSD ports. Getting this assert occasionally when continuing from a breakpoint: infrun.c:5565: internal-error: int finish_step_over(execution_control_state= *): Assertion `ecs->event_thread->control.trap_expected' failed. I ran with some debugging on to narrow it down (set debug target 1; set deb= ug infrun 1; set debug fbsd-lwp 1). Unfortunately it takes a long time to reproduce so the debug output is fairly large (30MB). Only the end is really relevant, I think. It appears to be an interaction (race condition) between= new threads being launched and the continuing of a thread from a breakpoint. Skipping over a lot of the verbose messages for brevity/clarity, you can see the sequence in the last continue: -> native->to_log_command (...) <- native->to_log_command (0x1d7f300, c) Continuing. ... infrun: resuming [LWP 102181 of process 23510] for step-over ... infrun: skipping breakpoint: stepping past insn at: 0x1df0c07 infrun: skipping breakpoint: stepping past insn at: 0x1df0c07 -> native->to_insert_breakpoint (...) ... <- native->to_insert_breakpoint (0x1d7f300, i386:x86-64, 0x000000080a335d00= ) =3D 0 ... infrun: resume (step=3D1, signal=3DGDB_SIGNAL_0), trap_expected=3D1, curren= t thread [LWP 102181 of process 23510] at 0x1df0c07 ... FLWP: fbsd_resume for ptid (23510, 102181, 0) So far so good, everything is setup to single-step LWP 102181. However, bec= ause it is single stepping, it is expecting to only receive events about that thread. However, there was already a thread-create event pending when the breakpoint occurred. Therefore the next event that gets returned from pthre= ad is actually a create for a different thread. FLWP: adding thread for LWP 101493 ... [New LWP 101493 of process 23510] ... infrun: target_wait (-1.0.0, status) =3D infrun: 23510.101493.0 [LWP 101493 of process 23510], infrun: status->kind =3D spurious ... infrun: TARGET_WAITKIND_SPURIOUS ... infrun: Switching context from LWP 102181 of process 23510=20 ... to LWP 101493 of process 23510 After it processes this new thread, it will now resume all threads. This is= not good, because the "continue" code still thinks it is in single-step mode. infrun: resume (step=3D0, signal=3DGDB_SIGNAL_0), trap_expected=3D0, curren= t thread [LWP 101493 of process 23510] at 0x80add2d20 ... FLWP: fbsd_resume for ptid (-1, 0, 0) Because all threads are now running, another thread hits the temporary breakpoint that was intended for the single-stepping thread. infrun: target_wait (-1.0.0, status) =3D infrun: 23510.101602.0 [LWP 101602 of process 23510], infrun: status->kind =3D stopped, signal =3D GDB_SIGNAL_TRAP ... infrun: TARGET_WAITKIND_STOPPED Now it checks to see that the thread that hit the breakpoint is the correct thread that was single-stepping. It was not, hence the assert. infrun.c:5565: internal-error: int finish_step_over(execution_control_state= *): Assertion `ecs->event_thread->control.trap_expected' failed. I hope this is clear. It seems there is a mismatch between what the "core" = gdb code expects in terms of ptrace event ordering and how the FreeBSD ptrace A= PI actually behaves. I'll attach the (unfiltered) end of the log to the report= as well. I can reproduce locally with our application relatively easily, but I= 've not come up with a standalone test program to cause it yet. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21376-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 17 05:09:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 81542 invoked by alias); 17 May 2017 05:09:06 -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 81017 invoked by uid 55); 17 May 2017 05:09:05 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug rust/21483] Rust expression evaluation can be really expensive Date: Wed, 17 May 2017 05:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q2/txt/msg00177.txt.bz2 Content-length: 1224 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21483 --- Comment #5 from cvs-commit at gcc dot gnu.org --- The gdb-8.0-branch branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D69e9e8a0d5ae= 31e9869658771a7d399a53ac7833 commit 69e9e8a0d5ae31e9869658771a7d399a53ac7833 Author: Tom Tromey Date: Thu May 11 22:22:36 2017 -0600 Avoid exponential behavior in rust_evaluate_subexp The STRUCTOP_STRUCT case in rust_evaluate_subexp would evaluate its LHS, and then, if it did not need Rust-specific treatment, it would back up and re-evaluate the entire STRUCTOP_STRUCT part of the expression using evaluate_subexp_standard. This yields exponential behavior and causes some expressions to evaluate extremely slowly. The fix is to simply do the needed work inline. This is PR rust/21483. 2017-05-12 Tom Tromey PR rust/21483: * rust-lang.c (rust_evaluate_subexp) : Don't recurse, just call value_struct_elt directly. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21377-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 17 05:17:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20069 invoked by alias); 17 May 2017 05:17:30 -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 19424 invoked by uid 48); 17 May 2017 05:17:30 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21483] Rust expression evaluation can be really expensive Date: Wed, 17 May 2017 05:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone 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: 2017-q2/txt/msg00178.txt.bz2 Content-length: 374 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21483 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21378-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 17 08:19:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 95506 invoked by alias); 17 May 2017 08:19: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 95478 invoked by uid 55); 17 May 2017 08:19:22 -0000 From: "ro at CeBiTec dot Uni-Bielefeld.DE" To: gdb-prs@sourceware.org Subject: [Bug tui/21482] gdb 8.0 tui doesn't build with native curses on Solaris Date: Wed, 17 May 2017 08:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE 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: 2017-q2/txt/msg00179.txt.bz2 Content-length: 1050 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21482 --- Comment #2 from Rainer Orth --- > --- Comment #1 from Yao Qi --- > Close this issue as it is fixed by > https://sourceware.org/ml/gdb-patches/2017-05/msg00287.html ? They are completely unrelated, unfortunately: this one persists even after the fix above went in. The problem boils down to $ cat cc.c #include const char *str =3D "msg"; void func (char *str) { (void) strlen (str); } void call (void) { func (str); } $ g++ -c -O2 -Wall -c cc.c cc.c: In function 'void call()': cc.c:14:12: error: invalid conversion from 'const char*' to 'char*' [-fpermissive] func (str); ^ cc.c:6:1: note: initializing argument 1 of 'void func(char*)' func (char *str) ^~~~ However (as I wasn't aware initially), you can simply cast the constness away in all calls to mvwaddstr. I'll give that a whirl. Rainer --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21379-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 17 08:39:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66332 invoked by alias); 17 May 2017 08:39:40 -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 66300 invoked by uid 55); 17 May 2017 08:39:39 -0000 From: "ro at CeBiTec dot Uni-Bielefeld.DE" To: gdb-prs@sourceware.org Subject: [Bug tui/21482] gdb 8.0 tui doesn't build with native curses on Solaris Date: Wed, 17 May 2017 08:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE 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: 2017-q2/txt/msg00180.txt.bz2 Content-length: 880 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21482 --- Comment #3 from Rainer Orth --- > --- Comment #2 from Rainer Orth --- [...] > However (as I wasn't aware initially), you can simply cast the constness > away in all calls to mvwaddstr. I'll give that a whirl. The attached patch worked for me, allowing a sparc-sun-solaris2.10 compilation to succeed on the 8.0 branch. Comparing gdb/tui on the branch and mainline, I noticed that the only difference between the two is this fix: 2017-05-13 Eli Zaretskii * tui/tui.c (tui_enable): Cast "unknown" to 'char *' to avoid a C++ compiler warning. for exactly the same problem (well, same problem, different function). Rainer --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21380-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 17 08:41:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 70081 invoked by alias); 17 May 2017 08:40:59 -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 70051 invoked by uid 48); 17 May 2017 08:40:58 -0000 From: "ro at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tui/21482] gdb 8.0 tui doesn't build with native curses on Solaris Date: Wed, 17 May 2017 08:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at gcc dot gnu.org 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: attachments.created 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: 2017-q2/txt/msg00181.txt.bz2 Content-length: 317 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21482 --- Comment #4 from Rainer Orth --- Created attachment 10054 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10054&action=3Ded= it proposed patch --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21381-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 17 15:05:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 24393 invoked by alias); 17 May 2017 15:05:16 -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 24350 invoked by uid 48); 17 May 2017 15:05:16 -0000 From: "hjl.tools at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21494] segfault in find_partial_die_in_comp_unit Date: Wed, 17 May 2017 15:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: dep_changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hjl.tools at gmail dot com 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: bug_status resolution 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: 2017-q2/txt/msg00182.txt.bz2 Content-length: 596 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21494 Bug 21494 depends on bug 20882, which changed state. Bug 20882 Summary: GNU ld discards sections required by relocations in .deb= ug_info with --gc-sections https://sourceware.org/bugzilla/show_bug.cgi?id=3D20882 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21382-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 17 16:18:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94988 invoked by alias); 17 May 2017 16:18:45 -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 94499 invoked by uid 48); 17 May 2017 16:18:44 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tui/21482] gdb 8.0 tui doesn't build with native curses on Solaris Date: Wed, 17 May 2017 16:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: 2017-q2/txt/msg00183.txt.bz2 Content-length: 332 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21482 --- Comment #5 from Yao Qi --- (In reply to Rainer Orth from comment #4) > Created attachment 10054 [details] > proposed patch Can you post the patch to gdb-patches@? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21383-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 18 08:57:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 104928 invoked by alias); 18 May 2017 08:57:30 -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 104889 invoked by uid 48); 18 May 2017 08:57:29 -0000 From: "ro at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tui/21482] gdb 8.0 tui doesn't build with native curses on Solaris Date: Thu, 18 May 2017 08:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at gcc dot gnu.org 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: bug_file_loc 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: 2017-q2/txt/msg00184.txt.bz2 Content-length: 605 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21482 Rainer Orth changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://sourceware.org/ml/g | |db-patches/2017-05/msg00410 | |.html --- Comment #6 from Rainer Orth --- Sure, patch posted. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21384-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 18 10:28:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 75684 invoked by alias); 18 May 2017 10:28:12 -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 75610 invoked by uid 48); 18 May 2017 10:28:10 -0000 From: "jrose.manila at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21500] New: gdb sizeof(long int)=4 but gcc sizeof(long int)=8 on x86_64-pc-cygwin Date: Thu, 18 May 2017 10:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jrose.manila at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcchost cf_gcctarget Message-ID: 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: 2017-q2/txt/msg00185.txt.bz2 Content-length: 2617 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21500 Bug ID: 21500 Summary: gdb sizeof(long int)=3D4 but gcc sizeof(long int)=3D8 on x86_64-pc-cygwin Product: gdb Version: 7.10.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: jrose.manila at gmail dot com Target Milestone: --- Host: CYGWIN_NT-10.0 Caroline-2 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin Target: x86_64 Cygwin gcc sizeof(long)=3D8 but gdb sizeof(long)=3D4 on current x86_64-pc-cygwin. Consistency between gdb and gcc is required for any given platform. The gdb build appears to be incorrect for x86_64-pc-cygwin. Tested with gcc 5.4.0 and gdb 7.10.1 (current cygwin versions) on x86_64-pc-cygwin running under Windows 10. Please refer to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D80777 for discussion whether gcc or gdb is incorrectly configured. In particular comment-8 there. Also refer to https://bugzilla.redhat.com/show_bug.cgi?id=3D518712 which describes the same issue under Linux. Repeating the same test described in comment-1 there when run under x86_64-pc-cygwin gets the wrong answer: $ gdb GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-cygwin". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) show arch The target architecture is set automatically (currently i386) (gdb) set arch Requires an argument. Valid arguments are i386, i386:x86-64, i386:x64-32, i8086, i386:intel, i386:x86-64:intel, i386:x64-32:intel, i386:nacl, i386:x86-64:nacl, i386:x64-32:nacl, auto. (gdb) set arch i386:x86-64 The target architecture is assumed to be i386:x86-64 (gdb) print sizeof(long) $1 =3D 4 (gdb) print sizeof(long long) $2 =3D 8 (gdb) print sizeof(long*) $3 =3D 8 (gdb) q --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21385-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 18 12:29:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 57437 invoked by alias); 18 May 2017 12:29:16 -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 56393 invoked by uid 48); 18 May 2017 12:29:15 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21500] gdb sizeof(long int)=4 but gcc sizeof(long int)=8 on x86_64-pc-cygwin Date: Thu, 18 May 2017 12:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00186.txt.bz2 Content-length: 1032 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21500 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- The problem is that while Cygwin and MinGW ABIs are different, GDB assumes they're the same. amd64-windows-tdep.c has: /* On Windows, "long"s are only 32bit. */ set_gdbarch_long_bit (gdbarch, 32); and this gdbarch is used by both Cygwin and MinGW. We need a new "show osabi" value for "Windows" (MinGW), and then come up wi= th some way to figure out automatically from the program binary which of the A= BIs is in effect. Looking at the dll import list for the cygwin dll may be a g= ood enough approximation. (And add a hardcoded case for the cygwin dll itself.) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21386-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 18 12:40:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 12626 invoked by alias); 18 May 2017 12:40:36 -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 12562 invoked by uid 48); 18 May 2017 12:40:34 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21497] FreeBSD: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed Date: Thu, 18 May 2017 12:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00187.txt.bz2 Content-length: 1146 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21497 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- Thanks for that analysis, that helps a lot. > So far so good, everything is setup to single-step LWP 102181. However,=20 > because it is single stepping, it is expecting to only receive events abo= ut=20 > that thread. However, there was already a thread-create event pending whe= n the=20 > breakpoint occurred. Therefore the next event that gets returned from pth= read > is actually a create for a different thread. That's the problem then. The backend should not report stop events to the = core for threads that the core did not resume. So until the core of GDB sends a wildcard "resume the whole process" resumption request, the backend should = hold that event pending somehow. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21387-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 18 23:35:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 118447 invoked by alias); 18 May 2017 23:35:24 -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 118417 invoked by uid 48); 18 May 2017 23:35:24 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21450] segfault when running -data-list-register-values x on rust executable Date: Thu, 18 May 2017 23:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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 cc resolution 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: 2017-q2/txt/msg00188.txt.bz2 Content-length: 652 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21450 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |tromey at sourceware dot o= rg Resolution|--- |DUPLICATE --- Comment #1 from Tom Tromey --- Dup. *** This bug has been marked as a duplicate of bug 21449 *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21388-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 18 23:35:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 118579 invoked by alias); 18 May 2017 23:35:25 -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 118479 invoked by uid 48); 18 May 2017 23:35:25 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21449] segfault when running -data-list-register-values x on rust executable Date: Thu, 18 May 2017 23:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00189.txt.bz2 Content-length: 265 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21449 --- Comment #1 from Tom Tromey --- *** Bug 21450 has been marked as a duplicate of this bug. *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21389-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 18 23:42:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 15424 invoked by alias); 18 May 2017 23:42:20 -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 15386 invoked by uid 48); 18 May 2017 23:42:20 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21449] segfault when running -data-list-register-values x on rust executable Date: Thu, 18 May 2017 23:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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 cc version resolution 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: 2017-q2/txt/msg00190.txt.bz2 Content-length: 950 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21449 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |tromey at sourceware dot o= rg Version|7.12.1 |8.0 Resolution|--- |FIXED --- Comment #2 from Tom Tromey --- > The bug was fixed in gdb's git repository, commit b96645f1a1e608 "Add sup= port for untagged unions in Rust", but is present in version 7.12 and 7.12.= 1.=20 I think there won't be another 7.12.x release, so I'm closing this, since I understand it to be fixed for 8.0. If this is in error, please reopen, thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21390-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 19 00:18:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 69032 invoked by alias); 19 May 2017 00:18:58 -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 69005 invoked by uid 48); 19 May 2017 00:18:58 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21185] add i128 and u128 support to rust Date: Fri, 19 May 2017 00:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q2/txt/msg00191.txt.bz2 Content-length: 382 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 --- Comment #1 from Tom Tromey --- I tried a hack that typedefs LONGEST and ULONGEST using __int128. This found a couple of type errors in the source. Unfortunately the resulting gdb doesn't seem to work properly. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21391-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 19 03:35:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 14007 invoked by alias); 19 May 2017 03:35:49 -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 13973 invoked by uid 48); 19 May 2017 03:35:49 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21185] add i128 and u128 support to rust Date: Fri, 19 May 2017 03:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q2/txt/msg00192.txt.bz2 Content-length: 413 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 --- Comment #2 from Tom Tromey --- I fixed up a few things and I'm sending this through the buildbot. I wonder though if this makes sense to put in. And, I wonder if my simple changes are really sufficient, given what I've already had to patch. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21392-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 19 04:50:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 52582 invoked by alias); 19 May 2017 04:50:04 -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 52544 invoked by uid 48); 19 May 2017 04:50:02 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21185] add i128 and u128 support to rust Date: Fri, 19 May 2017 04:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q2/txt/msg00193.txt.bz2 Content-length: 241 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 --- Comment #3 from Tom Tromey --- And, hah, the results are really bad. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21393-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 19 11:31:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63951 invoked by alias); 19 May 2017 11:31:38 -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 63924 invoked by uid 48); 19 May 2017 11:31:38 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21185] add i128 and u128 support to rust Date: Fri, 19 May 2017 11:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: cc 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: 2017-q2/txt/msg00194.txt.bz2 Content-length: 656 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #4 from Pedro Alves --- I expect you'll run into lots of assumptions that LONGEST =3D=3D 64-bit. Do many places in the codebase need to learn about the types? What does the hack spare you from doing manually? Arithmetic? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21394-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 19 12:04:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 13777 invoked by alias); 19 May 2017 12:04:40 -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 13743 invoked by uid 55); 19 May 2017 12:04:39 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tui/21482] gdb 8.0 tui doesn't build with native curses on Solaris Date: Fri, 19 May 2017 12:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q2/txt/msg00195.txt.bz2 Content-length: 649 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21482 --- Comment #7 from cvs-commit at gcc dot gnu.org --- The gdb-8.0-branch branch has been updated by Rainer Orth : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Da1cc26f6c361= 17f7abbd1e7d347030c37ebb30b6 commit a1cc26f6c36117f7abbd1e7d347030c37ebb30b6 Author: Rainer Orth Date: Fri May 19 14:01:50 2017 +0200 Fix tui compilation with Solaris libcurses: non-const last arg to mvwad= dstr (PR tui/21482) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21395-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 19 12:19:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 81850 invoked by alias); 19 May 2017 12:19:08 -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 81794 invoked by uid 55); 19 May 2017 12:19:04 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tui/21482] gdb 8.0 tui doesn't build with native curses on Solaris Date: Fri, 19 May 2017 12:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q2/txt/msg00196.txt.bz2 Content-length: 2349 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21482 --- Comment #8 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Rainer Orth : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D7a6e7fcc7799= 7bf7679cce4f1cfebcd57ba8af70 commit 7a6e7fcc77997bf7679cce4f1cfebcd57ba8af70 Author: Rainer Orth Date: Fri May 19 14:16:55 2017 +0200 Fix tui compilation with Solaris libcurses: non-const last arg to mvwad= dstr (PR tui/21482) On both mainline and the 8.0 branch, gdb compilation fails on Solaris 10 with the native libcurses in gdb/tui for several instances of the same problem: /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-winsource.c: In funct= ion `void tui_erase_source_content(tui_win_info*, int)': /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-winsource.c:257:18: error: invalid conversion from `const char*' to `char*' [-fpermissive] no_src_str); ^ In file included from /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/gdb_curses.h:42:0, from /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-data.h:26, from /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-winsource.c:33: =20=20=20 /vol/gcc-7/lib/gcc/sparc-sun-solaris2.10/7.1.0/include-fixed/curses.h:699:1= 2: note: initializing argument 4 of `int mvwaddstr(WINDOW*, int, int, char*)' extern int mvwaddstr(WINDOW *, int, int, char *); ^~~~~~~~~ make[2]: *** [Makefile:1927: tui-winsource.o] Error 1 Unlike ncurses, declares extern int mvwaddstr(WINDOW *, int, int, char *); i.e. the last arg is char *, not const char *. The patch fixes this by casting the last arg to mvwaddstr to char *, as was recently done on mainline in a newterm() call (the only difference between 8.0 and mainline gdb/tui). * tui/tui-windata.c (tui_erase_data_content): Cast last mvwaddstr arg to char *. * tui/tui-wingeneral.c (box_win): Likewise. * tui/tui-winsource.c (tui_erase_source_content): Likewise. (tui_show_source_line): Likewise. (tui_show_exec_info_content): Likewise. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21396-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 19 13:06:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 77839 invoked by alias); 19 May 2017 13:06:06 -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 77806 invoked by uid 55); 19 May 2017 13:06:05 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tui/21482] gdb 8.0 tui doesn't build with native curses on Solaris Date: Fri, 19 May 2017 13:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q2/txt/msg00197.txt.bz2 Content-length: 628 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21482 --- Comment #9 from cvs-commit at gcc dot gnu.org --- The gdb-8.0-branch branch has been updated by Rainer Orth : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D814385bb257f= ec68e0e64d43f2ccc40e219342e7 commit 814385bb257fec68e0e64d43f2ccc40e219342e7 Author: Rainer Orth Date: Fri May 19 15:03:52 2017 +0200 Fix tui compilation with Solaris libcurses: clear define (PR tui/21482) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21397-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 19 13:10:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 117276 invoked by alias); 19 May 2017 13:10:40 -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 117188 invoked by uid 55); 19 May 2017 13:10:39 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tui/21482] gdb 8.0 tui doesn't build with native curses on Solaris Date: Fri, 19 May 2017 13:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q2/txt/msg00198.txt.bz2 Content-length: 2026 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21482 --- Comment #10 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Rainer Orth : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D6e7e1744e96a= bbf1a4229d5f269caf2cc921ec58 commit 6e7e1744e96abbf1a4229d5f269caf2cc921ec58 Author: Rainer Orth Date: Fri May 19 15:08:45 2017 +0200 Fix tui compilation with Solaris libcurses: clear define (PR tui/21482) On both mainline and the 8.0 branch, gdb compilation fails on Solaris 10 with the native libcurses like this: In file included from /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/gdb_curses.h:42: 0, from /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-data.h:2 6, from /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-disasm.c :31: /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-disasm.c: In function `CORE_A DDR tui_disassemble(gdbarch*, tui_asm_line*, CORE_ADDR, int)': /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-disasm.c:71:19: error: `class string_file' has no member named `wclear'; did you mean `clear'? gdb_dis_out.clear (); ^ /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/tui/tui-disasm.c:78:19: error: `class string_file' has no member named `wclear'; did you mean `clear'? gdb_dis_out.clear (); ^ make[2]: *** [Makefile:1927: tui-disasm.o] Error 1 It turned out this happens because has #define clear() wclear(stdscr) This can be avoided by defining NOMACROS, which the patch below does. ncurses potentially has a similar problem, which can be avoided by defi= ning NCURSES_NOMACROS. PR tui/21482 * gdb_curses.h (NOMACROS): Define. (NCURSES_NOMACROS): Define. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21398-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 19 15:34:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35689 invoked by alias); 19 May 2017 15:34:35 -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 35647 invoked by uid 48); 19 May 2017 15:34:34 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21185] add i128 and u128 support to rust Date: Fri, 19 May 2017 15:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q2/txt/msg00199.txt.bz2 Content-length: 1269 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 --- Comment #5 from Tom Tromey --- (In reply to Pedro Alves from comment #4) > I expect you'll run into lots of assumptions that LONGEST =3D=3D 64-bit. Yeah. There were some spots in a few tdeps that assume that CORE_ADDR and ULONGEST are the same type. aarch64-tdep helpfully had self-tests pointing out some invalid assumptions -- not so with the other ones. And print-utils makes 64 bit assumptions. > Do many places in the codebase need to learn about the types? What does = the > hack spare you from doing manually? Arithmetic? I don't have a complete overview of the situation, but some things: * Printing a 128-bit integer doesn't work well right now. ... but that's print-utils, which currently use LONGEST/ULONGEST. Could be done manually for Rust, but since GCC has __int128 that doesn't seem best. * Arithmetic. This maybe means reimplementing a bunch of the value API? E.g. value_as_long returns a LONGEST. Could operate on the bytes instead, GMP-style. Hmm, maybe that's all I've got so far. I pushed the int-128 branch to my github in case you want to take a peek. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21399-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 19 16:27:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 98085 invoked by alias); 19 May 2017 16:27:22 -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 98027 invoked by uid 48); 19 May 2017 16:27:20 -0000 From: "jlott1 at yahoo dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21497] FreeBSD: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed Date: Fri, 19 May 2017 16:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jlott1 at yahoo dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00200.txt.bz2 Content-length: 868 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21497 --- Comment #2 from jlott1 at yahoo dot com --- I did a little more digging. I think the problem is that a brand-new thread= is non-suspended by default. GDB has not yet been informed about this nascent thread, so it doesn't know to suspend it when it suspends the other threads= for single-step mode. As a workaround, I keep track in fbsd-nat.c if we are in single-stepping mode. If I'm informed of a new thread while single-stepping= , I suspend the new thread and continue the process directly. I report the event itself as an "ignore" to the core. I'll attach the patch. The code could us= e a little improvement (use of the global var in particular is probably not good for multiple inferiors), but it shows the basic idea. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21400-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 19 16:28:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 98819 invoked by alias); 19 May 2017 16:28:07 -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 98790 invoked by uid 48); 19 May 2017 16:28:06 -0000 From: "jlott1 at yahoo dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21497] FreeBSD: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed Date: Fri, 19 May 2017 16:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jlott1 at yahoo dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00201.txt.bz2 Content-length: 307 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21497 --- Comment #3 from jlott1 at yahoo dot com --- Created attachment 10058 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10058&action=3Ded= it workaround patch --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21401-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 19 16:47:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64524 invoked by alias); 19 May 2017 16:47:17 -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 64472 invoked by uid 48); 19 May 2017 16:47:16 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21497] FreeBSD: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed Date: Fri, 19 May 2017 16:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jhb at FreeBSD dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00202.txt.bz2 Content-length: 1261 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21497 --- Comment #4 from jhb at FreeBSD dot org --- I have an old patch to try to fix a similar crash for kernels without LWP events that still didn't work in my testing. Rather than depending on a global, I ended up using the ptid passed to fbsd_resume. However, the patch also avoided adding new threads until single stepping was disabled. In particular, I wanted to be sure I didn't "lose" the event from the new thre= ad (in case the new thread had just hit a breakpoint and thus needed to be single-stepped across it). Perhaps that is unnecessary as the new thread w= ould simply repeat the breakpoint though when it is resumed. https://github.com/bsdjhb/gdb/compare/fbsd_single_step_thr (That patch doesn't work for LWP events so would need reworking anyway, but= it sounds like I'd need to handle it for both cases now anyway which might simplify the logic a bit. For the non-LWP event case if I don't care about reporting the event I can probably even just PT_SUSPEND the new LWP and ign= ore it and later come back to it). FYI, if you disable LWP events by hand in fbsd-nat.c do you still get the s= ame issue? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21402-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 19 19:07:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 104891 invoked by alias); 19 May 2017 19:07:06 -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 104862 invoked by uid 48); 19 May 2017 19:07:06 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21185] add i128 and u128 support to rust Date: Fri, 19 May 2017 19:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q2/txt/msg00203.txt.bz2 Content-length: 530 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 --- Comment #6 from Pedro Alves --- I'm having mixed feelings about LONGEST->__int128 :-( A lot of code uses (U)LONGEST for indexes, sizes and also to hold register values. Most of th= ese places won't ever need the extended precision. I'm not sure whether forcing everything to use 128-bit is a good idea, both efficiency/ABI -wise, and memory-space wise. :-/ --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21403-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 19 19:35:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 76850 invoked by alias); 19 May 2017 19:35:55 -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 76817 invoked by uid 48); 19 May 2017 19:35:54 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21185] add i128 and u128 support to rust Date: Fri, 19 May 2017 19:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q2/txt/msg00204.txt.bz2 Content-length: 1552 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 --- Comment #7 from Tom Tromey --- (In reply to Pedro Alves from comment #6) > I'm having mixed feelings about LONGEST->__int128 :-( A lot of code uses > (U)LONGEST for indexes, sizes and also to hold register values. Most of > these places won't ever need the extended precision. I'm not sure whether > forcing everything to use 128-bit is a good idea, both efficiency/ABI -wi= se, > and memory-space wise. :-/ Yes, I agree. I took this approach because I thought there was a chance that I could get 128-bit support working this way; because my feeling is that the other ways are probably difficult. What would be a better plan? Printing seems reasonably contained, perhaps. We could introduce analogues of the print-utils functions that work on gdb_byte arrays, supporting larger widths (avoiding the need for __int128 on the host). I suppose there aren't many spots that would need to be changed to make this work. Arithmetic seems difficult. Maybe a new type for this, then (the hard part) change various places to use the new type rather than (U)LONGEST? It seems like it would hard to even find the places, unless maybe the new type was a class that did not allow conversions from integer types. Hmm... I wonder if the Python layer also needs updates to be able to represent such values in Python. This sounds like a project probably out of reach of my free time. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21404-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat May 20 04:14:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 73882 invoked by alias); 20 May 2017 04:14:00 -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 73840 invoked by uid 55); 20 May 2017 04:13:59 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug rust/21484] watch -location does not work with rust Date: Sat, 20 May 2017 04:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q2/txt/msg00205.txt.bz2 Content-length: 3178 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21484 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D43cc5389bc46= 62b31cad02a9f13358bd367d0ab3 commit 43cc5389bc4662b31cad02a9f13358bd367d0ab3 Author: Tom Tromey Date: Sun May 14 11:12:14 2017 -0600 Use watchpoint's language when re-parsing expression PR rust/21484 notes that watch -location does not work with Rust: (gdb) watch -location a syntax error in expression, near `) 0x00007fffffffe0f4'. update_watchpoint tries to tell gdb that the new expression it creates has C syntax: /* The above expression is in C. */ b->language =3D language_c; However, update_watchpoint doesn't actually use this language when re-parsing the expression. Originally I was going to fix this by saving and restoring the language in update_watchpoint, but this regressed gdb.dlang/watch-loc.exp, because the constructed expression actually has D syntax (specifically the name is not parseable by C). Next I looked at directly constructing an expression, and not relying on the parser at all; but it seemed to me that upon a re-set, we'd want to reparse the type, and there is no existing API to do this correctly. So, in the end I made a hook to let each language choose what expression to use. I made all the languages other than Rust use the C expression, because that is the status quo ante. However, this is probably not truly correct. After this patch, at least, it is easy to correct by someone who knows the language(s) in question. Regtested by the buildbot. ChangeLog 2017-05-19 Tom Tromey PR rust/21484: * rust-lang.c (exp_descriptor_rust): New function. (rust_language_defn): Use it. * p-lang.c (pascal_language_defn): Update. * opencl-lang.c (opencl_language_defn): Update. * objc-lang.c (objc_language_defn): Update. * m2-lang.c (m2_language_defn): Update. * language.h (struct language_defn) : New member. * language.c (unknown_language_defn, auto_language_defn) (local_language_defn): Update. * go-lang.c (go_language_defn): Update. * f-lang.c (f_language_defn): Update. * d-lang.c (d_language_defn): Update. * c-lang.h (c_watch_location_expression): Declare. * c-lang.c (c_watch_location_expression): New function. (c_language_defn, cplus_language_defn, asm_language_defn) (minimal_language_defn): Use it. * breakpoint.c (watch_command_1): Call la_watch_location_expression. * ada-lang.c (ada_language_defn): Update. testsuite/ChangeLog 2017-05-19 Tom Tromey PR rust/21484: * gdb.rust/watch.exp: New file. * gdb.rust/watch.rs: New file. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21405-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat May 20 14:55:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 101555 invoked by alias); 20 May 2017 14:55:01 -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 101483 invoked by uid 48); 20 May 2017 14:55:00 -0000 From: "sourceware-bugzilla at zulan dot net" To: gdb-prs@sourceware.org Subject: [Bug gdb/21506] New: python execute(to_string=True) no longer captures certain output since e7ea3ec7 Date: Sat, 20 May 2017 14:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sourceware-bugzilla at zulan dot net X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00206.txt.bz2 Content-length: 1736 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21506 Bug ID: 21506 Summary: python execute(to_string=3DTrue) no longer captures certain output since e7ea3ec7 Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: sourceware-bugzilla at zulan dot net Target Milestone: --- python gdb.execute(to_string=3DTrue) no longer captures all output, in part= icular for the 'step' command, since f7c382926d. This is limits functionality, e.g. http://stackoverflow.com/questions/39602306/tracing-program-function-execut= ion-on-source-line-level Expected result (f7c382926d) $ ./gdb/gdb ../a.out GNU gdb (GDB) 7.11.50.20160331-git Reading symbols from ../a.out...done. (gdb) break main Breakpoint 1 at 0x4004aa: file test.c, line 3. (gdb) run Starting program: /home/tilsche/code/gdb/a.out=20 Breakpoint 1, main () at test.c:3 3 return 4; (gdb) python x =3D gdb.execute('step', to_string=3DTrue) (gdb) python print(x) 4 } Result since e7ea3ec7c6 $ ./gdb/gdb ../a.out=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20 GNU gdb (GDB) 7.11.50.20160331-git Reading symbols from ../a.out...done. (gdb) break main Breakpoint 1 at 0x4004aa: file test.c, line 3. (gdb) run Starting program: /home/tilsche/code/gdb/a.out=20 Breakpoint 1, main () at test.c:3 3 return 4; (gdb) python x =3D gdb.execute('step', to_string=3DTrue) 4 } (gdb) python print(x) Test code: int main() { return 4; } --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21406-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 21 19:09:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 92075 invoked by alias); 21 May 2017 19:09:40 -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 92042 invoked by uid 48); 21 May 2017 19:09:40 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21466] better printing of unsized types Date: Sun, 21 May 2017 19:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q2/txt/msg00207.txt.bz2 Content-length: 466 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21466 --- Comment #1 from Tom Tromey --- Printing the array's address is intentional, see generic_val_print_array. I suppose the idea is that we can't be sure there's even a single element. Maybe there's something better the rust code could print here, but I don't know what that might be at this point. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21407-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 21 22:59:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 14964 invoked by alias); 21 May 2017 22:59:41 -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 14934 invoked by uid 48); 21 May 2017 22:59:40 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21484] watch -location does not work with rust Date: Sun, 21 May 2017 22:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q2/txt/msg00208.txt.bz2 Content-length: 604 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21484 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Tom Tromey --- I'm probably not going to try to get this into 8.0. There's still no post-8.0 target milestone though. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21408-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 21 23:03:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 91695 invoked by alias); 21 May 2017 23:03:46 -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 89776 invoked by uid 55); 21 May 2017 23:03:46 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug rust/21466] better printing of unsized types Date: Sun, 21 May 2017 23:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q2/txt/msg00209.txt.bz2 Content-length: 1274 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21466 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3De6cf65f283b8= be44014fad0ad0aebfbcc71fceac commit e6cf65f283b8be44014fad0ad0aebfbcc71fceac Author: Tom Tromey Date: Sun May 21 17:00:10 2017 -0600 Print Rust unsized array types a bit more nicely It's a bit difficult to create an unsized array type in Rust, but if you do, right now ptype will show something like "[u8; ]". It really should print "[u8]", though, which is what this patch implements. This is part of PR 21466. Built and regtested on x86-64 Fedora 25. I'm checking this in. ChangeLog 2017-05-21 Tom Tromey PR rust/21466: * rust-lang.c (rust_print_type) : Print unsized arrays as "[T]", not "[T; ]". testsuite/ChangeLog 2017-05-21 Tom Tromey PR rust/21466: * gdb.rust/unsized.exp: New file. * gdb.rust/unsized.rs: New file. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21409-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun May 21 23:04:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78702 invoked by alias); 21 May 2017 23:04:18 -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 77171 invoked by uid 48); 21 May 2017 23:04:17 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21466] better printing of unsized types Date: Sun, 21 May 2017 23:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q2/txt/msg00210.txt.bz2 Content-length: 298 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21466 --- Comment #3 from Tom Tromey --- I'm leaving this one open until I decide what, if anything, to do about printing these values. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21410-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon May 22 03:20:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 125724 invoked by alias); 22 May 2017 03:20: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 125690 invoked by uid 48); 22 May 2017 03:20:22 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21185] add i128 and u128 support to rust Date: Mon, 22 May 2017 03:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q2/txt/msg00211.txt.bz2 Content-length: 361 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 --- Comment #8 from Tom Tromey --- Maybe printing doesn't need much attention, since now I see the print_*_chars family of functions in valprint.c. Weird that I've never run into these before. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21411-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon May 22 15:49:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 62362 invoked by alias); 22 May 2017 15:49:54 -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 61462 invoked by uid 48); 22 May 2017 15:49:54 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21185] add i128 and u128 support to rust Date: Mon, 22 May 2017 15:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q2/txt/msg00212.txt.bz2 Content-length: 744 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 --- Comment #9 from Pedro Alves --- > It seems like it would hard to even find the places, unless maybe the new > type was a class that did not allow conversions from integer types. > Hmm... Yeah, I think a class (plus arithmetic operators) would be what I'd try too= .=20=20 Maybe we could borrow gcc's wide_int (or parts of it). Not sure about disabling conversions from integer types. I'd assume it to = be handy, to allow natural initialization from 0 and 1 [integer foo =3D 1;], e= tc.=20 I'd think that it's conversion to (narrower) integer types that would be an issue. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21412-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon May 22 22:05:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66756 invoked by alias); 22 May 2017 22:05:36 -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 66729 invoked by uid 48); 22 May 2017 22:05:35 -0000 From: "samb1999 at hotmail dot co.uk" To: gdb-prs@sourceware.org Subject: [Bug guile/21104] 7.12.1 does not compile with latest guile (2.1.6) Date: Mon, 22 May 2017 22:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: guile X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: samb1999 at hotmail dot co.uk X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00213.txt.bz2 Content-length: 403 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21104 Sam Bazley changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |samb1999 at hotmail dot co= .uk --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21413-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon May 22 22:25:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68036 invoked by alias); 22 May 2017 22:25:45 -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 68002 invoked by uid 48); 22 May 2017 22:25:44 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21185] add i128 and u128 support to rust Date: Mon, 22 May 2017 22:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q2/txt/msg00214.txt.bz2 Content-length: 1014 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 --- Comment #10 from Tom Tromey --- (In reply to Pedro Alves from comment #9) > > It seems like it would hard to even find the places, unless maybe the n= ew > > type was a class that did not allow conversions from integer types. > > Hmm... >=20 > Yeah, I think a class (plus arithmetic operators) would be what I'd try t= oo. >=20 > Maybe we could borrow gcc's wide_int (or parts of it). >=20 > Not sure about disabling conversions from integer types. I'd assume it to > be handy, to allow natural initialization from 0 and 1 [integer foo =3D 1= ;], > etc. I'd think that it's conversion to (narrower) integer types that wou= ld > be an issue. Yeah, duh, that makes sense. I've got some cleanups to the scalar printing code that might be useful. Not quite done -- there's some weird stuff in there. I haven't looked at the arithmetic stuff. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21414-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 24 15:49:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127267 invoked by alias); 24 May 2017 15:49:15 -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 127204 invoked by uid 48); 24 May 2017 15:49:13 -0000 From: "82369082 at qq dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21515] New: Segmentation fault when gdb is started Date: Wed, 24 May 2017 15:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: 82369082 at qq dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00215.txt.bz2 Content-length: 555 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21515 Bug ID: 21515 Summary: Segmentation fault when gdb is started Product: gdb Version: 7.11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: 82369082 at qq dot com Target Milestone: --- Look here: https://github.com/pwndbg/pwndbg/issues/286 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21415-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 25 01:57:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 30865 invoked by alias); 25 May 2017 01:57:19 -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 30625 invoked by uid 48); 25 May 2017 01:57:17 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21185] add i128 and u128 support to rust Date: Thu, 25 May 2017 01:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q2/txt/msg00216.txt.bz2 Content-length: 544 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 --- Comment #11 from Tom Tromey --- This is pretty close, I think, but it turns out there are some tests that rely on the current behavior where gdb will print 128 bit values with zero padding; whereas the patch series I have turns this off. Updating the tests isn't too bad, so far, but since some occur in arch-specific tests I suspect there will be some that I can't test. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21417-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 25 02:53:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 21444 invoked by alias); 25 May 2017 02:53:34 -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 21413 invoked by uid 48); 25 May 2017 02:53:33 -0000 From: "peter at elemental dot software" To: gdb-prs@sourceware.org Subject: [Bug mi/11335] -var-evaluate-expression should return the pretty printer's to_string result Date: Thu, 25 May 2017 02:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: peter at elemental dot software X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.1 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: 2017-q2/txt/msg00218.txt.bz2 Content-length: 223 https://sourceware.org/bugzilla/show_bug.cgi?id=3D11335 --- Comment #8 from Peter Linss --- Patch sumbitted --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21416-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 25 02:53:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20735 invoked by alias); 25 May 2017 02:53:11 -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 20706 invoked by uid 48); 25 May 2017 02:53:11 -0000 From: "peter at elemental dot software" To: gdb-prs@sourceware.org Subject: [Bug mi/11335] -var-evaluate-expression should return the pretty printer's to_string result Date: Thu, 25 May 2017 02:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: peter at elemental dot software X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc attachments.created 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: 2017-q2/txt/msg00217.txt.bz2 Content-length: 635 https://sourceware.org/bugzilla/show_bug.cgi?id=3D11335 Peter Linss changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peter at elemental dot sof= tware --- Comment #7 from Peter Linss --- Created attachment 10068 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10068&action=3Ded= it Patch to always call to_string for pretty-printers --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21418-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 25 14:50:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122325 invoked by alias); 25 May 2017 14:50:56 -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 122299 invoked by uid 48); 25 May 2017 14:50:55 -0000 From: "82369082 at qq dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21515] Segmentation fault when gdb is started Date: Thu, 25 May 2017 14:50: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.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: 82369082 at qq dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00219.txt.bz2 Content-length: 1880 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21515 --- Comment #1 from 82369082 at qq dot com --- Hi, when I use python3.5 in GDB, the _rl_screenwidth is assigned a wrong va= lue. =3D=3D _rl_get_screen_size(): _rl_screenwidth: 0 =3D=3D _rl_get_screen_size(): _rl_screenwidth: 175 =3D=3D rl_get_screen_size(): _rl_screenwidth: 175, _rl_screenheight: 47 =3D=3D init_page_info(): rows 47, cols 175 =3D=3D _rl_set_screen_size(): rows: 47, cols: 175, _rl_screenwidth: 175 =3D=3D _rl_set_screen_size(): _rl_screenwidth: 174 GNU gdb (GDB) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=3Dx86_64-pc-linux-gnu --target=3Darm-lin= ux". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) python >import gdb >gdb.execute('set debug-file-directory %s' % "nihaoma", to_string=3DTrue, f= rom_tty=3DFalse) >end =3D=3D=3D execute_command_to_string(): p: set debug-file-directory nihaoma =3D=3D init_page_info(): rows -1, cols -1 =3D=3D _rl_set_screen_size(): rows: 2147483647, cols: 2147483647, _rl_scre= enwidth: 174 =3D=3D _rl_set_screen_size(): _rl_screenwidth: 2147483646 =3D=3D _rl_set_screen_size(): rows: 47, cols: 175, _rl_screenwidth: 214748= 3646 =3D=3D _rl_set_screen_size(): _rl_screenwidth: 174 (gdb) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21419-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 25 23:43:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 111682 invoked by alias); 25 May 2017 23:43:00 -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 111655 invoked by uid 48); 25 May 2017 23:43:00 -0000 From: "anton at samba dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21526] New: powerpc64: gdb should use local entry point symbol instead of loosely parsing instructions Date: Thu, 25 May 2017 23:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: anton at samba dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00220.txt.bz2 Content-length: 1876 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21526 Bug ID: 21526 Summary: powerpc64: gdb should use local entry point symbol instead of loosely parsing instructions Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: anton at samba dot org Target Milestone: --- gdb isn't using the local entry point when stepping over the global entry point. An example: #include .text FUNC_START(main) .rept 8 addpcis r3,0 ori r3,r3,0 .endr blr FUNC_END(main) (gdb) break main Breakpoint 1 at 0x7c8 (gdb) run Starting program: /tmp/f=20 Breakpoint 1, 0x00000000200007c8 in main () (gdb) disassemble=20 Dump of assembler code for function main: 0x0000000020000780 <+0>: addis r2,r12,2 0x0000000020000784 <+4>: addi r2,r2,30592 0x0000000020000788 <+8>: lnia r3 0x000000002000078c <+12>: ori r3,r3,0 0x0000000020000790 <+16>: lnia r3 0x0000000020000794 <+20>: ori r3,r3,0 0x0000000020000798 <+24>: lnia r3 0x000000002000079c <+28>: ori r3,r3,0 0x00000000200007a0 <+32>: lnia r3 0x00000000200007a4 <+36>: ori r3,r3,0 0x00000000200007a8 <+40>: lnia r3 0x00000000200007ac <+44>: ori r3,r3,0 0x00000000200007b0 <+48>: lnia r3 0x00000000200007b4 <+52>: ori r3,r3,0 0x00000000200007b8 <+56>: lnia r3 0x00000000200007bc <+60>: ori r3,r3,0 0x00000000200007c0 <+64>: lnia r3 0x00000000200007c4 <+68>: ori r3,r3,0 =3D> 0x00000000200007c8 <+72>: blr End of assembler dump. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21420-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri May 26 19:36:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 91927 invoked by alias); 26 May 2017 19:36:24 -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 91654 invoked by uid 48); 26 May 2017 19:36:24 -0000 From: "mjfoley at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21527] New: macro expand not correct after #undef and #define Date: Fri, 26 May 2017 19:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: mjfoley at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00221.txt.bz2 Content-length: 1363 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21527 Bug ID: 21527 Summary: macro expand not correct after #undef and #define Product: gdb Version: unknown Status: UNCONFIRMED Severity: minor Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: mjfoley at gmail dot com Target Milestone: --- Macro expansion does not honor #undef and #define, it seems to only use the first #define encountered for a given macro name in dwarves.h dwarf(Dopey) dwarf(Doc) dwarf(Sleepy) dwarf(Bashful) dwarf(Happy) dwarf(Sneezy) dwarf(Grumpy) in forest.c main() { printf("Deep in the forest.\n"); #define dwarf(name) printf("There was a dwarf named %s.\n",#name); #include // as you debug next will take you across each line of dwarves.h and expand properly #undef dwarf int namelength[10]=3D{0}; #define dwarf(name) namelength[strlen(#Name)]++; #include // as you debug here, "macro expand dwarf(Sleepy)" shows the printf not the= ++ #undef for (nl=3D0;nl<(sizeof(namelength)/sizeof(namelength[0]);nl++) if (namelength[nl]) printf("%d dwarf/dwarves have name(s) %d letters long\n", namelength[nl],nl): } --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21421-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue May 30 01:35:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 25212 invoked by alias); 30 May 2017 01:35:10 -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 25168 invoked by uid 48); 30 May 2017 01:35:09 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug cli/19551] weird "reading symbols" output Date: Tue, 30 May 2017 01:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q2/txt/msg00222.txt.bz2 Content-length: 276 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19551 --- Comment #1 from Tom Tromey --- One attempt: https://sourceware.org/ml/gdb-patches/2017-04/msg00388.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21422-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 31 12:20:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 48882 invoked by alias); 31 May 2017 12:20:37 -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 48835 invoked by uid 48); 31 May 2017 12:20:36 -0000 From: "jbm at bachmeier dot cc" To: gdb-prs@sourceware.org Subject: [Bug gdb/20948] --write option to GDB causes segmentation fault Date: Wed, 31 May 2017 12:20: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jbm at bachmeier dot cc X-Bugzilla-Status: UNCONFIRMED 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: cc attachments.created 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: 2017-q2/txt/msg00223.txt.bz2 Content-length: 556 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20948 jbm at bachmeier dot cc changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jbm at bachmeier dot cc --- Comment #2 from jbm at bachmeier dot cc --- Created attachment 10078 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10078&action=3Ded= it Full reproduction example --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21423-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 31 12:22:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53388 invoked by alias); 31 May 2017 12:22:15 -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 53355 invoked by uid 48); 31 May 2017 12:22:15 -0000 From: "jbm at bachmeier dot cc" To: gdb-prs@sourceware.org Subject: [Bug gdb/20948] --write option to GDB causes segmentation fault Date: Wed, 31 May 2017 12:22: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jbm at bachmeier dot cc X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00224.txt.bz2 Content-length: 2771 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20948 --- Comment #3 from jbm at bachmeier dot cc --- Comment on attachment 10078 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10078 Full reproduction example This indeed seems to be a problem in libbfd. I was encountered the problem while using the library.=20 The segfault seems to occur when opening a file for both reading and writin= g. Minimal example: $ cat bfdbug.c #include // Error checks omitted for clarity, see attachment int main(int argc, char **argv) { bfd *abfd =3D bfd_fopen(argv[1], "default", "r+", -1); bfd_check_format(abfd, bfd_object); bfd_close(abfd); } $ gcc bfdbug.c -g -lbfd -o bfdbug $ cp bfdbug test.elf $ gdb bfdbug GNU gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from bfdbug...done. (gdb) run test.elf Starting program: /home/bachme/bt-cgp/cgp/bfdbug test.elf Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7b1f391 in _bfd_elf_strtab_finalize () from /usr/lib/x86_64-linux-gnu/libbfd-2.28-system.so (gdb) where #0 0x00007ffff7b1f391 in _bfd_elf_strtab_finalize () from /usr/lib/x86_64-linux-gnu/libbfd-2.28-system.so #1 0x00007ffff7b01a17 in _bfd_elf_write_object_contents () from /usr/lib/x86_64-linux-gnu/libbfd-2.28-system.so #2 0x00007ffff7adff87 in bfd_close () from /usr/lib/x86_64-linux-gnu/libbfd-2.28-system.so #3 0x0000555555554856 in main (argc=3D2, argv=3D0x7fffffffe588) at bfdbug.= c:7 (gdb) When using "w" or "r" instead of "r+" as the mode argument to bfd_fopen (or using bfd_openr/bfd_openw instead), no error ocurrs (even when adding symbo= ls to the symtab / strtab) before closing. Binutils version: $ objdump -V GNU objdump (GNU Binutils for Ubuntu) 2.28 Copyright (C) 2017 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License version 3 or (at your option) any later vers= ion. This program has absolutely no warranty. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21424-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 31 13:03:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 83994 invoked by alias); 31 May 2017 13:03:54 -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 83971 invoked by uid 48); 31 May 2017 13:03:53 -0000 From: "wdijkstr at arm dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21535] New: gdb fails to build with GCC trunk Date: Wed, 31 May 2017 13:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wdijkstr at arm dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00225.txt.bz2 Content-length: 934 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21535 Bug ID: 21535 Summary: gdb fails to build with GCC trunk Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: wdijkstr at arm dot com Target Milestone: --- Typical error messages are: In file included from /native-arm-none-linux-gnueabihf/build/src/binutils-gdb/gdb/inferior.h:41:0, from /native-arm-none-linux-gnueabihf/build/src/binutils-gdb/gdb/arm-tdep.c:25: /native-arm-none-linux-gnueabihf/build/src/binutils-gdb/gdb/target.h:102:8: error: using template type parameter 'const _Alloc' after 'struct' struct syscall ^~~~~~~ There are many similar messages. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21425-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 31 17:33:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 90666 invoked by alias); 31 May 2017 17:33:21 -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 90641 invoked by uid 48); 31 May 2017 17:33:20 -0000 From: "wdijkstr at arm dot com" To: gdb-prs@sourceware.org Subject: [Bug build/21535] gdb fails to build with GCC trunk Date: Wed, 31 May 2017 17:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wdijkstr at arm 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q2/txt/msg00226.txt.bz2 Content-length: 576 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21535 Wilco changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Wilco --- Looks like this was an odd frontend bug in GCC r248686 but it is fixed after r248687. Closing. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21426-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 31 20:02:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49183 invoked by alias); 31 May 2017 20:02:28 -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 49160 invoked by uid 48); 31 May 2017 20:02:27 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21324] gdb hangs when 'thread apply all bt full' is used Date: Wed, 31 May 2017 20:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: simon.marchi at ericsson dot com 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: cc 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: 2017-q2/txt/msg00227.txt.bz2 Content-length: 787 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21324 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.marchi at ericsson d= ot com --- Comment #4 from Simon Marchi --- Hi Brian, My guess is that GDB is stuck in an infinite loop trying to unwind the stacks/generate the backtraces. One would need to step into GDB itself to understand what's going wrong. I'll try to rebuild the Ubuntu package for = vim, generate some core and see if I can reproduce the issue. Simon --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21427-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed May 31 21:32:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 92715 invoked by alias); 31 May 2017 21:32:46 -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 87985 invoked by uid 48); 31 May 2017 21:32:44 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21324] gdb hangs when 'thread apply all bt full' is used Date: Wed, 31 May 2017 21:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: simon.marchi at ericsson dot com 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: 2017-q2/txt/msg00228.txt.bz2 Content-length: 785 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21324 --- Comment #5 from Simon Marchi --- (In reply to Simon Marchi from comment #4) > Hi Brian, >=20 > My guess is that GDB is stuck in an infinite loop trying to unwind the > stacks/generate the backtraces. One would need to step into GDB itself to > understand what's going wrong. I'll try to rebuild the Ubuntu package for > vim, generate some core and see if I can reproduce the issue. >=20 > Simon I wasn't able to reproduce the problem using GNU gdb (GDB) 8.0.50.20170531-= git . I suppose it needs a particular situation for it to trigger. If you fin= d a way to reproduce easily, please share it. Simon --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21428-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 01 09:21:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53464 invoked by alias); 1 Jun 2017 09:21:37 -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 52280 invoked by uid 48); 1 Jun 2017 09:21:35 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21324] gdb hangs when 'thread apply all bt full' is used Date: Thu, 01 Jun 2017 09:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com 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: cc 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: 2017-q2/txt/msg00229.txt.bz2 Content-length: 576 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21324 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #6 from Pedro Alves --- > strace: [ Process PID=3D16418 runs in x32 mode. ] Does this mean that the GDB that hangs is built as a x32 process? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21429-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 01 09:22:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 82190 invoked by alias); 1 Jun 2017 09:22:05 -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 80763 invoked by uid 48); 1 Jun 2017 09:22:04 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21324] gdb hangs when 'thread apply all bt full' is used Date: Thu, 01 Jun 2017 09:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com 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: 2017-q2/txt/msg00230.txt.bz2 Content-length: 404 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21324 --- Comment #7 from Pedro Alves --- Brian, I assume you're detecting the hangs and killing GDB. Any chance you= can attach another GDB to the hung GDB before killing it, and get a "thread app= ly all bt" so can we see where is GDB stuck? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21430-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 01 10:14:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 69482 invoked by alias); 1 Jun 2017 10:14:44 -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 69267 invoked by uid 48); 1 Jun 2017 10:14:39 -0000 From: "jbm at bachmeier dot cc" To: gdb-prs@sourceware.org Subject: [Bug gdb/20948] --write option to GDB causes segmentation fault Date: Thu, 01 Jun 2017 10:14: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jbm at bachmeier dot cc X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00231.txt.bz2 Content-length: 466 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20948 --- Comment #4 from jbm at bachmeier dot cc --- This is a null-ptr dereference in bfd/elf-strtab.c:367, resulting from a null-ptr stringtab extracted in bfd/elf.c:6272. elf_shstrtab(abfd) =3D=3D abfd->tdata.elf_obj_data->o->strtab_ptr =3D=3D= NULL I don't know any BFD internals, so I sadly can't investigate this further. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21431-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 01 21:09:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 93488 invoked by alias); 1 Jun 2017 21:09:42 -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 92598 invoked by uid 48); 1 Jun 2017 21:09:41 -0000 From: "brian at ubuntu dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21324] gdb hangs when 'thread apply all bt full' is used Date: Thu, 01 Jun 2017 21:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: brian at ubuntu dot com 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: 2017-q2/txt/msg00232.txt.bz2 Content-length: 2829 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21324 --- Comment #8 from brian at ubuntu dot com --- I attached to the hung gdb process which was trying to retrace a crash from kodi. I then ran thread apply all bt and observed the following: (gdb) thread apply all bt Thread 1 (Thread 0x7fd6d1f41780 (LWP 8736)): #0 0x000055e6d9b0503d in ?? () #1 0x000055e6d9b0547f in ?? () #2 0x000055e6d9afe451 in ?? () #3 0x000055e6d9b041da in ?? () #4 0x000055e6d9b01221 in ?? () #5 0x000055e6d9b01f8a in ?? () #6 0x000055e6d9ae62bf in ?? () #7 0x000055e6d9aee9d1 in ?? () #8 0x000055e6d9ae60d8 in ?? () #9 0x000055e6d9ae8265 in ?? () #10 0x000055e6d9ae60a8 in ?? () #11 0x000055e6d9ae58cc in ?? () #12 0x000055e6d9ae467d in ?? () #13 0x000055e6d9ad81d2 in ?? () #14 0x000055e6d9ae4979 in ?? () #15 0x000055e6d9ae42e6 in ?? () #16 0x000055e6d9bdbbae in ?? () #17 0x000055e6d9bdae0a in ?? () #18 0x000055e6d9c2eea1 in ?? () #19 0x000055e6d9c2f0d1 in ?? () #20 0x000055e6d9a4dfaf in ?? () #21 0x000055e6d9ac7bb4 in ?? () #22 0x000055e6d9ac7ff6 in ?? () #23 0x000055e6d9ac2416 in ?? () #24 0x000055e6d9abe95c in ?? () #25 0x000055e6d9b30576 in ?? () #26 0x000055e6d9b300c0 in ?? () #27 0x000055e6d9b31c4b in ?? () #28 0x000055e6d9b3233d in ?? () #29 0x000055e6d9b324d3 in ?? () #30 0x000055e6d9b32b26 in ?? () #31 0x000055e6d9ac88a7 in ?? () #32 0x000055e6d9ac8a43 in ?? () #33 0x000055e6d9acf3ba in ?? () #34 0x000055e6d9c1532c in ?? () #35 0x000055e6d9c15ef7 in ?? () #36 0x000055e6d9c1713c in ?? () #37 0x000055e6d9c165a5 in ?? () #38 0x000055e6d9c189c2 in ?? () #39 0x000055e6d9c18ddb in ?? () #40 0x000055e6d99744d4 in ?? () #41 0x000055e6d9977861 in ?? () #42 0x000055e6d9c5dc50 in ?? () #43 0x000055e6d9c592a7 in ?? () #44 0x000055e6d99744d4 in ?? () #45 0x000055e6d9977861 in ?? () #46 0x000055e6d9c5dc50 in ?? () #47 0x000055e6d9b1df2a in ?? () #48 0x000055e6d9b1e337 in ?? () #49 0x000055e6d9b1d80e in ?? () #50 0x00007fd6d1b46d73 in rl_callback_read_char () from /lib/x86_64-linux-gnu/libreadline.so.7 #51 0x000055e6d9b1d6fa in ?? () #52 0x000055e6d9b1d779 in ?? () #53 0x000055e6d9b1ddc1 in ?? () #54 0x000055e6d9b1c097 in ?? () #55 0x000055e6d9b1c660 in ?? () #56 0x000055e6d9b1b3d6 in ?? () #57 0x000055e6d9b1b41d in ?? () #58 0x000055e6d9b998ac in ?? () #59 0x000055e6d9b1f460 in ?? () ---Type to continue, or q to quit--- #60 0x000055e6d9b9af03 in ?? () #61 0x000055e6d9b9af3b in ?? () #62 0x000055e6d98a9d39 in ?? () #63 0x00007fd6cfaa43f1 in __libc_start_main (main=3D0x55e6d98a9ce0, argc=3D= 13, argv=3D0x7ffe07075828, init=3D, fini=3D, rtld_fini=3D, stack_end=3D0x7ffe07075818) at ../csu/libc-sta= rt.c:291 #64 0x000055e6d98a9bda in ?? () --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21432-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 01 21:20:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 737 invoked by alias); 1 Jun 2017 21:20: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 130472 invoked by uid 48); 1 Jun 2017 21:20:22 -0000 From: "brian at ubuntu dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21324] gdb hangs when 'thread apply all bt full' is used Date: Thu, 01 Jun 2017 21:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: brian at ubuntu dot com 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: 2017-q2/txt/msg00233.txt.bz2 Content-length: 1231 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21324 --- Comment #9 from brian at ubuntu dot com --- I tried the same process, attaching gdb to the hung gdb which was this time retracing a core file from vim, and the output was similar to that with the kodi core file. Here's a snippet: Thread 1 (Thread 0x7f6ab8dd8780 (LWP 10437)): #0 0x0000559fa47219ce in ?? () ... #59 0x00007f6ab89ddd73 in rl_callback_read_char () from /lib/x86_64-linux-gnu/libreadline.so.7 60 0x0000559fa475a6fa in ?? () #61 0x0000559fa475a779 in ?? () #62 0x0000559fa475adc1 in ?? () #63 0x0000559fa4759097 in ?? () #64 0x0000559fa4759660 in ?? () #65 0x0000559fa47583d6 in ?? () #66 0x0000559fa475841d in ?? () #67 0x0000559fa47d68ac in ?? () #68 0x0000559fa475c460 in ?? () #69 0x0000559fa47d7f03 in ?? () #70 0x0000559fa47d7f3b in ?? () #71 0x0000559fa44e6d39 in ?? () #72 0x00007f6ab693b3f1 in __libc_start_main (main=3D0x559fa44e6ce0, argc=3D= 13, argv=3D0x7ffe65d3fe68, init=3D, fini=3D, rtld_fini=3D, stack_end=3D0x7ffe65d3fe58) at ../csu/libc-start.c:291 #73 0x0000559fa44e6bda in ?? () --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21433-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 01 21:31:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 124348 invoked by alias); 1 Jun 2017 21:31:21 -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 124320 invoked by uid 48); 1 Jun 2017 21:31:21 -0000 From: "brian at ubuntu dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21324] gdb hangs when 'thread apply all bt full' is used Date: Thu, 01 Jun 2017 21:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: brian at ubuntu dot com 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: attachments.created 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: 2017-q2/txt/msg00234.txt.bz2 Content-length: 586 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21324 --- Comment #10 from brian at ubuntu dot com --- Created attachment 10080 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10080&action=3Ded= it output from gdb when attached to gdb hang I installed debug symbols for gdb and received more detailed information wh= en running 'thread apply all bt'. I've added it as an attachment since it is rather lengthy. Please let me know if there is anything else you need. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21434-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 02 03:55:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 72163 invoked by alias); 2 Jun 2017 03:55:15 -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 71141 invoked by uid 48); 2 Jun 2017 03:54:18 -0000 From: "kinetik at flim dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/19221] Allow setting write watchpoint that trigger without changes Date: Fri, 02 Jun 2017 03:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kinetik at flim dot org 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: cc 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: 2017-q2/txt/msg00235.txt.bz2 Content-length: 393 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19221 Matthew Gregan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kinetik at flim dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21435-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 02 09:34:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36378 invoked by alias); 2 Jun 2017 09:34:44 -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 36343 invoked by uid 48); 2 Jun 2017 09:34:43 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/21324] gdb hangs when 'thread apply all bt full' is used Date: Fri, 02 Jun 2017 09:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com 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: 2017-q2/txt/msg00236.txt.bz2 Content-length: 1317 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21324 --- Comment #11 from Pedro Alves --- Is that a pristine upstream GDB, or an ubuntu GDB? The reason I ask is that ubuntu's gdb may have local patches that who knows, might cause this. It'd= be nice to test with current upstream master. That'd also let us know whether= the issue might be fixed already. Looking at the backtrace, we're in inline_frame_sniffer -> frame_unwind_register -> dwarf2_tailcall_sniffer_first, and then end up in = the dwarf reader. Both the inline and tailcall sniffers rely on accurate debug/unwind info. I can imagine cycles appearing with e.g., bad unwind info. I'd suspect something odd along those lines. Also, seeing the two sniffers in the same backtrace is suspicious. I think the next step would be to determine where exactly is the cycle. I.= e., once you get a hung gdb, attach to it, and step through the code until you figure out what's the infinite that never breaks. I'd disable the frame filters and whatever other scripts gdb may be loading= , to confirm that the problem isn't being triggered by something they're doing. = If that "fixes" the problem, them we have a better idea where to look next. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21436-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 02 19:22:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36439 invoked by alias); 2 Jun 2017 19:22:45 -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 36411 invoked by uid 48); 2 Jun 2017 19:22:44 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug exp/20991] __int128 type support Date: Fri, 02 Jun 2017 19:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: blocked dependson 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: 2017-q2/txt/msg00237.txt.bz2 Content-length: 857 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20991 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |21185 Depends on| |16225 --- Comment #2 from Tom Tromey --- Handling the printing in bug 16225, so maybe this bug could be for the operations. See some discussion in bug 21185 for how to do that. Referenced Bugs: https://sourceware.org/bugzilla/show_bug.cgi?id=3D16225 [Bug 16225] __int128_t types print strangely https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 [Bug 21185] add i128 and u128 support to rust --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21438-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 02 19:22:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36775 invoked by alias); 2 Jun 2017 19:22:47 -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 36593 invoked by uid 48); 2 Jun 2017 19:22:46 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21185] add i128 and u128 support to rust Date: Fri, 02 Jun 2017 19:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: dependson 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: 2017-q2/txt/msg00239.txt.bz2 Content-length: 485 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |20991 Referenced Bugs: https://sourceware.org/bugzilla/show_bug.cgi?id=3D20991 [Bug 20991] __int128 type support --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21437-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 02 19:22:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36566 invoked by alias); 2 Jun 2017 19:22:46 -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 36446 invoked by uid 48); 2 Jun 2017 19:22:45 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug exp/16225] __int128_t types print strangely Date: Fri, 02 Jun 2017 19:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: blocked 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: 2017-q2/txt/msg00238.txt.bz2 Content-length: 485 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16225 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |20991 Referenced Bugs: https://sourceware.org/bugzilla/show_bug.cgi?id=3D20991 [Bug 20991] __int128 type support --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21439-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 02 19:44:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109327 invoked by alias); 2 Jun 2017 19:44:38 -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 109286 invoked by uid 48); 2 Jun 2017 19:44:37 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug exp/16225] __int128_t types print strangely Date: Fri, 02 Jun 2017 19:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to 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: 2017-q2/txt/msg00240.txt.bz2 Content-length: 488 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16225 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg Assignee|unassigned at sourceware dot org |tromey at sourcewar= e dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21440-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jun 03 12:58:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 119675 invoked by alias); 3 Jun 2017 12:58:04 -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 118876 invoked by uid 48); 3 Jun 2017 12:58:03 -0000 From: "tree1891 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18624] GDB on windows with golang: buildsym_init Assertion `free_pendings == NULL` failed. Date: Sat, 03 Jun 2017 12:58: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: critical X-Bugzilla-Who: tree1891 at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q2/txt/msg00241.txt.bz2 Content-length: 645 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18624 tree1891 at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tree1891 at gmail dot com --- Comment #6 from tree1891 at gmail dot com --- (In reply to Paul C Brown from comment #5) > Actually, not a bug - just missing a command line argument (at least for > me). The missing argument is "-d $GOROOT" (I am actually debugging Go). what argument is it? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21441-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jun 05 15:04:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 115636 invoked by alias); 5 Jun 2017 15:04:26 -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 115587 invoked by uid 48); 5 Jun 2017 15:04:25 -0000 From: "grasshopper at vollbio dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] New: c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Mon, 05 Jun 2017 15:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: grasshopper at vollbio dot de X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00242.txt.bz2 Content-length: 3709 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 Bug ID: 21549 Summary: c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) =3D=3D TYPE_CODE_PT= R' failed. Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: grasshopper at vollbio dot de Target Milestone: --- GDB exits with exit code 0 and error message (copied from Eclipse console view): &"../../../gdb-7.12.1/gdb/c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, c= onst type_print_options*): Assertion `TYPE_CODE (args[0].type) =3D=3D TYPE_CODE_= PTR' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\n" &"\nThis is a bug, please report it." &" For instructions, see:\n." &"\n\n" 717-gdb-exit GDB is connect to the gdb-server of openocd and thru this to my ARM target. Stepping through the startup code (assembler code) of my target works, ente= ring the C++ part (main() routine) leads to the error above. The error renders the debug session unusable. I have archive all the sources and the relevant binary, so further tests or provision of them are possible. Host OS: Gentoo Linux # uname -a=20 Linux Ghost 4.4.21-gentoo-native-Ghost #3 SMP Sun Mar 19 18:12:33 CET 2017 = i686 Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz GenuineIntel GNU/Linux # arm-none-eabi-gdb --version GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=3Di686-pc-linux-gnu --target=3Darm-none-= eabi". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". # arm-none-eabi-gdb --configuration This GDB was configured as follows: configure --host=3Di686-pc-linux-gnu --target=3Darm-none-eabi --with-auto-load-dir=3D$debugdir:$datadir/auto-load --with-auto-load-safe-path=3D$debugdir:$datadir/auto-load --with-expat =20=20=20=20=20=20=20=20=20=20=20=20 --with-gdb-datadir=3D/home/lode/e_workspace/Stm32-Universal-Blinky+Shell/To= olchain/src/../arm-mcu-tools/share/gdb (relocatable) =20=20=20=20=20=20=20=20=20=20=20=20 --with-jit-reader-dir=3D/home/lode/e_workspace/Stm32-Universal-Blinky+Shell= /Toolchain/src/../arm-mcu-tools/lib/gdb (relocatable) --without-libunwind-ia64 --with-lzma --with-python=3D/usr --without-guile =20=20=20=20=20=20=20=20=20=20=20=20 --with-separate-debug-dir=3D/home/lode/e_workspace/Stm32-Universal-Blinky+S= hell/Toolchain/src/../arm-mcu-tools/lib/debug (relocatable) --without-babeltrace ("Relocatable" means the directory can be moved with the GDB installation tree, and GDB will still find it.) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21442-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jun 05 15:05:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 116302 invoked by alias); 5 Jun 2017 15:05:03 -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 116273 invoked by uid 48); 5 Jun 2017 15:05:03 -0000 From: "grasshopper at vollbio dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Mon, 05 Jun 2017 15:05: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: grasshopper at vollbio dot de X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00243.txt.bz2 Content-length: 400 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 joluxer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |grasshopper at vollbio dot= de --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21443-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 06 08:23:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64588 invoked by alias); 6 Jun 2017 08:23:04 -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 64561 invoked by uid 48); 6 Jun 2017 08:23:04 -0000 From: "grasshopper at vollbio dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Tue, 06 Jun 2017 08:23: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: grasshopper at vollbio dot de X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00244.txt.bz2 Content-length: 284 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 --- Comment #1 from joluxer --- The occurrence of the error is related to lto optimized code output of gcc V4.8.2. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21444-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 06 10:41:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 9658 invoked by alias); 6 Jun 2017 10:41:14 -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 9633 invoked by uid 48); 6 Jun 2017 10:41:13 -0000 From: "thopre01 at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/21553] New: Double free in gdb when running gdb.linespec/ls-errs.exp Date: Tue, 06 Jun 2017 10:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thopre01 at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00245.txt.bz2 Content-length: 1004 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21553 Bug ID: 21553 Summary: Double free in gdb when running gdb.linespec/ls-errs.exp Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: thopre01 at gcc dot gnu.org Target Milestone: --- Hi, GDB started to experience some double free issue when executing gdb.linespec/ls-errs.exp (gdb.linespec/ls-errs.exp: lang=3DC: break -line 3= 1) somewhere between revisions 0efdc7237e8eb2c75b9c74bc60175ef50719b8b8 and 0af6b29b9dcd8ff2c34d07a76e3416acf3758bfc. The exact error message is: Error in `/gdb/gdb': double free or corruption (fasttop): Please let me know what I can do to help resolve this. Best regards. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21445-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 06 11:00:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 13049 invoked by alias); 6 Jun 2017 11:00:54 -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 12890 invoked by uid 48); 6 Jun 2017 11:00:44 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/21553] Double free in gdb when running gdb.linespec/ls-errs.exp Date: Tue, 06 Jun 2017 11:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: cc 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: 2017-q2/txt/msg00246.txt.bz2 Content-length: 4271 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21553 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org --- Comment #1 from Yao Qi --- AddressSanitizer shows this problem more clearly, break -line 3 1^M =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D^M ^[[1m^[[31m=3D=3D28131=3D=3DERROR: AddressSanitizer: attempting double-free= on 0x602000138450 in thread T0:^M ^[[1m^[[0m #0 0x2b6671853631 in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.1+0x54631)^M #1 0x82c45e in xfree(void*) /home/yao/SourceCode/gnu/gdb/git/gdb/common/common-utils.c:100^M #2 0x7ced99 in breakpoint::~breakpoint() /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:12740^M #3 0x7cee1d in breakpoint::~breakpoint() /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:12742^M #4 0x7e0ee8 in std::default_delete::operator()(breakpoint*) const /usr/include/c++/4.9/bits/unique_ptr.h:76^M #5 0x7e01db in std::unique_ptr >::~unique_ptr() /usr/include/c++/4.9/bits/unique_ptr.h:236^M #6 0x7bf182 in create_breakpoint_sal /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:9328^M #7 0x7bf4f4 in create_breakpoints_sal /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:9378^M #8 0x7d5cf7 in create_breakpoints_sal_default /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:14368^M #9 0x7d0355 in bkpt_create_breakpoints_sal /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:13106^M .... ^M ^[[1m^[[32m0x602000138450 is located 0 bytes inside of 2-byte region [0x602000138450,0x602000138452)^M ^[[1m^[[0m^[[1m^[[35mfreed by thread T0 here:^[[1m^[[0m^M #0 0x2b6671853631 in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.1+0x54631)^M #1 0x82c45e in xfree(void*) /home/yao/SourceCode/gnu/gdb/git/gdb/common/common-utils.c:100^M #2 0x818844 in do_my_cleanups /home/yao/SourceCode/gnu/gdb/git/gdb/common/cleanups.c:154^M #3 0x818925 in do_cleanups(cleanup*) /home/yao/SourceCode/gnu/gdb/git/gdb/common/cleanups.c:176^M #4 0x82bad1 in throw_exception_cxx /home/yao/SourceCode/gnu/gdb/git/gdb/common/common-exceptions.c:289^M #5 0x82bc85 in throw_exception(gdb_exception) /home/yao/SourceCode/gnu/gdb/git/gdb/common/common-exceptions.c:317^M #6 0x82bf0e in throw_it /home/yao/SourceCode/gnu/gdb/git/gdb/common/common-exceptions.c:373^M #7 0x82bf3d in throw_verror(errors, char const*, __va_list_tag*) /home/yao/SourceCode/gnu/gdb/git/gdb/common/common-exceptions.c:379^M #8 0xbfa572 in verror(char const*, __va_list_tag*) /home/yao/SourceCode/gnu/gdb/git/gdb/utils.c:432^M #9 0x9318cd in error(char const*, ...) /home/yao/SourceCode/gnu/gdb/git/gdb/common/errors.c:43^M #10 0x7bed8c in init_breakpoint_sal /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:9294^M #11 0x7bf13b in create_breakpoint_sal /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:9326^M #12 0x7bf4f4 in create_breakpoints_sal /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:9378^M #13 0x7d5cf7 in create_breakpoints_sal_default /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:14368^M .... ^M ^[[1m^[[35mpreviously allocated by thread T0 here:^[[1m^[[0m^M #0 0x2b6671853862 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.1+0x54862)^M #1 0x82c315 in xmalloc /home/yao/SourceCode/gnu/gdb/git/gdb/common/common-utils.c:43^M #2 0x82cb37 in savestring(char const*, unsigned long) /home/yao/SourceCode/gnu/gdb/git/gdb/common/common-utils.c:179^M #3 0x7c067d in find_condition_and_thread /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:9594^M #4 0x7c0fa2 in create_breakpoint(gdbarch*, event_location const*, char*, int, char*, int, int, bptype, int, auto_boolean, breakpoint_ops const*, int, int, int, unsigned int) /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:9759^M --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21446-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 06 13:30:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 95024 invoked by alias); 6 Jun 2017 13:30:58 -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 94827 invoked by uid 48); 6 Jun 2017 13:30:52 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug testsuite/21553] Double free in gdb when running gdb.linespec/ls-errs.exp Date: Tue, 06 Jun 2017 13:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: cc 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: 2017-q2/txt/msg00247.txt.bz2 Content-length: 724 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21553 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #2 from Pedro Alves --- Caused by: c1fc2657206188767cb66813d07b9ecbb5e9ec51 is the first bad commit commit c1fc2657206188767cb66813d07b9ecbb5e9ec51 Author: Simon Marchi Date: Fri Jun 2 23:16:21 2017 +0200 C++ify breakpoint class hierarchy (destructors only) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21447-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 06 13:40:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 120556 invoked by alias); 6 Jun 2017 13:40:04 -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 120463 invoked by uid 48); 6 Jun 2017 13:40:01 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug testsuite/21553] Double free in gdb when running gdb.linespec/ls-errs.exp Date: Tue, 06 Jun 2017 13:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q2/txt/msg00248.txt.bz2 Content-length: 5036 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21553 --- Comment #3 from Pedro Alves --- Valgrind shows: $valgrind ./gdb ./testsuite/outputs/gdb.linespec/ls-errs/ls-errs -ex "b -li= ne 3 1" (...) Reading symbols from ./testsuite/outputs/gdb.linespec/ls-errs/ls-errs...don= e. =3D=3D21622=3D=3D Invalid free() / delete / delete[] / realloc() =3D=3D21622=3D=3D at 0x4C29CF0: free (vg_replace_malloc.c:530) =3D=3D21622=3D=3D by 0x60BBE5: xfree(void*) (common-utils.c:100) =3D=3D21622=3D=3D by 0x5E12B9: breakpoint::~breakpoint() (breakpoint.c:1= 2740) =3D=3D21622=3D=3D by 0x5E1319: breakpoint::~breakpoint() (breakpoint.c:1= 2742) =3D=3D21622=3D=3D by 0x5E94DB: std::default_delete::operator()(breakpoint*) const (unique_ptr.h:76) =3D=3D21622=3D=3D by 0x5E8CB4: std::unique_ptr >::~unique_ptr() (unique_ptr.h:236) =3D=3D21622=3D=3D by 0x5DA1FD: create_breakpoint_sal(gdbarch*, symtabs_a= nd_lines, std::unique_ptr&&, char*, char*, ch= ar*, bptype, bpdisp, int, int, int, breakpoint_ops const*, int, int, int, unsign= ed int, int) (breakpoint.c:9317) =3D=3D21622=3D=3D by 0x5DA396: create_breakpoints_sal(gdbarch*, linespec= _result*, char*, char*, bptype, bpdisp, int, int, int, breakpoint_ops const*, int, in= t, int, unsigned int) (breakpoint.c:9378) =3D=3D21622=3D=3D by 0x5E4246: create_breakpoints_sal_default(gdbarch*, linespec_result*, char*, char*, bptype, bpdisp, int, int, int, breakpoint_o= ps const*, int, int, int, unsigned int) (breakpoint.c:14368) =3D=3D21622=3D=3D by 0x5E1DB0: bkpt_create_breakpoints_sal(gdbarch*, linespec_result*, char*, char*, bptype, bpdisp, int, int, int, breakpoint_o= ps const*, int, int, int, unsigned int) (breakpoint.c:13106) =3D=3D21622=3D=3D by 0x5DB211: create_breakpoint(gdbarch*, event_locatio= n const*, char*, int, char*, int, int, bptype, int, auto_boolean, breakpoint_ops cons= t*, int, int, int, unsigned int) (breakpoint.c:9793) =3D=3D21622=3D=3D by 0x5DB731: break_command_1(char*, int, int) (breakpo= int.c:9886) =3D=3D21622=3D=3D Address 0x142aaa20 is 0 bytes inside a block of size 2 f= ree'd =3D=3D21622=3D=3D at 0x4C29CF0: free (vg_replace_malloc.c:530) =3D=3D21622=3D=3D by 0x60BBE5: xfree(void*) (common-utils.c:100) =3D=3D21622=3D=3D by 0x603893: do_my_cleanups(cleanup**, cleanup*) (clea= nups.c:154) =3D=3D21622=3D=3D by 0x6038EE: do_cleanups(cleanup*) (cleanups.c:176) =3D=3D21622=3D=3D by 0x60B671: throw_exception_cxx(gdb_exception) (common-exceptions.c:289) =3D=3D21622=3D=3D by 0x60B75A: throw_exception(gdb_exception) (common-exceptions.c:317) =3D=3D21622=3D=3D by 0x60B8A8: throw_it(return_reason, errors, char cons= t*, __va_list_tag*) (common-exceptions.c:373) =3D=3D21622=3D=3D by 0x60B8D2: throw_verror(errors, char const*, __va_li= st_tag*) (common-exceptions.c:379) =3D=3D21622=3D=3D by 0x7BF75D: verror(char const*, __va_list_tag*) (util= s.c:432) =3D=3D21622=3D=3D by 0x67D8C0: error(char const*, ...) (errors.c:43) =3D=3D21622=3D=3D by 0x5DA049: init_breakpoint_sal(breakpoint*, gdbarch*, symtabs_and_lines, std::unique_ptr&= &, char*, char*, char*, bptype, bpdisp, int, int, int, breakpoint_ops const*, = int, int, int, unsigned int, int) (breakpoint.c:9294) =3D=3D21622=3D=3D by 0x5DA1BB: create_breakpoint_sal(gdbarch*, symtabs_a= nd_lines, std::unique_ptr&&, char*, char*, ch= ar*, bptype, bpdisp, int, int, int, breakpoint_ops const*, int, int, int, unsign= ed int, int) (breakpoint.c:9326) =3D=3D21622=3D=3D Block was alloc'd at =3D=3D21622=3D=3D at 0x4C28BF6: malloc (vg_replace_malloc.c:299) =3D=3D21622=3D=3D by 0x60BABF: xmalloc (common-utils.c:43) =3D=3D21622=3D=3D by 0x60BFCF: savestring(char const*, unsigned long) (common-utils.c:179) =3D=3D21622=3D=3D by 0x5DABBA: find_condition_and_thread(char const*, un= signed long, char**, int*, int*, char**) (breakpoint.c:9594) =3D=3D21622=3D=3D by 0x5DB084: create_breakpoint(gdbarch*, event_locatio= n const*, char*, int, char*, int, int, bptype, int, auto_boolean, breakpoint_ops cons= t*, int, int, int, unsigned int) (breakpoint.c:9759) =3D=3D21622=3D=3D by 0x5DB731: break_command_1(char*, int, int) (breakpo= int.c:9886) =3D=3D21622=3D=3D by 0x5DBA0A: break_command(char*, int) (breakpoint.c:9= 947) =3D=3D21622=3D=3D by 0x4CF340: do_cfunc(cmd_list_element*, char*, int) (cli-decode.c:106) =3D=3D21622=3D=3D by 0x4D225A: cmd_func(cmd_list_element*, char*, int) (cli-decode.c:1896) =3D=3D21622=3D=3D by 0x7B5B70: execute_command(char*, int) (top.c:674) =3D=3D21622=3D=3D by 0x6FDF66: catch_command_errors(void (*)(char*, int)= , char*, int) (main.c:376) =3D=3D21622=3D=3D by 0x6FF131: captured_main_1(captured_main_args*) (mai= n.c:1121) =3D=3D21622=3D=3D=20 Garbage '1' at end of command (gdb) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21448-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 06 14:52:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64938 invoked by alias); 6 Jun 2017 14:52:56 -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 64898 invoked by uid 48); 6 Jun 2017 14:52:55 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21553] Double free in gdb when running gdb.linespec/ls-errs.exp Date: Tue, 06 Jun 2017 14:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: component 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: 2017-q2/txt/msg00249.txt.bz2 Content-length: 379 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21553 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Component|testsuite |breakpoints --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21449-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 06 14:55:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66411 invoked by alias); 6 Jun 2017 14:55:45 -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 65375 invoked by uid 55); 6 Jun 2017 14:55:44 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21553] Double free in gdb when running gdb.linespec/ls-errs.exp Date: Tue, 06 Jun 2017 14:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q2/txt/msg00250.txt.bz2 Content-length: 1740 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21553 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3De1e01040aa83= ddef0bb5c60a8b187f769b2b1ec3 commit e1e01040aa83ddef0bb5c60a8b187f769b2b1ec3 Author: Pedro Alves Date: Tue Jun 6 15:53:59 2017 +0100 Fix double free when running gdb.linespec/ls-errs.exp (PR breakpoints/21553) The problem is that b->extra_string is free'ed twice: Once in the breakpoint's dtor, and another time via make_cleanup (xfree). This patch gets rid of the cleanups, fixing the problem. Tested on x86_64 GNU/Linux. gdb/ChangeLog: 2017-06-06 Pedro Alves PR breakpoints/21553 * breakpoint.c (create_breakpoints_sal_default) (init_breakpoint_sal, create_breakpoint_sal): Use gdb::unique_xmalloc_ptr for string parameters. (create_breakpoint): Constify 'extra_string' and 'cond_string' parameters. Replace cleanups with gdb::unique_xmalloc_ptr. (base_breakpoint_create_breakpoints_sal) (bkpt_create_breakpoints_sal, tracepoint_create_breakpoints_sal) (strace_marker_create_breakpoints_sal) (create_breakpoints_sal_default): Use gdb::unique_xmalloc_ptr for string parameters. * breakpoint.h (breakpoint_ops::create_breakpoints_sal): Use gdb::unique_xmalloc_ptr for string parameters. (create_breakpoint): Constify 'extra_string' and 'cond_string' parameters. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21450-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 06 15:00:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 7044 invoked by alias); 6 Jun 2017 15:00:49 -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 6962 invoked by uid 48); 6 Jun 2017 15:00:45 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21553] Double free in gdb when running gdb.linespec/ls-errs.exp Date: Tue, 06 Jun 2017 15:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat 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: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-q2/txt/msg00251.txt.bz2 Content-length: 563 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21553 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |8.1 --- Comment #5 from Pedro Alves --- Fix pushed in. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21451-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 06 15:52:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 10282 invoked by alias); 6 Jun 2017 15:52:42 -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 10253 invoked by uid 48); 6 Jun 2017 15:52:41 -0000 From: "jepler at dsndata dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21555] New: "error re-setting breakpoint" on PIE executables Date: Tue, 06 Jun 2017 15:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jepler at dsndata dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00252.txt.bz2 Content-length: 2550 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21555 Bug ID: 21555 Summary: "error re-setting breakpoint" on PIE executables Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: jepler at dsndata dot com Target Milestone: --- When executables are built in PIE mode, all breakpoints are lost and cannot= be reset after gdb decides that the file debugged "has changed". This would o= ccur in natural use, when the program being debugged is rebuilt within a single = gdb session. [affected session, Debian Jessie, gcc 4.9, position independent executable] $ echo 'extern int puts(const char *); int main() { puts("hello world"); }'= > hello.c $ gcc -g -fPIE -pie -Wl,-z,relro hello.c $ gdb a.out GNU gdb (GDB) 8.0.50.20170606-git [snip] (gdb) b main Breakpoint 1 at 0x794: file hello.c, line 1. (gdb) r Starting program: /tmp/a.out=20 Breakpoint 1, main () at hello.c:1 1 extern int puts(const char *); int main() { puts("hello world"); } (gdb) shell touch a.out (gdb) r The program being debugged has been started already. Start it from the beginning? (y or n) y `/tmp/a.out' has changed; re-reading symbols. Error in re-setting breakpoint 1: Cannot access memory at address 0x555555554790 Starting program: /tmp/a.out=20 hello world [Inferior 1 (process 12780) exited with code 014] This has been reported to Debian (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D863620), but it affects= the master branch of gdb built without any debian-specific patches. Until now,= it wasn't understood that PIE executables were also part of the equation. This is slightly different than bug #9553, because of the extra steps (touc= hing the executable) before the problem occurs. Confirmed affected: GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 [Debian Jessie] GNU gdb (Debian 7.12-6) 7.12.0.20161007-git [Debian Stretch] GNU gdb (GDB) 8.0.50.20170606-git [git 9949827bea] I haven't been able to confirm that there is any gdb version which was not affected. Tested with gcc versions: gcc version 4.9.2 (Debian 4.9.2-10) [Debian Jessie] gcc version 6.3.0 20170516 (Debian 6.3.0-18) [Debian Stretch] Note that in debian Stretch, the default is to use PIE, which makes more De= bian users likely to encounter this problem. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21452-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 07 18:56:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 44230 invoked by alias); 7 Jun 2017 18:56:31 -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 44182 invoked by uid 48); 7 Jun 2017 18:56:30 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Wed, 07 Jun 2017 18:56: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00253.txt.bz2 Content-length: 1019 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com --- Comment #2 from Keith Seitz --- If you have a reproducer for this, I would really like to see it. The assertion is coming from cp_type_print_method_args, where we print out = any method qualifiers via inspection of `this': /* For non-static methods, read qualifiers from the type of THIS. */ if (!staticp) { struct type *domain; gdb_assert (nargs > 0); --> gdb_assert (TYPE_CODE (args[0].type) =3D=3D TYPE_CODE_PTR); domain =3D TYPE_TARGET_TYPE (args[0].type); In this case, the triggering assertion is that the `this' pointer is, in fa= ct, not a pointer. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21453-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 08 17:54:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 87778 invoked by alias); 8 Jun 2017 17:54:54 -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 87746 invoked by uid 48); 8 Jun 2017 17:54:54 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Thu, 08 Jun 2017 17:54: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: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00254.txt.bz2 Content-length: 266 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #10 from Adam Stylinski --- So it's been about 3 months, any luck reproducing this? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21454-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 08 21:38:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 15114 invoked by alias); 8 Jun 2017 21:38:58 -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 15094 invoked by uid 48); 8 Jun 2017 21:38:57 -0000 From: "fredf_oliveira at hotmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21558] New: symtab.fullname() can't handle directories with Unicode characters Date: Thu, 08 Jun 2017 21:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fredf_oliveira at hotmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00255.txt.bz2 Content-length: 735 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21558 Bug ID: 21558 Summary: symtab.fullname() can't handle directories with Unicode characters Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: fredf_oliveira at hotmail dot com Target Milestone: --- symtab.fullname() throws UnicodeEncodeError exception when dealing with directories that contains Unicode characters, making it impossible to access the absolute file name. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21455-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 08 22:47:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79964 invoked by alias); 8 Jun 2017 22:47:10 -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 79937 invoked by uid 48); 8 Jun 2017 22:47:10 -0000 From: "andrew at ishiboo dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21559] New: ../../gdb/regcache.c:1087: internal-error: void regcache_raw_supply(regcache, int, const void): Assertion `regnum >= 0 && regnum < regcache->descr->nr_raw_registers' failed. Date: Thu, 08 Jun 2017 22:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: andrew at ishiboo dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00256.txt.bz2 Content-length: 5803 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21559 Bug ID: 21559 Summary: ../../gdb/regcache.c:1087: internal-error: void regcache_raw_supply(regcache, int, const void): Assertion `regnum >=3D 0 && regnum < regcache->descr->nr_raw_registers' failed. Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: critical Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: andrew at ishiboo dot com Target Milestone: --- Running gdb 8.0 on a RHEL6 VM: $ uname -a Linux hostname 2.6.32-504.38.1.el6.x86_64 #1 SMP Sun Oct 4 13:43:08 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux Produced the following output: ../../gdb/regcache.c:1087: internal-error: void regcache_raw_supply(regcach= e, int, const void): Assertion `regnum >=3D 0 && regnum < regcache->descr->nr_raw_registers' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] Dumping the stack from the core file produces: (gdb) where #0 0x0000003fc3e32625 in raise () from /lib64/libc.so.6 #1 0x0000003fc3e33e05 in abort () from /lib64/libc.so.6 #2 0x000000000078267e in dump_core() () #3 0x0000000000782af7 in internal_vproblem(internal_problem*, char const*, int, char const*, __va_list_tag*) () #4 0x0000000000782b6f in internal_verror(char const*, int, char const*, __va_list_tag*) () #5 0x0000000000641e26 in internal_error(char const*, int, char const*, ...= ) () #6 0x0000000000712883 in regcache_raw_supply(regcache*, int, void const*) = () #7 0x000000000046c6f8 in amd64_linux_fetch_inferior_registers(target_ops*, regcache*, int) () #8 0x0000000000754802 in delegate_fetch_registers(target_ops*, regcache*, = int) () #9 0x0000000000768aa8 in target_fetch_registers(regcache*, int) () #10 0x0000000000479622 in ps_lgetregs () #11 0x00007f1f6252fb58 in __td_ta_lookup_th_unique () from /lib64/libthread_db.so.1 #12 0x00007f1f6252fd8a in td_ta_map_lwp2thr () from /lib64/libthread_db.so.1 #13 0x0000000000479c7c in thread_from_lwp(ptid_t) () #14 0x000000000047a4b1 in try_thread_db_load_1(thread_db_info*) () #15 0x000000000047a7df in try_thread_db_load(char const*, int) () #16 0x000000000047aab1 in try_thread_db_load_from_sdir() () #17 0x000000000047acbf in thread_db_load_search() () #18 0x000000000047ae41 in thread_db_load() () #19 0x000000000047af72 in check_for_thread_db() () #20 0x000000000047b007 in thread_db_new_objfile(objfile*) () #21 0x00000000006e2434 in observer_new_objfile_notification_stub(void const= *, void const*) () #22 0x00000000006e1802 in generic_observer_notify(observer_list*, void cons= t*) () #23 0x00000000006e24c7 in observer_notify_new_objfile(objfile*) () #24 0x000000000073c478 in symbol_file_add_with_addrs(bfd*, char const*, enum_flags, section_addr_info*, enum_flags, objfile*) () #25 0x000000000073c61e in symbol_file_add_from_bfd(bfd*, char const*, enum_flags, section_addr_info*, enum_flags, objfile*) () #26 0x0000000000721c66 in solib_read_symbols(so_list*, enum_flags) () #27 0x0000000000722490 in solib_add(char const*, int, int) () #28 0x0000000000458a77 in enable_break(svr4_info*, int) () #29 0x000000000045a655 in svr4_solib_create_inferior_hook(int) () #30 0x0000000000722e70 in solib_create_inferior_hook(int) () #31 0x000000000068e11e in post_create_inferior(target_ops*, int) () #32 0x00000000006920a0 in setup_inferior(int) () #33 0x00000000006920e6 in attach_post_wait(char const*, int, attach_post_wait_mode) () #34 0x00000000006922af in attach_command_continuation(void*, int) () #35 0x00000000005d4556 in do_my_continuations_1(continuation**, int) () #36 0x00000000005d45e1 in do_my_continuations(continuation**, int) () #37 0x00000000005d46d9 in do_all_inferior_continuations(int) () #38 0x000000000068b4a5 in inferior_event_handler(inferior_event_type, void*= ) () #39 0x000000000069be0e in fetch_inferior_event(void*) () #40 0x000000000068b43f in inferior_event_handler(inferior_event_type, void*= ) () #41 0x00000000006a653e in infrun_async_inferior_event_handler(void*) () #42 0x000000000064c4e3 in check_async_event_handlers() () #43 0x000000000064ae53 in gdb_do_one_event() () #44 0x000000000064aefa in start_event_loop() () #45 0x00000000006c1cbb in captured_command_loop(void*) () #46 0x000000000064e9ef in catch_errors(int (*)(void*), void*, char const*, return_mask) () #47 0x00000000006c30d0 in captured_main(void*) () #48 0x00000000006c30f9 in gdb_main(captured_main_args*) () #49 0x000000000040a817 in main () (gdb) up #6 0x0000000000712883 in regcache_raw_supply(regcache*, int, void const*) = () (gdb) info registers rax 0x0 0 rbx 0x2a648 173640 rcx 0xffffffffffffffff -1 rdx 0x6 6 rsi 0x2a8ed 174317 rdi 0x2a8ed 174317 rbp 0x7ffe49d38630 0x7ffe49d38630 rsp 0x7ffe49d38600 0x7ffe49d38600 r8 0xffffffff 4294967295 r9 0x7f1f63a70700 139772792604416 r10 0x8 8 r11 0x206 518 r12 0x7ffe49d39720 140730137024288 r13 0x7ffe49d39500 140730137023744 r14 0x0 0 r15 0x0 0 rip 0x712883 0x712883 eflags 0x206 [ PF IF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21456-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 08 22:59:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 7959 invoked by alias); 8 Jun 2017 22:59:06 -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 7138 invoked by uid 48); 8 Jun 2017 22:59:05 -0000 From: "andrew at ishiboo dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21559] ../../gdb/regcache.c:1087: internal-error: void regcache_raw_supply(regcache, int, const void): Assertion `regnum >= 0 && regnum < regcache->descr->nr_raw_registers' failed. Date: Thu, 08 Jun 2017 22:59: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: andrew at ishiboo dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00257.txt.bz2 Content-length: 1515 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21559 --- Comment #1 from Andrew Paprocki --- The bug appears to be here: #ifndef HAVE_STRUCT_USER_REGS_STRUCT_FS_BASE { /* PTRACE_ARCH_PRCTL is obsolete since 2.6.25, where the fs_base and gs_base fields of user_regs_struct can be used directly. */ unsigned long base; if (regnum =3D=3D -1 || regnum =3D=3D AMD64_FSBASE_REGNUM) { if (ptrace (PTRACE_ARCH_PRCTL, tid, &base, ARCH_GET_FS) < 0) perror_with_name (_("Couldn't get segment register fs_base")); regcache_raw_supply (regcache, AMD64_FSBASE_REGNUM, &base); } if (regnum =3D=3D -1 || regnum =3D=3D AMD64_GSBASE_REGNUM) { if (ptrace (PTRACE_ARCH_PRCTL, tid, &base, ARCH_GET_GS) < 0) perror_with_name (_("Couldn't get segment register gs_base")); regcache_raw_supply (regcache, AMD64_GSBASE_REGNUM, &base); } } #endif This code must be getting hit because the binary was built on a RHEL5 system with 2.6.18 kernel. The reg cache does not allow the pseudo registers into the cache: /* Construct a strictly RAW register cache. Don't allow pseudo's into the register cache. */ descr->nr_raw_registers =3D gdbarch_num_regs (gdbarch); descr->sizeof_raw_register_status =3D gdbarch_num_regs (gdbarch); --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21457-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 08 23:05:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 96625 invoked by alias); 8 Jun 2017 23:05:48 -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 96594 invoked by uid 48); 8 Jun 2017 23:05:47 -0000 From: "andrew at ishiboo dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21559] ../../gdb/regcache.c:1087: internal-error: void regcache_raw_supply(regcache, int, const void): Assertion `regnum >= 0 && regnum < regcache->descr->nr_raw_registers' failed. Date: Thu, 08 Jun 2017 23:05: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: andrew at ishiboo dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00258.txt.bz2 Content-length: 358 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21559 --- Comment #2 from Andrew Paprocki --- This appears to be the commit: https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommitdiff;h= =3D2735833d5fb220983d09770087b573fed5bf93cd --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21458-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 09 01:49:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 130534 invoked by alias); 9 Jun 2017 01:49:00 -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 130500 invoked by uid 48); 9 Jun 2017 01:48:58 -0000 From: "andrew at ishiboo dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21559] ../../gdb/regcache.c:1087: internal-error: void regcache_raw_supply(regcache, int, const void): Assertion `regnum >= 0 && regnum < regcache->descr->nr_raw_registers' failed. Date: Fri, 09 Jun 2017 01:49: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: andrew at ishiboo dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00259.txt.bz2 Content-length: 516 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21559 --- Comment #3 from Andrew Paprocki --- It should be noted that modifying `configure` to force on `HAVE_STRUCT_USER_REGS_STRUCT_FS_BASE` and `HAVE_STRUCT_USER_REGS_STRUCT_GS_BASE` fixes this issue. For some reason the `configure` tests for `fs_base` and `gs_base` fail even though `sys/user.h`= on RHEL5 has the fields defined in `user_regs_struct`. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21459-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 09 12:29:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 34240 invoked by alias); 9 Jun 2017 12:29:20 -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 33315 invoked by uid 48); 9 Jun 2017 12:29:18 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug cli/16242] print format for hex float Date: Fri, 09 Jun 2017 12:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: tromey at sourceware dot org 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: cc 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: 2017-q2/txt/msg00260.txt.bz2 Content-length: 591 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16242 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --- Comment #1 from Tom Tromey --- I think it would make sense to repurpose /x, because I don't see much value in how that currently handling floating point. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21460-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 09 13:16:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 106001 invoked by alias); 9 Jun 2017 13:16:50 -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 103006 invoked by uid 55); 9 Jun 2017 13:16:45 -0000 From: "linuxer at quantentunnel dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Fri, 09 Jun 2017 13:16: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: linuxer at quantentunnel dot de X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00261.txt.bz2 Content-length: 1093 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 --- Comment #3 from Johannes --- Hi Keith, (In reply to Keith Seitz from comment #2) > If you have a reproducer for this, I would really like to see it. > What do you need to reproduce the bug? Remote access to the debug session? The target is a Cortex-M3 microcontroller board (STM32F103C8), the binary is an .elf file. Where shall I put it to for your access? As an attechment to this bug? The sources can be made available too. Fortunately the sources belong to a small demo project for testing SW frameworks on different target boards, so I have no issues with making the sources open to you. But this is a bigger piece of download (several 100M bytes, when not stripped down to the single error situation). Same question for the sources, do you want and how do you want to access the sources? Attachments, cloud download, shared Github access or the like? Regards,Johannes Lode --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21461-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 09 15:21:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 125394 invoked by alias); 9 Jun 2017 15:21:40 -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 125346 invoked by uid 48); 9 Jun 2017 15:21:39 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Fri, 09 Jun 2017 15:21: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00262.txt.bz2 Content-length: 713 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 --- Comment #4 from Keith Seitz --- (In reply to Johannes from comment #3) > > What do you need to reproduce the bug? Remote access to the debug > session? The binary is probably more than enough. You can attach it to this bug if it isn't too large, or email it to me directly. I will probably need to see sources later when (if?) I figure out what's triggering the assert. Also, if you could copy/paste a session demonstrating the assert, that would be helpful for me to reproduce. Was this binary built with any optimization or stripped? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21462-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 09 22:55:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 28029 invoked by alias); 9 Jun 2017 22:55:00 -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 27961 invoked by uid 48); 9 Jun 2017 22:54:59 -0000 From: "mr.nuke.me at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21563] New: gdb segfaults when trying to read DWARF symbols created by TI compiler Date: Fri, 09 Jun 2017 22:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mr.nuke.me at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q2/txt/msg00263.txt.bz2 Content-length: 1375 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21563 Bug ID: 21563 Summary: gdb segfaults when trying to read DWARF symbols created by TI compiler Product: gdb Version: 7.6 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: mr.nuke.me at gmail dot com Target Milestone: --- Created attachment 10086 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10086&action=3Ded= it ELF file that causes GDB to go tits up arm-none-eabi-gdb will segfault when trying to read or demangle a symbol fr= om a DWARF section created with TI code composer studio. There are several ways to produce the crash, either by typing break, then hitting to autocomplete, or trying to break on a function name. The segfault happens in 'd_demangle_callback()' every time. $ arm-none-eabi-gdb ~/ti_ccs_gdb_crash.elf=20 GNU gdb (GDB) 7.6.2 [snip] Reading symbols from /home/mrnuke/ti_ccs_gdb_crash.elf...done. (gdb) break main Segmentation fault (core dumped) I expect that gdb either sets the correct breakpoint, or says that symbol cannot be found (if it cannot demangle the names). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21463-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 09 22:55:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 28884 invoked by alias); 9 Jun 2017 22:55:48 -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 28857 invoked by uid 48); 9 Jun 2017 22:55:47 -0000 From: "mr.nuke.me at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21563] gdb segfaults when trying to read DWARF symbols created by TI compiler Date: Fri, 09 Jun 2017 22:55: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.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mr.nuke.me at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00264.txt.bz2 Content-length: 333 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21563 --- Comment #1 from mrnuke --- Created attachment 10087 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10087&action=3Ded= it GDB Backtrace of GDB crashing --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21464-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jun 10 15:09:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 9144 invoked by alias); 10 Jun 2017 15:09:08 -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 9108 invoked by uid 48); 10 Jun 2017 15:09:08 -0000 From: "linuxer at quantentunnel dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Sat, 10 Jun 2017 15:09: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: linuxer at quantentunnel dot de X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00265.txt.bz2 Content-length: 410 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 --- Comment #5 from Johannes --- Created attachment 10089 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10089&action=3Ded= it ELF binary file, that triggers the assert, when loaded to the target and ru= n by the gdb to main(). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21465-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jun 10 15:10:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 10057 invoked by alias); 10 Jun 2017 15:10:17 -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 10025 invoked by uid 48); 10 Jun 2017 15:10:16 -0000 From: "linuxer at quantentunnel dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Sat, 10 Jun 2017 15:10: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: linuxer at quantentunnel dot de X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00266.txt.bz2 Content-length: 349 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 --- Comment #6 from Johannes --- Created attachment 10090 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10090&action=3Ded= it The linker output map for the ELF file. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21466-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jun 10 15:14:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 13375 invoked by alias); 10 Jun 2017 15:14:46 -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 13345 invoked by uid 48); 10 Jun 2017 15:14:46 -0000 From: "linuxer at quantentunnel dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Sat, 10 Jun 2017 15:14: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: linuxer at quantentunnel dot de X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00267.txt.bz2 Content-length: 995 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 --- Comment #7 from Johannes --- (In reply to Keith Seitz from comment #4) > The binary is probably more than enough. You can attach it to this bug if= it > isn't too large, or email it to me directly. Is attached, as well as the linker map file. This unstripped binary was giv= en to the gdb and this way loaded into the target board. > I will probably need to see sources later when (if?) I figure out what's > triggering the assert. Also, if you could copy/paste a session demonstrat= ing > the assert, that would be helpful for me to reproduce. Session trace (copied from the Eclipse gdb console window) is put as an attachment. > Was this binary built with any optimization or stripped? The ELF file was built with "g++ -std=3Dc++11 -O2 -lto ..." in the compilin= g and the linking stage. Regards,=20 Johannes --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21467-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jun 10 15:16:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36056 invoked by alias); 10 Jun 2017 15:16:18 -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 36018 invoked by uid 48); 10 Jun 2017 15:16:18 -0000 From: "linuxer at quantentunnel dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Sat, 10 Jun 2017 15:16: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: linuxer at quantentunnel dot de X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00268.txt.bz2 Content-length: 393 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 --- Comment #8 from Johannes --- Created attachment 10091 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10091&action=3Ded= it Session trace from gdb start to the assert, copied from Eclipse gdb console window. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21468-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jun 10 17:24:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 98580 invoked by alias); 10 Jun 2017 17:24:43 -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 98388 invoked by uid 48); 10 Jun 2017 17:24:32 -0000 From: "mjashdev at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21100] clang follow-fork-mode child internal-error Date: Sat, 10 Jun 2017 17:24: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.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mjashdev at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00269.txt.bz2 Content-length: 5601 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21100 mjashdev at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mjashdev at gmail dot com --- Comment #1 from mjashdev at gmail dot com --- I can confirm this bug when debugging a forked LLVM process on arch linux w= ith gdb 8.0 compiled from the arch build system. If anyone could provide a workaround I would be very appreciative.=20 The following is a backtrace before the error occurs: #0 free_objfile_data (objfile=3D0x3945b60, data=3D0x31efe10) at jit.c:1491 #1 0x00000000006f24c9 in objfileregistry_callback_adaptor (func=3D0x6c20a4 , container=3D0x3945b60, data=3D0x31efe= 10) at objfiles.c:61 #2 0x00000000007274b3 in registry_clear_data (data_registry=3D0xe3a390 ,=20 adaptor=3D0x6f2483 , container=3D0x3945b60, fields=3D0x3945c58) at registry.c:79 #3 0x0000000000727555 in registry_container_free_data (data_registry=3D0xe= 3a390 ,=20 adaptor=3D0x6f2483 , container=3D0x3945b60, fields=3D0x3945c58) at registry.c:92 #4 0x00000000006f253d in objfile_free_data (container=3D0x3945b60) at objfiles.c:61 #5 0x00000000006f3bfe in free_objfile (objfile=3D0x3945b60) at objfiles.c:= 689 #6 0x00000000006f4b6f in objfile_purge_solibs () at objfiles.c:1099 #7 0x0000000000735995 in no_shared_libraries (ignored=3D0x0, from_tty=3D0)= at solib.c:1271 #8 0x00000000006aef6e in follow_exec (ptid=3D..., exec_file_target=3D0x16a= 4df0 "/home/mason/Development/opencut/opencut_qt/build/opencut_core") at infrun.c:1188 #9 0x00000000006b5cf4 in handle_inferior_event_1 (ecs=3D0x7fffffffde10) at infrun.c:5336 (More stack frames follow...) #0 0x00007ffff613b670 in raise () from /usr/lib/libc.so.6 #1 0x00007ffff613cd00 in abort () from /usr/lib/libc.so.6 #2 0x00000000007929a9 in dump_core () at utils.c:465 #3 0x0000000000792ddb in internal_vproblem(internal_problem *, const char = *, int, const char *, typedef __va_list_tag __va_list_tag *) ( problem=3D0xe15040 , file=3D0x969d57 "breakpoin= t.c", line=3D13757, fmt=3D0x969a50 "%s: Assertion `%s' failed.", ap=3D0x7fffffffd= 898) at utils.c:676 #4 0x0000000000792e4f in internal_verror (file=3D0x969d57 "breakpoint.c", line=3D13757, fmt=3D0x969a50 "%s: Assertion `%s' failed.", ap=3D0x7fffffffd= 898) at utils.c:702 #5 0x000000000065c7d1 in internal_error (file=3D0x969d57 "breakpoint.c", line=3D13757, fmt=3D0x969a50 "%s: Assertion `%s' failed.") at common/errors= .c:55 #6 0x00000000005c834c in delete_breakpoint (bpt=3D0x0) at breakpoint.c:137= 57 #7 0x00000000006c2115 in free_objfile_data (objfile=3D0x39895b0, data=3D0x= 324b340) at jit.c:1491 #8 0x00000000006f24c9 in objfileregistry_callback_adaptor (func=3D0x6c20a4 , container=3D0x39895b0, data=3D0x324b3= 40) at objfiles.c:61 #9 0x00000000007274b3 in registry_clear_data (data_registry=3D0xe3a390 ,=20 adaptor=3D0x6f2483 , container=3D0x39895b0, fields=3D0x39896a8) at registry.c:79 #10 0x0000000000727555 in registry_container_free_data (data_registry=3D0xe= 3a390 ,=20 adaptor=3D0x6f2483 , container=3D0x39895b0, fields=3D0x39896a8) at registry.c:92 #11 0x00000000006f253d in objfile_free_data (container=3D0x39895b0) at objfiles.c:61 #12 0x00000000006f3bfe in free_objfile (objfile=3D0x39895b0) at objfiles.c:= 689 #13 0x00000000006f4b6f in objfile_purge_solibs () at objfiles.c:1099 #14 0x0000000000735995 in no_shared_libraries (ignored=3D0x0, from_tty=3D0)= at solib.c:1271 #15 0x00000000006aef6e in follow_exec (ptid=3D..., exec_file_target=3D0x15f= 5790 "/home/mason/Development/opencut/opencut_qt/build/opencut_core") at infrun.c:1188 #16 0x00000000006b5cf4 in handle_inferior_event_1 (ecs=3D0x7fffffffde10) at infrun.c:5336 #17 0x00000000006b6006 in handle_inferior_event (ecs=3D0x7fffffffde10) at infrun.c:5427 #18 0x00000000006b33c4 in fetch_inferior_event (client_data=3D0x0) at infrun.c:3932 #19 0x00000000006a3e20 in inferior_event_handler (event_type=3DINF_REG_EVEN= T, client_data=3D0x0) at inf-loop.c:43 #20 0x000000000047a6c5 in handle_target_event (error=3D0, client_data=3D0x0= ) at linux-nat.c:4522 #21 0x00000000006663cc in handle_file_event (file_ptr=3D0x16cced0, ready_ma= sk=3D1) at event-loop.c:733 #22 0x0000000000666957 in gdb_wait_for_event (block=3D0) at event-loop.c:859 #23 0x00000000006657f8 in gdb_do_one_event () at event-loop.c:322 #24 0x00000000006658a4 in start_event_loop () at event-loop.c:371 #25 0x00000000006d7807 in captured_command_loop (data=3D0x0) at main.c:325 #26 0x000000000066928a in catch_errors (func=3D0x6d77c5 , func_args=3D0x0, errstring=3D0x9c05dc "", mask=3DRETURN_MASK_ALL) at exceptions.c:236 #27 0x00000000006d8b4a in captured_main (data=3D0x7fffffffe190) at main.c:1= 150 #28 0x00000000006d8b73 in gdb_main (args=3D0x7fffffffe190) at main.c:1160 #29 0x000000000040e0de in main (argc=3D2, argv=3D0x7fffffffe298) at gdb.c:32 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21469-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jun 10 17:43:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 8816 invoked by alias); 10 Jun 2017 17:43:48 -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 8786 invoked by uid 48); 10 Jun 2017 17:43:47 -0000 From: "linuxer at quantentunnel dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Sat, 10 Jun 2017 17:43: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: linuxer at quantentunnel dot de X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00270.txt.bz2 Content-length: 451 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 --- Comment #9 from Johannes --- (In reply to Johannes from comment #7) > The ELF file was built with "g++ -std=3Dc++11 -O2 -lto ..." in the compil= ing > and the linking stage. There is a typo in the compiler flags, it should read: g++ -std=3Dc++11 -O2 -flto ... :-) Johannes --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21470-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jun 12 13:48:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 40990 invoked by alias); 12 Jun 2017 13:48:44 -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 40080 invoked by uid 48); 12 Jun 2017 13:48:05 -0000 From: "mlen at mlen dot pl" To: gdb-prs@sourceware.org Subject: [Bug gdb/21051] nat/x86-linux-dregs.c:146: internal-error: void x86_linux_update_debug_registers(lwp_info*): Assertion `lwp_is_stopped (lwp)' failed. Date: Mon, 12 Jun 2017 13:48: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mlen at mlen dot pl X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00271.txt.bz2 Content-length: 244 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21051 --- Comment #2 from Mateusz Lenik --- Sadly, this issue is still present in gdb 8.0. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21473-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jun 12 21:44:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94566 invoked by alias); 12 Jun 2017 21:44:27 -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 94489 invoked by uid 55); 12 Jun 2017 21:44:25 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug exp/16225] __int128_t types print strangely Date: Mon, 12 Jun 2017 21:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q2/txt/msg00274.txt.bz2 Content-length: 954 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16225 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D4ac0cb1cf04f= 105586746a6cce5b0f93d76f2b33 commit 4ac0cb1cf04f105586746a6cce5b0f93d76f2b33 Author: Tom Tromey Date: Mon May 22 16:32:25 2017 -0600 Let print_decimal_chars handle signed values This changes print_decimal_chars to handle signed values. gdb/ChangeLog 2017-06-12 Tom Tromey PR exp/16225: * valprint.h (print_decimal_chars): Update. * valprint.c (maybe_negate_by_bytes): New function. (print_decimal_chars): Add "is_signed" argument. * printcmd.c (print_scalar_formatted): Update. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21472-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jun 12 21:44:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94522 invoked by alias); 12 Jun 2017 21:44:26 -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 94416 invoked by uid 55); 12 Jun 2017 21:44:24 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug exp/16225] __int128_t types print strangely Date: Mon, 12 Jun 2017 21:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q2/txt/msg00273.txt.bz2 Content-length: 2535 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16225 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D30a254669b16= b86166fed1f9a4c4f9cc55a07fdc commit 30a254669b16b86166fed1f9a4c4f9cc55a07fdc Author: Tom Tromey Date: Mon May 22 03:55:58 2017 -0600 Don't always zero pad in print_*_chars This changes print_octal_chars and print_decimal_chars to never zero pad, and changes print_binary_chars and print_hex_chars to only optionally zero-pad, based on a flag. ChangeLog 2017-06-12 Tom Tromey PR exp/16225: * valprint.h (print_binary_chars, print_hex_chars): Update. * valprint.c (val_print_type_code_int): Update. (print_binary_chars): Add "zero_pad" argument. (emit_octal_digit): New function. (print_octal_chars): Don't zero-pad. (print_decimal_chars): Likewise. (print_hex_chars): Add "zero_pad" argument. * sh64-tdep.c (sh64_do_fp_register): Update. * regcache.c (regcache::dump): Update. * printcmd.c (print_scalar_formatted): Update. * infcmd.c (default_print_one_register_info): Update. 2017-06-12 Tom Tromey PR exp/16225: * gdb.reverse/i386-sse-reverse.exp: Update tests. * gdb.arch/vsx-regs.exp: Update tests. * gdb.arch/s390-vregs.exp (hex128): New proc. Update test. * gdb.arch/altivec-regs.exp: Update tests. --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D4ac0cb1cf04f= 105586746a6cce5b0f93d76f2b33 commit 4ac0cb1cf04f105586746a6cce5b0f93d76f2b33 Author: Tom Tromey Date: Mon May 22 16:32:25 2017 -0600 Let print_decimal_chars handle signed values This changes print_decimal_chars to handle signed values. gdb/ChangeLog 2017-06-12 Tom Tromey PR exp/16225: * valprint.h (print_decimal_chars): Update. * valprint.c (maybe_negate_by_bytes): New function. (print_decimal_chars): Add "is_signed" argument. * printcmd.c (print_scalar_formatted): Update. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21471-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jun 12 21:44:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94458 invoked by alias); 12 Jun 2017 21:44:24 -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 94378 invoked by uid 55); 12 Jun 2017 21:44:21 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug exp/16225] __int128_t types print strangely Date: Mon, 12 Jun 2017 21:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q2/txt/msg00272.txt.bz2 Content-length: 1717 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16225 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D30a254669b16= b86166fed1f9a4c4f9cc55a07fdc commit 30a254669b16b86166fed1f9a4c4f9cc55a07fdc Author: Tom Tromey Date: Mon May 22 03:55:58 2017 -0600 Don't always zero pad in print_*_chars This changes print_octal_chars and print_decimal_chars to never zero pad, and changes print_binary_chars and print_hex_chars to only optionally zero-pad, based on a flag. ChangeLog 2017-06-12 Tom Tromey PR exp/16225: * valprint.h (print_binary_chars, print_hex_chars): Update. * valprint.c (val_print_type_code_int): Update. (print_binary_chars): Add "zero_pad" argument. (emit_octal_digit): New function. (print_octal_chars): Don't zero-pad. (print_decimal_chars): Likewise. (print_hex_chars): Add "zero_pad" argument. * sh64-tdep.c (sh64_do_fp_register): Update. * regcache.c (regcache::dump): Update. * printcmd.c (print_scalar_formatted): Update. * infcmd.c (default_print_one_register_info): Update. 2017-06-12 Tom Tromey PR exp/16225: * gdb.reverse/i386-sse-reverse.exp: Update tests. * gdb.arch/vsx-regs.exp: Update tests. * gdb.arch/s390-vregs.exp (hex128): New proc. Update test. * gdb.arch/altivec-regs.exp: Update tests. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21474-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jun 12 21:45:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 100058 invoked by alias); 12 Jun 2017 21:45:46 -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 99936 invoked by uid 48); 12 Jun 2017 21:45:41 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug exp/16225] __int128_t types print strangely Date: Mon, 12 Jun 2017 21:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-q2/txt/msg00275.txt.bz2 Content-length: 561 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16225 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |8.1 --- Comment #3 from Tom Tromey --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21475-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jun 12 21:45:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 100228 invoked by alias); 12 Jun 2017 21:45:49 -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 100082 invoked by uid 48); 12 Jun 2017 21:45:46 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug exp/20991] __int128 type support Date: Mon, 12 Jun 2017 21:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: dep_changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_status resolution 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: 2017-q2/txt/msg00276.txt.bz2 Content-length: 544 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20991 Bug 20991 depends on bug 16225, which changed state. Bug 16225 Summary: __int128_t types print strangely https://sourceware.org/bugzilla/show_bug.cgi?id=3D16225 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21476-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jun 12 22:01:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31930 invoked by alias); 12 Jun 2017 22:01:06 -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 31879 invoked by uid 48); 12 Jun 2017 22:01:04 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Mon, 12 Jun 2017 22:01: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00277.txt.bz2 Content-length: 1876 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 --- Comment #10 from Keith Seitz --- Looking at the DWARF and session information you've provided, I *think* GDB= is asserting on the following symbol: _ZN5Shell6TinySh8cmd_helpERS0_iPPKc That is: Shell::TinySh::cmd_help(Shell::TinySh&, int, char const**). According to the debug info, "Shell" is a namespace. "TinySh" is a structur= e, and cmd_help is a *method* of that structure: <3><15dc>: Abbrev Number: 68 (DW_TAG_subprogram) <15dd> DW_AT_external : 1=20=20=20=20=20=20 <15dd> DW_AT_name : (indirect string, offset: 0x1621): cmd_hel= p=20=20=20=20 <15e1> DW_AT_decl_file : 20=20=20=20=20=20 <15e2> DW_AT_decl_line : 49=20=20=20=20=20 <15e3> DW_AT_linkage_name: (indirect string, offset: 0xa7b): _ZN5Shell6Tin ySh8cmd_helpERS0_iPPKc=20=20 <15e7> DW_AT_prototyped : 1=20=20=20=20=20=20 <15e7> DW_AT_accessibility: 3 (private) <15e8> DW_AT_declaration : 1=20=20=20=20=20=20 <4><15e8>: Abbrev Number: 13 (DW_TAG_formal_parameter) <15e9> DW_AT_type : <0x1691>=20=20=20=20=20=20=20 <4><15ed>: Abbrev Number: 13 (DW_TAG_formal_parameter) <15ee> DW_AT_type : <0x4f>=20 <4><15f2>: Abbrev Number: 13 (DW_TAG_formal_parameter) <15f3> DW_AT_type : <0x1697>=20=20=20=20=20=20=20 <4><15f7>: Abbrev Number: 0 The first parameter of this (private) method has type given by 0x1691, whic= h is a *reference* to TinySh, not a pointer. Not only that, but this first param= eter is also not marked artificial. Can you provide the source declaration for Shell::TinySh::cmd_help? >>From what I can infer from this, GDB (erroneously) marks cmd_help as a non-static member function, but it's really just a guess. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21477-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 13 00:01:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 82196 invoked by alias); 13 Jun 2017 00:01:58 -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 82152 invoked by uid 48); 13 Jun 2017 00:01:57 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Tue, 13 Jun 2017 00:01: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00278.txt.bz2 Content-length: 3542 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 --- Comment #11 from Keith Seitz --- (In reply to Keith Seitz from comment #10) > From what I can infer from this, GDB (erroneously) marks cmd_help as a > non-static member function, but it's really just a guess. Red herring. Ignore my previous comment. I built up an arm-none-eabi-gdb and was able to easily step through the cod= e. A simple "ptype Shell::TinySh" triggers the assertion. The symbol we actually falter on is the one in DIE 0xa013: <3>: Abbrev Number: 53 (DW_TAG_subprogram) DW_AT_external : 1=20=20=20=20=20=20 DW_AT_name : (indirect string, offset: 0x2806): _ZN5Shell6TinySh7char_inEc.constprop.67=20=20=20=20=20 DW_AT_decl_file : 9=20=20=20=20=20=20 DW_AT_decl_line : 487=20=20=20=20 DW_AT_accessibility: 3 (private) DW_AT_declaration : 1=20=20=20=20=20=20 DW_AT_sibling : <0xa026>=20=20=20=20=20=20=20 <4>: Abbrev Number: 11 (DW_TAG_formal_parameter) DW_AT_type : <0x9630>=20=20=20=20=20=20=20 DW_AT_artificial : 1=20=20=20=20=20=20 <4>: Abbrev Number: 0 >>From this, we see the `this' pointer (properly marked artificial) has type given by 0x9630: <1><9630>: Abbrev Number: 2 (DW_TAG_base_type) <9631> DW_AT_byte_size : 1=20=20=20=20=20=20 <9632> DW_AT_encoding : 8 (unsigned char) <9633> DW_AT_name : (indirect string, offset: 0x30fd): char=20= =20=20=20=20=20=20=20 Yup. The `this' pointer is of type `char'. That is clearly really bad. [I d= on't know if this is a linking problem or a compiler problem -- I've never seen DW_AT_name like the one listed above). I don't know if we really want to "fix" this, it is showing a pretty serious error somewhere. However, if you wanted to workaround this, I would modify cp_type_print_method_args: diff --git a/gdb/c-typeprint.c b/gdb/c-typeprint.c index 5a23e92..dafc080 100644 --- a/gdb/c-typeprint.c +++ b/gdb/c-typeprint.c @@ -641,27 +641,27 @@ cp_type_print_method_args (struct type *mtype, const = char *prefix, THIS. */ if (!staticp) { - struct type *domain; - gdb_assert (nargs > 0); - gdb_assert (TYPE_CODE (args[0].type) =3D=3D TYPE_CODE_PTR); - domain =3D TYPE_TARGET_TYPE (args[0].type); - if (TYPE_CONST (domain)) - fprintf_filtered (stream, " const"); + if (TYPE_CODE (args[0].type) =3D=3D TYPE_CODE_PTR) + { + struct type *domain =3D TYPE_TARGET_TYPE (args[0].type); + + if (TYPE_CONST (domain)) + fprintf_filtered (stream, " const"); - if (TYPE_VOLATILE (domain)) - fprintf_filtered (stream, " volatile"); + if (TYPE_VOLATILE (domain)) + fprintf_filtered (stream, " volatile"); - if (TYPE_RESTRICT (domain)) - fprintf_filtered (stream, " restrict"); + if (TYPE_RESTRICT (domain)) + fprintf_filtered (stream, " restrict"); - if (TYPE_ATOMIC (domain)) - fprintf_filtered (stream, " _Atomic"); + if (TYPE_ATOMIC (domain)) + fprintf_filtered (stream, " _Atomic"); + } } } - /* Print any asterisks or open-parentheses needed before the variable name (to describe its type). [That's mostly whitespace change.] That will get you going again while I discuss with maintainers what we shou= ld do. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21478-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 13 08:18:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 70970 invoked by alias); 13 Jun 2017 08:18:36 -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 70937 invoked by uid 48); 13 Jun 2017 08:18:35 -0000 From: "david at engster dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21078] gdb compiled with mingw32 crashes on Windows7 when entering any invalid command Date: Tue, 13 Jun 2017 08:18: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: david at engster dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00279.txt.bz2 Content-length: 530 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21078 --- Comment #5 from David Engster --- I just tested again with gdb 8.0 and gcc 6.3.0 from MSYS2 32bit (i686-w64-mingw32-gcc), and I still see the same problem. I have no idea wh= y it works for you. I can however also confirm that the patch from Orgad in bug 21187 and using "--disable-staticlib" fixes this issue, so it is definitely an issue with static linking. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21479-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 13 08:22:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 81463 invoked by alias); 13 Jun 2017 08:22:02 -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 81436 invoked by uid 48); 13 Jun 2017 08:22:02 -0000 From: "david at engster dot org" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Tue, 13 Jun 2017 08:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: david at engster dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: mishra.nitish.88 at gmail dot com X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q2/txt/msg00280.txt.bz2 Content-length: 735 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 David Engster changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david at engster dot org --- Comment #14 from David Engster --- This issue is also present when compiling for w32 (see bug 21087). I can confirm that applying this patch and using '--disable-staticlib' for 'configure' fixes this issue when compiling gdb on Windows using MSYS2, hen= ce I'd much appreciate if this patch could be applied. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21480-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 13 08:30:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 93646 invoked by alias); 13 Jun 2017 08:30:56 -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 93397 invoked by uid 48); 13 Jun 2017 08:30:44 -0000 From: "david at engster dot org" To: gdb-prs@sourceware.org Subject: [Bug build/21187] Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform Date: Tue, 13 Jun 2017 08:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: david at engster dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: mishra.nitish.88 at gmail dot com X-Bugzilla-Target-Milestone: 8.0 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: 2017-q2/txt/msg00281.txt.bz2 Content-length: 241 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21187 --- Comment #15 from David Engster --- Sorry, the above refers to bug 21078. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21481-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 13 09:50:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79423 invoked by alias); 13 Jun 2017 09:50:05 -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 76167 invoked by uid 55); 13 Jun 2017 09:50:03 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Tue, 13 Jun 2017 09:50: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00282.txt.bz2 Content-length: 1465 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 --- Comment #12 from Pedro Alves --- On 06/13/2017 01:01 AM, keiths at redhat dot com wrote: >=20 > <3>: Abbrev Number: 53 (DW_TAG_subprogram) > DW_AT_external : 1=20=20=20=20=20=20 > DW_AT_name : (indirect string, offset: 0x2806): > _ZN5Shell6TinySh7char_inEc.constprop.67=20=20=20=20=20 Hmm, constprop here might well be related. This is: $ echo _ZN5Shell6TinySh7char_inEc.constprop.67 | c++filt=20 Shell::TinySh::char_in(char) [clone .constprop.67] I think that means that the compiler cloned the "char_in(char)" function, constant-propagated some argument in that clone. I'd guess it decided the char_in function does not use the "this" pointer for anything, and got rid of it in the clone? And then the compiler's debug info emission code gets confused and always emits the first parameter as artificial, even though it's no longer the "this" hidden arg? Just guessing. Or could maybe "Shell::TinySh::char_in(char)" be really a static method, and the "char" parameter ends up marked artificial because that's what the compiler "const propagated"? I.e., that parameter doesn't really exist in the generated code? It'd be good to know what exactly was "Shell::TinySh::char_in(char)" compiled from -- free function, method, static method? Etc. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21482-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 13 13:22:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 56089 invoked by alias); 13 Jun 2017 13:22:41 -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 56022 invoked by uid 55); 13 Jun 2017 13:22:40 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/15391] DW_OP_GNU_implicit_pointer bug Date: Tue, 13 Jun 2017 13:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at redhat dot com X-Bugzilla-Target-Milestone: 7.7 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: 2017-q2/txt/msg00283.txt.bz2 Content-length: 2194 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15391 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Andreas Arnez : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dd5d1163eff24= 15a01895f1cff8bbee32b3f0ab66 commit d5d1163eff2415a01895f1cff8bbee32b3f0ab66 Author: Andreas Arnez Date: Tue Jun 13 15:20:26 2017 +0200 write_pieced_value: Fix size capping logic A field f in a structure composed of DWARF pieces may be located in multiple pieces, where the first and last of those may contain bits from other fields as well. So when writing to f, the beginning of the first and the end of the last of those pieces may have to be skipped. But the logic in write_pieced_value for handling one of those pieces is flawed when the first and last piece are the same, i.e., f is contained in a single piece: < - - - - - - - - - piece_size - - - - - - - - - -> +-------------------------------------------------+ | skipped_bits | f_bits | / / / / / / / / / / | +-------------------------------------------------+ The current logic determines the size of the sub-piece to operate on by limiting the piece size to the bit size of f and then subtracting the skipped bits: min (piece_size, f_bits) - skipped_bits Instead of: min (piece_size - skipped_bits, f_bits) So the resulting sub-piece size is corrupted, leading to wrong handling= of this piece in write_pieced_value. Note that the same bug was already found in read_pieced_value and fixed there (but not in write_pieced_value), see PR 15391. This patch swaps the calculations, bringing them into the same (correct) order as in read_pieced_value. gdb/ChangeLog: * dwarf2loc.c (write_pieced_value): Fix order of calculations for size capping. gdb/testsuite/ChangeLog: * gdb.dwarf2/var-pieces.exp: Add test case for modifying a variable at nonzero offset. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21483-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 13 13:22:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 56674 invoked by alias); 13 Jun 2017 13:22:46 -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 56623 invoked by uid 55); 13 Jun 2017 13:22:45 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21226] DW_OP_stack_value pieces yield wrong data on big-endian targets Date: Tue, 13 Jun 2017 13:22: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: arnez at linux dot vnet.ibm.com 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: 2017-q2/txt/msg00284.txt.bz2 Content-length: 1715 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21226 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Andreas Arnez : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3De93523245b70= 4bc126705620969b4736b00350c5 commit e93523245b704bc126705620969b4736b00350c5 Author: Andreas Arnez Date: Tue Jun 13 15:20:26 2017 +0200 PR gdb/21226: Take DWARF stack value pieces from LSB end When taking a DW_OP_piece or DW_OP_bit_piece from a DW_OP_stack_value, = the existing logic always takes the piece from the lowest-addressed end, wh= ich is wrong on big-endian targets. The DWARF standard states that the "DW_OP_bit_piece operation describes a sequence of bits using the least significant bits of that value", and this also matches the current logic in GCC. For instance, the GCC guality test case pr54970.c fails on s39= 0x because of this. This fix adjusts the piece accordingly on big-endian targets. It is assumed that: * DW_OP_piece shall take the piece from the LSB end as well; * pieces reaching outside the stack value bits are considered undefined, and a zero value can be used instead. gdb/ChangeLog: PR gdb/21226 * dwarf2loc.c (read_pieced_value): Anchor stack value pieces at the LSB end, independent of endianness. gdb/testsuite/ChangeLog: PR gdb/21226 * gdb.dwarf2/nonvar-access.exp: Add checks for verifying that stack value pieces are taken from the LSB end. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21484-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 13 15:32:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 29712 invoked by alias); 13 Jun 2017 15:32:47 -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 29661 invoked by uid 48); 13 Jun 2017 15:32:46 -0000 From: "fhomborg at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21574] New: `help run` message says arguments are expanded via "sh" Date: Tue, 13 Jun 2017 15:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: fhomborg at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00285.txt.bz2 Content-length: 834 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21574 Bug ID: 21574 Summary: `help run` message says arguments are expanded via "sh" Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: minor Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: fhomborg at gmail dot com Target Milestone: --- In response to `help run`, gdb says "Args may include "*", or "[...]"; they= are expanded using "sh".". That's incorrect - they are expanded using $SHELL, whatever that may be (unless it is undefined, which it usually isn't at lea= st on UNIX-like systems). The info documentation seems correct. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21485-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 13 16:53:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 45911 invoked by alias); 13 Jun 2017 16:53:54 -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 45885 invoked by uid 48); 13 Jun 2017 16:53:53 -0000 From: "linuxer at quantentunnel dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Tue, 13 Jun 2017 16:53: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: linuxer at quantentunnel dot de X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00286.txt.bz2 Content-length: 375 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 --- Comment #13 from Johannes --- Created attachment 10095 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10095&action=3Ded= it Header file for the Shell::TinySh class, implementation follows. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21486-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 13 16:55:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 82004 invoked by alias); 13 Jun 2017 16:55:08 -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 81337 invoked by uid 48); 13 Jun 2017 16:55:07 -0000 From: "linuxer at quantentunnel dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Tue, 13 Jun 2017 16:55: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: linuxer at quantentunnel dot de X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00287.txt.bz2 Content-length: 354 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 --- Comment #14 from Johannes --- Created attachment 10096 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10096&action=3Ded= it Implementation for the Shell::TinySh class. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21487-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 13 17:03:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49954 invoked by alias); 13 Jun 2017 17:03:28 -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 49918 invoked by uid 48); 13 Jun 2017 17:03:27 -0000 From: "linuxer at quantentunnel dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/21549] c-typeprint.c:262: internal-error: void cp_type_print_method_args(type*, const char*, const char*, int, ui_file*, const type_print_options*): Assertion `TYPE_CODE (args[0].type) == TYPE_CODE_PTR' failed. Date: Tue, 13 Jun 2017 17:03: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: linuxer at quantentunnel dot de X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00288.txt.bz2 Content-length: 585 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21549 --- Comment #15 from Johannes --- Created attachment 10097 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10097&action=3Ded= it The linker input for the Shell::TinySh class. (in reply to comment #10, #11. #12) I attached the mentioned Shell::TinySh class in source and the linker input= for that. I hope that helps for your investigation. Best regards and many thanks for your efforts,=20 Johannes --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21488-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 14 15:51:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63108 invoked by alias); 14 Jun 2017 15:51:27 -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 63063 invoked by uid 48); 14 Jun 2017 15:51:26 -0000 From: "arnez at linux dot vnet.ibm.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21226] DW_OP_stack_value pieces yield wrong data on big-endian targets Date: Wed, 14 Jun 2017 15:51: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arnez at linux dot vnet.ibm.com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: arnez at linux dot vnet.ibm.com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution 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: 2017-q2/txt/msg00289.txt.bz2 Content-length: 972 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21226 Andreas Arnez changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |krebbel at linux dot vnet.= ibm.com Resolution|--- |FIXED --- Comment #5 from Andreas Arnez --- (In reply to cvs-commit@gcc.gnu.org from comment #4) > commit e93523245b704bc126705620969b4736b00350c5 > Author: Andreas Arnez > Date: Tue Jun 13 15:20:26 2017 +0200 >=20 > PR gdb/21226: Take DWARF stack value pieces from LSB end This commit fixes the problem. In particular all FAILs from pr54970.c in G= CC's guality test suite go away. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21489-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 14 20:29:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 38235 invoked by alias); 14 Jun 2017 20:29:33 -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 38155 invoked by uid 48); 14 Jun 2017 20:29:33 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21574] `help run` message says arguments are expanded via "sh" Date: Wed, 14 Jun 2017 20:29: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc component assigned_to everconfirmed 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: 2017-q2/txt/msg00290.txt.bz2 Content-length: 713 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21574 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-06-14 CC| |sergiodj at redhat dot com Component|tui |gdb Assignee|unassigned at sourceware dot org |sergiodj at redhat = dot com Ever confirmed|0 |1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21490-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 14 21:01:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31152 invoked by alias); 14 Jun 2017 21:01:01 -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 31037 invoked by uid 48); 14 Jun 2017 21:00:59 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21599] New: gdb crashes when in TUI mode and terminal window is made small Date: Wed, 14 Jun 2017 21:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: 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: 2017-q2/txt/msg00291.txt.bz2 Content-length: 1058 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21599 Bug ID: 21599 Summary: gdb crashes when in TUI mode and terminal window is made small Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: tui Assignee: sergiodj at redhat dot com Reporter: sergiodj at redhat dot com CC: jlebon at redhat dot com Target Milestone: --- [ Clone of https://bugzilla.redhat.com/show_bug.cgi?id=3D1459334 ] Description of problem: gdb will crash in TUI mode if the terminal window gets too small. Version-Release number of selected component (if applicable): $ rpm -q gdb gdb-7.12.1-48.fc25.x86_64 How reproducible: Always Steps to Reproduce: 1. Start gdb 2. Enter TUI mode 3. Make the terminal window (or tmux pane) very small Actual results: gdb crashes Expected results: gdb doesn't crash Additional info: --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21491-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 14 21:09:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49261 invoked by alias); 14 Jun 2017 21:09:53 -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 49234 invoked by uid 48); 14 Jun 2017 21:09:52 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21599] gdb crashes when in TUI mode and terminal window is made small Date: Wed, 14 Jun 2017 21:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status 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: 2017-q2/txt/msg00292.txt.bz2 Content-length: 825 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21599 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #1 from Sergio Durigan Junior --- More instructions on how to reproduce. 1) Enter tmux. I am assuming that the modifier sequence for your tmux is C= -b (the default). 2) Split the pane horizontally (C-b "). 3) Start GDB in TUI mode (gdb -tui) on the upper pane. 4) Resize the upper pane, making it as small as possible (C-b , repeatedly). You should see a segmentation fault. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21492-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 02:22:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 87085 invoked by alias); 15 Jun 2017 02:22:16 -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 86642 invoked by uid 48); 15 Jun 2017 02:22:15 -0000 From: "kanglictf at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/21600] New: Fail to detect invalid FDE header, can exhaust gdb process's virtual memory and terminate debug session Date: Thu, 15 Jun 2017 02:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kanglictf at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00293.txt.bz2 Content-length: 1867 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21600 Bug ID: 21600 Summary: Fail to detect invalid FDE header, can exhaust gdb process's virtual memory and terminate debug session Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: backtrace Assignee: unassigned at sourceware dot org Reporter: kanglictf at gmail dot com Target Milestone: --- GDB fails to catch an invalid length informaiton in dwarf debug frame FDE headers. A carefully created ELF file or core file can cause gdb to termina= te the debug session due to memory exhausted error. This bug was found by Kang Li and Yue Yin . We also thank Guodong Zhu for help troubleshooting. This bug was found and verified on 32-bit Ubuntu 14.04 LTS (and tested on Ubuntu 12.04.5 as well) The software was checkout from git://sourceware.org/git/binutils-gdb.git on 2017/06/14 and the latest commit f7e16c2a9cc405707e646e951397938d2b4eea48 The package was built with gcc 4.8.3 . * Two ways to reproduce the error Method A: 1. Use gdb to open a malformed core file (file cb and core are in attachm= ent) $ gdb cb core 2. after sometime, gdb will show virtual memory exhausted error.=20 Method B: 1. Use gdb to load a malformed ELF binary (file trouble_bin is in attachm= ent) $ gdb trouble_bin 2. Set a breakpoint. It does not matter where as long as it will be hit at run time. In this example, we put a breakpoint at the start of .init section. (gdb) br *0x80482b0=20=20=20=20=20=20=20=20=20=20=20 3. run and gdb will show virtual memory exhausted error after it hit a breakpoint. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21493-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 02:23:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 114580 invoked by alias); 15 Jun 2017 02:23:48 -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 114545 invoked by uid 48); 15 Jun 2017 02:23:47 -0000 From: "kanglictf at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/21600] Fail to detect invalid FDE header, can exhaust gdb process's virtual memory and terminate debug session Date: Thu, 15 Jun 2017 02:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kanglictf at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00294.txt.bz2 Content-length: 417 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21600 --- Comment #1 from Kang --- Created attachment 10141 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10141&action=3Ded= it malformed core file gdb runs into error when open this file along with the normal binary (the attachment called cb) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21494-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 02:25:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 115766 invoked by alias); 15 Jun 2017 02:25:01 -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 115643 invoked by uid 48); 15 Jun 2017 02:24:53 -0000 From: "kanglictf at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/21600] Fail to detect invalid FDE header, can exhaust gdb process's virtual memory and terminate debug session Date: Thu, 15 Jun 2017 02:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kanglictf at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00295.txt.bz2 Content-length: 411 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21600 --- Comment #2 from Kang --- Created attachment 10142 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10142&action=3Ded= it a regular ELF file (cb), used to load with the core file use gdb to load this ELF and the core file together. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21495-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 02:26:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 14643 invoked by alias); 15 Jun 2017 02:26:36 -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 12890 invoked by uid 48); 15 Jun 2017 02:26:33 -0000 From: "kanglictf at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/21600] Fail to detect invalid FDE header, can exhaust gdb process's virtual memory and terminate debug session Date: Thu, 15 Jun 2017 02:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kanglictf at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00296.txt.bz2 Content-length: 380 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21600 --- Comment #3 from Kang --- Created attachment 10143 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10143&action=3Ded= it a malformed ELF file gdb shows error message after run this with a breakpoint. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21496-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 02:28:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 111417 invoked by alias); 15 Jun 2017 02:28: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 111057 invoked by uid 48); 15 Jun 2017 02:28:22 -0000 From: "kanglictf at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/21600] Fail to detect invalid FDE header, can exhaust gdb process's virtual memory and terminate debug session Date: Thu, 15 Jun 2017 02:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kanglictf at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00297.txt.bz2 Content-length: 318 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21600 --- Comment #4 from Kang --- Created attachment 10144 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10144&action=3Ded= it sample patch file --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21497-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 02:29:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53790 invoked by alias); 15 Jun 2017 02:29:55 -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 52668 invoked by uid 48); 15 Jun 2017 02:29:54 -0000 From: "kanglictf at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/21600] Fail to detect invalid FDE header, can exhaust gdb process's virtual memory and terminate debug session Date: Thu, 15 Jun 2017 02:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kanglictf at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00298.txt.bz2 Content-length: 346 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21600 --- Comment #5 from Kang --- Created attachment 10145 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10145&action=3Ded= it screenshot or gdb failure when open core file --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21498-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 02:31:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94235 invoked by alias); 15 Jun 2017 02:31:11 -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 75822 invoked by uid 48); 15 Jun 2017 02:30:50 -0000 From: "kanglictf at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/21600] Fail to detect invalid FDE header, can exhaust gdb process's virtual memory and terminate debug session Date: Thu, 15 Jun 2017 02:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kanglictf at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q2/txt/msg00299.txt.bz2 Content-length: 343 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21600 --- Comment #6 from Kang --- Created attachment 10146 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10146&action=3Ded= it screenshot when gdb fails during debugging --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21499-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 02:36:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 121420 invoked by alias); 15 Jun 2017 02:36:36 -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 119793 invoked by uid 48); 15 Jun 2017 02:36:35 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21419] Unable to list program after loading symbolic table Date: Thu, 15 Jun 2017 02:36: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: WAITING 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: bug_status cf_reconfirmed_on cc everconfirmed 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: 2017-q2/txt/msg00300.txt.bz2 Content-length: 910 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21419 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2017-06-15 CC| |sergiodj at redhat dot com Ever confirmed|0 |1 --- Comment #2 from Sergio Durigan Junior --- I am not sure if I understand this bug. Do you have the source file on the same directory as your binary? If there is a binary but you don't have the corresponding source file, GDB won't be able to list anything. Can you pro= vide more information, please? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21500-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 02:46:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88279 invoked by alias); 15 Jun 2017 02:46:45 -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 88237 invoked by uid 55); 15 Jun 2017 02:46:43 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21574] `help run` message says arguments are expanded via "sh" Date: Thu, 15 Jun 2017 02:46: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: 2017-q2/txt/msg00301.txt.bz2 Content-length: 1142 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21574 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D45159d6ad394= fe7db840b2b92eaa69508b8a8fe7 commit 45159d6ad394fe7db840b2b92eaa69508b8a8fe7 Author: Sergio Durigan Junior Date: Wed Jun 14 16:45:20 2017 -0400 PR gdb/21574: Mention $SHELL and startup-with-shell on "help run" This simple patch updates the documentation of "help run" in order to mention that the shell used to start the inferior comes from the $SHELL environment variable. It also mentions that this behaviour can be disabled by using the "set startup-with-shell off" command. gdb/ChangeLog: 2017-06-14 Sergio Durigan Junior PR gdb/21574 * infcmd.c (_initialize_infcmd): Expand "help run" documentation to mention $SHELL and startup-with-shell. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21501-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 02:46:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88593 invoked by alias); 15 Jun 2017 02:46:51 -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 88560 invoked by uid 48); 15 Jun 2017 02:46:50 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21574] `help run` message says arguments are expanded via "sh" Date: Thu, 15 Jun 2017 02:46: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q2/txt/msg00302.txt.bz2 Content-length: 526 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21574 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Sergio Durigan Junior --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21502-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 09:05:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23116 invoked by alias); 15 Jun 2017 09:05:44 -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 23068 invoked by uid 48); 15 Jun 2017 09:05:44 -0000 From: "vishwanath.patil at pathpartnertech dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21419] Unable to list program after loading symbolic table Date: Thu, 15 Jun 2017 09:05: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: vishwanath.patil at pathpartnertech dot com X-Bugzilla-Status: WAITING 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: 2017-q2/txt/msg00303.txt.bz2 Content-length: 311 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21419 --- Comment #3 from vishwanath --- It is cross compiling , only building with -g (with symbols) can't it list = the program ? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21503-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 09:06:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23715 invoked by alias); 15 Jun 2017 09:06:21 -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 23686 invoked by uid 48); 15 Jun 2017 09:06:20 -0000 From: "vishwanath.patil at pathpartnertech dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21419] Unable to list program after loading symbolic table Date: Thu, 15 Jun 2017 09:06: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: vishwanath.patil at pathpartnertech dot com X-Bugzilla-Status: WAITING 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: 2017-q2/txt/msg00304.txt.bz2 Content-length: 311 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21419 --- Comment #4 from vishwanath --- It is cross compiling , only building with -g (with symbols) can't it list = the program ? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21504-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 16:46:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3669 invoked by alias); 15 Jun 2017 16:46:15 -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 3643 invoked by uid 48); 15 Jun 2017 16:46:14 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21419] Unable to list program after loading symbolic table Date: Thu, 15 Jun 2017 16:46: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: WAITING 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: 2017-q2/txt/msg00305.txt.bz2 Content-length: 404 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21419 --- Comment #5 from Sergio Durigan Junior --- (In reply to vishwanath from comment #4) > It is cross compiling , only building with -g (with symbols) can't it list > the program ? But do you have access to the source code on the target? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21505-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 16:51:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 100430 invoked by alias); 15 Jun 2017 16:51:09 -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 100405 invoked by uid 48); 15 Jun 2017 16:51:08 -0000 From: "vishwanath.patil at pathpartnertech dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21419] Unable to list program after loading symbolic table Date: Thu, 15 Jun 2017 16:51: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: vishwanath.patil at pathpartnertech dot com X-Bugzilla-Status: WAITING 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: 2017-q2/txt/msg00306.txt.bz2 Content-length: 346 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21419 --- Comment #6 from vishwanath --- No , Even i am guessing now how can -g alone can help to get whole source c= ode. atleast break to function name will work ? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21506-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 16:58:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122093 invoked by alias); 15 Jun 2017 16:58:24 -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 121739 invoked by uid 48); 15 Jun 2017 16:58:23 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/21600] Fail to detect invalid FDE header, can exhaust gdb process's virtual memory and terminate debug session Date: Thu, 15 Jun 2017 16:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00307.txt.bz2 Content-length: 901 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21600 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #7 from Sergio Durigan Junior --- Thanks for the bug report. I see you have a possible patch to fix this iss= ue, and it is rather trivial (in the sense that it just modifies a few lines of code). In this case, I would suggest you to submit the patch, along with a description of what it does, to gdb-patches@sourceware.org. We have a wiki page which contains a contribution checklist: https://sourceware.org/gdb/wiki/ContributionChecklist. Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21507-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 18:13:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78649 invoked by alias); 15 Jun 2017 18:13:49 -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 78619 invoked by uid 48); 15 Jun 2017 18:13:49 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21419] Unable to list program after loading symbolic table Date: Thu, 15 Jun 2017 18:13: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: WAITING 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: 2017-q2/txt/msg00308.txt.bz2 Content-length: 705 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21419 --- Comment #7 from Sergio Durigan Junior --- (In reply to vishwanath from comment #6) > No , Even i am guessing now how can -g alone can help to get whole source > code. >=20 > atleast break to function name will work ? If GDB doesn't have access to the source code, it cannot list the program. = You can verify that by compiling a simple program on your machine, and then moving/removing the source code and trying to use the 'list' command inside GDB. As for break, yes, "break " should work without access to the source code. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21508-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 19:51:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 56690 invoked by alias); 15 Jun 2017 19:51:46 -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 56655 invoked by uid 48); 15 Jun 2017 19:51:45 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/21600] Fail to detect invalid FDE header, can exhaust gdb process's virtual memory and terminate debug session Date: Thu, 15 Jun 2017 19:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00309.txt.bz2 Content-length: 251 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21600 --- Comment #8 from Sergio Durigan Junior --- BTW, bug is confirmed on i686 targets. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21509-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 20:02:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 95256 invoked by alias); 15 Jun 2017 20:02:07 -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 95229 invoked by uid 55); 15 Jun 2017 20:02:06 -0000 From: "kanglictf at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/21600] Fail to detect invalid FDE header, can exhaust gdb process's virtual memory and terminate debug session Date: Thu, 15 Jun 2017 20:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kanglictf at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00310.txt.bz2 Content-length: 590 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21600 --- Comment #9 from Kang --- Got it! Will check how to fix this. On Thu, Jun 15, 2017 at 3:51 PM, sergiodj at redhat dot com < sourceware-bugzilla@sourceware.org> wrote: > https://sourceware.org/bugzilla/show_bug.cgi?id=3D21600 > > --- Comment #8 from Sergio Durigan Junior --- > BTW, bug is confirmed on i686 targets. > > -- > You are receiving this mail because: > You reported the bug. > --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21510-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 15 20:09:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 97786 invoked by alias); 15 Jun 2017 20:09:38 -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 97755 invoked by uid 48); 15 Jun 2017 20:09:37 -0000 From: "kanglictf at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/21600] Fail to detect invalid FDE header, can exhaust gdb process's virtual memory and terminate debug session Date: Thu, 15 Jun 2017 20:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kanglictf at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00311.txt.bz2 Content-length: 439 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21600 --- Comment #10 from Kang --- BTW, we just tested on earlier version of gdb (7.4 & 7.7). The bug affects earlier versions of gdb as well, i.e. malformed/malicious ELF binaries can prevent gdb from debugging by forcing session termination. We will work on= a new patch. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21511-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 16 12:41:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 9765 invoked by alias); 16 Jun 2017 12:41:04 -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 9220 invoked by uid 48); 16 Jun 2017 12:41:03 -0000 From: "david at engster dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21603] New: powerpc-linux-gnu-gdb throws internal error on remote debugging: 'gdbarch!=NULL' failed Date: Fri, 16 Jun 2017 12:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: david at engster dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00312.txt.bz2 Content-length: 1327 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21603 Bug ID: 21603 Summary: powerpc-linux-gnu-gdb throws internal error on remote debugging: 'gdbarch!=3DNULL' failed Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: david at engster dot org Target Milestone: --- This is with latest gdb 8.0, configured solely with '--target=3Dpowerpc-linux-gnu' on a GNU/Linux 64bit host system. When I try= to remote debug through gdbserver on a PowerPC e500v2 system, I get the follow= ing assertion: (gdb) target remote 172.20.5.224:2345 Remote debugging using 172.20.5.224:2345 Reading symbols from /bsp/sysroot/lib/ld.so.1...(no debugging symbols found)...done. gdbarch.c:3228: internal-error: int gdbarch_elf_make_msymbol_special_p(gdbarch*): Assertion `gdbarch !=3D NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y Version 7.12.1 has the same problem, but version 7.11 works, so this must be due to a change between those two versions. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21512-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 16 20:34:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78115 invoked by alias); 16 Jun 2017 20:34:24 -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 78092 invoked by uid 48); 16 Jun 2017 20:34:24 -0000 From: "evaned at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21606] New: Python: gdb.SYMBOL_FUNCTIONS_DOMAIN misspelled in documentation Date: Fri, 16 Jun 2017 20:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: evaned at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00313.txt.bz2 Content-length: 1447 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21606 Bug ID: 21606 Summary: Python: gdb.SYMBOL_FUNCTIONS_DOMAIN misspelled in documentation Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: evaned at gmail dot com Target Milestone: --- https://sourceware.org/gdb/current/onlinedocs/gdb/Symbols-In-Python.html#Sy= mbols-In-Python That page documents "gdb.SYMBOL_FUNCTION_DOMAIN", but it's FUNCTION*S* rath= er than FUNCTION. FUNCTIONS is correct on my 7.11 installation, but from a qui= ck grep of the 8.0 source, it doesn't seem to have changed names or had the do= cs corrected. Some of the documentation appears to be correct, and some is not: $ grep -R SYMBOL_FUNCTIONS_DOMAIN gdb/doc/python.texi:@vindex SYMBOL_FUNCTIONS_DOMAIN gdb/guile/lib/gdb.scm: SYMBOL_FUNCTIONS_DOMAIN gdb/python/py-symbol.c: || PyModule_AddIntConstant (gdb_module, "SYMBOL_FUNCTIONS_DOMAIN", $ grep -R SYMBOL_FUNCTION_DOMAIN=20 gdb/doc/python.texi:@item gdb.SYMBOL_FUNCTION_DOMAIN gdb/doc/guile.texi:@item SYMBOL_FUNCTION_DOMAIN gdb/doc/gdb.info-4:'gdb.SYMBOL_FUNCTION_DOMAIN' gdb/doc/gdb.info-4:'SYMBOL_FUNCTION_DOMAIN' (That's in gdb-8.0.tar.xz) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21513-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jun 19 14:49:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 76293 invoked by alias); 19 Jun 2017 14:49:08 -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 74221 invoked by uid 48); 19 Jun 2017 14:49:05 -0000 From: "krkhan at inspirated dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21623] New: add-symbol-file not loading symbols at the provided .text offset Date: Mon, 19 Jun 2017 14:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: krkhan at inspirated dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00314.txt.bz2 Content-length: 1285 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21623 Bug ID: 21623 Summary: add-symbol-file not loading symbols at the provided .text offset Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: krkhan at inspirated dot com Target Milestone: --- On a guest VM: > # cat /sys/module/dm_crypt/sections/{.text,.data} > 0xffffffffa049f000 > 0xffffffffa04a4000 Debugger: > (gdb) add-symbol-file drivers/md/dm-crypt.ko 0xffffffffa049f000 -s .data = 0xffffffffa04a4000 > add symbol table from file "drivers/md/dm-crypt.ko" at > .text_addr =3D 0xffffffffa049f000 > .data_addr =3D 0xffffffffa04a4000 > (y or n) y > Reading symbols from drivers/md/dm-crypt.ko...done. > (gdb) p crypt_target.version > $1 =3D {1, 15, 0} > (gdb) info addr crypt_target > Symbol "crypt_target" is static storage at address 0xffffffffa04a4020. > (gdb) info addr dm_crypt_exit > Symbol "dm_crypt_exit" is a function at address 0x4e. > (gdb) b dm_crypt_exit > Cannot access memory at address 0x4e --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21514-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jun 19 14:53:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23796 invoked by alias); 19 Jun 2017 14:53:32 -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 23770 invoked by uid 48); 19 Jun 2017 14:53:31 -0000 From: "krkhan at inspirated dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21623] add-symbol-file not loading symbols at the provided .text offset Date: Mon, 19 Jun 2017 14:53: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: krkhan at inspirated dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00315.txt.bz2 Content-length: 402 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21623 Kamran Khan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |krkhan at inspirated dot c= om --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21515-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jun 19 19:58:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 124218 invoked by alias); 19 Jun 2017 19:58:05 -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 124188 invoked by uid 48); 19 Jun 2017 19:58:04 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Mon, 19 Jun 2017 19:58: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: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00316.txt.bz2 Content-length: 542 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #11 from Keith Seitz --- (In reply to Adam Stylinski from comment #10) > So it's been about 3 months, any luck reproducing this? I'm very sorry, I've not been able to work on this for some time, but I do = have plans to investigate this further soon. I just wanted to drop you a note letting you know that I haven't (completely) forgotten about you/your probl= em. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21516-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 20 16:46:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 18816 invoked by alias); 20 Jun 2017 16:46:03 -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 18685 invoked by uid 48); 20 Jun 2017 16:45:56 -0000 From: "mjambor at suse dot cz" To: gdb-prs@sourceware.org Subject: [Bug c++/16874] Setting a breakpoint on function in anonymous namespace is unnecessarily awkward Date: Tue, 20 Jun 2017 16:46: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: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: mjambor at suse dot cz X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: patrick at parcs dot ath.cx X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q2/txt/msg00317.txt.bz2 Content-length: 472 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16874 Martin Jambor changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mjambor at suse dot cz --- Comment #13 from Martin Jambor --- ...and so did I. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21518-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 21 01:33:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 51557 invoked by alias); 21 Jun 2017 01:33:29 -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 51524 invoked by uid 48); 21 Jun 2017 01:33:29 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21606] Python: gdb.SYMBOL_FUNCTIONS_DOMAIN misspelled in documentation Date: Wed, 21 Jun 2017 01:33: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat 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 cc resolution 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: 2017-q2/txt/msg00319.txt.bz2 Content-length: 635 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21606 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |sergiodj at redhat dot com Resolution|--- |FIXED --- Comment #2 from Sergio Durigan Junior --- Thanks for the report. Fixed upstream. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21517-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 21 01:33:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49173 invoked by alias); 21 Jun 2017 01:33:03 -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 47731 invoked by uid 55); 21 Jun 2017 01:33:02 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21606] Python: gdb.SYMBOL_FUNCTIONS_DOMAIN misspelled in documentation Date: Wed, 21 Jun 2017 01:33: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00318.txt.bz2 Content-length: 1104 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21606 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Deb83230b4d5c= 0129174937846ded9eaa9f78ff28 commit eb83230b4d5c0129174937846ded9eaa9f78ff28 Author: Sergio Durigan Junior Date: Tue Jun 20 21:30:11 2017 -0400 Fix PR gdb/21606: SYMBOL_FUNCTIONS_DOMAIN misspelled in documentation Both Python and Guile documentations misspelled SYMBOL_FUNCTIONS_DOMAIN, writing SYMBOL_FUNCTION_DOMAIN instead. This obvious commit fixes it. gdb/doc/ChangeLog: 2017-06-20 Sergio Durigan Junior PR gdb/21606 * python.texi (Python representation of Symbols.): Replace SYMBOL_FUNCTION_DOMAIN by SYMBOL_FUNCTIONS_DOMAIN, fixing typo. * guile.texi (Guile representation of Symbols.): Likewise. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21519-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 21 08:46:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 90155 invoked by alias); 21 Jun 2017 08:46:45 -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 90038 invoked by uid 48); 21 Jun 2017 08:46:44 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/16874] Setting a breakpoint on function in anonymous namespace is unnecessarily awkward Date: Wed, 21 Jun 2017 08:46: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: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: patrick at parcs dot ath.cx X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q2/txt/msg00320.txt.bz2 Content-length: 742 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16874 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #14 from Pedro Alves --- This series will help with this: [PATCH 00/40] C++ debugging improvements: breakpoints, TAB completion, more https://sourceware.org/ml/gdb-patches/2017-06/msg00012.html You can find it in the users/palves/cxx-breakpoint-improvements branch meanwhile, if you want to give it a try. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21520-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 21 17:22:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 11979 invoked by alias); 21 Jun 2017 17:22:19 -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 11938 invoked by uid 48); 21 Jun 2017 17:22:17 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/13877] gdb7.4 doesn't build on FreeBSD ia64 Date: Wed, 21 Jun 2017 17:22: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.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jhb at FreeBSD dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WONTFIX 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 cc resolution 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: 2017-q2/txt/msg00321.txt.bz2 Content-length: 688 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13877 jhb at FreeBSD dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jhb at FreeBSD dot org Resolution|--- |WONTFIX --- Comment #7 from jhb at FreeBSD dot org --- FreeBSD/ia64 has been retired by FreeBSD. I do not think it is likely that support for FreeBSD/ia64 will ever be added to upstream gdb at this point. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21521-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 21 17:23:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 14266 invoked by alias); 21 Jun 2017 17:23:43 -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 14218 invoked by uid 48); 21 Jun 2017 17:23:42 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21239] gdb doesn't show any threads for some users Date: Wed, 21 Jun 2017 17:23: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jhb at FreeBSD dot org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00322.txt.bz2 Content-length: 475 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21239 jhb at FreeBSD dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jhb at FreeBSD dot org --- Comment #1 from jhb at FreeBSD dot org --- Do you have a sample program that demonstrates this? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21522-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 21 17:27:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 44238 invoked by alias); 21 Jun 2017 17:27:15 -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 43858 invoked by uid 48); 21 Jun 2017 17:27:14 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/8990] Compile error with gdb-cvs/gdb/i386fbsd-tdep.c Date: Wed, 21 Jun 2017 17:27: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jhb at FreeBSD dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: OBSOLETE X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution 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: 2017-q2/txt/msg00323.txt.bz2 Content-length: 650 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8990 jhb at FreeBSD dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |jhb at FreeBSD dot org Resolution|--- |OBSOLETE --- Comment #1 from jhb at FreeBSD dot org --- The code has changed and there is no longer an extern declaration of the now-static variable in i386fbsd-tdep.h. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21523-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 21 17:42:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 26469 invoked by alias); 21 Jun 2017 17:42:48 -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 26438 invoked by uid 48); 21 Jun 2017 17:42:47 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug build/18996] Build fails on FreesBSD 8.1 Date: Wed, 21 Jun 2017 17:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 7.10 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jhb at FreeBSD dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jhb at FreeBSD dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc assigned_to attachments.created 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: 2017-q2/txt/msg00324.txt.bz2 Content-length: 859 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18996 jhb at FreeBSD dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |jhb at FreeBSD dot org Assignee|unassigned at sourceware dot org |jhb at FreeBSD dot = org --- Comment #2 from jhb at FreeBSD dot org --- Created attachment 10210 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10210&action=3Ded= it nocoredump.patch Please try this patch. I see that the NOCOREDUMP flag was added later in 8= .x.=20 The upshot of this is that 'gcore' in gdb won't honor MAP_NOCORE flags pass= ed to mmap(). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21524-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 21 17:47:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 55386 invoked by alias); 21 Jun 2017 17:47:17 -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 55148 invoked by uid 48); 21 Jun 2017 17:47:16 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/13791] crash in breakpoint.c Date: Wed, 21 Jun 2017 17:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jhb at FreeBSD dot org 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: cc 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: 2017-q2/txt/msg00325.txt.bz2 Content-length: 807 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13791 jhb at FreeBSD dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jhb at FreeBSD dot org --- Comment #1 from jhb at FreeBSD dot org --- If you enabled the THREADS option in the gdb port that added an extra patch with thread support using libthread_db that itself was somewhat buggy. It = is quite possible that the error was in that patch rather than in gdb itself.= =20 Would you be able to retest with a more recent version of gdb (such as 7.11= or later) which includes a different implementation of thread support? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21525-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 21 20:26:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20073 invoked by alias); 21 Jun 2017 20:26:14 -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 20001 invoked by uid 48); 21 Jun 2017 20:26:13 -0000 From: "hjl.tools at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug record/21655] New: Process record does not support instruction 0xf6f at address 0x400170 Date: Wed, 21 Jun 2017 20:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hjl.tools at gmail dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget attachments.created Message-ID: 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: 2017-q2/txt/msg00326.txt.bz2 Content-length: 2501 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21655 Bug ID: 21655 Summary: Process record does not support instruction 0xf6f at address 0x400170 Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: record Assignee: unassigned at sourceware dot org Reporter: hjl.tools at gmail dot com Target Milestone: --- Target: x86-64 Created attachment 10211 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10211&action=3Ded= it A testcase [hjl@gnu-6 glibc-test]$ make gcc -g -c -o test.o test.c gcc -g -c -o record.o record.S gcc -g -c -o start.o start.S gcc -g -c -o syscall.o syscall.S ld -o test test.o record.o start.o syscall.o time ./test 0.00user 0.00system 0:00.00elapsed 73%CPU (0avgtext+0avgdata 288maxresident= )k 0inputs+0outputs (0major+140minor)pagefaults 0swaps [hjl@gnu-6 glibc-test]$ gdb ./test GNU gdb (GDB) Fedora 7.12.1-48.fc25 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./test...done. (gdb) b _start Breakpoint 1 at 0x400175: file start.S, line 28. (gdb) r Starting program: /export/ssd/git/glibc-test/test=20 Breakpoint 1, _start () at start.S:28 28 xorl %ebp, %ebp (gdb) record full (gdb) c Continuing. Process record does not support instruction 0xf6f at address 0x400170. Process record: failed to record execution log. Program stopped. record () at record.S:7 7 movq (%rsi,%rdx), %mm7 (gdb) disass/r=20 Dump of assembler code for function record: =3D> 0x0000000000400170 <+0>: 0f 6f 3c 16 movq (%rsi,%rdx,1),%mm7 0x0000000000400174 <+4>: c3 retq=20=20=20 End of assembler dump. (gdb) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21526-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 21 20:32:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 13236 invoked by alias); 21 Jun 2017 20:32:32 -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 13206 invoked by uid 48); 21 Jun 2017 20:32:32 -0000 From: "egbertst1 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug record/21655] Process record does not support instruction 0xf6f at address 0x400170 Date: Wed, 21 Jun 2017 20:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: egbertst1 at gmail dot com 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: cc 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: 2017-q2/txt/msg00327.txt.bz2 Content-length: 382 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21655 egbertst1 at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |egbertst1 at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21527-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 21 20:40:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 115472 invoked by alias); 21 Jun 2017 20:40:02 -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 114742 invoked by uid 48); 21 Jun 2017 20:40:01 -0000 From: "hjl.tools at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug record/21655] Process record does not support instruction 0xf6f at address 0x400170 Date: Wed, 21 Jun 2017 20:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hjl.tools at gmail dot com 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: 2017-q2/txt/msg00328.txt.bz2 Content-length: 309 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21655 --- Comment #1 from H.J. Lu --- i386_mmx_regnum_p (gdbarch=3D0xfd1940, regnum=3D6) returns false since (top-gdb) p tdep->mm0_regnum $4 =3D -1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21528-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 21 20:42:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20730 invoked by alias); 21 Jun 2017 20:42:21 -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 20630 invoked by uid 48); 21 Jun 2017 20:42:20 -0000 From: "egbertst1 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug record/21655] Process record does not support instruction 0xf6f at address 0x400170 Date: Wed, 21 Jun 2017 20:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: egbertst1 at gmail dot com 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: 2017-q2/txt/msg00329.txt.bz2 Content-length: 981 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21655 --- Comment #2 from egbertst1 at gmail dot com --- Confirmed. Missing separate debuginfos, use: debuginfo-install libgcc-4.4.7-18.el6.x86= _64 libstdc++-4.4.7-18.el6.x86_64 pcre-7.8-7.el6.x86_64 gdb$ record full gdb$ set record full insn-number-max 2000000 gdb$ c Continuing. Process record does not support instruction 0xf6f at address 0x33af241b20. Process record: failed to record execution log. Program stopped. __mpn_lshift () at ../sysdeps/x86_64/lshift.S:26 26 movq -8(%rsi,%rdx,8), %mm7 gdb$ x /i $pc =3D> 0x33af241b20 <__mpn_lshift>: movq -0x8(%rsi,%rdx,8),%mm7 gdb$ x /4x $pc 0x33af241b20 <__mpn_lshift>: 0xd67c6f0f 0xc96e0ff8 0x000040b8 0x0fc82900 And wanted you to know that this bug has been reintroduced back in latest binutils. CentOS: 6.9 binutils-2.20.51.0.2-5.47.el6_9.1.x86_64 g++ 5.3.1 20160406 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21529-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 21 20:44:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 24041 invoked by alias); 21 Jun 2017 20:44:08 -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 23904 invoked by uid 48); 21 Jun 2017 20:44:06 -0000 From: "hjl.tools at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug record/21655] Process record does not support instruction 0xf6f at address 0x400170 Date: Wed, 21 Jun 2017 20:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hjl.tools at gmail dot com 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: 2017-q2/txt/msg00330.txt.bz2 Content-length: 452 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21655 --- Comment #3 from H.J. Lu --- (In reply to H.J. Lu from comment #1) > i386_mmx_regnum_p (gdbarch=3D0xfd1940, regnum=3D6) returns false since >=20 > (top-gdb) p tdep->mm0_regnum > $4 =3D -1 It is due to /* Avoid wiring in the MMX registers for now. */ tdep->num_mmx_regs =3D 0; --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21530-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 21 20:47:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 29564 invoked by alias); 21 Jun 2017 20:47:41 -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 29533 invoked by uid 48); 21 Jun 2017 20:47:40 -0000 From: "hjl.tools at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug record/21655] Process record does not support instruction 0xf6f at address 0x400170 Date: Wed, 21 Jun 2017 20:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hjl.tools at gmail dot com 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: 2017-q2/txt/msg00331.txt.bz2 Content-length: 357 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21655 --- Comment #4 from H.J. Lu --- (In reply to egbertst1 from comment #2) >=20=20 > And wanted you to know that this bug has been reintroduced back in latest > binutils. >=20 It never worked. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21531-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 22 04:49:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 103955 invoked by alias); 22 Jun 2017 04:49:43 -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 103848 invoked by uid 48); 22 Jun 2017 04:49:36 -0000 From: "bgkweb at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21656] New: Missing last character when target-charset set to CP1255 Date: Thu, 22 Jun 2017 04:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bgkweb at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00332.txt.bz2 Content-length: 1373 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21656 Bug ID: 21656 Summary: Missing last character when target-charset set to CP1255 Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: bgkweb at gmail dot com Target Milestone: --- When the target charset is set to CP1255, strings are most of the time miss= ing their last character. Reproduction steps: $ gdb GNU gdb (GDB) 8.0 This GDB was configured as "x86_64-pc-linux-gnu". (gdb) show host-charset=20 The host character set is "auto; currently UTF-8". (gdb) set target-charset CP1255 (gdb) print "=D7=A9=D7=AA=D7=9B=D7=A0=D7=A0=D7=95" $1 =3D "=D7=A9=D7=AA=D7=9B=D7=A0=D7=A0" (gdb)=20 Notice how the last "=D7=95" from the input string is missing. (Hebrew is a= right to left language, the last character is on the left in a browser) This is most likely due to the fact that CP1255 is a stateful encoding in i= conv and the iconv conversion state is not flushed. man 3 iconv explains iconv must be called a second time with inbuf =3D NULL= to flush the conversion state to the output buffer. See also #1124. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21532-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 22 15:44:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 56820 invoked by alias); 22 Jun 2017 15:44:47 -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 56791 invoked by uid 48); 22 Jun 2017 15:44:47 -0000 From: "sourceware.bugs at andred dot net" To: gdb-prs@sourceware.org Subject: [Bug server/21658] New: gdbserver invalid use of sigprocmask() (fails to start on musl) Date: Thu, 22 Jun 2017 15:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sourceware.bugs at andred dot net X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q2/txt/msg00333.txt.bz2 Content-length: 1022 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21658 Bug ID: 21658 Summary: gdbserver invalid use of sigprocmask() (fails to start on musl) Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: server Assignee: unassigned at sourceware dot org Reporter: sourceware.bugs at andred dot net Target Milestone: --- Created attachment 10213 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10213&action=3Ded= it fix >>From the attached patch: --- snip --- As per POSIX, The pthread_sigmask() and sigprocmask() functions shall fail if: [EINVAL] The value of the how argument is not equal to one of the defined values. and this is how musl-libc is currently doing. ---snap--- Please see attached patch (used both in OpenEmbedded and LEDE projects) fix= ing the issue. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21533-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 22 15:50:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 67222 invoked by alias); 22 Jun 2017 15:50:50 -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 67179 invoked by uid 48); 22 Jun 2017 15:50:49 -0000 From: "sourceware.bugs at andred dot net" To: gdb-prs@sourceware.org Subject: [Bug server/21658] gdbserver invalid use of sigprocmask() (fails to start on musl) Date: Thu, 22 Jun 2017 15:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: std-posix X-Bugzilla-Severity: normal X-Bugzilla-Who: sourceware.bugs at andred dot net X-Bugzilla-Status: UNCONFIRMED 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: keywords cf_gcctarget bug_file_loc cf_gcchost 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: 2017-q2/txt/msg00334.txt.bz2 Content-length: 806 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21658 Andr=C3=A9 Draszik changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |std-posix Target| |linux-musl URL| |https://bugs.lede-project.o | |rg/index.php?do=3Ddetails&= tas | |k_id=3D637&openedfrom=3D-1= %2Bwe | |ek Host| |linux-musl --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21534-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 22 18:30:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 97819 invoked by alias); 22 Jun 2017 18:30:50 -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 97635 invoked by uid 48); 22 Jun 2017 18:30:39 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug server/21658] gdbserver invalid use of sigprocmask() (fails to start on musl) Date: Thu, 22 Jun 2017 18:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: std-posix X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00335.txt.bz2 Content-length: 702 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21658 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #1 from Sergio Durigan Junior --- The fix makes sense to me. Would you like to post this patch to gdb-patches@sourceware.org and see what others think? I believe it should = be accepted as is, and you don't need a copyright assignment for it. Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21535-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 23 08:19:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 24210 invoked by alias); 23 Jun 2017 08:19:19 -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 24173 invoked by uid 48); 23 Jun 2017 08:19:19 -0000 From: "sourceware.bugs at andred dot net" To: gdb-prs@sourceware.org Subject: [Bug server/21658] gdbserver invalid use of sigprocmask() (fails to start on musl) Date: Fri, 23 Jun 2017 08:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: std-posix X-Bugzilla-Severity: normal X-Bugzilla-Who: sourceware.bugs at andred dot net X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00336.txt.bz2 Content-length: 278 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21658 --- Comment #2 from Andr=C3=A9 Draszik = --- https://sourceware.org/ml/gdb-patches/2017-06/msg00671.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21536-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jun 26 13:07:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 54567 invoked by alias); 26 Jun 2017 13:07:17 -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 54542 invoked by uid 48); 26 Jun 2017 13:07:17 -0000 From: "jonah at kichwacoders dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21675] New: Regression since 8.0 in Printing/formatting some values Date: Mon, 26 Jun 2017 13:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jonah at kichwacoders dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00337.txt.bz2 Content-length: 1048 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21675 Bug ID: 21675 Summary: Regression since 8.0 in Printing/formatting some values Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jonah at kichwacoders dot com Target Milestone: --- For example on current HEAD: $ gdb/gdb -q -ex 'print/o -5' -ex quit $1 =3D 037773777773 Instead previous versions do this: $ gdb.8.0 -q -ex 'print/o -5' -ex quit $1 =3D 037777777773 AFAICT This is a regression caused by d9109c8080ac0a2caeaa5f3d51e8a3b4891a6= 8a8 (Simplify print_scalar_formatted) There are many other examples of things that fail in a similar way. They we= re picked up by the DSF-GDB testsuite for Eclipse CDT. https://ci.eclipse.org/cdt/view/Debug/job/debug-tests-master-gdb-master --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21537-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jun 26 13:30:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53957 invoked by alias); 26 Jun 2017 13:30:48 -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 53689 invoked by uid 48); 26 Jun 2017 13:30:24 -0000 From: "jonah at kichwacoders dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21675] Regression since 8.0 printing has changed format for decimal/octal/others Date: Mon, 26 Jun 2017 13:30: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jonah at kichwacoders dot com X-Bugzilla-Status: UNCONFIRMED 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: short_desc 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: 2017-q2/txt/msg00338.txt.bz2 Content-length: 921 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21675 Jonah Graham changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Regression since 8.0 in |Regression since 8.0 |Printing/formatting some |printing has changed format |values |for decimal/octal/others --- Comment #1 from Jonah Graham --- Here is another example, demonstrating the problem is not just octal printi= ng: $ gdb/gdb -q -ex 'print/d 1.5' -ex quit $1 =3D 1.5 $ gdb.8.0 -q -ex 'print/d 1.5' -ex quit $1 =3D 1 and $ gdb/gdb -q -ex 'print/u 1.5' -ex quit $1 =3D 4609434218613702656 $ gdb.8.0 -q -ex 'print/u 1.5' -ex quit $1 =3D 1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21538-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 27 00:05:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 86355 invoked by alias); 27 Jun 2017 00:05:14 -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 86312 invoked by uid 48); 27 Jun 2017 00:05:13 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21497] FreeBSD: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed Date: Tue, 27 Jun 2017 00:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jhb at FreeBSD dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00339.txt.bz2 Content-length: 1155 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21497 --- Comment #5 from jhb at FreeBSD dot org --- So I've reworked my previous patchset a bit. It does automatically PT_SUSP= END new threads and do an explicit PT_CONTINUE instead of returning an event to= the core and relying on the core to invoke fbsd_resume() to suspend the thread similar to your patch, though I don't actually return an event but loop aro= und in fbsd_wait(). I also have attempted to add the same handling for the non-LWP-event case. I've done some simple testing of these patches for both LWP events and non-LWP events, but I'm not able to reproduce your original issue either. (The one other test case for which my original patch referre= d to above tried to handle is still not fixed by this patchset, but I don't see = an easy way to fix it and it only breaks for the non-LWP-event case.) I've pushed my current set of changes to a 'fbsd_suspend_new_thr' branch at github.com/bsdjhb/gdb.git. You can view a diff via: https://github.com/bsdjhb/gdb/compare/master...fbsd_suspend_new_thr --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21539-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 27 09:36:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 126757 invoked by alias); 27 Jun 2017 09:36:28 -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 126722 invoked by uid 48); 27 Jun 2017 09:36:27 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21675] Regression since 8.0 printing has changed format for decimal/octal/others Date: Tue, 27 Jun 2017 09:36: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00340.txt.bz2 Content-length: 473 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21675 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com, | |tromey at sourceware dot o= rg --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21540-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jun 27 19:50:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 25138 invoked by alias); 27 Jun 2017 19:50:19 -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 24955 invoked by uid 48); 27 Jun 2017 19:50:18 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/21681] New: Provide a way for GDB to conveniently attach to processes by name Date: Tue, 27 Jun 2017 19:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00341.txt.bz2 Content-length: 1347 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21681 Bug ID: 21681 Summary: Provide a way for GDB to conveniently attach to processes by name Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: cli Assignee: unassigned at sourceware dot org Reporter: simon.marchi at ericsson dot com Target Milestone: --- lldb allows you to attach to processes by name if there's no ambiguity, I t= hink that's quite convenient. If there is some ambiguity, it shows you something like this: (lldb) attach gdb error: attach failed: more than one process named gdb: PID PARENT USER TRIPLE ARGUMENTS =3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D 43851 43820 simark x86_64-apple-macosx ./gdb 43784 43572 simark x86_64-apple-macosx ./gdb --data-directory=3Ddata-directory /Users/simark/test You can do "attach " on the command line, or you can do "lldb -n " from the shell. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21541-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 28 02:01:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 9766 invoked by alias); 28 Jun 2017 02:01:31 -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 115740 invoked by uid 55); 28 Jun 2017 02:01:01 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21337] [mips] segfault when re-reading symbols with remote debugging. Date: Wed, 28 Jun 2017 02:01: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00342.txt.bz2 Content-length: 2291 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21337 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Maciej W. Rozycki : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D41664b45ab63= 87184bd0e7512fcf7a72c58744e7 commit 41664b45ab6387184bd0e7512fcf7a72c58744e7 Author: Doug Gilmore Date: Wed Jun 28 02:54:22 2017 +0100 Fix PR 21337: segfault when re-reading symbols. Fix issue exposed by commit 3e29f34. The basic issue is that section data referenced through an objfile pointer can also be referenced via the program-space data pointer, although via a separate mapping mechanism, which is set up by update_section_map. Thus once section data attached to an objfile pointer is released, the section map associated with the program-space data pointer must be marked dirty to ensure that update_section_map is called to prevent stale data being referenced. For the matter at hand this marking is being done via a call to objfiles_changed. Before commit 3e29f34 objfiles_changed could be called after all of the objfile pointers were processed in reread_symbols since section data references via the program-space data pointer would not occur in the calls of read_symbols performed by reread_symbols. With commit 3e29f34 MIPS target specific calls to find_pc_section were added to the code for DWARF information processing, which is called via read_symbols. Thus in reread_symbols the call to objfiles_changed needs to be called before calling read_symbols, otherwise stale section data can be referenced. Thanks to Luis Machado for providing text for the main comment associated with the change. gdb/ 2017-06-28 Doug Gilmore PR gdb/21337 * symfile.c (reread_symbols): Call objfiles_changed just before read_symbols. gdb/testsuite/ 2017-06-28 Doug Gilmore PR gdb/21337 * gdb.base/reread-readsym.exp: New file. * gdb.base/reread-readsym.c: New file. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21542-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 28 16:05:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78563 invoked by alias); 28 Jun 2017 16:05:47 -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 78490 invoked by uid 48); 28 Jun 2017 16:05:47 -0000 From: "joel.sherrill at oarcorp dot com" To: gdb-prs@sourceware.org Subject: [Bug guile/21104] 7.12.1 does not compile with latest guile (2.1.6) Date: Wed, 28 Jun 2017 16:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: guile X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: joel.sherrill at oarcorp dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00343.txt.bz2 Content-length: 412 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21104 Joel Sherrill changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joel.sherrill at oarcorp d= ot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21543-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 28 16:11:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 101223 invoked by alias); 28 Jun 2017 16:11: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 101173 invoked by uid 48); 28 Jun 2017 16:11:22 -0000 From: "joel.sherrill at oarcorp dot com" To: gdb-prs@sourceware.org Subject: [Bug guile/21104] 7.12.1 does not compile with latest guile (2.1.6) Date: Wed, 28 Jun 2017 16:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: guile X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: joel.sherrill at oarcorp dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00344.txt.bz2 Content-length: 467 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21104 --- Comment #4 from Joel Sherrill --- An ArchLinux user reported this via RTEMS so I wanted to ask some questions. Is this a problem with gdb 8? Is there a way to detect the newer guile via autoconf and automatically dis= able it? And the basic question of... What is guile even used for? :) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21544-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 28 16:19:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 62725 invoked by alias); 28 Jun 2017 16:19:10 -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 62044 invoked by uid 48); 28 Jun 2017 16:19:09 -0000 From: "freddie_chopin at op dot pl" To: gdb-prs@sourceware.org Subject: [Bug guile/21104] 7.12.1 does not compile with latest guile (2.1.6) Date: Wed, 28 Jun 2017 16:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: guile X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: freddie_chopin at op dot pl X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00345.txt.bz2 Content-length: 550 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21104 --- Comment #5 from Freddie Chopin --- > Is this a problem with gdb 8? Most likely yes, as in ArchLinux GDB 8.0 is build with older version of gui= le (2.0). > And the basic question of... What is guile even used for? :) >>From my understanding guile is used for the very same thing as python - yo= u can write guile (scheme) scripts in it and GDB will be able to understand them. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21545-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 28 16:24:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88967 invoked by alias); 28 Jun 2017 16:24:02 -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 88915 invoked by uid 48); 28 Jun 2017 16:24:01 -0000 From: "joel.sherrill at oarcorp dot com" To: gdb-prs@sourceware.org Subject: [Bug guile/21104] 7.12.1 does not compile with latest guile (2.1.6) Date: Wed, 28 Jun 2017 16:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: guile X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: joel.sherrill at oarcorp dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00346.txt.bz2 Content-length: 1050 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21104 --- Comment #6 from Joel Sherrill --- (In reply to Freddie Chopin from comment #5) > > Is this a problem with gdb 8? >=20 > Most likely yes, as in ArchLinux GDB 8.0 is build with older version of > guile (2.0). Hmm... RTEMS has something we call the RTEMS Source Builder which is logica= lly comparable to BSD ports. The user uses it to automate fetching all the sour= ce, applying patches, and building tools. That gives us two options: + add building a known guile as part of building gdb + disable guile. > > And the basic question of... What is guile even used for? :) >=20 > From my understanding guile is used for the very same thing as python - y= ou > can write guile (scheme) scripts in it and GDB will be able to understand > them. Thanks. I don't want to get into an Internet war over guile vs Python but personall= y I would lean to disabling guile for RTEMS. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21546-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 28 19:17:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 21902 invoked by alias); 28 Jun 2017 19:17:19 -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 21866 invoked by uid 48); 28 Jun 2017 19:17:18 -0000 From: "mmalcomson.public at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21688] New: `python` command ignores argument when invoked inside `if` clause Date: Wed, 28 Jun 2017 19:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: mmalcomson.public at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00347.txt.bz2 Content-length: 1059 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21688 Bug ID: 21688 Summary: `python` command ignores argument when invoked inside `if` clause Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: minor Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: mmalcomson.public at gmail dot com Target Milestone: --- For version 7.12 the following would print 'Hello' ``` (gdb) if 1 > python print('Hello') > end (gdb) ``` Now, with version 8.0 I get ``` (gdb) if 1 > python print('Hello') > end > ``` If I exit both nested structures ... ``` (gdb) if 1 > python print('Hello') > end > end ``` I get no output. The following works as expected: ``` (gdb) python print('Hello') Hello (gdb) ``` It appears that the argument to the `python` function is getting ignored, b= ut only when in an `if` clause. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21547-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 28 19:52:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 54448 invoked by alias); 28 Jun 2017 19:52:21 -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 54423 invoked by uid 48); 28 Jun 2017 19:52:21 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug server/21658] gdbserver invalid use of sigprocmask() (fails to start on musl) Date: Wed, 28 Jun 2017 19:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: std-posix X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q2/txt/msg00348.txt.bz2 Content-length: 961 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21658 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Sergio Durigan Junior --- Well, apparently this is not a bug on GDB. I didn't know this topic had be= en covered before, but the thread is here: https://sourceware.org/ml/gdb-patches/2017-03/msg00426.html Which, according to Pedro, lead to: http://austingroupbugs.net/view.php?id=3D1132 So, given this outcome, I'm closing this bug as INVALID (since we don't hav= e a NOTABUG marker). Feel free to post updates to this issue here if you want, though. Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21548-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 28 20:26:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 45874 invoked by alias); 28 Jun 2017 20:26:27 -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 45845 invoked by uid 48); 28 Jun 2017 20:26:26 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21688] `python` command ignores argument when invoked inside `if` clause Date: Wed, 28 Jun 2017 20:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q2/txt/msg00349.txt.bz2 Content-length: 509 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21688 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #1 from Sergio Durigan Junior --- I'm taking a look at this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21549-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 28 20:55:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 98005 invoked by alias); 28 Jun 2017 20:55:01 -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 94992 invoked by uid 48); 28 Jun 2017 20:54:58 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21688] `python` command ignores argument when invoked inside `if` clause Date: Wed, 28 Jun 2017 20:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00350.txt.bz2 Content-length: 1433 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21688 --- Comment #2 from Sergio Durigan Junior --- 604c4576fdcfc4e7c28f569b3748a1b6b4e0dbd4 is the first bad commit commit 604c4576fdcfc4e7c28f569b3748a1b6b4e0dbd4 Author: Jerome Guitton Date: Tue Jan 10 15:15:53 2017 +0100 Command abbreviation in define When defining a new macro, "command" is not recognized as an alias for "commands": (gdb) define breakmain Type commands for definition of "breakmain". End with a line saying just "end". >break main >command >echo "IN MAIN\n" >end (gdb) There is a special case for while-stepping, where 'ws' and 'stepping' a= re recognized explicitely. Instead of adding more special cases, this chan= ge uses cli-decode. gdb/ChangeLog: * cli/cli-decode.c (find_command_name_length): Make it extern. * cli/cli-decode.h (find_command_name_length): Declare. * cli/cli-script.c (command_name_equals, line_first_arg): New functions. (process_next_line): Use cli-decode to parse command names. (build_command_line): Make args a constant pointer. gdb/testsuite/ChangeLog: * gdb.base/define.exp: Add test for command abbreviations in define. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21550-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 28 21:17:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 119076 invoked by alias); 28 Jun 2017 21:17:17 -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 119055 invoked by uid 48); 28 Jun 2017 21:17:16 -0000 From: "hi-angel at yandex dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/21689] New: artifacts in prompt rendering when using colors Date: Wed, 28 Jun 2017 21:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hi-angel at yandex dot ru X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00351.txt.bz2 Content-length: 897 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21689 Bug ID: 21689 Summary: artifacts in prompt rendering when using colors Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: hi-angel at yandex dot ru Target Milestone: --- Steps to reproduce: 1. Start "gdb -nh" 2. Type "set prompt \033[31mgdb =CE=BB \033[0m", press enter. 3. Press Ctrl+R, type "hello" 4. Press Result: you'll see the word "hello" at the prompt, even though there's actu= ally nothing. FTR: found by using this gdbinit https://github.com/gdbinit/Gdbinit/blob/master/gdbinit which is very popula= r. Surprising that nobody reported. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21551-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 28 21:26:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3059 invoked by alias); 28 Jun 2017 21:26:36 -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 3021 invoked by uid 48); 28 Jun 2017 21:26:34 -0000 From: "hi-angel at yandex dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/21690] New: Cannot interrupt failing command-history search Date: Wed, 28 Jun 2017 21:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hi-angel at yandex dot ru X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00352.txt.bz2 Content-length: 731 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21690 Bug ID: 21690 Summary: Cannot interrupt failing command-history search Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: hi-angel at yandex dot ru Target Milestone: --- Steps: 1. Run "gdb -nh" 2. Press Ctrl+r, and type e.g. "f" (you should see a failing search) 3. Press Ctrl+c (you'll see it's interrupted) 4. Type e.g. "b" Result: it resumes the failing search, and appends "b" there. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21552-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 28 22:30:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 15700 invoked by alias); 28 Jun 2017 22:30:55 -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 15525 invoked by uid 48); 28 Jun 2017 22:30:46 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21688] `python` command ignores argument when invoked inside `if` clause Date: Wed, 28 Jun 2017 22:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q2/txt/msg00353.txt.bz2 Content-length: 310 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21688 --- Comment #3 from Sergio Durigan Junior --- I have a patch to fix the issue. I'm writing the testcase now, and will su= bmit eveything soon. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21553-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 29 01:16:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 90281 invoked by alias); 29 Jun 2017 01:16:02 -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 90241 invoked by uid 48); 29 Jun 2017 01:16:01 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/21688] `python` command ignores argument when invoked inside `if` clause Date: Thu, 29 Jun 2017 01:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on component assigned_to everconfirmed 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: 2017-q2/txt/msg00354.txt.bz2 Content-length: 762 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21688 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-06-29 Component|python |cli Assignee|unassigned at sourceware dot org |sergiodj at redhat = dot com Ever confirmed|0 |1 --- Comment #4 from Sergio Durigan Junior --- Moving to cli component and assigning to myself. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21554-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 29 02:06:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 30161 invoked by alias); 29 Jun 2017 02:06:11 -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 30121 invoked by uid 48); 29 Jun 2017 02:06:09 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/21688] `python` command ignores argument when invoked inside `if` clause Date: Thu, 29 Jun 2017 02:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: 2017-q2/txt/msg00355.txt.bz2 Content-length: 279 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21688 --- Comment #5 from Sergio Durigan Junior --- Patch: https://sourceware.org/ml/gdb-patches/2017-06/msg00778.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21555-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 29 04:10:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 84209 invoked by alias); 29 Jun 2017 04:10:35 -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 84184 invoked by uid 48); 29 Jun 2017 04:10:34 -0000 From: "orivej at gmx dot fr" To: gdb-prs@sourceware.org Subject: [Bug cli/21688] `python` command ignores argument when invoked inside `if` clause Date: Thu, 29 Jun 2017 04:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: orivej at gmx dot fr X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q2/txt/msg00356.txt.bz2 Content-length: 384 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21688 Orivej Desh changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |orivej at gmx dot fr --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21556-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 29 14:04:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 80876 invoked by alias); 29 Jun 2017 14:04:03 -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 80606 invoked by uid 48); 29 Jun 2017 14:04:02 -0000 From: "jidanni at jidanni dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21693] New: same length extra question fools unwary users Date: Thu, 29 Jun 2017 14:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jidanni at jidanni dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00357.txt.bz2 Content-length: 1890 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21693 Bug ID: 21693 Summary: same length extra question fools unwary users Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jidanni at jidanni dot org Target Milestone: --- The user thinks "Let me out of here. No I don't want to report anything": ---- ^C /build/gdb-AqwUtn/gdb-8.0/gdb/linux-nat.c:2010: internal-error: wait return= ed unexpected status 0x0 A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) q Please answer y or n. /build/gdb-AqwUtn/gdb-8.0/gdb/linux-nat.c:2010: internal-error: wait return= ed unexpected status 0x0 A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y This is a bug, please report it. For instructions, see: . /build/gdb-AqwUtn/gdb-8.0/gdb/linux-nat.c:2010: internal-error: wait return= ed unexpected status 0x0 A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) y ---- The user didn't want to create a core file and use up all they bytes left on his disk. But you slipped an extra same sized question in at the end, which of course the user thinks is just the third y or n to get out. (I mean you already asked him if he wanted to quit, so he didn't expect any further questions, he thought there was something wrong with some keypress again, so unless he looks carefully, he will just hit y again.) Maybe change the last question to "(c or n)". gdb 8.0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21557-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jun 29 17:57:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 129583 invoked by alias); 29 Jun 2017 17:57:55 -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 129557 invoked by uid 48); 29 Jun 2017 17:57:54 -0000 From: "Doug.Gilmore at imgtec dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21337] [mips] segfault when re-reading symbols with remote debugging. Date: Thu, 29 Jun 2017 17:57: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: Doug.Gilmore at imgtec 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q2/txt/msg00358.txt.bz2 Content-length: 566 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21337 Doug Gilmore changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Doug Gilmore --- Bug no longer occurs with ToT gdb (fixed per comment 2). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21558-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 30 11:15:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 100780 invoked by alias); 30 Jun 2017 11:15:47 -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 100564 invoked by uid 55); 30 Jun 2017 11:15:38 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug cli/21688] `python` command ignores argument when invoked inside `if` clause Date: Fri, 30 Jun 2017 11:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: 2017-q2/txt/msg00359.txt.bz2 Content-length: 3105 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21688 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D51ed89aa0dce= 3db46561235efdc4bbc0661bcf37 commit 51ed89aa0dce3db46561235efdc4bbc0661bcf37 Author: Sergio Durigan Junior Date: Wed Jun 28 21:55:03 2017 -0400 PR cli/21688: Fix multi-line/inline command differentiation This bug is a regression caused by the following commit: 604c4576fdcfc4e7c28f569b3748a1b6b4e0dbd4 is the first bad commit commit 604c4576fdcfc4e7c28f569b3748a1b6b4e0dbd4 Author: Jerome Guitton Date: Tue Jan 10 15:15:53 2017 +0100 The problem happens because, on cli/cli-script.c:process_next_line, GDB is not using the command line string to identify which command to run, but it instead using the 'struct cmd_list_element *' that is obtained by using the mentioned string. The problem with that is that the 'struct cmd_list_element *' doesn't have any information on whether the command issued by the user is a multi-line or inline one. A multi-line command is a command that will necessarily be composed of more than 1 line. For example: (gdb) if 1 >python >print ('hello') >end >end As can be seen in the example above, the 'python' command actually "opens" a new command line (represented by the change in the indentation) that will then be used to enter Python code. OTOH, an inline command is a command that is "self-contained" in a single line, for example: (gdb) if 1 >python print ('hello') >end This Python command is a one-liner, and therefore there is no other Python code that can be entered for this same block. There is also no change in the indentation. So, the fix is somewhat simple: we have to revert the change and use the full command line string passed to process_next_line in order to identify whether we're dealing with a multi-line or an inline command. This commit does just that. As can be seen, this regression also affects other languages, like guile or the compile framework. To make things clearer, I decided to create a new helper function responsible for identifying a non-inline command. Testcase is attached. gdb/ChangeLog: 2017-06-30 Sergio Durigan Junior PR cli/21688 * cli/cli-script.c (command_name_equals_not_inline): New function. (process_next_line): Adjust 'if' clauses for "python", "compile" and "guile" to use command_name_equals_not_inline. gdb/testsuite/ChangeLog: 2017-06-30 Sergio Durigan Junior PR cli/21688 * gdb.python/py-cmd.exp (test_python_inline_or_multiline): New procedure. Call it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21559-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 30 12:39:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88481 invoked by alias); 30 Jun 2017 12:39:22 -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 87619 invoked by uid 48); 30 Jun 2017 12:39:21 -0000 From: "thopre01 at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/21695] New: Loss of line info Date: Fri, 30 Jun 2017 12:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thopre01 at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q2/txt/msg00360.txt.bz2 Content-length: 3240 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21695 Bug ID: 21695 Summary: Loss of line info Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: thopre01 at gcc dot gnu.org Target Milestone: --- Hi, Using a trunk gdb built with: ./configure --target=3Darm-none-eabi --disable-nls --disable-sim --disable-= gas --disable-binutils --disable-ld --disable-gprof --with-libexpat --with-lzma= =3Dno --build=3Dx86_64-linux-gnu --host=3Dx86_64-linux-gnu --with-python=3Dno When loading the gdb_test.elf file attached to this ticket (https://bugs.launchpad.net/gcc-arm-embedded/+bug/1700646), the following occurs: $ ../build-gdb/build-gdb-1/gdb/gdb GNU gdb (GDB) 8.0.50.20170614-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=3Dx86_64-linux-gnu --target=3Darm-none-e= abi". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) add-symbol-file gdb_test.elf 0x1fff0000 add symbol table from file "gdb_test.elf" at .text_addr =3D 0x1fff0000 (y or n) y Reading symbols from gdb_test.elf...done. (gdb) info line main No line number information available for address 0x1fff0000
(gdb)=20 When the same elf file is run with gdb 7.8 built with the same configure, o= ne gets: $ build-gdb-7-8/gdb/gdb GNU gdb (GDB) 7.8.2.20150113-cvs Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=3Dx86_64-linux-gnu --target=3Darm-none-e= abi". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) add-symbol-file gdb_test.elf 0x1fff0000 add symbol table from file "gdb_test.elf" at .text_addr =3D 0x1fff0000 (y or n) y Reading symbols from gdb_test.elf...done. (gdb) info line main Line 76 of "main.c" starts at address 0x1fff0000
and ends at 0x1fff0006 . (gdb)=20 So with the same configuration and object file, GDB 7.8 manages to display = line info but not trunk GDB. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21560-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 30 12:40:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 13331 invoked by alias); 30 Jun 2017 12:40:14 -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 12648 invoked by uid 48); 30 Jun 2017 12:40:13 -0000 From: "thopre01 at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/21695] Loss of line info Date: Fri, 30 Jun 2017 12:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thopre01 at gcc dot gnu.org 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: cf_gcctarget 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: 2017-q2/txt/msg00361.txt.bz2 Content-length: 391 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21695 Thomas Preud'homme changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |arm-none-eabi --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21561-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 30 13:51:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 38242 invoked by alias); 30 Jun 2017 13:51:15 -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 38063 invoked by uid 55); 30 Jun 2017 13:51:14 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug cli/21688] `python` command ignores argument when invoked inside `if` clause Date: Fri, 30 Jun 2017 13:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: 2017-q2/txt/msg00362.txt.bz2 Content-length: 2053 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21688 --- Comment #7 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Ddc4bde35d16d= f749e529229657b3468417937cfc commit dc4bde35d16df749e529229657b3468417937cfc Author: Sergio Durigan Junior Date: Fri Jun 30 08:27:29 2017 -0400 PR cli/21688: Detect aliases when issuing python/compile/guile commands (and fix last commit) My last commit fixed a regression that happened when using inline/multi-line commands for Python/Compile/Guile, but introduced another regression: it is now not possible to use aliases for the commands mentioned above. The fix is to almost revert the change I've made and go back to using the 'struct cmd_list_element *', but at the same time make sure that we advance the 'cmd_name' variable past all the whitespace characters after the command name. If, after skipping the whitespace, we encounter a '\0', it means that the command is not inline. Otherwise, it is. This patch also expands the testcase in order to check for aliases and for trailing whitespace after the command name. gdb/ChangeLog: 2017-06-30 Sergio Durigan Junior Pedro Alves PR cli/21688 * cli/cli-script.c (command_name_equals_not_inline): Remove functio= n. (process_next_line): New variable 'inline_cmd'. Adjust 'if' clauses for "python", "compile" and "guile" to use 'command_name_equals' and check for '!inline_cmd'. gdb/testsuite/ChangeLog: 2017-06-30 Sergio Durigan Junior PR cli/21688 * gdb.python/py-cmd.exp (test_python_inline_or_multiline): Add new tests for alias commands and trailing whitespace. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21562-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jun 30 13:51:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66674 invoked by alias); 30 Jun 2017 13:51:54 -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 65070 invoked by uid 48); 30 Jun 2017 13:51:53 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/21688] `python` command ignores argument when invoked inside `if` clause Date: Fri, 30 Jun 2017 13:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q2/txt/msg00363.txt.bz2 Content-length: 526 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21688 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #8 from Sergio Durigan Junior --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21563-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jul 01 10:22:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 46387 invoked by alias); 1 Jul 2017 10:22:53 -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 46355 invoked by uid 48); 1 Jul 2017 10:22:52 -0000 From: "belagod at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug python/21698] New: Stepping from python interface broken? Date: Sat, 01 Jul 2017 10:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: belagod at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00000.txt.bz2 Content-length: 4672 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21698 Bug ID: 21698 Summary: Stepping from python interface broken? Product: gdb Version: 8.0.1 Status: NEW Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: belagod at gcc dot gnu.org Target Milestone: --- I built my trunk and 7.10 gdb configured as: $ configure --disable-nls --disable-sim --disable-gas --disable-binutils --disable-ld --disable-gprof --with-libexpat --with-lzma=3Dno --with-python=3Dyes --prefix=3D/tmp/val/build-gdb/native/7.10/install/ --with-gdb-datadir=3D/tmp/val/build-gdb/native/7.10/install/share/gdb on x86_64 Ubuntu 14.04 I'm trying to debug a program with gdbserver and gdb. For trunk gdb, In one terminal on host: $ gdbserver localhost:3334 ./a.out Process ./a.out created; pid =3D 17642 Listening on port 3334 Another terminal: $ ../build-gdb/native/trunk/install/bin/gdb -x gdb_simple.py ./a.out GNU gdb (GDB) 8.0.50.20170630-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./a.out...done. (gdb) Reading /lib64/ld-linux-x86-64.so.2 from remote target... warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead. Reading /lib64/ld-linux-x86-64.so.2 from remote target... Reading /lib64/ld-2.19.so from remote target... warning: the debug information found in "target:/lib64/ld-2.19.so" does not match "target:/lib64/ld-linux-x86-64.so.2" (CRC mismatch). Reading /lib64/.debug/ld-2.19.so from remote target... 0x00007ffff7ddb2d0 in ?? () from target:/lib64/ld-linux-x86-64.so.2 Step returned: '' 0x00007ffff7ddb2d3 in ?? () from target:/lib64/ld-linux-x86-64.so.2 For gdb 7.10: $ gdbserver localhost:3334 ./a.out Process ./a.out created; pid =3D 17642 Listening on port 3334 $ ../build-gdb/native/7.10/install/bin/gdb -x gdb_simple.py ./a.out GNU gdb (GDB) 7.10.1.20160210-cvs Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./a.out...done. (gdb) Reading /lib64/ld-linux-x86-64.so.2 from remote target... warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead. Reading /lib64/ld-linux-x86-64.so.2 from remote target... Reading /lib64/ld-2.19.so from remote target... warning: the debug information found in "target:/lib64/ld-2.19.so" does not match "target:/lib64/ld-linux-x86-64.so.2" (CRC mismatch). Reading /lib64/.debug/ld-2.19.so from remote target... 0x00007ffff7ddb2d0 in ?? () from target:/lib64/ld-linux-x86-64.so.2 Step returned: '0x00007ffff7ddb2d3 in ?? () from target:/lib64/ld-linux-x86-64.so.2 ' Step returned: '0x00007ffff7ddea40 in ?? () from target:/lib64/ld-linux-x86-64.so.2 ' Step returned: '0x00007ffff7ddea41 in ?? () from target:/lib64/ld-linux-x86-64.so.2 ' Step returned: '0x00007ffff7ddea44 in ?? () from target:/lib64/ld-linux-x86-64.so.2 ' Step returned: '0x00007ffff7ddea46 in ?? () from target:/lib64/ld-linux-x86-64.so.2 ' Stepping successful Where gdb_simple.py is https://bugs.launchpad.net/gcc-arm-embedded/+bug/1700595/+attachment/490367= 1/+files/gdb_script_simple.py and a.out is a hello world compiled using 'gcc -g hello.c' --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21564-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jul 01 10:23:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 47267 invoked by alias); 1 Jul 2017 10:23:51 -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 47241 invoked by uid 48); 1 Jul 2017 10:23:50 -0000 From: "belagod at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug python/21698] Stepping from python interface broken? Date: Sat, 01 Jul 2017 10:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: belagod at gcc dot gnu.org 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: cf_gcchost cf_gccbuild 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: 2017-q3/txt/msg00001.txt.bz2 Content-length: 446 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21698 Tejas Belagod changed: What |Removed |Added ---------------------------------------------------------------------------- Host| |x86_64-linux Build| |x86_64-linux --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21565-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jul 02 10:53:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 100263 invoked by alias); 2 Jul 2017 10:53:29 -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 100231 invoked by uid 48); 2 Jul 2017 10:53:28 -0000 From: "mmalcomson.public at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21699] New: printf "%s", $_as_string(...) can include characters from the child Date: Sun, 02 Jul 2017 10:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: mmalcomson.public at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q3/txt/msg00002.txt.bz2 Content-length: 1620 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21699 Bug ID: 21699 Summary: printf "%s", $_as_string(...) can include characters from the child Product: gdb Version: HEAD Status: UNCONFIRMED Severity: minor Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: mmalcomson.public at gmail dot com Target Milestone: --- Created attachment 10235 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10235&action=3Ded= it Test program When calling `printf`, the value gets put into the child process and printed from there. Python strings coerced to gdb values are not NULL terminated. Combined, this means that calling the `printf` command with a python string results in printing a string that isn't NULL terminated in the inferior. This can hence result in extra junk in the output. e.g. a session running on the attached program ~ [11:48:23] % share/repos/gdb-source/build/gdb/gdb -q --data-directory=3D"/usr/share/gdb" test Reading symbols from test...done. (gdb) start Temporary breakpoint 1 at 0x4004c8: file test.c, line 17. Starting program: /home/matthew/test=20 Temporary breakpoint 1, main () at test.c:17 17 return 0; (gdb) printf "%s\n", $_as_string("hello") "hello"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx (gdb) quit A debugging session is active. Inferior 1 [process 13368] will be killed. Quit anyway? (y or n) y ~ [11:49:07] % --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21566-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jul 02 12:46:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 7475 invoked by alias); 2 Jul 2017 12:45:59 -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 7296 invoked by uid 48); 2 Jul 2017 12:45:54 -0000 From: "schwab@linux-m68k.org" To: gdb-prs@sourceware.org Subject: [Bug python/21699] printf "%s", $_as_string(...) can include characters from the child Date: Sun, 02 Jul 2017 12:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: schwab@linux-m68k.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00003.txt.bz2 Content-length: 220 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21699 --- Comment #1 from Andreas Schwab --- Don't do that then? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21567-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jul 02 13:25:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 85918 invoked by alias); 2 Jul 2017 13:25:10 -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 85805 invoked by uid 48); 2 Jul 2017 13:25:08 -0000 From: "mmalcomson.public at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21699] printf "%s", $_as_string(...) can include characters from the child Date: Sun, 02 Jul 2017 13:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: mmalcomson.public at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00004.txt.bz2 Content-length: 492 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21699 --- Comment #2 from Matthew Malcomson = --- I don't, I work around it in a few user commands I define. I still thought it counted as a bug and that people might like to know. I did hope the Python string coercion might be changed to include a NULL terminator, but if you don't feel like doing it that's fair enough. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21568-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 04 14:18:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49439 invoked by alias); 4 Jul 2017 14:18:56 -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 49399 invoked by uid 48); 4 Jul 2017 14:18:55 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug sim/20863] gdb-7.12 powerpc-rtems4.12-gdb does not build on FreeBSD. Date: Tue, 04 Jul 2017 14:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jhb at FreeBSD dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jhb at FreeBSD dot org X-Bugzilla-Target-Milestone: 8.0.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to target_milestone everconfirmed 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: 2017-q3/txt/msg00005.txt.bz2 Content-length: 1100 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20863 jhb at FreeBSD dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-07-04 CC| |jhb at FreeBSD dot org Assignee|unassigned at sourceware dot org |jhb at FreeBSD dot = org Target Milestone|--- |8.0.1 Ever confirmed|0 |1 --- Comment #1 from jhb at FreeBSD dot org --- This is a regression in 7.12 and later (including 8.0). It results in build failures on both FreeBSD and OS X. It probably results in runtime failures= on Linux as the powerpc simulator code is invoking the 'error' function from g= libc with a different prototype. A patch has been posted to gdb-patches@ since November of 2016 but is await= ing review by an approver. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21569-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 05 17:11:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 111340 invoked by alias); 5 Jul 2017 17:11:36 -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 111226 invoked by uid 48); 5 Jul 2017 17:11:36 -0000 From: "marc-andre.hebert at tmx dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21714] New: static member derived class print loop Date: Wed, 05 Jul 2017 17:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marc-andre.hebert at tmx dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00006.txt.bz2 Content-length: 1966 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21714 Bug ID: 21714 Summary: static member derived class print loop Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: marc-andre.hebert at tmx dot com Target Milestone: --- While trying to debug some of our source code, I stumbled upon a crash.=20 It seems very similar in description to bugs 9167 and 10687 but it is still failing in 8.0 (also confirmed under 7.11.1). When using mi2 gdb does a segfault. With usual command line the print loops. Here is a sample code: class MyClass { public: int mValue; MyClass(int Value=3D0) : mValue(Value) {} static MyClass StaticMember; }; class MyClass2 : public MyClass { public: double mValue; MyClass2(double Value=3D0.0) : mValue(Value) {} static MyClass2 StaticMember2; }; MyClass MyClass::StaticMember(100); MyClass2 MyClass2::StaticMember2(100); int main(int argc, char** charv) { MyClass2 i; return -1; } ------------------------------ (gdb) print i $1 =3D { =3D {mValue =3D 0, static StaticMember =3D {mValue =3D 10= 0, static StaticMember =3D }}, mValue = =3D 0, static StaticMember2 =3D { =3D {mValue =3D 0, static StaticMember = =3D { mValue =3D 100, static StaticMember =3D }}, mValue =3D 100, static StaticMember2 =3D { = =3D {mValue =3D 0, static StaticMember =3D {mValue =3D 100,=20 static StaticMember =3D }}, mValue =3D 100, static StaticMember2 =3D { =3D {mValue = =3D 0, static StaticMember =3D {..... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21570-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 05 20:58:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 71067 invoked by alias); 5 Jul 2017 20:58:12 -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 71011 invoked by uid 48); 5 Jul 2017 20:58:12 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug exp/21717] New: "print $fpscr" says "" until some VFP data register is printed Date: Wed, 05 Jul 2017 20:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00007.txt.bz2 Content-length: 1382 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21717 Bug ID: 21717 Summary: "print $fpscr" says "" until some VFP data register is printed Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: exp Assignee: unassigned at sourceware dot org Reporter: b7.10110111 at gmail dot com Target Milestone: --- To reproduce: 1. Run the following command to start debuggee and stop at entry point: gdb /bin/true -ex 'b *0' -ex r -ex 'd 1' 2. Issue "p $fpscr", see the output "$1 =3D " (the bug) 3. Issue "p $s0", see output "$2 =3D 0" 4. Now you can finally get FPSCR via "p $fpscr", having "$3 =3D 0" as output 5. Step one instruction using "si" command 6. Issue "p $fpscr" to see again Tested on Raspberry Pi 1 Model B under Raspbian GNU/Linux 8. /proc/cpuinfo says: model name : ARMv6-compatible processor rev 7 (v6l) BogoMIPS : 697.95 Features : half thumb fastmult vfp edsp java tls=20 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xb76 CPU revision : 7 Hardware : BCM2835 Revision : 000e Serial : 000000009c40fec4 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21571-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jul 06 17:46:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 43850 invoked by alias); 6 Jul 2017 17:46:49 -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 43823 invoked by uid 48); 6 Jul 2017 17:46:48 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21693] same length extra question fools unwary users Date: Thu, 06 Jul 2017 17:46: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00008.txt.bz2 Content-length: 1225 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21693 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #1 from Sergio Durigan Junior --- I'm not sure about changing the answer expected; "y or n" is a default ques= tion and there's infrastructure for generating it on GDB already. However, I can relate to the complaint that the error message is repeated before the coref= ile question. Maybe something like: =3D=3D /build/gdb-AqwUtn/gdb-8.0/gdb/linux-nat.c:2010: internal-error: wait return= ed unexpected status 0x0 A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y This is a bug, please report it. For instructions, see: . Create a core file of GDB? (y or n) y =3D=3D would be clearer. I'll propose a patch soon to adjust that. Would that wo= rk for you? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21572-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 07 06:23:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 87943 invoked by alias); 7 Jul 2017 06:22:58 -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 62230 invoked by uid 48); 7 Jul 2017 06:22:39 -0000 From: "jidanni at jidanni dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21693] same length extra question fools unwary users Date: Fri, 07 Jul 2017 06:22: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jidanni at jidanni dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00009.txt.bz2 Content-length: 601 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21693 --- Comment #2 from jidanni at jidanni dot org --- (In reply to Sergio Durigan Junior from comment #1) > would be clearer. I'll propose a patch soon to adjust that. Would that > work for you? No because you are asking the same exact two questions. When you ask if he wants to quit and he says yes, then "keep your promise" and let him quit, no further questions. If you want to ask about making corefiles, do so first, before asking him i= f he wants to quit. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21573-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 07 21:19:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64704 invoked by alias); 7 Jul 2017 21:19:34 -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 64655 invoked by uid 48); 7 Jul 2017 21:19:32 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21693] same length extra question fools unwary users Date: Fri, 07 Jul 2017 21:19: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00010.txt.bz2 Content-length: 885 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21693 --- Comment #3 from Sergio Durigan Junior --- (In reply to jidanni from comment #2) > (In reply to Sergio Durigan Junior from comment #1) > > would be clearer. I'll propose a patch soon to adjust that. Would that > > work for you? > No because you are asking the same exact two questions. No, it is not. > When you ask if he wants to quit and he says yes, then "keep your promise" > and let him quit, no further questions. >=20 > If you want to ask about making corefiles, do so first, before asking him= if > he wants to quit. Well, it is possible to generate a corefile and not quit, so I think it mak= es sense to ask the user if she wants a corefile before asking if she wants to quit the debugging sessions. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21574-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jul 08 06:46:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 17061 invoked by alias); 8 Jul 2017 06:46:57 -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 16875 invoked by uid 48); 8 Jul 2017 06:46:33 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21737] New: TUI becomes garbled when GDB is not waiting for input but receives a newline while cursor is at the bottom Date: Sat, 08 Jul 2017 06:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00011.txt.bz2 Content-length: 1310 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21737 Bug ID: 21737 Summary: TUI becomes garbled when GDB is not waiting for input but receives a newline while cursor is at the bottom Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: b7.10110111 at gmail dot com Target Milestone: --- To reproduce: 1. Launch GDB as: gdb -tui /bin/sleep -ex 'layout asm' -ex 'catch syscall nanosleep' -ex 'r 5' -ex 'set pagination off' -ex 'info all-reg' 2. When the inferior stops, type "ni" followed by two or more pres= ses 3. Notice how the console contents moved up as you pressed the sec= ond time 4. Now after 5 seconds, when the inferior stops, the screen is partially updated, leaving no longer valid contents in multiple places: the old (scro= lled up) highlighted current line in the disassembly window, the disassembly (partially correct, partially scrolled), PC value in the bottom-right corne= r of the disassembly window (its updated lowest digits are under the old "status bar"), ... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21575-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jul 08 06:56:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 37777 invoked by alias); 8 Jul 2017 06:56:01 -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 37699 invoked by uid 48); 8 Jul 2017 06:55:53 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21737] TUI becomes garbled when GDB is not waiting for input but receives a newline while cursor is at the bottom Date: Sat, 08 Jul 2017 06:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q3/txt/msg00012.txt.bz2 Content-length: 507 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21737 --- Comment #1 from Ruslan --- Created attachment 10253 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10253&action=3Ded= it How it looks after several "ni" steps because of garbling Here is a screenshot of how the TUI looks after I repeated the "ni" command after the inferior's syscall ended, to exit from __kernel_vsyscall. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21576-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jul 09 22:20:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 48161 invoked by alias); 9 Jul 2017 22:20:06 -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 48123 invoked by uid 48); 9 Jul 2017 22:20:05 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21675] Regression since 8.0 printing has changed format for decimal/octal/others Date: Sun, 09 Jul 2017 22:20: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: 2017-q3/txt/msg00013.txt.bz2 Content-length: 408 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21675 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |tromey at sourcewar= e dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21577-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jul 09 23:13:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 33911 invoked by alias); 9 Jul 2017 23:13:50 -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 33887 invoked by uid 48); 9 Jul 2017 23:13:50 -0000 From: "krkhan at inspirated dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21623] add-symbol-file not loading symbols at the provided .text offset Date: Sun, 09 Jul 2017 23:13: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: krkhan at inspirated dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00014.txt.bz2 Content-length: 281 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21623 --- Comment #1 from Kamran Khan --- Ping.. This can be repro-ed reliably using gdb-8 and any 4.10 series kernel. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21578-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 10 21:43:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 129483 invoked by alias); 10 Jul 2017 21:43:15 -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 128674 invoked by uid 48); 10 Jul 2017 21:43:15 -0000 From: "maks at fb dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21747] New: gdb disassembly uses wrong range for non-contiguous (partitioned) functions Date: Mon, 10 Jul 2017 21:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: maks at fb dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q3/txt/msg00015.txt.bz2 Content-length: 2345 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21747 Bug ID: 21747 Summary: gdb disassembly uses wrong range for non-contiguous (partitioned) functions Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: maks at fb dot com Target Milestone: --- Created attachment 10254 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10254&action=3Ded= it .s with partitioned function "foo" When disassembling a function with non-contiguous address range, e.g. partitioned into fragments after PGO, gdb appears to use an address range of [min(low1, low2), max(high1, high2)) instead of using 2 address ranges [low= 1, high1), [low2, high2) indicated in DWARF. The attached .s test case was compiled with PGO on x86-64 using GCC 4.9. $ gcc -o code-split code-split.s $ gdb code-split ... (gdb) disassemble foo Dump of assembler code for function foo: 0x0000000000400440 <+0>: mov $0x400616,%edi 0x0000000000400445 <+5>: callq 0x400410 0x000000000040044a <+10>: mov $0x2a,%eax 0x000000000040044f <+15>: jmpq 0x400489 0x0000000000400454 <+20>: nopw %cs:0x0(%rax,%rax,1) 0x000000000040045e <+30>: xchg %ax,%ax 0x0000000000400460 <+0>: push %rax 0x0000000000400461 <+1>: callq 0x400470 0x0000000000400466 <+6>: xor %eax,%eax 0x0000000000400468 <+8>: pop %rdx 0x0000000000400469 <+9>: retq 0x000000000040046a: nopw 0x0(%rax,%rax,1) 0x0000000000400470 <+0>: sub $0x1,%edi 0x0000000000400473 <+3>: push %rcx 0x0000000000400474 <+4>: jg 0x400440 0x000000000040047a <+10>: mov $0x400610,%edi 0x000000000040047f <+15>: callq 0x400410 0x0000000000400484 <+20>: mov $0x27,%eax 0x0000000000400489 <+25>: pop %rdx 0x000000000040048a <+26>: retq End of assembler dump. The disassembly includes both fragments of function "foo" and function "mai= n" in-between the two. It becomes ugly when there's more code between fragment= s in the binary. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21579-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 11 02:34:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 6827 invoked by alias); 11 Jul 2017 02:34:08 -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 6538 invoked by uid 48); 11 Jul 2017 02:34:08 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21675] Regression since 8.0 printing has changed format for decimal/octal/others Date: Tue, 11 Jul 2017 02:34: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed 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: 2017-q3/txt/msg00016.txt.bz2 Content-length: 932 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21675 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-07-11 Ever confirmed|0 |1 --- Comment #2 from Tom Tromey --- (In reply to Jonah Graham from comment #1) > Here is another example, demonstrating the problem is not just octal > printing: > $ gdb.8.0 -q -ex 'print/d 1.5' -ex quit > $1 =3D 1 > $ gdb.8.0 -q -ex 'print/u 1.5' -ex quit > $1 =3D 1 These still seem weird to me but I think we agreed to try to preserve this in: https://sourceware.org/ml/gdb-patches/2017-06/msg00314.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21580-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 11 10:57:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 93585 invoked by alias); 11 Jul 2017 10:57:42 -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 93361 invoked by uid 48); 11 Jul 2017 10:57:41 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21555] "error re-setting breakpoint" on PIE executables Date: Tue, 11 Jul 2017 10:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed 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: 2017-q3/txt/msg00017.txt.bz2 Content-length: 704 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21555 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-07-11 CC| |qiyao at gcc dot gnu.org Assignee|unassigned at sourceware dot org |qiyao at gcc dot gn= u.org Ever confirmed|0 |1 --- Comment #1 from Yao Qi --- Mine. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21581-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 11 12:25:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 73685 invoked by alias); 11 Jul 2017 12:25:48 -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 73652 invoked by uid 48); 11 Jul 2017 12:25:47 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21675] Regression since 8.0 printing has changed format for decimal/octal/others Date: Tue, 11 Jul 2017 12:25: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q3/txt/msg00018.txt.bz2 Content-length: 485 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21675 --- Comment #3 from Tom Tromey --- (In reply to Jonah Graham from comment #0) > For example on current HEAD: > $ gdb/gdb -q -ex 'print/o -5' -ex quit > $1 =3D 037773777773 This bug is that one of the constants in print_octals_chars is wrong. I guess it's been wrong for years and years and nobody noticed before... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21582-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 11 12:56:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 120082 invoked by alias); 11 Jul 2017 12:56:42 -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 115042 invoked by uid 48); 11 Jul 2017 12:56:39 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21675] Regression since 8.0 printing has changed format for decimal/octal/others Date: Tue, 11 Jul 2017 12:56: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q3/txt/msg00019.txt.bz2 Content-length: 701 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21675 --- Comment #4 from Pedro Alves --- (In reply to Tom Tromey from comment #2) > (In reply to Jonah Graham from comment #1) > > Here is another example, demonstrating the problem is not just octal > > printing: >=20 > > $ gdb.8.0 -q -ex 'print/d 1.5' -ex quit > > $1 =3D 1 >=20 > > $ gdb.8.0 -q -ex 'print/u 1.5' -ex quit > > $1 =3D 1 >=20 > These still seem weird to me=20 OOC, how would you see them ideally be printed? > but I think we agreed to try to preserve this in: > https://sourceware.org/ml/gdb-patches/2017-06/msg00314.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21583-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 11 15:35:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127022 invoked by alias); 11 Jul 2017 15:35:37 -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 126275 invoked by uid 48); 11 Jul 2017 15:35:36 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21675] Regression since 8.0 printing has changed format for decimal/octal/others Date: Tue, 11 Jul 2017 15:35: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q3/txt/msg00020.txt.bz2 Content-length: 511 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21675 --- Comment #5 from Tom Tromey --- (In reply to Pedro Alves from comment #4) > > https://sourceware.org/ml/gdb-patches/2017-06/msg00314.html For floating point types, I think /d and /u should work just like not having a flag; /o should probably just be an error or ignored, and /x should print in hex float. I'm not sure what /t should do. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21584-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 11 19:58:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88251 invoked by alias); 11 Jul 2017 19:58:53 -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 88012 invoked by uid 48); 11 Jul 2017 19:58:52 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21675] Regression since 8.0 printing has changed format for decimal/octal/others Date: Tue, 11 Jul 2017 19:58: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q3/txt/msg00021.txt.bz2 Content-length: 343 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21675 --- Comment #6 from Pedro Alves --- Given structs with mixed types, it seems to me that erroring wouldn't be desirable. E.g.: struct { int i; float f; } var; (gdb) p /o var --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21585-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 12 02:19:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 741 invoked by alias); 12 Jul 2017 02:19:34 -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 414 invoked by uid 48); 12 Jul 2017 02:19:33 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21675] Regression since 8.0 printing has changed format for decimal/octal/others Date: Wed, 12 Jul 2017 02:19: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q3/txt/msg00022.txt.bz2 Content-length: 634 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21675 --- Comment #7 from Tom Tromey --- (In reply to Pedro Alves from comment #6) > Given structs with mixed types, it seems to me that erroring wouldn't be > desirable. E.g.: >=20 > struct { int i; float f; } var; > (gdb) p /o var Good point. Maybe /o and /t could be ignored for floating point. My main concern there would be possible confusion (like, "p/t 1.1" could be weird) -- though on the other hand I think the current behavior is already very confusing. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21586-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 12 07:28:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 65880 invoked by alias); 12 Jul 2017 07:28:53 -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 65826 invoked by uid 48); 12 Jul 2017 07:28:51 -0000 From: "adi.raghava3 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21755] New: No "step" event Date: Wed, 12 Jul 2017 07:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adi.raghava3 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00023.txt.bz2 Content-length: 682 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21755 Bug ID: 21755 Summary: No "step" event Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: adi.raghava3 at gmail dot com Target Milestone: --- I am trying to save the value of a register at every execution. I am not sure if record would be the correct fit. I was hoping there is a s= pace to call a hook for every step, or next command. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21587-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 12 07:30:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66971 invoked by alias); 12 Jul 2017 07:30:00 -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 66931 invoked by uid 48); 12 Jul 2017 07:29:59 -0000 From: "adi.raghava3 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21755] No "step" event Date: Wed, 12 Jul 2017 07:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adi.raghava3 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cf_gcctarget cc cf_gcchost version 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: 2017-q3/txt/msg00024.txt.bz2 Content-length: 572 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21755 adi.raghava3 at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |KL46Z (arm cortex m0+) CC| |adi.raghava3 at gmail dot = com Host| |Mac OSX Version|unknown |7.0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21588-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 12 15:28:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127242 invoked by alias); 12 Jul 2017 15:28:19 -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 127140 invoked by uid 48); 12 Jul 2017 15:28:19 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21761] New: Missed step-resume breakpoints when placed over a false conditional breakpoint Date: Wed, 12 Jul 2017 15:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00025.txt.bz2 Content-length: 1209 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21761 Bug ID: 21761 Summary: Missed step-resume breakpoints when placed over a false conditional breakpoint Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: remote Assignee: unassigned at sourceware dot org Reporter: simon.marchi at ericsson dot com Target Milestone: --- A step-resume breakpoint placed at the same address as a conditional breakp= oint whose condition is false (condition evaluated by target) is missed. The re= ason is that GDB doesn't consider the step-resume breakpoint when deciding what = the final condition for this address should be. As a result, we place a breakp= oint whose condition is false. The placed breakpoint should be unconditional, because step-resume breakpoints are always unconditional. I'll attach a test that fails with running with native-gdbserver: $ make check TESTS=3D"*/step-into-function-on-false-break-cond.exp" RUNTESTFLAGS=3D"--target_board=3Dnative-gdbserver" --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21589-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 12 15:29:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 5852 invoked by alias); 12 Jul 2017 15:29:03 -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 5536 invoked by uid 48); 12 Jul 2017 15:29:02 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21761] Missed step-resume breakpoints when placed over a false conditional breakpoint Date: Wed, 12 Jul 2017 15:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: attachments.created 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: 2017-q3/txt/msg00026.txt.bz2 Content-length: 330 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21761 --- Comment #1 from Simon Marchi --- Created attachment 10255 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10255&action=3Ded= it Test file (exp) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21590-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 12 15:29:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 12403 invoked by alias); 12 Jul 2017 15:29:20 -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 12380 invoked by uid 48); 12 Jul 2017 15:29:19 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21761] Missed step-resume breakpoints when placed over a false conditional breakpoint Date: Wed, 12 Jul 2017 15:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: attachments.created 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: 2017-q3/txt/msg00027.txt.bz2 Content-length: 328 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21761 --- Comment #2 from Simon Marchi --- Created attachment 10256 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10256&action=3Ded= it Test file (c) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21591-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 12 20:09:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 82406 invoked by alias); 12 Jul 2017 20:09:02 -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 81908 invoked by uid 48); 12 Jul 2017 20:09:01 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21763] New: gdb.lookup_type fails for rust Date: Wed, 12 Jul 2017 20:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00028.txt.bz2 Content-length: 963 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21763 Bug ID: 21763 Summary: gdb.lookup_type fails for rust Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- The Python API gdb.lookup_type fails for Rust. >>From jrmuizel: struct Foo { g: u32, h: u32 } fn main() { let f =3D Foo{ g: 8, h: 9 }; println!("Hello, world!"); } gives: (gdb) python print(gdb.lookup_type(str(gdb.parse_and_eval("f").type))) Traceback (most recent call last): File "", line 1, in gdb.error: No type named tmp::Foo. Error while executing Python code. (gdb) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21592-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 12 20:10:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 39791 invoked by alias); 12 Jul 2017 20:10:26 -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 39495 invoked by uid 48); 12 Jul 2017 20:10:26 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21764] New: sizeof(type) does not work in rust Date: Wed, 12 Jul 2017 20:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00029.txt.bz2 Content-length: 702 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21764 Bug ID: 21764 Summary: sizeof(type) does not work in rust Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- See the test case in https://sourceware.org/bugzilla/show_bug.cgi?id=3D21763 Printing the size of q::Foo does not work: (gdb) p sizeof(q::Foo) ?error in operator_length_standard It works ok for i32, though. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21593-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 12 21:16:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 84187 invoked by alias); 12 Jul 2017 21:16:02 -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 83963 invoked by uid 48); 12 Jul 2017 21:15:39 -0000 From: "jrmuizel at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21763] gdb.lookup_type fails for rust Date: Wed, 12 Jul 2017 21:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jrmuizel at gmail dot com 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: cc 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: 2017-q3/txt/msg00030.txt.bz2 Content-length: 397 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21763 Jeff Muizelaar changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrmuizel at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21594-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 12 21:16:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 84227 invoked by alias); 12 Jul 2017 21:16:03 -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 84012 invoked by uid 48); 12 Jul 2017 21:15:47 -0000 From: "jrmuizel at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21764] sizeof(type) does not work in rust Date: Wed, 12 Jul 2017 21:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jrmuizel at gmail dot com 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: cc 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: 2017-q3/txt/msg00031.txt.bz2 Content-length: 397 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21764 Jeff Muizelaar changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrmuizel at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21595-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 12 22:59:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 91022 invoked by alias); 12 Jul 2017 22:59:25 -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 90990 invoked by uid 48); 12 Jul 2017 22:59:24 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21763] gdb.lookup_type fails for rust Date: Wed, 12 Jul 2017 22:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q3/txt/msg00032.txt.bz2 Content-length: 865 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21763 --- Comment #1 from Tom Tromey --- The issue seems to be that lookup_typename looks in VAR_DOMAIN, but the symbol in question is in STRUCT_DOMAIN. Two possible fixes come to mind. One is to attempt to put all Rust types into VAR_DOMAIN. This arguably even makes sense because VAR_DOMAIN is defined as holding typedefs (which seems weird -- having a real "types" domain might be preferable, but much harder). This change could probably be done just in dwarf2read.c, though patching rust_lookup_type would be good to do as well. It's unclear what other issues this might introduce. The second possible fix is to have typy_lookup_typename also search STRUCT_DOMAIN if the VAR_DOMAIN search fails. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21596-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 12 23:01:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 92908 invoked by alias); 12 Jul 2017 23:01:22 -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 92879 invoked by uid 48); 12 Jul 2017 23:01:22 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug python/21765] New: gdb.SYMBOL_TYPES_DOMAIN leads to wrong behavior Date: Wed, 12 Jul 2017 23:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00033.txt.bz2 Content-length: 963 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21765 Bug ID: 21765 Summary: gdb.SYMBOL_TYPES_DOMAIN leads to wrong behavior Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- Python defines this: || PyModule_AddIntConstant (gdb_module, "SYMBOL_TYPES_DOMAIN", TYPES_DOMAIN) < 0) ... however if this is actually passed to gdb.lookup_symbol (as seemingly recommended in the docs), the result will not do what the user might expect, as TYPES_DOMAIN isn't a constant in domain_enum, but rather in search_domain. This applies to SYMBOL_VARIABLES_DOMAIN and SYMBOL_FUNCTIONS_DOMAIN as well. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21597-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jul 13 02:27:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 126155 invoked by alias); 13 Jul 2017 02:26:59 -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 126106 invoked by uid 48); 13 Jul 2017 02:26:57 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21763] gdb.lookup_type fails for rust Date: Thu, 13 Jul 2017 02:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q3/txt/msg00034.txt.bz2 Content-length: 320 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21763 --- Comment #2 from Tom Tromey --- Actually the simplest is just adding to the special case in symbol_matches_domain. I sort of hate to do this but... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21598-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jul 13 12:13:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31274 invoked by alias); 13 Jul 2017 12:13:10 -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 31116 invoked by uid 48); 13 Jul 2017 12:13:10 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21769] New: crash in maint selftest Date: Thu, 13 Jul 2017 12:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00035.txt.bz2 Content-length: 3533 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21769 Bug ID: 21769 Summary: crash in maint selftest Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- I get a crash in main selftest: (gdb) maint selftest During symbol reading, DW_AT_GNU_call_site_target target DIE has invalid low pc, for referencing DIE 0x2648fee [in module /home/tromey/gdb/build/gdb/gdb= ]. During symbol reading, cannot get low and high bounds for subprogram DIE at 40144933. Program received signal SIGSEGV, Segmentation fault. During symbol reading, incomplete CFI data; unspecified registers (e.g., ra= x) at 0x7810f7. During symbol reading, unsupported tag: 'DW_TAG_unspecified_type'. During symbol reading, unexpected tag in read_type_die: 'DW_TAG_rvalue_reference_type'. During symbol reading, No DW_FORM_block* DW_AT_GNU_call_site_value for DW_TAG_GNU_call_site child DIE 0x200f297 [in module /home/tromey/gdb/build/gdb/gdb]. During symbol reading, Child DIE 0x200ec01 and its abstract origin 0x20169af have different parents. htab_remove_elt_with_hash (htab=3Dhtab@entry=3D0x106f210, element=3D, hash=3D) at ../../binutils-gdb/libiberty/hashtab.c:728 (top-gdb) p slot $1 =3D (void **) 0x0 (top-gdb) up #1 0x0000000000781121 in htab_remove_elt (htab=3Dhtab@entry=3D0x106f210, element=3D) at ../../binutils-gdb/libiberty/hashtab.c:714 (top-gdb)=20 During symbol reading, Multiple children of DIE 0x9baae refer to DIE 0x9c1c= 3 as their abstract origin. #2 0x00000000006742b0 in tdesc_use_registers (gdbarch=3Dgdbarch@entry=3D0x= 106d6d0, target_desc=3D0xdb4960, early_data=3Dearly_data@entry=3D0x106c2e0) at ../../binutils-gdb/gdb/target-descriptions.c:1328 (top-gdb)=20 #3 0x000000000042fb8d in i386_gdbarch_init (info=3D..., arches=3D) at ../../binutils-gdb/gdb/i386-tdep.c:8634 (top-gdb)=20 #4 0x00000000005c4071 in gdbarch_find_by_info (info=3D...) at ../../binutils-gdb/gdb/gdbarch.c:5394 (top-gdb) down #3 0x000000000042fb8d in i386_gdbarch_init (info=3D..., arches=3D) at ../../binutils-gdb/gdb/i386-tdep.c:8634 (top-gdb)=20 #2 0x00000000006742b0 in tdesc_use_registers (gdbarch=3Dgdbarch@entry=3D0x= 106d6d0, target_desc=3D0xdb4960, early_data=3Dearly_data@entry=3D0x106c2e0) at ../../binutils-gdb/gdb/target-descriptions.c:1328 This patch seems to fix the problem for me, but since I don't know if there= 's some underlying issue, and due to lack of time, I'm just going to leave it = here rather than try to submit it. diff --git a/gdb/target-descriptions.c b/gdb/target-descriptions.c index 0b5b46f..836e640 100644 --- a/gdb/target-descriptions.c +++ b/gdb/target-descriptions.c @@ -1325,7 +1325,12 @@ tdesc_use_registers (struct gdbarch *gdbarch, VEC_iterate (tdesc_arch_reg, data->arch_regs, ixr, arch_reg); ixr++) if (arch_reg->reg) - htab_remove_elt (reg_hash, arch_reg->reg); + { + void **slot =3D htab_find_slot (reg_hash, arch_reg->reg, NO_INSERT); + + if (slot !=3D NULL) + htab_clear_slot (reg_hash, slot); + } /* Assign numbers to the remaining registers and add them to the list of registers. The new numbers are always above gdbarch_num_regs. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21599-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jul 13 12:41:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127068 invoked by alias); 13 Jul 2017 12:41:08 -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 126243 invoked by uid 48); 13 Jul 2017 12:41:08 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21769] crash in maint selftest Date: Thu, 13 Jul 2017 12:41: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q3/txt/msg00036.txt.bz2 Content-length: 3213 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21769 --- Comment #1 from Tom Tromey --- This seems to affect ordinary startup as well sometimes. (top-gdb) run Starting program: /home/tromey/gdb/build/gdb/gdb -nx ./outputs/gdb.rust/simple/simple ... Program received signal SIGSEGV, Segmentation fault. htab_remove_elt_with_hash ( During symbol reading, incomplete CFI data; unspecified registers (e.g., ra= x) at 0x7810f7. During symbol reading, unsupported tag: 'DW_TAG_unspecified_type'. During symbol reading, unexpected tag in read_type_die: 'DW_TAG_rvalue_reference_type'. During symbol reading, No DW_FORM_block* DW_AT_GNU_call_site_value for DW_TAG_GNU_call_site child DIE 0x200f054 [in module /home/tromey/gdb/build/gdb/gdb]. During symbol reading, Child DIE 0x200e9be and its abstract origin 0x201676c have different parents. htab=3Dhtab@entry=3D0xfa0520, element=3D, hash=3D) at ../../binutils-gdb/libiberty/hashtab.c:728 728 if (*slot =3D=3D HTAB_EMPTY_ENTRY) (top-gdb) bt #0 0x00000000007810d0 in htab_remove_elt_with_hash (htab=3D0xfa0520, element=3D, hash=3D) at ../../binutils-gdb/libiberty/hashtab.c:728 During symbol reading, Multiple children of DIE 0x9baae refer to DIE 0x9c1c= 3 as their abstract origin. #1 0x0000000000781121 in htab_remove_elt (htab=3D0xfa0520, element=3D) at ../../binutils-gdb/libiberty/hashtab.c:714 #2 0x00000000006742b0 in tdesc_use_registers(gdbarch*, target_desc const*, tdesc_arch_data*) (gdbarch=3D0xfb21e0, target_desc=3D0xdc08b0, early_data= =3D0xf4b170) at ../../binutils-gdb/gdb/target-descriptions.c:1328 #3 0x000000000042fb8d in i386_gdbarch_init(gdbarch_info, gdbarch_list*) (info=3D..., arches=3D) at ../../binutils-gdb/gdb/i386-tdep.c:8634 #4 0x00000000005c4071 in gdbarch_find_by_info(gdbarch_info) (info=3D...) at ../../binutils-gdb/gdb/gdbarch.c:5394 #5 0x000000000051c605 in set_gdbarch_from_file(bfd*) ( During symbol reading, Member function "~regcache" (offset 30802782) is vir= tual but the vtable offset is not specified. abfd=3D) at ../../binutils-gdb/gdb/arch-utils.c:618 #6 0x00000000005a80e4 in exec_file_attach(char const*, int) (filename=3D0x7fffffffe6f2 "./outputs/gdb.rust/simple/simple", from_tty=3D1= ) at ../../binutils-gdb/gdb/exec.c:380 #7 0x00000000005f9d98 in catch_command_errors_const(catch_command_errors_const_ftype*, char const*, = int) (command=3D0x5a7f40 , arg=3D0x7fffffffe= 6f2 "./outputs/gdb.rust/simple/simple", from_tty=3D1) at ../../binutils-gdb/gdb/main.c:403 #8 0x00000000005fad5e in captured_main_1 (context=3D0x7fffffffe0f0) at ../../binutils-gdb/gdb/main.c:1035 #9 0x00000000005fad5e in captured_main (data=3D0x7fffffffe0f0) at ../../binutils-gdb/gdb/main.c:1142 #10 0x00000000005fad5e in gdb_main(captured_main_args*) (args=3D0x7fffffffe= 220) at ../../binutils-gdb/gdb/main.c:1160 #11 0x000000000040cb75 in main(int, char**) (argc=3D, argv=3D) at ../../binutils-gdb/gdb/gdb.c:32 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21600-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jul 13 21:05:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94481 invoked by alias); 13 Jul 2017 21:05:22 -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 94439 invoked by uid 48); 13 Jul 2017 21:05:21 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21763] gdb.lookup_type fails for rust Date: Thu, 13 Jul 2017 21:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: 2017-q3/txt/msg00037.txt.bz2 Content-length: 492 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21763 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |tromey at sourcewar= e dot org --- Comment #3 from Tom Tromey --- Testing a patch. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21601-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jul 13 22:26:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 8507 invoked by alias); 13 Jul 2017 22:26:08 -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 8472 invoked by uid 48); 13 Jul 2017 22:26:08 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21764] sizeof(type) does not work in rust Date: Thu, 13 Jul 2017 22:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: 2017-q3/txt/msg00038.txt.bz2 Content-length: 547 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21764 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |tromey at sourcewar= e dot org --- Comment #1 from Tom Tromey --- This is a bug in ast->expr conversion in rust-exp.y. I'm testing a fix. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21602-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 14 14:04:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 57583 invoked by alias); 14 Jul 2017 14:04:00 -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 57525 invoked by uid 48); 14 Jul 2017 14:04:00 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21769] crash in maint selftest Date: Fri, 14 Jul 2017 14:04: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-q3/txt/msg00039.txt.bz2 Content-length: 626 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21769 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |8.1 --- Comment #2 from Tom Tromey --- Fixed here: https://sourceware.org/ml/gdb-patches/2017-07/msg00166.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21603-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 14 16:17:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63723 invoked by alias); 14 Jul 2017 16:17:38 -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 63698 invoked by uid 55); 14 Jul 2017 16:17:38 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug rust/21763] gdb.lookup_type fails for rust Date: Fri, 14 Jul 2017 16:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q3/txt/msg00040.txt.bz2 Content-length: 1176 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21763 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D65547233e04b= 32e087f74f8f5e9d3ffb6fe2c198 commit 65547233e04b32e087f74f8f5e9d3ffb6fe2c198 Author: Tom Tromey Date: Thu Jul 13 15:03:27 2017 -0600 Make gdb.lookup_typename work for Rust types PR rust/21763 points out that gdb.lookup_typename does not work properly for (some) Rust types. I tracked this down to a missing case in symbol_matches_domain. Tested by the buildbot. 2017-07-14 Tom Tromey PR rust/21763: * symtab.c (symbol_matches_domain): Add language_rust to special case. * rust-exp.y (convert_ast_to_expression) : Don't treat LOC_TYPEDEF symbols as variables. 2017-07-14 Tom Tromey * gdb.rust/simple.exp: Add regression test for PR rust/21763. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21604-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 14 16:24:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 91463 invoked by alias); 14 Jul 2017 16:24:03 -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 91358 invoked by uid 48); 14 Jul 2017 16:24:00 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21763] gdb.lookup_type fails for rust Date: Fri, 14 Jul 2017 16:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-q3/txt/msg00041.txt.bz2 Content-length: 570 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21763 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |8.1 --- Comment #5 from Tom Tromey --- Fix checked in. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21605-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 14 18:35:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3731 invoked by alias); 14 Jul 2017 18:35:11 -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 3700 invoked by uid 55); 14 Jul 2017 18:35:10 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug rust/21764] sizeof(type) does not work in rust Date: Fri, 14 Jul 2017 18:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q3/txt/msg00042.txt.bz2 Content-length: 1265 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21764 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D8880f2a9cb51= 51ce1c2714a75d123ba0f63668ac commit 8880f2a9cb5151ce1c2714a75d123ba0f63668ac Author: Tom Tromey Date: Fri Jul 14 08:10:39 2017 -0600 Handle sizeof(type) in Rust PR rust/21764 notes that "sizeof" does not work correctly for all types in Rust. The bug turns out to be an error in the conversion of the AST to gdb expressions. This patch fixes the bug and also avoids generating incorrect expressions in another case. Tested on the buildbot. I'm checking this in. 2017-07-14 Tom Tromey PR rust/21764: * rust-exp.y (convert_ast_to_expression): Add "want_type" parameter. : Split into separate case. : Handle want_type. Add error case. 2017-07-14 Tom Tromey PR rust/21764: * gdb.rust/simple.exp: Add tests. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21606-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 14 18:36:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 5757 invoked by alias); 14 Jul 2017 18:36:26 -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 5731 invoked by uid 48); 14 Jul 2017 18:36:25 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21764] sizeof(type) does not work in rust Date: Fri, 14 Jul 2017 18:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-q3/txt/msg00043.txt.bz2 Content-length: 570 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21764 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |8.1 --- Comment #3 from Tom Tromey --- Fix checked in. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21607-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 14 19:05:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 30744 invoked by alias); 14 Jul 2017 19:05:20 -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 30640 invoked by uid 48); 14 Jul 2017 19:05:19 -0000 From: "jrmuizel at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/17095] print alignof (type or expression) Date: Fri, 14 Jul 2017 19:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jrmuizel at gmail dot com 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: cc 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: 2017-q3/txt/msg00044.txt.bz2 Content-length: 397 https://sourceware.org/bugzilla/show_bug.cgi?id=3D17095 Jeff Muizelaar changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrmuizel at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21608-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jul 15 10:08:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 106022 invoked by alias); 15 Jul 2017 10:08:20 -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 105993 invoked by uid 48); 15 Jul 2017 10:08:20 -0000 From: "dilyan.palauzov at aegee dot org" To: gdb-prs@sourceware.org Subject: =?UTF-8?B?W0J1ZyBidWlsZC8yMTc3M10gTmV3OiBiaW51dGlscy1nZGIvZ2RiL2NvbW1v?= =?UTF-8?B?bi92ZWMuaDoxMDg1OjMxOiBlcnJvcjog4oCYdm9pZCogbWVtY3B5KHZvaWQq?= =?UTF-8?B?LCBjb25zdCB2b2lkKiwgc2l6ZV90KeKAmSBjb3B5aW5nIGFuIG9iamVjdCBv?= =?UTF-8?B?ZiBub24tdHJpdmlhbCB0eXBlIOKAmGJ0cmFjZV9pbnNuX3Mge2FrYSBzdHJ1?= =?UTF-8?B?Y3QgYnRyYWNlX2luc2594oCZIGZyb20gYW4gYXJyYXkgb2Yg4oCYYnRyYWNl?= =?UTF-8?B?X2luc25fcyBbMV0ge2FrYSBzdHJ1Y3QgYnRyYWNlX2luc24gWzFdfeKAmSBb?= =?UTF-8?B?LVdlcnJvcj1jbGFzcy1t?= Date: Sat, 15 Jul 2017 10:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dilyan.palauzov at aegee dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00045.txt.bz2 Content-length: 7171 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21773 Bug ID: 21773 Summary: binutils-gdb/gdb/common/vec.h:1085:31: error: =E2=80=98= void* memcpy(void*, const void*, size_t)=E2=80=99 copying an = object of non-trivial type =E2=80=98btrace_insn_s {aka struct btrace_insn}=E2=80=99 from an array of =E2=80=98btrace_= insn_s [1] {aka struct btrace_insn [1]}=E2=80=99 [-Werror=3Dclass-m Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: dilyan.palauzov at aegee dot org Target Milestone: --- Most current gdb does not compile with most current gcc: make[6]: Leaving directory '/home/d/binutils/gdb/build-gnulib/import' make[5]: Leaving directory '/home/d/binutils/gdb/build-gnulib' make[4]: Leaving directory '/home/d/binutils/gdb/build-gnulib' make[3]: Leaving directory '/home/d/binutils/gdb' g++ -x c++ -g -O2 -I. -I/git/binutils-gdb/gdb -I/git/binutils-gdb/gdb/co= mmon -I/git/binutils-gdb/gdb/config -DLOCALEDIR=3D"\"/usr/local/share/locale\"" -DHAVE_CONFIG_H -I/git/binutils-gdb/gdb/../include/opcode -I/git/binutils-gdb/gdb/../opcodes/.. -I../bfd -I/git/binutils-gdb/gdb/..= /bfd -I/git/binutils-gdb/gdb/../include -I../libdecnumber -I/git/binutils-gdb/gdb/../libdecnumber -I/git/binutils-gdb/gdb/gnulib/imp= ort -Ibuild-gnulib/import -I/usr/local/include/python3.5m -I/usr/local/include/python3.5m -Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-b= ody -Wunused-but-set-parameter -Wunused-but-set-variable -Wno-sign-compare -Wno-narrowing -Wno-error=3Dmaybe-uninitialized -Werror -c -o arc-tdep.o -MT arc-tdep.o -MMD -MP -MF .deps/arc-tdep.Tpo /git/binutils-gdb/gdb/arc-tdep.c In file included from /git/binutils-gdb/gdb/common/gdb_vecs.h:23:0, from /git/binutils-gdb/gdb/symtab.h:24, from /git/binutils-gdb/gdb/language.h:26, from /git/binutils-gdb/gdb/frame.h:72, from /git/binutils-gdb/gdb/gdbarch.h:39, from /git/binutils-gdb/gdb/defs.h:636, from /git/binutils-gdb/gdb/arc-tdep.c:22: /git/binutils-gdb/gdb/btrace.h: In function =E2=80=98VEC_btrace_insn_s* VEC_btrace_insn_s_copy(VEC_btrace_insn_s*)=E2=80=99: /git/binutils-gdb/gdb/common/vec.h:1065:58: error: =E2=80=98void* memcpy(vo= id*, const void*, size_t)=E2=80=99 copying an object of non-trivial type =E2=80=98btra= ce_insn_s {aka struct btrace_insn}=E2=80=99 from an array of =E2=80=98btrace_insn_s [1] {a= ka struct btrace_insn [1]}=E2=80=99 [-Werror=3Dclass-memaccess] memcpy (new_vec_->vec, vec_->vec, sizeof (T) * len_); \ ^ /git/binutils-gdb/gdb/common/vec.h:461:1: note: in expansion of macro =E2=80=98DEF_VEC_ALLOC_FUNC_O=E2=80=99 DEF_VEC_ALLOC_FUNC_O(T) \ ^~~~~~~~~~~~~~~~~~~~ /git/binutils-gdb/gdb/btrace.h:86:1: note: in expansion of macro =E2=80=98D= EF_VEC_O=E2=80=99 DEF_VEC_O (btrace_insn_s); ^~~~~~~~~ In file included from /git/binutils-gdb/gdb/target.h:74:0, from /git/binutils-gdb/gdb/exec.h:23, from /git/binutils-gdb/gdb/gdbcore.h:29, from /git/binutils-gdb/gdb/arc-tdep.c:28: /git/binutils-gdb/gdb/btrace.h:69:8: note: =E2=80=98btrace_insn_s {aka stru= ct btrace_insn}=E2=80=99 declared here struct btrace_insn ^~~~~~~~~~~ In file included from /git/binutils-gdb/gdb/common/gdb_vecs.h:23:0, from /git/binutils-gdb/gdb/symtab.h:24, from /git/binutils-gdb/gdb/language.h:26, from /git/binutils-gdb/gdb/frame.h:72, from /git/binutils-gdb/gdb/gdbarch.h:39, from /git/binutils-gdb/gdb/defs.h:636, from /git/binutils-gdb/gdb/arc-tdep.c:22: /git/binutils-gdb/gdb/btrace.h: In function =E2=80=98VEC_btrace_insn_s* VEC_btrace_insn_s_merge(VEC_btrace_insn_s*, VEC_btrace_insn_s*)=E2=80=99: /git/binutils-gdb/gdb/common/vec.h:1083:65: error: =E2=80=98void* memcpy(vo= id*, const void*, size_t)=E2=80=99 copying an object of non-trivial type =E2=80=98btra= ce_insn_s {aka struct btrace_insn}=E2=80=99 from an array of =E2=80=98btrace_insn_s [1] {a= ka struct btrace_insn [1]}=E2=80=99 [-Werror=3Dclass-memaccess] memcpy (new_vec_->vec, vec1_->vec, sizeof (T) * vec1_->num); \ ^ /git/binutils-gdb/gdb/common/vec.h:461:1: note: in expansion of macro =E2=80=98DEF_VEC_ALLOC_FUNC_O=E2=80=99 DEF_VEC_ALLOC_FUNC_O(T) \ ^~~~~~~~~~~~~~~~~~~~ /git/binutils-gdb/gdb/btrace.h:86:1: note: in expansion of macro =E2=80=98D= EF_VEC_O=E2=80=99 DEF_VEC_O (btrace_insn_s); ^~~~~~~~~ In file included from /git/binutils-gdb/gdb/target.h:74:0, from /git/binutils-gdb/gdb/exec.h:23, from /git/binutils-gdb/gdb/gdbcore.h:29, from /git/binutils-gdb/gdb/arc-tdep.c:28: /git/binutils-gdb/gdb/btrace.h:69:8: note: =E2=80=98btrace_insn_s {aka stru= ct btrace_insn}=E2=80=99 declared here struct btrace_insn ^~~~~~~~~~~ In file included from /git/binutils-gdb/gdb/common/gdb_vecs.h:23:0, from /git/binutils-gdb/gdb/symtab.h:24, from /git/binutils-gdb/gdb/language.h:26, from /git/binutils-gdb/gdb/frame.h:72, from /git/binutils-gdb/gdb/gdbarch.h:39, from /git/binutils-gdb/gdb/defs.h:636, from /git/binutils-gdb/gdb/arc-tdep.c:22: /git/binutils-gdb/gdb/common/vec.h:1085:31: error: =E2=80=98void* memcpy(vo= id*, const void*, size_t)=E2=80=99 copying an object of non-trivial type =E2=80=98btra= ce_insn_s {aka struct btrace_insn}=E2=80=99 from an array of =E2=80=98btrace_insn_s [1] {a= ka struct btrace_insn [1]}=E2=80=99 [-Werror=3Dclass-memaccess] sizeof (T) * vec2_->num); \ ^ /git/binutils-gdb/gdb/common/vec.h:461:1: note: in expansion of macro =E2=80=98DEF_VEC_ALLOC_FUNC_O=E2=80=99 DEF_VEC_ALLOC_FUNC_O(T) \ ^~~~~~~~~~~~~~~~~~~~ /git/binutils-gdb/gdb/btrace.h:86:1: note: in expansion of macro =E2=80=98D= EF_VEC_O=E2=80=99 DEF_VEC_O (btrace_insn_s); ^~~~~~~~~ In file included from /git/binutils-gdb/gdb/target.h:74:0, from /git/binutils-gdb/gdb/exec.h:23, from /git/binutils-gdb/gdb/gdbcore.h:29, from /git/binutils-gdb/gdb/arc-tdep.c:28: /git/binutils-gdb/gdb/btrace.h:69:8: note: =E2=80=98btrace_insn_s {aka stru= ct btrace_insn}=E2=80=99 declared here struct btrace_insn ^~~~~~~~~~~ cc1plus: all warnings being treated as errors make[2]: *** [Makefile:1910: arc-tdep.o] Error 1 make[2]: Leaving directory '/home/d/binutils/gdb' make[1]: *** [Makefile:10439: all-gdb] Error 2 make[1]: Leaving directory '/home/d/binutils' make: *** [Makefile:850: all] Error 2 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21609-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jul 15 13:45:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78247 invoked by alias); 15 Jul 2017 13:45: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 75718 invoked by uid 48); 15 Jul 2017 13:45:47 -0000 From: "zwj_xjtu at 126 dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21774] New: Ubuntu: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed Date: Sat, 15 Jul 2017 13:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: zwj_xjtu at 126 dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: 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: 2017-q3/txt/msg00046.txt.bz2 Content-length: 4376 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21774 Bug ID: 21774 Summary: Ubuntu: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed Product: gdb Version: 7.11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: zwj_xjtu at 126 dot com CC: jhb at FreeBSD dot org, jlott1 at yahoo dot com, palves= at redhat dot com, unassigned at sourceware dot org Target Milestone: --- I use gdb to debug a kernel module, when the code hits the breakpoints, and= =20=20 i type 'c' ,then the same internel-error as follow. +++ This bug was initially created as a clone of Bug #21497 +++ I'm using gdb7121 from FreeBSD ports. Getting this assert occasionally when continuing from a breakpoint: infrun.c:5565: internal-error: int finish_step_over(execution_control_state= *): Assertion `ecs->event_thread->control.trap_expected' failed. I ran with some debugging on to narrow it down (set debug target 1; set deb= ug infrun 1; set debug fbsd-lwp 1). Unfortunately it takes a long time to reproduce so the debug output is fairly large (30MB). Only the end is really relevant, I think. It appears to be an interaction (race condition) between= new threads being launched and the continuing of a thread from a breakpoint. Skipping over a lot of the verbose messages for brevity/clarity, you can see the sequence in the last continue: -> native->to_log_command (...) <- native->to_log_command (0x1d7f300, c) Continuing. ... infrun: resuming [LWP 102181 of process 23510] for step-over ... infrun: skipping breakpoint: stepping past insn at: 0x1df0c07 infrun: skipping breakpoint: stepping past insn at: 0x1df0c07 -> native->to_insert_breakpoint (...) ... <- native->to_insert_breakpoint (0x1d7f300, i386:x86-64, 0x000000080a335d00= ) =3D 0 ... infrun: resume (step=3D1, signal=3DGDB_SIGNAL_0), trap_expected=3D1, curren= t thread [LWP 102181 of process 23510] at 0x1df0c07 ... FLWP: fbsd_resume for ptid (23510, 102181, 0) So far so good, everything is setup to single-step LWP 102181. However, bec= ause it is single stepping, it is expecting to only receive events about that thread. However, there was already a thread-create event pending when the breakpoint occurred. Therefore the next event that gets returned from pthre= ad is actually a create for a different thread. FLWP: adding thread for LWP 101493 ... [New LWP 101493 of process 23510] ... infrun: target_wait (-1.0.0, status) =3D infrun: 23510.101493.0 [LWP 101493 of process 23510], infrun: status->kind =3D spurious ... infrun: TARGET_WAITKIND_SPURIOUS ... infrun: Switching context from LWP 102181 of process 23510=20 ... to LWP 101493 of process 23510 After it processes this new thread, it will now resume all threads. This is= not good, because the "continue" code still thinks it is in single-step mode. infrun: resume (step=3D0, signal=3DGDB_SIGNAL_0), trap_expected=3D0, curren= t thread [LWP 101493 of process 23510] at 0x80add2d20 ... FLWP: fbsd_resume for ptid (-1, 0, 0) Because all threads are now running, another thread hits the temporary breakpoint that was intended for the single-stepping thread. infrun: target_wait (-1.0.0, status) =3D infrun: 23510.101602.0 [LWP 101602 of process 23510], infrun: status->kind =3D stopped, signal =3D GDB_SIGNAL_TRAP ... infrun: TARGET_WAITKIND_STOPPED Now it checks to see that the thread that hit the breakpoint is the correct thread that was single-stepping. It was not, hence the assert. infrun.c:5565: internal-error: int finish_step_over(execution_control_state= *): Assertion `ecs->event_thread->control.trap_expected' failed. I hope this is clear. It seems there is a mismatch between what the "core" = gdb code expects in terms of ptrace event ordering and how the FreeBSD ptrace A= PI actually behaves. I'll attach the (unfiltered) end of the log to the report= as well. I can reproduce locally with our application relatively easily, but I= 've not come up with a standalone test program to cause it yet. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21610-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jul 15 15:45:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20156 invoked by alias); 15 Jul 2017 15:45:51 -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 19940 invoked by uid 48); 15 Jul 2017 15:45:24 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21774] Ubuntu: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed Date: Sat, 15 Jul 2017 15:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jhb at FreeBSD dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00047.txt.bz2 Content-length: 338 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21774 --- Comment #1 from jhb at FreeBSD dot org --- Can you clarify what host OS you are seeing this on? The other bug is FreeBSD-specific and should not affect debugging on Ubuntu or other Linux systems. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21611-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jul 16 02:16:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 7022 invoked by alias); 16 Jul 2017 02:16:22 -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 6691 invoked by uid 48); 16 Jul 2017 02:15:44 -0000 From: "zwj_xjtu at 126 dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21774] Ubuntu: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed Date: Sun, 16 Jul 2017 02:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: zwj_xjtu at 126 dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00048.txt.bz2 Content-length: 421 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21774 --- Comment #2 from spring --- My host os is Ubuntu 16.04.1 LTS. My guest os is the same distribution, but= I clone the source code of the distribution's kernel and recomplie with `-O1` flags, so my guest os is Ubuntu 16.04.1 LTS (GNU/Linux 4.4.13 x86_64). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21612-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 17 21:51:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79904 invoked by alias); 17 Jul 2017 21:51:43 -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 79859 invoked by uid 48); 17 Jul 2017 21:51:42 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21774] Ubuntu: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed Date: Mon, 17 Jul 2017 21:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jhb at FreeBSD dot org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00049.txt.bz2 Content-length: 416 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21774 jhb at FreeBSD dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC|jhb at FreeBSD dot org, | |jlott1 at yahoo dot com | --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21613-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 18 21:10:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 69015 invoked by alias); 18 Jul 2017 21:10:27 -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 68989 invoked by uid 48); 18 Jul 2017 21:10:26 -0000 From: "emaste at freebsd dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21785] New: sysroot option does not apply to standalone debug Date: Tue, 18 Jul 2017 21:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: emaste at freebsd dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00050.txt.bz2 Content-length: 513 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21785 Bug ID: 21785 Summary: sysroot option does not apply to standalone debug Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: emaste at freebsd dot org Target Milestone: --- --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21614-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 18 21:19:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68473 invoked by alias); 18 Jul 2017 21:19:47 -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 68444 invoked by uid 48); 18 Jul 2017 21:19:46 -0000 From: "emaste at freebsd dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21785] sysroot option does not apply to standalone debug Date: Tue, 18 Jul 2017 21:19: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: emaste at freebsd dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00051.txt.bz2 Content-length: 1665 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21785 --- Comment #1 from emaste at freebsd dot org --- Background: debugging a FreeBSD/i386 core file from an application running = in a chroot on FreeBSD/amd64. I start gdb while in the top-level directory of my chroot dir, and set the sysroot to . and open the core file: (gdb) set sysroot . (gdb) core-file sh.core [New LWP 100854] warning: the debug information found in "/usr/lib/debug/./lib/libedit.so.7.debug" does not match "./lib/libedit.so.= 7" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/./lib/libc.so.7.deb= ug" does not match "./lib/libc.so.7" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/./lib/libncursesw.so.8.debug" does not match "./lib/libncursesw.so.8" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/./libexec/ld-elf.so.1.debug" does not match "./libexec/ld-elf.so.1" (CRC mismatch). Core was generated by `sh'. Program terminated with signal SIGABRT, Aborted. #0 0x012589d3 in thr_kill () from ./lib/libc.so.7 The .so files have a .gnu_debuglink entry of "libedit.so.7.debug", and GDB = duly searches for this file in the standalone debug path list (from ktrace): ./lib/libedit.so.7.debug ./lib/.debug/libedit.so.7.debug /usr/lib/debug/./lib/libedit.so.7.debug It finds libedit.so.7.debug on the third try, but it is the system's libedit.so.7.debug found by absolute path, not the desired sysroot one; the sysroot should be prepended to absolute debug search paths, so that we find ./usr/lib/debug/./lib/libedit.so.7.debug --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21615-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 18 21:22:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 76371 invoked by alias); 18 Jul 2017 21:22:39 -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 76332 invoked by uid 48); 18 Jul 2017 21:22:38 -0000 From: "emaste at freebsd dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/9645] GDB needs a --sysroot command line option Date: Tue, 18 Jul 2017 21:22: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: 6.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: emaste at freebsd dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q3/txt/msg00052.txt.bz2 Content-length: 379 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9645 emaste at freebsd dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emaste at freebsd dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21616-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 18 21:23:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 77395 invoked by alias); 18 Jul 2017 21:23:29 -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 77368 invoked by uid 48); 18 Jul 2017 21:23:28 -0000 From: "emaste at freebsd dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21785] sysroot option does not apply to standalone debug Date: Tue, 18 Jul 2017 21:23: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: emaste at freebsd dot org X-Bugzilla-Status: UNCONFIRMED 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: see_also 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: 2017-q3/txt/msg00053.txt.bz2 Content-length: 459 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21785 emaste at freebsd dot org changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://sourceware.org/bugz | |illa/show_bug.cgi?id=3D9645 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21617-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 19 09:23:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 102931 invoked by alias); 19 Jul 2017 09:23:21 -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 102892 invoked by uid 48); 19 Jul 2017 09:23:19 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/9645] GDB needs a --sysroot command line option Date: Wed, 19 Jul 2017 09:23: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: 6.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q3/txt/msg00054.txt.bz2 Content-length: 907 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9645 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #2 from Pedro Alves --- > I think that this is the actual bug; we should have a way to run > commands before or after loading. Indeed, and we have "-iex" for that nowadays: $ gdb --help ... --eval-command=3DCOMMAND, -ex Execute a single GDB command. May be used multiple times and in conjunction with --command. --init-eval-command=3DCOMMAND, -iex Like -ex but before loading inferior. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21618-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 19 11:40:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31799 invoked by alias); 19 Jul 2017 11:40:08 -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 31058 invoked by uid 48); 19 Jul 2017 11:40:07 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug exp/21717] "print $fpscr" says "" until some VFP data register is printed Date: Wed, 19 Jul 2017 11:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00055.txt.bz2 Content-length: 715 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21717 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org --- Comment #1 from Yao Qi --- (In reply to Ruslan from comment #0) > To reproduce: >=20 > 1. Run the following command to start debuggee and stop at entry point: > gdb /bin/true -ex 'b *0' -ex r -ex 'd 1' Could you show me the gdb output here? I wonder why /bin/true 's entry is = on address 0x0. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21619-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 19 13:50:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 115512 invoked by alias); 19 Jul 2017 13:50:12 -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 115387 invoked by uid 48); 19 Jul 2017 13:50:11 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug exp/21717] "print $fpscr" says "" until some VFP data register is printed Date: Wed, 19 Jul 2017 13:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00056.txt.bz2 Content-length: 1002 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21717 --- Comment #2 from Ruslan --- (In reply to Yao Qi from comment #1) > Could you show me the gdb output here? I wonder why /bin/true 's entry is > on address 0x0. It's not on address zero. It's just a hack to make GDB stop on the first instruction available to the inferior process =E2=80=94 otherwise, if you d= on't have debug symbols, you'll not be able to stop at the beginning of execution =E2= =80=94 be it _start or main (to my knowledge, this is the easiest way to achieve this). Here's how the session begins: $ gdb -q /bin/true -ex 'b *0' -ex r -ex 'd 1' -ex 'info reg $pc' Reading symbols from /bin/true...(no debugging symbols found)...done. Breakpoint 1 at 0x0 Starting program: /bin/true=20 Warning: Cannot insert breakpoint 1. Cannot access memory at address 0x0 pc 0xb6fcfca0 0xb6fcfca0 <_start> --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21620-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 19 16:03:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 790 invoked by alias); 19 Jul 2017 16:03:55 -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 302 invoked by uid 48); 19 Jul 2017 16:03:54 -0000 From: "orivej at gmx dot fr" To: gdb-prs@sourceware.org Subject: [Bug c++/16874] Setting a breakpoint on function in anonymous namespace is unnecessarily awkward Date: Wed, 19 Jul 2017 16:03: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: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: orivej at gmx dot fr X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: patrick at parcs dot ath.cx X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q3/txt/msg00057.txt.bz2 Content-length: 384 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16874 Orivej Desh changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |orivej at gmx dot fr --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21621-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jul 20 07:10:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 98579 invoked by alias); 20 Jul 2017 07:10:17 -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 98489 invoked by uid 48); 20 Jul 2017 07:10:16 -0000 From: "ciro.santilli at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21798] New: Cannot alias monitor commands for gdbserver, fails with "Invalid command to alias to: monitor exit" Date: Thu, 20 Jul 2017 07:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ciro.santilli at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00058.txt.bz2 Content-length: 616 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21798 Bug ID: 21798 Summary: Cannot alias monitor commands for gdbserver, fails with "Invalid command to alias to: monitor exit" Product: gdb Version: 7.7 Status: UNCONFIRMED Severity: normal Priority: P2 Component: remote Assignee: unassigned at sourceware dot org Reporter: ciro.santilli at gmail dot com Target Milestone: --- alias moe =3D monitor exit --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21622-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 21 11:37:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 116475 invoked by alias); 21 Jul 2017 11:37:00 -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 116032 invoked by uid 48); 21 Jul 2017 11:37:00 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug exp/21717] "print $fpscr" says "" until some VFP data register is printed Date: Fri, 21 Jul 2017 11:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00059.txt.bz2 Content-length: 1453 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21717 --- Comment #3 from Yao Qi --- (In reply to Ruslan from comment #2) >=20 > Here's how the session begins: >=20 > $ gdb -q /bin/true -ex 'b *0' -ex r -ex 'd 1' -ex 'info reg $pc' > Reading symbols from /bin/true...(no debugging symbols found)...done. > Breakpoint 1 at 0x0 > Starting program: /bin/true=20 > Warning: > Cannot insert breakpoint 1. > Cannot access memory at address 0x0 >=20 > pc 0xb6fcfca0 0xb6fcfca0 <_start> I still can't reproduce it on armv7l panda board, gdb -q /bin/true -ex 'b *0' -ex r -ex 'd 1' Reading symbols from /bin/true...(no debugging symbols found)...done. Breakpoint 1 at 0x0 Starting program: /bin/true=20 Warning: Cannot insert breakpoint 1. Cannot access memory at address 0x0 (gdb) p $fpscr $1 =3D 0 My board is armv7l, having vfp and vfpv3, but your board only has vfp. I d= on't have armv6l hardware. Can you build GDB from source and debug it yourself? You can debug GDB by setting breakpoint on arm_linux_fetch_inferior_registers and fetch_vfp_regs, and run GDB like this, (gdb) run -q /bin/true -ex 'b *0' -ex r -ex 'd 1' GDB should call arm_linux_fetch_inferior_registers first, and then it should call fetch_vfp_regs to fetch VFP registers. I suspect "" is caused by that fetch_vfp_regs is not called. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21623-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 21 13:36:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 112409 invoked by alias); 21 Jul 2017 13:36:55 -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 112383 invoked by uid 48); 21 Jul 2017 13:36:54 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug exp/21717] "print $fpscr" says "" until some VFP data register is printed Date: Fri, 21 Jul 2017 13:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00060.txt.bz2 Content-length: 1064 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21717 --- Comment #4 from Ruslan --- OK, here's what happens: in arm_linux_fetch_inferior_registers the last bra= nch else if (tdep->vfp_register_count > 0 && regno >=3D ARM_D0_REGNUM && regno <=3D ARM_D0_REGNUM + tdep->vfp_register_count) fetch_vfp_regs (regcache); has tdep->vfp_register_count=3D=3D16, while regno=3D90 (ARM_FPSCR_REGNUM). = As ARM_D0_REGNUM=3D=3D58, the call to fetch_vfp_regs(regcache) doesn't happen. What seems to mismatch here is that VFP register count is 16, i.e. D0-D15, = but enum gdb_regnum contains values up to ARM_D31_REGNUM, thus the next value, ARM_FPSCR_REGNUM, is not reached by the comparisons. Thus it's not surprisi= ng that the code does work on VFPv3, where there're 32 VFP double-precision registers. I suppose there should be a "|| regno=3D=3DARM_FPSCR_REGNUM" or something l= ike that inside the if-condition. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21624-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 21 14:57:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 72696 invoked by alias); 21 Jul 2017 14:57:39 -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 72663 invoked by uid 48); 21 Jul 2017 14:57:38 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21436] frame filter should allow duplicated underlying frames Date: Fri, 21 Jul 2017 14:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pmuldoon at redhat dot com 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: cc 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: 2017-q3/txt/msg00061.txt.bz2 Content-length: 1897 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21436 Phil Muldoon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmuldoon at redhat dot com --- Comment #1 from Phil Muldoon --- I've been looking at this, but I cannot produce the scenario where frames a= re printed in duplicate. At first, I thought maybe something is triggering a f= rame cache invalidation. I could find no evidence of that (other than the user triggering "gdb.invalidate_cached_frames" in the frame decorators, but that would be a self-destructive thing to do). In Fedora, we have the ability to= run gdb.Commands that release the GIL (for long running GDB commands) and I tho= ught maybe it could be that (some other concurrent Python code invalidating the cache). But there's no guarantee that you are running Fedora or using that,= and the only way I could find to invalidate the cache in a concurrent call was = to call that invalidate API or switch threads. I've looked at the iterator handling code to make sure we are doing the right thing there and it seems = to be. I also looked at the SpiderMonkey code and whilst it was only a brief look (it's a bit complicated for the likes of me ;)) it all seems ok. So do you have a smaller test case? Also, I think I'll put in a FrameDecorator.architecture() call to FrameDecorator objects. Now that we have a Python Architecture object we can just pass Architecture objects around and not whole frames which will make FrameDecorator for synthetic frames easier to write. We can make the .frame= () call optional and build in backward compatibility for older frame filters on new GDBs. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21625-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 21 14:58:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 87468 invoked by alias); 21 Jul 2017 14:58:20 -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 87430 invoked by uid 48); 21 Jul 2017 14:58:19 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug exp/21717] "print $fpscr" says "" until some VFP data register is printed Date: Fri, 21 Jul 2017 14:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed 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: 2017-q3/txt/msg00062.txt.bz2 Content-length: 1569 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21717 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-07-21 Assignee|unassigned at sourceware dot org |qiyao at gcc dot gn= u.org Ever confirmed|0 |1 --- Comment #5 from Yao Qi --- (In reply to Ruslan from comment #4) > OK, here's what happens: in arm_linux_fetch_inferior_registers the last > branch >=20 > else if (tdep->vfp_register_count > 0 > && regno >=3D ARM_D0_REGNUM > && regno <=3D ARM_D0_REGNUM + tdep->vfp_register_count) > fetch_vfp_regs (regcache); >=20 > has tdep->vfp_register_count=3D=3D16, while regno=3D90 (ARM_FPSCR_REGNUM)= . As > ARM_D0_REGNUM=3D=3D58, the call to fetch_vfp_regs(regcache) doesn't happe= n. >=20 > What seems to mismatch here is that VFP register count is 16, i.e. D0-D15, > but enum gdb_regnum contains values up to ARM_D31_REGNUM, thus the next > value, ARM_FPSCR_REGNUM, is not reached by the comparisons. Thus it's not > surprising that the code does work on VFPv3, where there're 32 VFP > double-precision registers. >=20 > I suppose there should be a "|| regno=3D=3DARM_FPSCR_REGNUM" or something= like > that inside the if-condition. Indeed, I'll fix it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21626-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 21 15:07:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 30199 invoked by alias); 21 Jul 2017 15:07:22 -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 30072 invoked by uid 48); 21 Jul 2017 15:07:21 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug remote/21798] Cannot alias monitor commands for gdbserver, fails with "Invalid command to alias to: monitor exit" Date: Fri, 21 Jul 2017 15:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00063.txt.bz2 Content-length: 552 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21798 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org --- Comment #1 from Yao Qi --- GDB only has command "monitor". "monitor exit" is not a GDB command, so you can't create an alias to it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21627-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 21 15:46:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68384 invoked by alias); 21 Jul 2017 15:46:32 -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 68349 invoked by uid 48); 21 Jul 2017 15:46:31 -0000 From: "ciro.santilli at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21798] Cannot alias monitor commands for gdbserver, fails with "Invalid command to alias to: monitor exit" Date: Fri, 21 Jul 2017 15:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ciro.santilli at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00064.txt.bz2 Content-length: 251 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21798 --- Comment #2 from Ciro Santilli --- Ah, going crazy. I'll just use a function. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21628-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 21 18:58:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 98342 invoked by alias); 21 Jul 2017 18:58:31 -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 98305 invoked by uid 48); 21 Jul 2017 18:58:29 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21436] frame filter should allow duplicated underlying frames Date: Fri, 21 Jul 2017 18:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pmuldoon at redhat dot com 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: 2017-q3/txt/msg00065.txt.bz2 Content-length: 568 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21436 --- Comment #2 from Phil Muldoon --- For this: "Now that we have a Python Architecture object we can just pass Architecture objects around and not whole frames which will make FrameDecorator for synthetic frames easier to write" I meant "We can just pass Architecture objects around and not whole frames in synth= etic frames which will make FrameDecorators for synthetic frames easier to write= ." --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21629-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 21 19:13:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 103148 invoked by alias); 21 Jul 2017 19:13:03 -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 103125 invoked by uid 48); 21 Jul 2017 19:13:03 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/21814] New: Make it possible to view disassembly with raw bytes using x/i command Date: Fri, 21 Jul 2017 19:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00066.txt.bz2 Content-length: 1061 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21814 Bug ID: 21814 Summary: Make it possible to view disassembly with raw bytes using x/i command Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: cli Assignee: unassigned at sourceware dot org Reporter: b7.10110111 at gmail dot com Target Milestone: --- I know two modes of GDB disassembly: First command be used to show instructions as well as raw byte, but it seem= s to not accept number of instructions to disassemble =E2=80=94 only memory rang= e: disas/r $pc,+30 Second command can disassemble exactly N instructions, like follows, but without raw bytes: x/10i $pc I'd be good to have a hybrid of these two modes: make the raw bytes visible= as in disas/r and be able to specify exact number of instructions to disassemb= le as in x/10i. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21630-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 21 21:38:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 117831 invoked by alias); 21 Jul 2017 21:38:01 -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 117791 invoked by uid 48); 21 Jul 2017 21:38:01 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21798] Cannot alias monitor commands for gdbserver, fails with "Invalid command to alias to: monitor exit" Date: Fri, 21 Jul 2017 21:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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 cc resolution 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: 2017-q3/txt/msg00067.txt.bz2 Content-length: 624 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21798 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |sergiodj at redhat dot com Resolution|--- |INVALID --- Comment #3 from Sergio Durigan Junior --- Resolving as INVALID then. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21631-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jul 22 21:39:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 50988 invoked by alias); 22 Jul 2017 21:39:21 -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 50965 invoked by uid 48); 22 Jul 2017 21:39:20 -0000 From: "jim at realintent dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21817] New: gdb session suspended when run in background Date: Sat, 22 Jul 2017 21:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jim at realintent dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00068.txt.bz2 Content-length: 5005 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21817 Bug ID: 21817 Summary: gdb session suspended when run in background Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: jim at realintent dot com Target Milestone: --- Help! I'm running gdb 7.12.1 under CentOS 6.8. My application has a signal handler that invokes gdb in batch when a SEGV o= r=20 other bad signals occur. It invokes gdb with the application's process ID = as gdb --pid=3D --nx -x cmd.gdb --batch This had worked fine under RH-5 and older versions of gdb. With gdb 7.12.1, the gdb process is immediately suspended before any comman= ds are run. I debugged the suspended gdb process, which shows that gdb was stopped in=20 set_tty_state(). This ought not to have happened, as gdb was run as a=20 background process and should not have tried to configure the terminal. The output of 'where' and 'backtrace full' are below. Is there a workaround for this problem? (gdb) where #0 0x0000003a78ee0048 in tcsetattr () from /lib64/libc.so.6 #1 0x00000000004491e1 in set_tty_state (scb=3D, state=3D) at ser-unix.c:152 #2 hardwire_set_tty_state (scb=3D, ttystate=3D) at ser-unix.c:209 #3 0x0000000000660d4b in child_terminal_inferior (self=3D) = at inflow.c:276 #4 0x000000000044e5b9 in linux_nat_terminal_inferior (self=3D) at linux-nat.c:4462 #5 0x0000000000587f09 in target_terminal_inferior () at target.c:501 #6 0x000000000053a8aa in attach_command (args=3D0x26bbf70 "11882", args@entry=3D0x7ffce9adc284 "11882", from_tty=3Dfrom_tty@entry=3D0) at infc= md.c:2863 #7 0x00000000005575b8 in catch_command_errors (command=3D0x53a810 , arg=3Darg@entry=3D0x7ffce9adc284 "11882", fro= m_tty=3D0) at main.c:375 #8 0x000000000055818b in captured_main (data=3D0x7ffce9ad9db0) at main.c:1= 065 #9 gdb_main (args=3Dargs@entry=3D0x7ffce9ad9ed0) at main.c:1159 #10 0x0000000000409595 in main (argc=3D, argv=3D) at gdb.c:32 (gdb) backtrace full=20 #0 0x0000003a78ee0048 in tcsetattr () from /lib64/libc.so.6 No symbol table info available. #1 0x00000000004491e1 in set_tty_state (scb=3D, state=3D) at ser-unix.c:152 No locals. #2 hardwire_set_tty_state (scb=3D, ttystate=3D) at ser-unix.c:209 state =3D #3 0x0000000000660d4b in child_terminal_inferior (self=3D) = at inflow.c:276 result =3D inf =3D 0x27b2f20 tinfo =3D 0x27b7cd0 #4 0x000000000044e5b9 in linux_nat_terminal_inferior (self=3D) at linux-nat.c:4462 No locals. #5 0x0000000000587f09 in target_terminal_inferior () at target.c:501 ui =3D #6 0x000000000053a8aa in attach_command (args=3D0x26bbf70 "11882", args@entry=3D0x7ffce9adc284 "11882", from_tty=3Dfrom_tty@entry=3D0) at infc= md.c:2863 async_exec =3D 0 attach_target =3D 0x0 inferior =3D 0x27b2f20 args_chain =3D 0x7a87e0 mode =3D #7 0x00000000005575b8 in catch_command_errors (command=3D0x53a810 , arg=3Darg@entry=3D0x7ffce9adc284 "11882", fro= m_tty=3D0) at main.c:375 was_sync =3D 0 exception_try_scope_instance =3D {saved_state =3D 0x26bc070} #8 0x000000000055818b in captured_main (data=3D0x7ffce9ad9db0) at main.c:1= 065 execarg =3D cdarg =3D 0x0 save_auto_load =3D 1 argc =3D ttyarg =3D 0x0 cmdarg_vec =3D 0x26bc790 system_gdbinit =3D 0x0 inhibit_home_gdbinit =3D 0 print_help =3D 0 context =3D 0x7ffce9ad9db0 argv =3D local_gdbinit =3D 0x0 i =3D objfile =3D pre_stat_chain =3D 0x7a87e0 pid_or_core_arg =3D 0x0 cmdarg_p =3D 0x0 home_gdbinit =3D 0x27b7d10 "/home/jim/.gdbinit" print_version =3D 0 corearg =3D 0x0 set_args =3D 0 symarg =3D pidarg =3D 0x7ffce9adc284 "11882" dirarg =3D 0x26bbf70 dirsize =3D 1 ndir =3D quiet =3D 1 print_configuration =3D 0 #9 gdb_main (args=3Dargs@entry=3D0x7ffce9ad9ed0) at main.c:1159 exception_try_scope_instance =3D {saved_state =3D 0x7a87e0 } #10 0x0000000000409595 in main (argc=3D, argv=3D) at gdb.c:32 args =3D {argc =3D 6, argv =3D 0x7ffce9ad9fd8, interpreter_p =3D 0x= 755884 "console"} --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21632-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jul 22 21:47:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 67790 invoked by alias); 22 Jul 2017 21:47:49 -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 67715 invoked by uid 48); 22 Jul 2017 21:47:46 -0000 From: "jim at realintent dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21817] gdb session suspended when run in background Date: Sat, 22 Jul 2017 21:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jim at realintent dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00069.txt.bz2 Content-length: 381 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21817 --- Comment #1 from Jim Foley --- I should add that the gdb process is suspended when the application is run in background. If the application (and gdb itself) is run in foregro= und, then it runs correctly. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21633-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jul 23 11:31:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35963 invoked by alias); 23 Jul 2017 11:31:37 -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 35883 invoked by uid 48); 23 Jul 2017 11:31:29 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/21818] New: disassemble with v5TE remote: Assertion `info->mach == bfd_get_mach (exec_bfd)' failed. Date: Sun, 23 Jul 2017 11:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00070.txt.bz2 Content-length: 1757 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21818 Bug ID: 21818 Summary: disassemble with v5TE remote: Assertion `info->mach =3D= =3D bfd_get_mach (exec_bfd)' failed. Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: b7.10110111 at gmail dot com Target Milestone: --- When debugging a remote ARM binary with Tag_CPU_arch set to v5TE, attempt to use `disassemble` command result in assertion failure. Steps to reproduce: * On remote machine: gcc -x c -o test -march=3Darmv5te -nostdlib - <<< 'int _start(){}' gdbserver :1337 ./test * On local machine: arm-unknown-linux-gnueabihf-gdb -q -ex 'target remote rpi:1337' -ex disas `rpi` above is my remote machine's hostname. Here's the output I get from `disas`: Dump of assembler code for function _start: =3D> 0x000100b8 <+0>: push {r11} ; (str r11, [sp, #-4]!) 0x000100bc <+4>: ../../binutils-gdb/gdb/arch-utils.c:979: internal-error: int default_print_insn(bfd_vma, disassemble_info*): Assertion `info->mach =3D=3D bfd_get_mach (exec_bfd)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. What we have here is that `bfd_get_mach (exec_bfd)` returns 9=3D=3Dbfd_mach_arm_5TE, while `info->mach` has been set to 0=3D=3Dbfd_mach= _arm_unknown at `arm-dis.c:print_insn()` due to `info->flags` being 0. On newer ARM arches, like 6zk, `bfd_get_mach (exec_bfd)` returns 0, and this coincides with `info->mach`, so there's no problem. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21634-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jul 23 11:42:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 51580 invoked by alias); 23 Jul 2017 11:42:25 -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 51549 invoked by uid 48); 23 Jul 2017 11:42:24 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21819] New: Ctrl+C leads to "terminate called after throwing an instance of 'gdb_exception_RETURN_MASK_QUIT'" Date: Sun, 23 Jul 2017 11:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q3/txt/msg00071.txt.bz2 Content-length: 1640 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21819 Bug ID: 21819 Summary: Ctrl+C leads to "terminate called after throwing an instance of 'gdb_exception_RETURN_MASK_QUIT'" Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: b7.10110111 at gmail dot com Target Milestone: --- Created attachment 10282 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10282&action=3Ded= it Backtrace Tested on remote Raspbian system with gdb-8.0 compiled from source and local x86 system with gdb 8.0.50.20170709-git compiled with "--host=3Di686-pc-lin= ux-gnu --target=3Darm-unknown-linux-gnueabihf". To reproduce: * On remote machine: gdbserver :1337 gdbserver * On local machine: run the following command and press Ctrl+C when it's reading symbols: arm-unknown-linux-gnueabihf-gdb -q -ex 'target remote rpi:1337' I get the following output: Remote debugging using rpi:1337 Reading /home/pi/opt/gdb-8.0/bin/gdbserver from remote target... warning: File transfers from remote targets can be slow. Use "set sysroot" = to access files locally instead. Reading /home/pi/opt/gdb-8.0/bin/gdbserver from remote target... Reading symbols from target:/home/pi/opt/gdb-8.0/bin/gdbserver...^Cterminate called after throwing an instance of 'gdb_exception_RETURN_MASK_QUIT' Aborted (core dumped) Attaching backtrace from the core file generated. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21635-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 24 16:08:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 43597 invoked by alias); 24 Jul 2017 16:08: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 43573 invoked by uid 48); 24 Jul 2017 16:08:50 -0000 From: "source-ware at trk dot nickurak.ca" To: gdb-prs@sourceware.org Subject: [Bug exp/21827] New: Regression: gdb command lookup became case-insensitive Date: Mon, 24 Jul 2017 16:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: source-ware at trk dot nickurak.ca X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00072.txt.bz2 Content-length: 2477 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21827 Bug ID: 21827 Summary: Regression: gdb command lookup became case-insensitive Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: exp Assignee: unassigned at sourceware dot org Reporter: source-ware at trk dot nickurak.ca Target Milestone: --- Input: $ echo -e 'define aSDF\n print "in-func" \n end \n aSDF \n aSDF \n asdf"' |= gdb Expected behavior, as correctly observed in 7.x: * function gets defined * function gets called twice $ echo -e 'define aSDF\n print "in-func" \n end \n aSDF \n aSDF \n asdf"' |= gdb GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: . (gdb) >>(gdb) $1 =3D "in-func" (gdb) $2 =3D "in-func" (gdb) $3 =3D "in-func" Observed behavior, incorrect under 8.x: * function gets defined but converted to lower-case * calling function capitalized in the same was as it was defined fails $ echo -e 'define aSDF\n print "in-func" \n end \n aSDF \n aSDF \n asdf"' |= gdb GNU gdb (GDB) Fedora 8.0-13.fc26 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) >>(gdb) Undefined command: "aSDF". Try "help". (gdb) Undefined command: "aSDF". Try "help". (gdb) $1 =3D "in-func" --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21637-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 24 18:23:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41691 invoked by alias); 24 Jul 2017 18:23:49 -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 40961 invoked by uid 48); 24 Jul 2017 18:23:48 -0000 From: "vivekrane at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21829] GDB internal error: Assertion `name[prefix_len + 1] == ':'' failed. Date: Mon, 24 Jul 2017 18:23: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.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vivekrane at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00074.txt.bz2 Content-length: 390 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21829 Vivek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vivekrane at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21636-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 24 18:23:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20776 invoked by alias); 24 Jul 2017 18:23:29 -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 19013 invoked by uid 48); 24 Jul 2017 18:23:27 -0000 From: "vivekrane at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21829] New: GDB internal error: Assertion `name[prefix_len + 1] == ':'' failed. Date: Mon, 24 Jul 2017 18:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vivekrane at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00073.txt.bz2 Content-length: 1782 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21829 Bug ID: 21829 Summary: GDB internal error: Assertion `name[prefix_len + 1] =3D= =3D ':'' failed. Product: gdb Version: 7.11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: vivekrane at gmail dot com Target Milestone: --- When debugging TensorFlow on UBuntu, stopped at a breakpoint, trying to cal= l a function that pretty prints the object, this error often shows up. Here's t= he text from my console: Thread 1 "python" hit Breakpoint 12, tensorflow::DFS(tensorflow::Graph cons= t&, std::function const&, std::function const&) (g=3D..., enter=3D..., leave=3D...) at tensorflow/core/graph/algorithm.cc:34 34 stack.push_back(Work{g.source_node(), false}); (gdb) p g.source_node()->DebugString() /build/gdb-cXfXJ3/gdb-7.11.1/gdb/cp-namespace.c:252: internal-error: cp_search_static_and_baseclasses: Assertion `name[prefix_len + 1] =3D=3D ':= '' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) n This is a bug, please report it. For instructions, see: . /build/gdb-cXfXJ3/gdb-7.11.1/gdb/cp-namespace.c:252: internal-error: cp_search_static_and_baseclasses: Assertion `name[prefix_len + 1] =3D=3D ':= '' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) n Command aborted. (gdb) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21638-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 24 19:29:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 126451 invoked by alias); 24 Jul 2017 19:29:19 -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 114191 invoked by uid 48); 24 Jul 2017 19:29:12 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21829] GDB internal error: Assertion `name[prefix_len + 1] == ':'' failed. Date: Mon, 24 Jul 2017 19:29: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.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00075.txt.bz2 Content-length: 693 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21829 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com --- Comment #1 from Keith Seitz --- This sounds vaguely like breakpoints/18303, which was fixed by=20 commit 1cafadb4e4eb329dea01355c6632b3077113d80c Date: Tue Mar 15 15:18:28 2016 -0700 I see that patch was never put into 7.11. Are you able to test with 7.12 or 8.0? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21639-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 24 20:02:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 29302 invoked by alias); 24 Jul 2017 20:02:30 -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 28765 invoked by uid 48); 24 Jul 2017 20:02:29 -0000 From: "source-ware at trk dot nickurak.ca" To: gdb-prs@sourceware.org Subject: [Bug exp/21827] Regression: gdb command lookup became case-insensitive Date: Mon, 24 Jul 2017 20:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: source-ware at trk dot nickurak.ca X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00076.txt.bz2 Content-length: 896 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21827 --- Comment #1 from Jeremy Nickurak --- simark from IRC pointed out this change as the source of the regression via bisection: https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommit;h=3D3= d7b173c29900879c9a5958dd6029fd36666e57c As well as this this thread: https://sourceware.org/ml/gdb-patches/2017-01/msg00157.html A couple thoughts: * If this backwards-incompatible change is desired, it should probably be in the release-notes. * If case-sensitivity is the desired behavior here, one should probably be = able to define a command with a specified case. In my example here, I've specifi= ed some upper-case letters in the name of my definition, but it was converted = to lowercase at define-time. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21640-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 24 20:03:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 77403 invoked by alias); 24 Jul 2017 20:03:41 -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 76741 invoked by uid 48); 24 Jul 2017 20:03:40 -0000 From: "source-ware at trk dot nickurak.ca" To: gdb-prs@sourceware.org Subject: [Bug exp/21827] Regression: gdb command lookup became case-sensitive Date: Mon, 24 Jul 2017 20:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: source-ware at trk dot nickurak.ca X-Bugzilla-Status: UNCONFIRMED 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: short_desc 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: 2017-q3/txt/msg00077.txt.bz2 Content-length: 532 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21827 Jeremy Nickurak changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Regression: gdb command |Regression: gdb command |lookup became |lookup became |case-insensitive |case-sensitive --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21641-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 24 20:04:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 126451 invoked by alias); 24 Jul 2017 20:04:13 -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 124923 invoked by uid 48); 24 Jul 2017 20:04:12 -0000 From: "source-ware at trk dot nickurak.ca" To: gdb-prs@sourceware.org Subject: [Bug exp/21827] Regression: gdb command lookup became case-sensitive; but definitions are forced into lowercase Date: Mon, 24 Jul 2017 20:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: source-ware at trk dot nickurak.ca X-Bugzilla-Status: UNCONFIRMED 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: short_desc 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: 2017-q3/txt/msg00078.txt.bz2 Content-length: 673 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21827 Jeremy Nickurak changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Regression: gdb command |Regression: gdb command |lookup became |lookup became |case-sensitive |case-sensitive; but | |definitions are forced into | |lowercase --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21642-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 24 20:16:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88103 invoked by alias); 24 Jul 2017 20:16:36 -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 85787 invoked by uid 48); 24 Jul 2017 20:16:34 -0000 From: "source-ware at trk dot nickurak.ca" To: gdb-prs@sourceware.org Subject: [Bug exp/21827] Regression: gdb command lookup became case-sensitive; but definitions are forced into lowercase Date: Mon, 24 Jul 2017 20:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: source-ware at trk dot nickurak.ca X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00079.txt.bz2 Content-length: 662 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21827 --- Comment #2 from Jeremy Nickurak --- Other strange things that come out of this; The following gdb snippet fails unexpectedly: define myFunction print "hello" end document myFunction Just a dummy test function end -> Type "apropos word" to search for commands related to "word". (gdb) define myFunction Type commands for definition of "myFunction". End with a line saying just "end". > print "hello" >end (gdb) document myFunction Undefined command: "myFunction". Try "help". --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21643-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 25 00:31:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 44949 invoked by alias); 25 Jul 2017 00:31:43 -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 44439 invoked by uid 48); 25 Jul 2017 00:31:25 -0000 From: "jim at realintent dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/21817] gdb session suspended when run in background Date: Tue, 25 Jul 2017 00:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jim at realintent dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00080.txt.bz2 Content-length: 684 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21817 --- Comment #2 from Jim Foley --- More about this: I've fixed this in a customized gdb build with this change in inflow.c: ---- static int gdb_has_a_terminal (void) { // return initial_gdb_ttystate !=3D NULL; return (initial_gdb_ttystate !=3D NULL) && (batch_flag =3D=3D 0); } ---- This fix works successfully for our purposes.=20 I've tried to create a reproducible testcase on a 'hello world' style binary but didn't succeed. It must be that something in my application contributes to the reason gdb hangs. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21644-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 25 09:07:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 65673 invoked by alias); 25 Jul 2017 09:07:36 -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 62860 invoked by uid 55); 25 Jul 2017 09:07:34 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug exp/21717] "print $fpscr" says "" until some VFP data register is printed Date: Tue, 25 Jul 2017 09:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.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: 2017-q3/txt/msg00081.txt.bz2 Content-length: 1596 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21717 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Yao Qi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D02ad7fc29f82= 4a9742f8386bcf5793b81ff798f5 commit 02ad7fc29f824a9742f8386bcf5793b81ff798f5 Author: Yao Qi Date: Fri Jul 21 16:35:23 2017 +0100 [ARM] Access FPSCR on vfpv2 GDB can fetch or store FPSCR on vfpv3, which has 32 VFP registers, but fail to do so on vfpv2, which has 16 VFP registers. GDB code is incorr= ect for vfpv2, else if (tdep->vfp_register_count > 0 && regno >=3D ARM_D0_REGNUM && regno <=3D ARM_D0_REGNUM + tdep->vfp_register_count) while FPSCR register number is defined as ARM_D0_REGNUM + 32. ARM_D0_REGNUM, /* VFP double-precision registers. */ ARM_D31_REGNUM =3D ARM_D0_REGNUM + 31, ARM_FPSCR_REGNUM, The code above uses "<=3D" rather than "<", in order to put FPSCR in the range, but it is only correct when tdep->vfp_register_count is 32. On vpfv2, it is 16, and FPSCR is out of the range, so fetch_vfp_regs or store_vfp_regs are not called. gdb: 2017-07-25 Yao Qi PR tdep/21717 * arm-linux-nat.c (arm_linux_fetch_inferior_registers): Update condition for FPSCR. (arm_linux_store_inferior_registers): Likewise. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21645-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 25 09:16:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 50911 invoked by alias); 25 Jul 2017 09:16: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 49939 invoked by uid 55); 25 Jul 2017 09:16:51 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug exp/21717] "print $fpscr" says "" until some VFP data register is printed Date: Tue, 25 Jul 2017 09:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.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: 2017-q3/txt/msg00082.txt.bz2 Content-length: 1604 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21717 --- Comment #7 from cvs-commit at gcc dot gnu.org --- The gdb-8.0-branch branch has been updated by Yao Qi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D50e64da58e64= 8ff8708935add5b2a87b4e590edf commit 50e64da58e648ff8708935add5b2a87b4e590edf Author: Yao Qi Date: Tue Jul 25 10:15:25 2017 +0100 [ARM] Access FPSCR on vfpv2 GDB can fetch or store FPSCR on vfpv3, which has 32 VFP registers, but fail to do so on vfpv2, which has 16 VFP registers. GDB code is incorr= ect for vfpv2, else if (tdep->vfp_register_count > 0 && regno >=3D ARM_D0_REGNUM && regno <=3D ARM_D0_REGNUM + tdep->vfp_register_count) while FPSCR register number is defined as ARM_D0_REGNUM + 32. ARM_D0_REGNUM, /* VFP double-precision registers. */ ARM_D31_REGNUM =3D ARM_D0_REGNUM + 31, ARM_FPSCR_REGNUM, The code above uses "<=3D" rather than "<", in order to put FPSCR in the range, but it is only correct when tdep->vfp_register_count is 32. On vpfv2, it is 16, and FPSCR is out of the range, so fetch_vfp_regs or store_vfp_regs are not called. gdb: 2017-07-25 Yao Qi PR tdep/21717 * arm-linux-nat.c (arm_linux_fetch_inferior_registers): Update condition for FPSCR. (arm_linux_store_inferior_registers): Likewise. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21646-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 25 09:26:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49144 invoked by alias); 25 Jul 2017 09:26:02 -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 48860 invoked by uid 48); 25 Jul 2017 09:26:02 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tdep/21717] "print $fpscr" says "" until some VFP data register is printed Date: Tue, 25 Jul 2017 09:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.0.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status component resolution target_milestone 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: 2017-q3/txt/msg00083.txt.bz2 Content-length: 652 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21717 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Component|exp |tdep Resolution|--- |FIXED Target Milestone|--- |8.0.1 --- Comment #8 from Yao Qi --- Patch is pushed to both master and 8.0 branch. Close it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21647-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 25 10:40:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 75776 invoked by alias); 25 Jul 2017 10:40:22 -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 75246 invoked by uid 55); 25 Jul 2017 10:40:21 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21555] "error re-setting breakpoint" on PIE executables Date: Tue, 25 Jul 2017 10:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.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: 2017-q3/txt/msg00084.txt.bz2 Content-length: 4952 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21555 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Yao Qi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D46a62268b87b= d5e8215636b695380bca9a9f3b63 commit 46a62268b87bd5e8215636b695380bca9a9f3b63 Author: Yao Qi Date: Tue Jul 25 11:38:50 2017 +0100 Catch exceptions thrown from gdbarch_skip_prologue PR 21555 is caused by the exception during the prologue analysis when re-set a breakpoint. (gdb) bt #0 memory_error_message (err=3DTARGET_XFER_E_IO, gdbarch=3D0x153db50, memaddr=3D93824992233232) at ../../binutils-gdb/gdb/corefile.c:192 #1 0x00000000005718ed in memory_error (err=3DTARGET_XFER_E_IO, memaddr=3Dmemaddr@entry=3D93824992233232) at ../../binutils-gdb/gdb/corefil= e.c:220 #2 0x00000000005719d6 in read_memory_object (object=3Dobject@entry=3DTARGET_OBJECT_CODE_MEMORY, memaddr=3D9382499223323= 2, memaddr@entry=3D1, myaddr=3Dmyaddr@entry=3D0x7fffffffd0a0 "P\333S\001", len=3Dlen@entry=3D1) at ../../binutils-gdb/gdb/corefile.c:259 #3 0x0000000000571c6e in read_code (len=3D1, myaddr=3D0x7fffffffd0a0 "P\333S\001", memaddr=3D) at ../../binutils-gdb/gdb/corefile= .c:287 #4 read_code_unsigned_integer (memaddr=3Dmemaddr@entry=3D938249922332= 32, len=3Dlen@entry=3D1, byte_order=3Dbyte_order@entry=3DBFD_ENDIAN_LITTLE)=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 at ../../binutils-gdb/gdb/corefile.c:362 #5 0x000000000041d4a0 in amd64_analyze_prologue (gdbarch=3Dgdbarch@entry=3D0x153db50, pc=3Dpc@entry=3D93824992233232, current_pc=3Dcurrent_pc@entry=3D18446744073709551615, cache=3Dcache@entry=3D0x7fffffffd1e0) at ../../binutils-gdb/gdb/amd64-tdep.= c:2310 #6 0x000000000041e404 in amd64_skip_prologue (gdbarch=3D0x153db50, start_pc=3D93824992233232) at ../../binutils-gdb/gdb/amd64-tdep.c:2459 #7 0x000000000067bfb0 in skip_prologue_sal (sal=3Dsal@entry=3D0x7ffff= fffd4e0) at ../../binutils-gdb/gdb/symtab.c:3628 #8 0x000000000067c4d8 in find_function_start_sal (sym=3Dsym@entry=3D0x1549960, funfirstline=3D1) at ../../binutils-gdb/gdb/symtab.c:3501 #9 0x000000000060999d in symbol_to_sal (result=3Dresult@entry=3D0x7fffffffd5f0, funfirstline=3D, sym=3Dsym@entry=3D0x1549960) at ../../binutils-gdb/gdb/linespec.c:3860 .... #16 0x000000000054b733 in location_to_sals (b=3Db@entry=3D0x15792d0, location=3D0x157c230, search_pspace=3Dsearch_pspace@entry=3D0x1148120, found=3Dfound@entry=3D0x7fffffffdc64) at ../../binutils-gdb/gdb/breakpoint.= c:14211 #17 0x000000000054c1f5 in breakpoint_re_set_default (b=3D0x15792d0) at ../../binutils-gdb/gdb/breakpoint.c:14301 #18 0x00000000005412a9 in breakpoint_re_set_one (bint=3Dbint@entry=3D0x15792d0) at ../../binutils-gdb/gdb/breakpoint.c:14412 This problem can be fixed by - either each prologue analyzer doesn't throw exception, - or catch the exception thrown from gdbarch_skip_prologue, I choose the latter because the former needs to fix *every* prologue analyzer to not throw exception. This error can be reproduced by changing reread.exp. The test reread.e= xp has already test that breakpoint can be reset correctly after the executable is re-read. This patch extends this test by compiling test c file with and without -fPIE. (gdb) run ^M The program being debugged has been started already.^M Start it from the beginning? (y or n) y^M x86_64/gdb/testsuite/outputs/gdb.base/reread/reread' has changed; re-reading symbols. Error in re-setting breakpoint 1: Cannot access memory at address 0x555555554790^M Error in re-setting breakpoint 2: Cannot access memory at address 0x555555554790^M Starting program: /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/outputs/gdb.base/reread/rer= ead ^M This is foo^M [Inferior 1 (process 27720) exited normally]^M (gdb) FAIL: gdb.base/reread.exp: opts=3D "-fPIE" "ldflags=3D-pie" : run= to foo() second time (the program exited) This patch doesn't re-indent the code, to keep the patch simple. gdb: 2017-07-25 Yao Qi PR gdb/21555 * arch-utils.c (gdbarch_skip_prologue_noexcept): New function. * arch-utils.h (gdbarch_skip_prologue_noexcept): Declare. * infrun.c: Include arch-utils.h (handle_step_into_function): Call gdbarch_skip_prologue_noexcept. (handle_step_into_function_backward): Likewise. * symtab.c (skip_prologue_sal): Likewise. gdb/testsuite: 2017-07-25 Yao Qi PR gdb/21555 * gdb.base/reread.exp: Wrap the whole test with two kinds of compilation flags, with -fPIE and without -fPIE. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21648-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 25 10:55:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 77443 invoked by alias); 25 Jul 2017 10:55:49 -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 72983 invoked by uid 55); 25 Jul 2017 10:55:45 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21555] "error re-setting breakpoint" on PIE executables Date: Tue, 25 Jul 2017 10:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.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: 2017-q3/txt/msg00085.txt.bz2 Content-length: 4960 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21555 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The gdb-8.0-branch branch has been updated by Yao Qi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dcd33a03d183a= 268b83ccbcae07f3788308e8d9f4 commit cd33a03d183a268b83ccbcae07f3788308e8d9f4 Author: Yao Qi Date: Tue Jul 25 11:38:50 2017 +0100 Catch exceptions thrown from gdbarch_skip_prologue PR 21555 is caused by the exception during the prologue analysis when re-set a breakpoint. (gdb) bt #0 memory_error_message (err=3DTARGET_XFER_E_IO, gdbarch=3D0x153db50, memaddr=3D93824992233232) at ../../binutils-gdb/gdb/corefile.c:192 #1 0x00000000005718ed in memory_error (err=3DTARGET_XFER_E_IO, memaddr=3Dmemaddr@entry=3D93824992233232) at ../../binutils-gdb/gdb/corefil= e.c:220 #2 0x00000000005719d6 in read_memory_object (object=3Dobject@entry=3DTARGET_OBJECT_CODE_MEMORY, memaddr=3D9382499223323= 2, memaddr@entry=3D1, myaddr=3Dmyaddr@entry=3D0x7fffffffd0a0 "P\333S\001", len=3Dlen@entry=3D1) at ../../binutils-gdb/gdb/corefile.c:259 #3 0x0000000000571c6e in read_code (len=3D1, myaddr=3D0x7fffffffd0a0 "P\333S\001", memaddr=3D) at ../../binutils-gdb/gdb/corefile= .c:287 #4 read_code_unsigned_integer (memaddr=3Dmemaddr@entry=3D938249922332= 32, len=3Dlen@entry=3D1, byte_order=3Dbyte_order@entry=3DBFD_ENDIAN_LITTLE)=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 at ../../binutils-gdb/gdb/corefile.c:362 #5 0x000000000041d4a0 in amd64_analyze_prologue (gdbarch=3Dgdbarch@entry=3D0x153db50, pc=3Dpc@entry=3D93824992233232, current_pc=3Dcurrent_pc@entry=3D18446744073709551615, cache=3Dcache@entry=3D0x7fffffffd1e0) at ../../binutils-gdb/gdb/amd64-tdep.= c:2310 #6 0x000000000041e404 in amd64_skip_prologue (gdbarch=3D0x153db50, start_pc=3D93824992233232) at ../../binutils-gdb/gdb/amd64-tdep.c:2459 #7 0x000000000067bfb0 in skip_prologue_sal (sal=3Dsal@entry=3D0x7ffff= fffd4e0) at ../../binutils-gdb/gdb/symtab.c:3628 #8 0x000000000067c4d8 in find_function_start_sal (sym=3Dsym@entry=3D0x1549960, funfirstline=3D1) at ../../binutils-gdb/gdb/symtab.c:3501 #9 0x000000000060999d in symbol_to_sal (result=3Dresult@entry=3D0x7fffffffd5f0, funfirstline=3D, sym=3Dsym@entry=3D0x1549960) at ../../binutils-gdb/gdb/linespec.c:3860 .... #16 0x000000000054b733 in location_to_sals (b=3Db@entry=3D0x15792d0, location=3D0x157c230, search_pspace=3Dsearch_pspace@entry=3D0x1148120, found=3Dfound@entry=3D0x7fffffffdc64) at ../../binutils-gdb/gdb/breakpoint.= c:14211 #17 0x000000000054c1f5 in breakpoint_re_set_default (b=3D0x15792d0) at ../../binutils-gdb/gdb/breakpoint.c:14301 #18 0x00000000005412a9 in breakpoint_re_set_one (bint=3Dbint@entry=3D0x15792d0) at ../../binutils-gdb/gdb/breakpoint.c:14412 This problem can be fixed by - either each prologue analyzer doesn't throw exception, - or catch the exception thrown from gdbarch_skip_prologue, I choose the latter because the former needs to fix *every* prologue analyzer to not throw exception. This error can be reproduced by changing reread.exp. The test reread.e= xp has already test that breakpoint can be reset correctly after the executable is re-read. This patch extends this test by compiling test c file with and without -fPIE. (gdb) run ^M The program being debugged has been started already.^M Start it from the beginning? (y or n) y^M x86_64/gdb/testsuite/outputs/gdb.base/reread/reread' has changed; re-reading symbols. Error in re-setting breakpoint 1: Cannot access memory at address 0x555555554790^M Error in re-setting breakpoint 2: Cannot access memory at address 0x555555554790^M Starting program: /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/outputs/gdb.base/reread/rer= ead ^M This is foo^M [Inferior 1 (process 27720) exited normally]^M (gdb) FAIL: gdb.base/reread.exp: opts=3D "-fPIE" "ldflags=3D-pie" : run= to foo() second time (the program exited) This patch doesn't re-indent the code, to keep the patch simple. gdb: 2017-07-25 Yao Qi PR gdb/21555 * arch-utils.c (gdbarch_skip_prologue_noexcept): New function. * arch-utils.h (gdbarch_skip_prologue_noexcept): Declare. * infrun.c: Include arch-utils.h (handle_step_into_function): Call gdbarch_skip_prologue_noexcept. (handle_step_into_function_backward): Likewise. * symtab.c (skip_prologue_sal): Likewise. gdb/testsuite: 2017-07-25 Yao Qi PR gdb/21555 * gdb.base/reread.exp: Wrap the whole test with two kinds of compilation flags, with -fPIE and without -fPIE. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21649-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jul 25 11:01:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 115131 invoked by alias); 25 Jul 2017 11:01: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 114965 invoked by uid 48); 25 Jul 2017 11:01:50 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21555] "error re-setting breakpoint" on PIE executables Date: Tue, 25 Jul 2017 11:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.0.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone 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: 2017-q3/txt/msg00086.txt.bz2 Content-length: 483 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21555 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.0.1 --- Comment #4 from Yao Qi --- Patch is pushed in to master and 8.0 branch. Close it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21650-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 26 19:20:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 50278 invoked by alias); 26 Jul 2017 19:20:43 -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 50251 invoked by uid 48); 26 Jul 2017 19:20:42 -0000 From: "jim at realintent dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21842] New: gdb configured without curses still requires curses Date: Wed, 26 Jul 2017 19:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jim at realintent dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00087.txt.bz2 Content-length: 758 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21842 Bug ID: 21842 Summary: gdb configured without curses still requires curses Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jim at realintent dot com Target Milestone: --- If I configure gdb (version 7.12.1) with either --without-curses or=20 --with-curses=3Dno, the build will still look for and include the curses=20 header file and will still link with -lncurses. I'll attach the config.log which shows this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21651-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 26 19:22:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 52186 invoked by alias); 26 Jul 2017 19:22:13 -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 52158 invoked by uid 48); 26 Jul 2017 19:22:13 -0000 From: "jim at realintent dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21842] gdb configured without curses still requires curses Date: Wed, 26 Jul 2017 19:22: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jim at realintent dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q3/txt/msg00088.txt.bz2 Content-length: 392 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21842 --- Comment #1 from Jim Foley --- Created attachment 10286 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10286&action=3Ded= it config.log config.log file showing --without-curses but including curses in the build. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21652-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jul 26 20:46:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 43153 invoked by alias); 26 Jul 2017 20:45:56 -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 43008 invoked by uid 48); 26 Jul 2017 20:45:38 -0000 From: "vivekrane at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21829] GDB internal error: Assertion `name[prefix_len + 1] == ':'' failed. Date: Wed, 26 Jul 2017 20:45: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.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vivekrane at gmail 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00089.txt.bz2 Content-length: 568 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21829 Vivek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Vivek --- I checked with 8.0 and looks like the bug is gone. Thanks for letting me kn= ow! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21653-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jul 27 13:39:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 83144 invoked by alias); 27 Jul 2017 13:39:11 -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 82789 invoked by uid 48); 27 Jul 2017 13:39:11 -0000 From: "ghjghj530-bubu at yahoo dot de" To: gdb-prs@sourceware.org Subject: [Bug c++/19436] C++11 ABI tag does not work Date: Thu, 27 Jul 2017 13: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: ghjghj530-bubu at yahoo dot de 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: cc 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: 2017-q3/txt/msg00090.txt.bz2 Content-length: 868 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19436 ghjghj530-bubu at yahoo dot de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ghjghj530-bubu at yahoo do= t de --- Comment #2 from ghjghj530-bubu at yahoo dot de --- Still a problem in GCC 6.3, GDB 7.10 -> With -D_GLIBCXX_USE_CXX11_ABI=3D1 (gdb) p fooVar p fooVar No symbol "fooVar" in current context. (gdb) info variables ... std::__cxx11::string fooVar[abi:cxx11]; .... (gdb) p 'fooVar[abi:cxx11]' p 'fooVar[abi:cxx11]' $2 =3D "hello world" -> With -D_GLIBCXX_USE_CXX11_ABI=3D0 (gdb) p fooVar p fooVar $2 =3D "hello world" Any chance somebody can have a look at this? thanks! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21654-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jul 27 15:20:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 58361 invoked by alias); 27 Jul 2017 15:20:06 -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 57859 invoked by uid 48); 27 Jul 2017 15:20:06 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21851] New: Loading i386 binary after running x86_64 one results in abort "arch-utils.c:524: internal-error: could not select an architecture automatically" Date: Thu, 27 Jul 2017 15:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00091.txt.bz2 Content-length: 1554 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21851 Bug ID: 21851 Summary: Loading i386 binary after running x86_64 one results in abort "arch-utils.c:524: internal-error: could not select an architecture automatically" Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: b7.10110111 at gmail dot com Target Milestone: --- Crash happens on GDB 7.11 as well as 8.0.50.20170727-git. Steps to reproduce: gcc -x c -g -o test32 -m32 - <<< 'int main(){}' gcc -x c -g -o test64 -m64 - <<< 'int main(){}' gdb -q -ex 'set confirm off' ./test64 -ex start -ex 'file ./test32' -ex 'set arch auto' Output from GDB: Reading symbols from ./test64...done. Temporary breakpoint 1 at 0x4004ff: file , line 1. Starting program: /tmp/test64=20 Temporary breakpoint 1, main () at :1 1 : No such file or directory. warning: Selected architecture i386 is not compatible with reported target architecture i386:x86-64 Architecture of file not recognized. warning: Selected architecture i386 is not compatible with reported target architecture i386:x86-64 arch-utils.c:524: internal-error: could not select an architecture automatically A problem internal to GDB has been detected, further debugging may prove unreliable. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21655-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jul 27 21:36:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 121646 invoked by alias); 27 Jul 2017 21:36:12 -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 121474 invoked by uid 48); 27 Jul 2017 21:36:11 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21852] New: Remote run without specifying a local binary crashes GDB Date: Thu, 27 Jul 2017 21:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00092.txt.bz2 Content-length: 1512 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21852 Bug ID: 21852 Summary: Remote run without specifying a local binary crashes GDB Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: remote Assignee: unassigned at sourceware dot org Reporter: simon.marchi at ericsson dot com Target Milestone: --- Start gdbserver: $ ./gdbserver/gdbserver --once --multi :1234 And start gdb like this: $ ./gdb -nx -q --data-directory=3Ddata-directory -ex "tar ext :1234" -ex "s= et remote exec-file /bin/ls" -ex r Remote debugging using :1234 Starting program:=20=20 Reading /bin/ls from remote target... warning: File transfers from remote targets can be slow. Use "set sysroot" = to access files locally instead. Reading /bin/ls from remote target... Reading symbols from target:/bin/ls...Reading /bin/bc0fb9b3f60f72bbad3c5a1d24c9e2a1fde775.debug from remote target... Reading /bin/.debug/bc0fb9b3f60f72bbad3c5a1d24c9e2a1fde775.debug from remote target... (no debugging symbols found)...done. /home/emaisin/src/binutils-gdb/gdb/thread.c:1609: internal-error: scoped_restore_current_thread::scoped_restore_current_thread(): Assertion `= tp !=3D NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21656-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 28 05:34:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78336 invoked by alias); 28 Jul 2017 05:34:08 -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 77320 invoked by uid 48); 28 Jul 2017 05:32:10 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21852] Remote run without specifying a local binary crashes GDB Date: Fri, 28 Jul 2017 05:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com 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: cc 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: 2017-q3/txt/msg00093.txt.bz2 Content-length: 579 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21852 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #1 from Sergio Durigan Junior --- I've also stumbled upon this a while ago, but forgot to report. Anyway, I'm interested in this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21657-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 28 05:36:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 82598 invoked by alias); 28 Jul 2017 05:36:10 -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 82562 invoked by uid 48); 28 Jul 2017 05:36:08 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21852] Remote run without specifying a local binary crashes GDB Date: Fri, 28 Jul 2017 05:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com 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: 2017-q3/txt/msg00094.txt.bz2 Content-length: 309 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21852 --- Comment #2 from Sergio Durigan Junior --- I've also stumbled upon this a while ago, but forgot to report. Anyway, I'm interested in this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21658-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 28 09:17:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 80910 invoked by alias); 28 Jul 2017 09:17:04 -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 80878 invoked by uid 48); 28 Jul 2017 09:17:03 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21855] New: finish in a function returning a typedef to void compiled with clang crashes GDB Date: Fri, 28 Jul 2017 09:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00095.txt.bz2 Content-length: 1349 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21855 Bug ID: 21855 Summary: finish in a function returning a typedef to void compiled with clang crashes GDB Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: simon.marchi at ericsson dot com Target Milestone: --- Test program: typedef void foo; static foo func () { } int main () { func (); return 0; } Compiled with: $ clang-3.8 test.c -o test -g3 -O0 Crashes like this: $ ./gdb -q --data-directory=3Ddata-directory -nx test -ex "tb func" -ex r -= ex fin=20 Reading symbols from test...done. Temporary breakpoint 1 at 0x400504: file test.c, line 6. Starting program: /home/emaisin/Videos/test=20 Temporary breakpoint 1, func () at test.c:6 6 } Run till exit from #0 func () at test.c:6 /home/emaisin/src/binutils-gdb/gdb/infcmd.c:1610: internal-error: value* get_return_value(value*, type*): Assertion `TYPE_CODE (value_type) !=3D TYPE_CODE_VOID' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21659-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 28 09:18:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 85493 invoked by alias); 28 Jul 2017 09:18:43 -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 85451 invoked by uid 48); 28 Jul 2017 09:18:41 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21856] New: --data-directory doesn't expand ~ Date: Fri, 28 Jul 2017 09:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00096.txt.bz2 Content-length: 849 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21856 Bug ID: 21856 Summary: --data-directory doesn't expand ~ Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: simon.marchi at ericsson dot com Target Milestone: --- I can launch GDB like this: $ ~/build/binutils-gdb/gdb/gdb --data-directory=3D$HOME/build/binutils-gdb/gdb/data-directory but not like this $ ~/build/binutils-gdb/gdb/gdb --data-directory=3D~/build/binutils-gdb/gdb/data-directory Warning: ~/build/binutils-gdb/gdb/data-directory: No such file or directory. GDB should probably tilde-expand the path. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21660-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 28 16:44:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 10802 invoked by alias); 28 Jul 2017 16:44:56 -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 10716 invoked by uid 48); 28 Jul 2017 16:44:53 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/19436] C++11 ABI tag does not work Date: Fri, 28 Jul 2017 16:44: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: keiths at redhat dot com 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: cc 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: 2017-q3/txt/msg00097.txt.bz2 Content-length: 637 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19436 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com --- Comment #3 from Keith Seitz --- There is a patch series that has been submitted by Pedro which should addre= ss (or at least mitigate) this issue. See https://sourceware.org/ml/gdb-patches/2017-06/msg00012.html . --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21661-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 28 16:46:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 11915 invoked by alias); 28 Jul 2017 16:46:03 -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 11669 invoked by uid 48); 28 Jul 2017 16:45:45 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21829] GDB internal error: Assertion `name[prefix_len + 1] == ':'' failed. Date: Fri, 28 Jul 2017 16:46: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.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution 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: 2017-q3/txt/msg00098.txt.bz2 Content-length: 504 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21829 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |DUPLICATE --- Comment #3 from Keith Seitz --- *** This bug has been marked as a duplicate of bug 18303 *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21662-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jul 28 16:46:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 12444 invoked by alias); 28 Jul 2017 16:46:27 -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 12285 invoked by uid 48); 28 Jul 2017 16:46:19 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/18303] Assertation: -breakpoint-insert with windows paths of file in non-current directory Date: Fri, 28 Jul 2017 16:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.9 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: donbreazeal at gmail dot com X-Bugzilla-Target-Milestone: 7.12 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q3/txt/msg00099.txt.bz2 Content-length: 520 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18303 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vivekrane at gmail dot com --- Comment #9 from Keith Seitz --- *** Bug 21829 has been marked as a duplicate of this bug. *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21663-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jul 29 11:15:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 70559 invoked by alias); 29 Jul 2017 11:15:53 -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 70322 invoked by uid 48); 29 Jul 2017 11:15:42 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/16242] print format for hex float Date: Sat, 29 Jul 2017 11:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: b7.10110111 at gmail dot com 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: cc 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: 2017-q3/txt/msg00100.txt.bz2 Content-length: 397 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16242 Ruslan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |b7.10110111 at gmail dot c= om --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21664-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jul 29 11:24:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78521 invoked by alias); 29 Jul 2017 11:24:56 -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 78308 invoked by uid 48); 29 Jul 2017 11:24:44 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/16242] print format for hex float Date: Sat, 29 Jul 2017 11:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: b7.10110111 at gmail dot com 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: 2017-q3/txt/msg00101.txt.bz2 Content-length: 646 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16242 --- Comment #2 from Ruslan --- There is /z format, which for floating-point values appears to print raw da= ta. The only problem is that this isn't documented. Instead, `help x` says "x(h= ex)" and "z(hex, zero padded on the left)", without mentioning that the former converts to integer while the latter prints true raw value. I guess the fix for this would be to make the documentation correct and to = add some tests checking that the documentation matches actual behavior. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21665-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jul 29 17:55:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23561 invoked by alias); 29 Jul 2017 17:55:00 -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 23524 invoked by uid 48); 29 Jul 2017 17:54:59 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug cli/16242] print format for hex float Date: Sat, 29 Jul 2017 17:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q3/txt/msg00102.txt.bz2 Content-length: 799 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16242 --- Comment #3 from Tom Tromey --- (In reply to Ruslan from comment #2) > There is /z format, which for floating-point values appears to print raw > data. The only problem is that this isn't documented. Instead, `help x` s= ays > "x(hex)" and "z(hex, zero padded on the left)", without mentioning that t= he > former converts to integer while the latter prints true raw value. >=20 > I guess the fix for this would be to make the documentation correct and to > add some tests checking that the documentation matches actual behavior. I think that would be good to do, but hex float is not the same as printing the raw bits in hex. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21666-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jul 29 18:50:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 65583 invoked by alias); 29 Jul 2017 18:50:19 -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 65545 invoked by uid 48); 29 Jul 2017 18:50:17 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/16242] print format for hex float Date: Sat, 29 Jul 2017 18:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: b7.10110111 at gmail dot com 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: 2017-q3/txt/msg00103.txt.bz2 Content-length: 236 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16242 --- Comment #4 from Ruslan --- Ah, I misunderstood this bug report. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21667-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jul 29 20:36:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 37549 invoked by alias); 29 Jul 2017 20:36:20 -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 37525 invoked by uid 48); 29 Jul 2017 20:36:20 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/16213] -var-update still keeps "var1." Date: Sat, 29 Jul 2017 20:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00104.txt.bz2 Content-length: 604 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16213 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Jan Kratochvil --- Seems to be fixed with: eclipse-cdt-9.2.1-2.fc25.x86_64 gdb-7.12.1-48.fc25.x86_64 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21668-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jul 30 11:33:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 119005 invoked by alias); 30 Jul 2017 11:33:20 -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 118974 invoked by uid 48); 30 Jul 2017 11:33:19 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/21865] New: MMX registers are presented in wrong order when FSW.TOP!=0 Date: Sun, 30 Jul 2017 11:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00105.txt.bz2 Content-length: 1685 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21865 Bug ID: 21865 Summary: MMX registers are presented in wrong order when FSW.TOP!=3D0 Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: b7.10110111 at gmail dot com Target Milestone: --- Consider the following x86 assembly program (compiled by FASM): format ELF executable fldpi fldl2t fldl2e fldln2 fldlg2 int3 movd eax, mm0 movd ecx, mm1 movd edx, mm2 movd ebx, mm3 xor ebx, ebx mov eax, 1 int 0x80 Running it with gdb -q ./test -ex r -ex 'p/x {$mm0.v2_int32[0],$mm1.v2_int32[0],$mm2.v2_int32[0],$mm3.v2_int32[0]}' -ex = 'si 4' -ex 'p/x {$eax,$ecx,$edx,$ebx}' -ex 'p/x {$mm0.v2_int32[0],$mm1.v2_int32[0],$mm2.v2_int32[0],$mm3.v2_int32[0]}' gives us: Program received signal SIGTRAP, Trace/breakpoint trap. 0x0804805f in ?? () $1 =3D {0xcd1b8afe, 0x2168c235, 0x0, 0x0} 0x0804806b in ?? () $2 =3D {0x0, 0x0, 0x0, 0xfbcff799} $3 =3D {0x0, 0x0, 0x0, 0xfbcff799} The $1 result is wrong, since MMn registers are actually mapped to Rn FPU registers, while GDB seems to somehow think of the mapping being dependent = on STn or something. If I set $fstat=3D0 (so that TOP=3D0), then the order of = MMn register values on subsequent printing is correct. The result $3 is right, but it is only due to the access to MM0 by MOVD instruction, which clears TOP field in $fstat. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21669-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jul 30 14:56:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 47458 invoked by alias); 30 Jul 2017 14:56:06 -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 47422 invoked by uid 48); 30 Jul 2017 14:56:04 -0000 From: "benno.fuenfstueck at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21866] New: Stepi does not make progress with memory error Date: Sun, 30 Jul 2017 14:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: benno.fuenfstueck at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00106.txt.bz2 Content-length: 1276 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21866 Bug ID: 21866 Summary: Stepi does not make progress with memory error Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: benno.fuenfstueck at gmail dot com Target Milestone: --- On certain programs, GDB's `stepi` command does not work anymore (neither do `break` or any of the examine commands). Only `continue` works in this situation): 0x080485ee in main () (gdb) display/i $pc 1: x/i $pc =3D> 0x80485ee : mov DWORD PTR ds:0x804a020,0x2 (gdb) si Cannot access memory at address 0xdeadbeeb (gdb) si Cannot access memory at address 0xdeadbeeb (gdb) bt Python Exception Cannot access memory at address 0xdeadbeeb:=20 #0 0x080485ee in main () Cannot access memory at address 0xdeadbeeb (gdb) p/x $pc $1 =3D 0x80485ee (gdb) si Cannot access memory at address 0xdeadbeeb (gdb) p/x $pc $2 =3D 0x80485ee (gdb)=20 Program to reproduce: https://gist.github.com/bennofs/84b5007fe807d59bbadc13c0b6ae2849 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21670-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jul 30 14:58:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 55589 invoked by alias); 30 Jul 2017 14:58:09 -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 54912 invoked by uid 48); 30 Jul 2017 14:58:07 -0000 From: "benno.fuenfstueck at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21866] Stepi does not make progress with memory error Date: Sun, 30 Jul 2017 14:58: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: benno.fuenfstueck at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q3/txt/msg00107.txt.bz2 Content-length: 360 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21866 --- Comment #1 from Benno F=C3=BCnfst=C3=BCck --- Created attachment 10293 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10293&action=3Ded= it Example program to reproduce --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21671-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jul 30 15:02:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 87792 invoked by alias); 30 Jul 2017 15:02:10 -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 87710 invoked by uid 48); 30 Jul 2017 15:02:08 -0000 From: "benno.fuenfstueck at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21866] Stepi does not make progress with memory error Date: Sun, 30 Jul 2017 15:02: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: benno.fuenfstueck at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00108.txt.bz2 Content-length: 424 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21866 --- Comment #2 from Benno F=C3=BCnfst=C3=BCck --- Note that the bug is not specific to the `int 3` instruction, I just insert= ed that to make reproducing simpler (you can manually set a breakpoint and reproduce it with other instructions as well) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21672-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jul 30 22:37:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 52200 invoked by alias); 30 Jul 2017 22:37:06 -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 52171 invoked by uid 48); 30 Jul 2017 22:37:06 -0000 From: "scott at mathworks dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/16577] GDB crash on attempted read from deleted shared library Date: Sun, 30 Jul 2017 22:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: scott at mathworks dot com 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: cc 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: 2017-q3/txt/msg00109.txt.bz2 Content-length: 503 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16577 Scott French changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scott at mathworks dot com --- Comment #2 from Scott French --- This is still happening as of gdb 8.0. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21673-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 31 07:59:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 76184 invoked by alias); 31 Jul 2017 07:59:13 -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 76150 invoked by uid 48); 31 Jul 2017 07:59:12 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21436] frame filter should allow duplicated underlying frames Date: Mon, 31 Jul 2017 07:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pmuldoon at redhat dot com X-Bugzilla-Status: WAITING 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: bug_status 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: 2017-q3/txt/msg00110.txt.bz2 Content-length: 378 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21436 Phil Muldoon changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21674-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 31 15:21:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64791 invoked by alias); 31 Jul 2017 15:21:44 -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 64318 invoked by uid 48); 31 Jul 2017 15:21:44 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21870] New: aarc64: Leftover uncleared debug registers Date: Mon, 31 Jul 2017 15:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q3/txt/msg00111.txt.bz2 Content-length: 1039 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21870 Bug ID: 21870 Summary: aarc64: Leftover uncleared debug registers Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Target Milestone: --- Created attachment 10295 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10295&action=3Ded= it .c standalone testcase Testcase verifies if the debug registers are cleared after it is run. Standalone execution is OK but being spawned from GDB reports an error: # ./gdb ~/aarch64-watchpoint GNU gdb (GDB) 8.0.50.20170731-git (gdb) run Starting program: /root/aarch64-watchpoint=20 aarch64-watchpoint: aarch64-watchpoint.c:91: set_watchpoint: Assertion `(((dreg_state.dbg_regs[0].ctrl) >> 5) & 0xff) =3D=3D 0' failed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21675-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 31 15:22:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 7105 invoked by alias); 31 Jul 2017 15:22:31 -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 6113 invoked by uid 48); 31 Jul 2017 15:22:30 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21870] aarc64: Leftover uncleared debug registers Date: Mon, 31 Jul 2017 15:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: cc 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: 2017-q3/txt/msg00112.txt.bz2 Content-length: 488 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21870 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jan.kratochvil at redhat d= ot com, | |qiyao at gcc dot gnu.org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21676-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 31 15:23:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27142 invoked by alias); 31 Jul 2017 15:22:59 -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 27113 invoked by uid 48); 31 Jul 2017 15:22:58 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21870] aarch64: Leftover uncleared debug registers Date: Mon, 31 Jul 2017 15:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: cf_gcctarget cf_gcchost short_desc 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: 2017-q3/txt/msg00113.txt.bz2 Content-length: 597 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21870 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |aarch64-linux Host| |aarch64-linux Summary|aarc64: Leftover uncleared |aarch64: Leftover uncleared |debug registers |debug registers --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21677-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 31 20:03:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 25029 invoked by alias); 31 Jul 2017 20:03:57 -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 24987 invoked by uid 48); 31 Jul 2017 20:03:56 -0000 From: "ihkose at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] New: GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Mon, 31 Jul 2017 20:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ihkose at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q3/txt/msg00114.txt.bz2 Content-length: 1706 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 Bug ID: 21873 Summary: GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Product: gdb Version: 7.4 Status: UNCONFIRMED Severity: critical Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: ihkose at gmail dot com Target Milestone: --- Created attachment 10297 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10297&action=3Ded= it Core file that has crash info I am debugging my firmware on MAX32630FTHR target using openocd server. Whi= le running the firmware, i hit the Ctrl+C keystore to be stop the firmware and enable command line in TUI mode. It crashes suddenly after the key pressing= . I am running it on Ubuntu 16.04. The target links are here. https://www.maximintegrated.com/en/products/digital/microcontrollers/MAX326= 30FTHR.html https://developer.mbed.org/platforms/MAX32630FTHR/ My gdbinit content are here. define connect set trace-commands on set remotetimeout 1000000000 set logging on target remote localhost:3333 end define reset monitor reset halt c end define settings # set unlimited string size while print set print elements 0 end define program monitor reset halt load build/output.elf monitor reset halt end define run_openocd target remote | openocd scripts/jtag/max3263x_hdk.cfg -c "gdb_port pipe; log_output ./openocd.log" end connect settings program c --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21678-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 31 20:04:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 25900 invoked by alias); 31 Jul 2017 20:04:29 -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 25872 invoked by uid 48); 31 Jul 2017 20:04:28 -0000 From: "ihkose at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Mon, 31 Jul 2017 20:04: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ihkose at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00115.txt.bz2 Content-length: 385 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 Ismail changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ihkose at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21679-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 31 20:06:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31884 invoked by alias); 31 Jul 2017 20:06:43 -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 31848 invoked by uid 48); 31 Jul 2017 20:06:42 -0000 From: "ihkose at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Mon, 31 Jul 2017 20:06: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ihkose at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00116.txt.bz2 Content-length: 791 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 --- Comment #1 from Ismail --- Here is the arm-none-eabi-gdb -version command output. GNU gdb (GNU Tools for ARM Embedded Processors) 7.4.1.20130913-cvs Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=3Dx86_64-linux-gnu --target=3Darm-none-e= abi". For bug reporting instructions, please see: . --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21681-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 31 20:07:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 33275 invoked by alias); 31 Jul 2017 20:07:46 -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 33251 invoked by uid 48); 31 Jul 2017 20:07:45 -0000 From: "ihkose at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Mon, 31 Jul 2017 20:07: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ihkose at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cf_gcchost 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: 2017-q3/txt/msg00118.txt.bz2 Content-length: 374 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 Ismail changed: What |Removed |Added ---------------------------------------------------------------------------- Host| |Ubuntu 16.04 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21680-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 31 20:07:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 32364 invoked by alias); 31 Jul 2017 20:07:04 -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 32324 invoked by uid 48); 31 Jul 2017 20:07:04 -0000 From: "ihkose at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Mon, 31 Jul 2017 20:07: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ihkose at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00117.txt.bz2 Content-length: 791 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 --- Comment #2 from Ismail --- Here is the arm-none-eabi-gdb -version command output. GNU gdb (GNU Tools for ARM Embedded Processors) 7.4.1.20130913-cvs Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=3Dx86_64-linux-gnu --target=3Darm-none-e= abi". For bug reporting instructions, please see: . --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21682-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 31 20:08:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 33907 invoked by alias); 31 Jul 2017 20:08:09 -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 33882 invoked by uid 48); 31 Jul 2017 20:08:09 -0000 From: "ihkose at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Mon, 31 Jul 2017 20:08: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ihkose at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: priority 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: 2017-q3/txt/msg00119.txt.bz2 Content-length: 364 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 Ismail changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21683-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jul 31 21:17:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 120077 invoked by alias); 31 Jul 2017 21:17:25 -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 120051 invoked by uid 48); 31 Jul 2017 21:17:25 -0000 From: "ihkose at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Mon, 31 Jul 2017 21:17: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ihkose at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 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: 2017-q3/txt/msg00120.txt.bz2 Content-length: 304 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 --- Comment #3 from Ismail --- 5154 segmentation fault (core dumped) arm-none-eabi-gdb -tui ./build/output.elf -x scripts/gdb/max32630.gdb --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21684-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 01 09:25:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 71567 invoked by alias); 1 Aug 2017 09:25:41 -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 71523 invoked by uid 48); 1 Aug 2017 09:25:39 -0000 From: "leszek at swirski dot co.uk" To: gdb-prs@sourceware.org Subject: [Bug symtab/20899] "dwarf2_string_attr" does not check for "DW_FORM_GNU_str_index" Date: Tue, 01 Aug 2017 09:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: leszek at swirski dot co.uk X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00121.txt.bz2 Content-length: 337 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20899 --- Comment #2 from Lech Swirski --- Thanks Raphael, I've now started the "proper" patch submission process: https://sourceware.org/ml/gdb-patches/2017-08/msg00003.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21685-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 01 14:46:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 123665 invoked by alias); 1 Aug 2017 14:46:49 -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 123267 invoked by uid 48); 1 Aug 2017 14:46:48 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/21875] New: GDB/MI shouldn't print repeating values as Date: Tue, 01 Aug 2017 14:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00122.txt.bz2 Content-length: 1413 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21875 Bug ID: 21875 Summary: GDB/MI shouldn't print repeating values as Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: mi Assignee: unassigned at sourceware dot org Reporter: b7.10110111 at gmail dot com Target Milestone: --- Tested with GDB 8.0.50.20170801-git on x86_64 Linux system. Test command: cat << EOF | gdb -i=3Dmi -file-exec-and-symbols /bin/true -break-insert *0 -exec-run -data-list-register-values r 40 EOF The -data-list-register-values command prints SSE register as ^done,register-values=3D[{number=3D"40",value=3D"{v4_float =3D {0x00000000,= 0x00000000, 0x00000000, 0x00000000}, v2_double =3D {0x0000000000000000, 0x0000000000000= 000}, v16_int8 =3D {0x00 }, v8_int16 =3D {0x0000, 0x0000, 0x000= 0, 0x0000, 0x0000, 0x0000, 0x0000, 0x0000}, v4_int32 =3D {0x00000000, 0x000000= 00, 0x00000000, 0x00000000}, v2_int64 =3D {0x0000000000000000, 0x00000000000000= 00}, uint128 =3D 0x00000000000000000000000000000000}"}] Notice the "v16_int8 =3D {0x00 }". This is not really machine-friendly. All repetitions should be explicitly spelled out. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21686-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 01 14:46:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127362 invoked by alias); 1 Aug 2017 14:46:59 -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 127220 invoked by uid 48); 1 Aug 2017 14:46:58 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tdep/21818] disassemble with v5TE remote: Assertion `info->mach == bfd_get_mach (exec_bfd)' failed. Date: Tue, 01 Aug 2017 14:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to 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: 2017-q3/txt/msg00123.txt.bz2 Content-length: 547 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21818 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org Assignee|unassigned at sourceware dot org |qiyao at gcc dot gn= u.org --- Comment #1 from Yao Qi --- I'll take a look. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21687-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 01 14:55:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23056 invoked by alias); 1 Aug 2017 14:55:50 -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 23007 invoked by uid 48); 1 Aug 2017 14:55:49 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Tue, 01 Aug 2017 14:55: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q3/txt/msg00124.txt.bz2 Content-length: 880 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org --- Comment #4 from Yao Qi --- GDB 7.4.1 is too old. Could you please try GDB 8.0, and build it from sour= ce?=20 If the crash is still there, use your host gdb to debug arm-none-eabi gdb, = and show the stack backtrace of crash. That will be very helpful to triage the issue. $ mkdir build-gdb $ cd build-gdb $ ../binutils-gdb/configure --target=3Darm-none-eabi --disable-binutils --disable-ld --disable-gold --disable-gprof $ make then you can use ./gdb/gdb. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21688-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 01 18:20:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 25919 invoked by alias); 1 Aug 2017 18:20:28 -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 25861 invoked by uid 48); 1 Aug 2017 18:20:28 -0000 From: "guillaume at morinfr dot org" To: gdb-prs@sourceware.org Subject: [Bug c++/20020] GDB segfault on printing objects Date: Tue, 01 Aug 2017 18:20: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: guillaume at morinfr dot org 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: cc 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: 2017-q3/txt/msg00125.txt.bz2 Content-length: 406 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20020 Guillaume Morin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guillaume at morinfr dot o= rg --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21689-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 01 18:26:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 50641 invoked by alias); 1 Aug 2017 18:26:04 -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 50305 invoked by uid 48); 1 Aug 2017 18:26:03 -0000 From: "guillaume at morinfr dot org" To: gdb-prs@sourceware.org Subject: [Bug c++/20607] gdb printing google's protobuf object will crash Date: Tue, 01 Aug 2017 18:26: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: guillaume at morinfr dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.11.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q3/txt/msg00126.txt.bz2 Content-length: 406 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20607 Guillaume Morin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guillaume at morinfr dot o= rg --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21690-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 01 19:32:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4825 invoked by alias); 1 Aug 2017 19:32:57 -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 4734 invoked by uid 48); 1 Aug 2017 19:32:52 -0000 From: "ihkose at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Tue, 01 Aug 2017 19:32: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ihkose at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 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: 2017-q3/txt/msg00127.txt.bz2 Content-length: 2243 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 --- Comment #5 from Ismail --- I downloaded gdb from the following read only repository and configure it w= ith your parameters and then built it. GDB 8 git clone git://sourceware.org/git/binutils-gdb.git Here is the GDB version output $ gdb/gdb --version=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 GNU gdb (GDB) 8.0.50.20170801-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=3Dx86_64-pc-linux-gnu --target=3Darm-non= e-eabi". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". I dont know if generated bin files has issues. I use the following gcc comp= iler version. I sometimes see dwarf errors. But, the firmware itself works well. arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.7.4 20130913 (release) [ARM/embedded-4_7-branch revision 202601] Copyright (C) 2012 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I am not sure how to debug the gdb itself. It seems little bit complicated.= I have to use openocd in order to run and debug the program on the target.=20 I will have one GDB as runner and debugger, the second one that works in TUI mode will connect to openocd and debug the firmware.=20 I would be happy if you can give me some documents/guidance to debug it. Thanks Ismail --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21691-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 01 21:25:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 98190 invoked by alias); 1 Aug 2017 21:25:15 -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 98062 invoked by uid 48); 1 Aug 2017 21:25:02 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Tue, 01 Aug 2017 21:25: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 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: 2017-q3/txt/msg00128.txt.bz2 Content-length: 1173 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 --- Comment #6 from Yao Qi --- (In reply to Ismail from comment #5) >=20 > I am not sure how to debug the gdb itself. It seems little bit complicate= d. > I have to use openocd in order to run and debug the program on the target= .=20 >=20 > I will have one GDB as runner and debugger, the second one that works in = TUI > mode will connect to openocd and debug the firmware.=20 >=20 > I would be happy if you can give me some documents/guidance to debug it. Use the built GDB as usual. Start it in TUI mode, and connect to OpenOCD.= =20 Start a new terminal, check the pid of the arm-none-eabi-gdb, like, $ ps -elf | grep gdb then start your host GDB (shipped in your distro) to attach the arm-none-eabi-gdb, like $ gdb -p PID (gdb) continue and then go back the first terminal (using arm-none-eabi-gdb in TUI mode).= =20 Continue use it to reproduce the crash. If it crashes, the host GDB will c= atch the SIGSEGV signal, and you can show the stack backtrace of crash, and exam= ine why it crashes. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21692-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 01 21:49:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 65828 invoked by alias); 1 Aug 2017 21:49:24 -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 65800 invoked by uid 48); 1 Aug 2017 21:49:23 -0000 From: "ihkose at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Tue, 01 Aug 2017 21:49: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ihkose at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 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: 2017-q3/txt/msg00129.txt.bz2 Content-length: 489 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 --- Comment #7 from Ismail --- I did that works to start debugging the GDB. But, the only problem is when I attach the GDB that will be debugged does not responses to anything includi= ng Ctrl+C keystrokes. The other debugger GDB gets stop. In order to continue, i need to go to the other terminal and continue. That's weird. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21693-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 07:32:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53004 invoked by alias); 2 Aug 2017 07:32:14 -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 52969 invoked by uid 48); 2 Aug 2017 07:32:12 -0000 From: "ciro.santilli at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/21044] Text or color mark on current line in code listing Date: Wed, 02 Aug 2017 07:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: ciro.santilli at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00130.txt.bz2 Content-length: 1104 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21044 Ciro Santilli changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ciro.santilli at gmail dot= com --- Comment #3 from Ciro Santilli --- I really want this, especially with a full line color highlight like TUI. TUI breaks when you have large stdout, and with vim bindings. I'm currently using GDB dashboard just for this feature basically: https://github.com/cyrus-and/gdb-dashboard The problem is that requires Python scripting, which is not available on so= me targets. If the highlight were possible natively, I would just put a list on hook-st= op, and everything would be perfect. Another advantage over TUI is that the shell history keeps the debug path if you want to scroll up. Then just use the "edit" command as well to make things even better. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21694-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 07:44:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 21155 invoked by alias); 2 Aug 2017 07:44:36 -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 21058 invoked by uid 48); 2 Aug 2017 07:44:33 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Wed, 02 Aug 2017 07:44: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 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: 2017-q3/txt/msg00131.txt.bz2 Content-length: 788 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 --- Comment #8 from Yao Qi --- (In reply to Ismail from comment #7) > I did that works to start debugging the GDB. But, the only problem is whe= n I > attach the GDB that will be debugged does not responses to anything > including Ctrl+C keystrokes. The other debugger GDB gets stop. In order to > continue, i need to go to the other terminal and continue. That's weird. Maybe it is easier to get coredump. If you don't debug arm-none-eabi-gdb, = does it still crash? If it does, you can get the coredump, and then, start your host gdb like this, $ gdb ./gdb ./core and gdb command "bt" can tell us why gdb is crashed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21695-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 09:46:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68157 invoked by alias); 2 Aug 2017 09:46:18 -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 67881 invoked by uid 48); 2 Aug 2017 09:45:55 -0000 From: "skimo-bugzilla2 at kotnet dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/20603] gdb fails to properly restart a rust test executable Date: Wed, 02 Aug 2017 09:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: skimo-bugzilla2 at kotnet dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q3/txt/msg00132.txt.bz2 Content-length: 2154 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20603 Sven Verdoolaege changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |skimo-bugzilla2 at kotnet = dot org --- Comment #2 from Sven Verdoolaege --- I can reliably reproduce a very similar problem on Ubuntu 17.04, although it does not seem to be related to rust. In particular, as shown below, gdb fails to restart properly after recompiling the program that is being debugged: $ cat test.c int main() { return 0; } $ gcc -g -o test test.c $ gdb ./test GNU gdb (GDB) 8.0 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./test...done. (gdb) b main Breakpoint 1 at 0x664: file test.c, line 3. (gdb) r Starting program: /tmp/test=20 Breakpoint 1, main () at test.c:3 3 return 0; (gdb) shell $ gcc -g -o test test.c $ exit exit (gdb) r The program being debugged has been started already. Start it from the beginning? (y or n) y `/tmp/test' has changed; re-reading symbols. Error in re-setting breakpoint 1: Cannot access memory at address 0x555555554660 Starting program: /tmp/test=20 warning: Probes-based dynamic linker interface failed. Reverting to original interface. [Inferior 1 (process 27665) exited normally] --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21696-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 13:49:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 71592 invoked by alias); 2 Aug 2017 13:49:01 -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 70768 invoked by uid 48); 2 Aug 2017 13:48:59 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20603] gdb fails to properly restart a rust test executable Date: Wed, 02 Aug 2017 13:49: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: REOPENED 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: bug_status component resolution 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: 2017-q3/txt/msg00133.txt.bz2 Content-length: 613 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20603 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Component|rust |gdb Resolution|WORKSFORME |--- --- Comment #3 from Tom Tromey --- Sven asked me to reopen this given that he has a reproducer. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21697-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 17:44:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 104187 invoked by alias); 2 Aug 2017 17:44:12 -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 103416 invoked by uid 48); 2 Aug 2017 17:44:11 -0000 From: "macro@linux-mips.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21886] New: Compressed MIPS code debugging impossible due to memory breakpoint misplacement Date: Wed, 02 Aug 2017 17:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: macro@linux-mips.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: macro@linux-mips.org X-Bugzilla-Target-Milestone: 8.0.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget Message-ID: 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: 2017-q3/txt/msg00134.txt.bz2 Content-length: 1350 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21886 Bug ID: 21886 Summary: Compressed MIPS code debugging impossible due to memory breakpoint misplacement Product: gdb Version: HEAD Status: NEW Severity: critical Priority: P1 Component: breakpoints Assignee: macro@linux-mips.org Reporter: macro@linux-mips.org Target Milestone: 8.0.1 Target: mips*-*-* As from commit cd6c3b4ffc4e ("New gdbarch methods breakpoint_kind_from_pc=20 and sw_breakpoint_from_kind") it is not possible to debug compressed MIPS code due to the ISA bit being retained in the memory breakpoint location. Consequently the software breakpoint instruction is patched in starting from the second byte of the intended original instruction and therefore corrupts code being debugged. This usually renders debugging impossible, e.g. with MIPS16 code and the Linux target any dynamic executable crashes: (gdb) continue Continuing. Program received signal SIGBUS, Bus error. _dl_debug_initialize (ldbase=3D0, ns=3D0) at dl-debug.c:51 51 r =3D &_r_debug; (gdb) See for a proposed fix. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21698-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 17:44:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4963 invoked by alias); 2 Aug 2017 17:44:45 -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 4941 invoked by uid 48); 2 Aug 2017 17:44:44 -0000 From: "macro@linux-mips.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21886] Compressed MIPS code debugging impossible due to memory breakpoint misplacement Date: Wed, 02 Aug 2017 17:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: macro@linux-mips.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: macro@linux-mips.org X-Bugzilla-Target-Milestone: 8.0.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status 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: 2017-q3/txt/msg00135.txt.bz2 Content-length: 378 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21886 Maciej W. Rozycki changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21699-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 18:25:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 50604 invoked by alias); 2 Aug 2017 18:25:12 -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 102395 invoked by uid 48); 2 Aug 2017 18:24:30 -0000 From: "guillaume at morinfr dot org" To: gdb-prs@sourceware.org Subject: [Bug c++/20020] GDB segfault on printing objects Date: Wed, 02 Aug 2017 18:25: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: guillaume at morinfr dot org 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: 2017-q3/txt/msg00136.txt.bz2 Content-length: 5801 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20020 --- Comment #2 from Guillaume Morin --- We have started experiencing a similar crash when we switched to g++ 7.1 wi= th c++17 semantics. When gdb tries to print a "static constexpr", it triggers= a "error reading variable: Missing ELF symbol" exception and then crashes at = the same place as the original reporter. This seems to happen with every releas= e at least from gdb 7.11. I also built the git master and could reproduce the problem as well. It's not entirely clear that this is the same exact bug but the crash backt= race is completely similar I have a simple reproducer: $ cat main.cpp=20 struct A { static constexpr const char *a =3D "a"; void foo() { } }; int main(void) { A a; a.foo(); } Compile with g++ 7.1 with C++17 semantics: g++-7 -std=3Dc++17 -g -o main ma= in.cpp Now run it with gdb: $ gdb main GNU gdb (Debian 7.11.1-2~bpo8+1) 7.11.1 (...) (gdb) b A::foo Breakpoint 1 at 0x40055e: file main.cpp, line 6. (gdb) r Starting program: main=20 Breakpoint 1, A::foo (this=3D0x7fffffffe09f) at main.cpp:6 6 void foo() { } (gdb) print *this Segmentation fault (core dumped) If I patch the source with the workaround mentioned by Thilo (i.e set the p= tr to NULL in the catch block and call cp_print_static_field() only if v is not NULL), it does not crash: (gdb) print *this $1 =3D {static a =3D } If I compile the program above with the default c++ semantics(c++ 14), I ge= t=20 (gdb) print *this $1 =3D {static a =3D } With the current git master (8.0.50.20170801-git), this is the backtrace I = get for the gdb crash: Program terminated with signal SIGSEGV, Segmentation fault. #0 value_entirely_covered_by_range_vector (value=3D0x0, ranges=3D0x90) at value.c:401 401 if (value->lazy) (gdb) bt #0 value_entirely_covered_by_range_vector (value=3D0x0, ranges=3D0x90) at value.c:401 #1 0x0000000000563282 in cp_print_static_field (options=3D, recurse=3D, stream=3D, val=3D, type=3D) at cp-valprint.c:640 #2 cp_print_value_fields (type=3D0x0, real_type=3D0x90, real_type@entry=3D= 0xf1cd00, offset=3Doffset@entry=3D0, address=3D0, address@entry=3D140737488347295, stream=3D0xf194c0, recurse=3D16998736, recurse@entry=3D0, val=3D0xf8fc00, options=3D0x7fffffffda20, dont_print_vb=3D0x0, dont_print_statmem=3D0) at cp-valprint.c:335 #3 0x00000000005639ca in cp_print_value_fields_rtti (type=3D, type@entry=3D0xf1cd00, valaddr=3D0xf6a330 "", offset=3Doffset@entry=3D0, address=3D140737488347295, stream=3D0xf194c0, recurse=3D0, val=3D0xf8fc00, options=3D0x7fffffffda20, dont_print_vb=3D0x0, dont_print_statmem=3D0) at cp-valprint.c:456 #4 0x000000000054bf52 in c_val_print_struct (type=3D0xf1cd00, valaddr=3D, embedded_offset=3D0, address=3D, stream=3D, recurse=3D, original_value=3D0xf8fc00, options=3D0x7fffffffd= a20) at c-valprint.c:412 #5 0x000000000054c46f in c_val_print (type=3D0xf1cd00, embedded_offset=3D0, address=3D0, stream=3D0xf194c0, recurse=3D0, original_value=3D0xf8fc00, options=3D0x7fffffffda20) at c-valprint.c:530 #6 0x0000000000699270 in val_print (type=3D0x0, type@entry=3D0xf1cd00, embedded_offset=3D0, address=3D15846656, address@entry=3D140737488347295, stream=3Dstream@entry=3D0xf194c0, recurse=3D32767, recurse@entry=3D0, val=3Dval@entry=3D0xf8fc00, options=3D0x7fffffffdae0, language=3D0x843b80 ) at valprint.c:1109 #7 0x000000000054cc1f in c_value_print (val=3D0xf8fc00, stream=3D0xf194c0, options=3D) at c-valprint.c:702 #8 0x0000000000622218 in print_value (val=3Dval@entry=3D0xf8fc00, fmtp=3Dfmtp@entry=3D0x7fffffffdbf0) at ./printcmd.c:1179 #9 0x00000000006222ae in print_command_1 (exp=3D0xd3e366 "*this", voidprin= t=3D1) at ./printcmd.c:1207 #10 0x00000000004999e9 in cmd_func (cmd=3D, args=3D, from_tty=3D) at cli/cli-decode.c:1902 #11 0x0000000000684ce6 in execute_command (p=3D, p@entry=3D0= xd3e360 "print *this", from_tty=3D1) at top.c:675 #12 0x00000000005ab7dc in command_handler (command=3D0xd3e360 "print *this"= ) at event-top.c:590 #13 0x00000000005abad8 in command_line_handler (rl=3D) at event-top.c:780 #14 0x00000000005aae2c in gdb_rl_callback_handler (rl=3D0xf6a330 "") at event-top.c:213 #15 0x00000000006c6698 in rl_callback_read_char () at callback.c:220 #16 0x00000000005aad6e in gdb_rl_callback_read_char_wrapper_noexcept () at event-top.c:175 #17 0x00000000005aadd9 in gdb_rl_callback_read_char_wrapper (client_data=3D) at event-top.c:192 #18 0x00000000005ab300 in stdin_event_handler (error=3D, client_data=3D0xd3ebc0) at event-top.c:518 #19 0x00000000005aa215 in gdb_wait_for_event (block=3Dblock@entry=3D1) at event-loop.c:859 #20 0x00000000005aa3d3 in gdb_do_one_event () at event-loop.c:347 #21 0x00000000005aa485 in start_event_loop () at event-loop.c:371 #22 0x00000000005ff408 in captured_command_loop (data=3Ddata@entry=3D0x0) at main.c:325 #23 0x00000000005ac3c3 in catch_errors (func=3Dfunc@entry=3D0x5ff3e0 , func_args=3Dfunc_args@entry=3D0x0, errstring=3Derrstring@entry=3D0x7f0ede "", mask=3Dmask@entry=3DRETURN_MASK_= ALL) at exceptions.c:236 #24 0x0000000000600366 in captured_main (data=3D0x7fffffffdec0) at main.c:1= 150 #25 gdb_main (args=3Dargs@entry=3D0x7fffffffdff0) at main.c:1160 #26 0x0000000000411ae5 in main (argc=3D, argv=3D) at gdb.c:32 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21701-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 19:55:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 129353 invoked by alias); 2 Aug 2017 19:55:47 -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 129312 invoked by uid 48); 2 Aug 2017 19:55:45 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/20020] GDB segfault on printing objects Date: Wed, 02 Aug 2017 19:55: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: keiths at redhat dot com 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: cc 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: 2017-q3/txt/msg00138.txt.bz2 Content-length: 3145 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20020 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com --- Comment #3 from Keith Seitz --- (In reply to Thilo Voertler from comment #1) > Any comment would be appreciated Thank you for chasing this down. I have investigated this a little, and I s= ee this hunk from commit 492d29ea is probably the culprit: @@ -313,18 +313,21 @@ cp_print_value_fields (struct type *type, struct type *rea l_type, } else if (field_is_static (&TYPE_FIELD (type, i))) { - volatile struct gdb_exception ex; struct value *v =3D NULL; - TRY_CATCH (ex, RETURN_MASK_ERROR) + TRY { v =3D value_static_field (type, i); } - if (ex.reason < 0) - fprintf_filtered (stream, - _(""), - ex.message); + CATCH (ex, RETURN_MASK_ERROR) + { + fprintf_filtered (stream, + _(""), + ex.message); + } + END_CATCH + cp_print_static_field (TYPE_FIELD_TYPE (type, i), v, stream, recurse + 1, options); Your patch should fix that. Would you care to submit your (properly formatt= ed) patch (and ChangeLog) to gdb-patches@sourceware.org? (In reply to Guillaume Morin from comment #2) > We have started experiencing a similar crash when we switched to g++ 7.1 > with c++17 semantics. When gdb tries to print a "static constexpr", it > triggers a "error reading variable: Missing ELF symbol" exception and then > crashes at the same place as the original reporter. This seems to happen > with every release at least from gdb 7.11. I also built the git master and > could reproduce the problem as well. This appears consistent with this bug, thank you for reporting. > I have a simple reproducer: >=20 Awesome! Thank you very much for this! > Now run it with gdb: I tried your test case (using gcc 7.0-20160916 (experimental) -- the gdb c++ compile branch) and did not reproduce the crash. I will try building someth= ing newer. Can you give me the exact compiler version you are using? [g++ -v] > If I compile the program above with the default c++ semantics(c++ 14), I = get=20 > (gdb) print *this > $1 =3D {static a =3D } >=20 That appears to be another issue (which I have also investigated). I'm goin= g to open a new bug about this, c++/21892. Let's move the "optimized out" discus= sion there. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21700-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 19:55:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 128319 invoked by alias); 2 Aug 2017 19:55:07 -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 128295 invoked by uid 48); 2 Aug 2017 19:55:06 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21892] New: value of constexpr variable is "" (no optimization) Date: Wed, 02 Aug 2017 19:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00137.txt.bz2 Content-length: 1155 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21892 Bug ID: 21892 Summary: value of constexpr variable is "" (no optimization) Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: keiths at redhat dot com Target Milestone: --- Reported originally in c++/20020 ----- snip ----- $ cat main.cpp=20 struct A { static constexpr const char *a =3D "a"; void foo() { } }; int main(void) { A a; a.foo(); } Compile with g++ 7.1 with C++17 semantics: g++-7 -std=3Dc++17 -g -o main ma= in.cpp Now run it with gdb: $ gdb main GNU gdb (Debian 7.11.1-2~bpo8+1) 7.11.1 (...) (gdb) b A::foo Breakpoint 1 at 0x40055e: file main.cpp, line 6. (gdb) r Starting program: main=20 Breakpoint 1, A::foo (this=3D0x7fffffffe09f) at main.cpp:6 6 void foo() { } (gdb) print *this $1 =3D {static a =3D } ----- end ----- --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21702-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 20:18:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63878 invoked by alias); 2 Aug 2017 20:18:07 -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 63782 invoked by uid 48); 2 Aug 2017 20:18:06 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/20020] GDB segfault on printing objects Date: Wed, 02 Aug 2017 20:18: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: keiths at redhat dot com 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: 2017-q3/txt/msg00139.txt.bz2 Content-length: 667 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20020 --- Comment #4 from Keith Seitz --- (In reply to Keith Seitz from comment #3) > (In reply to Thilo Voertler from comment #1) > > Any comment would be appreciated >=20 > Thank you for chasing this down. I have investigated this a little, and I > see this hunk from commit 492d29ea is probably the culprit: Actually to be pedantic, that's not the problem. The NULL check was already missing by the time that patch was applied. It *does* appear in commit ee86786c, so something between the two erased it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21703-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 21:20:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 72285 invoked by alias); 2 Aug 2017 21:20:20 -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 72261 invoked by uid 48); 2 Aug 2017 21:20:18 -0000 From: "jrmuizel at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21893] New: template_argument(0) gives syntax error Date: Wed, 02 Aug 2017 21:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jrmuizel at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00140.txt.bz2 Content-length: 827 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21893 Bug ID: 21893 Summary: template_argument(0) gives syntax error Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: jrmuizel at gmail dot com Target Milestone: --- Given the following program: use std::collections::HashMap; fn main() { let m : HashMap> =3D HashMap::new(); println!("Hello, world! {:?}", m); } print(gdb.parse_and_eval("m")["table"].type.template_argument(0)) gives a: RuntimeError: syntax error, near `>>' Error while executing Python code. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21704-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 21:20:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 72720 invoked by alias); 2 Aug 2017 21:20:36 -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 72686 invoked by uid 48); 2 Aug 2017 21:20:36 -0000 From: "jrmuizel at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21893] template_argument(0) gives syntax error Date: Wed, 02 Aug 2017 21:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jrmuizel at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00141.txt.bz2 Content-length: 402 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21893 Jeff Muizelaar changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21705-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 22:34:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 45014 invoked by alias); 2 Aug 2017 22:34:06 -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 40140 invoked by uid 48); 2 Aug 2017 22:34:02 -0000 From: "ihkose at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Wed, 02 Aug 2017 22:34: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ihkose at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 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: 2017-q3/txt/msg00142.txt.bz2 Content-length: 4303 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 --- Comment #9 from Ismail --- Here is the backtrace output. Hopefully, It may be helpful to locate the bu= g. Thanks (gdb) bt #0 strlen () at ../sysdeps/x86_64/strlen.S:106 #1 0x000000000061222b in find_and_open_source (filename=3D0x20c , dirname=3D0x303078302829745f , fullname=3Dfullname@entry=3D0x2912d28) at ../../binutils-gdb/gdb/source= .c:1098 #2 0x000000000061235c in symtab_to_fullname (s=3D0x2912cf0) at ../../binutils-gdb/gdb/source.c:1167 #3 0x0000000000477b44 in tui_update_breakpoint_info (win=3Dwin@entry=3D0x2= 539a90, current_only=3Dcurrent_only@entry=3D0) at ../../binutils-gdb/gdb/tui/tui-winsource.c:461 #4 0x000000000047816b in tui_update_source_window_as_is (win_info=3D0x2539= a90, gdbarch=3Dgdbarch@entry=3D0x271f920, s=3Ds@entry=3D0x25cf840, line_or_addr= =3D..., noerror=3Dnoerror@entry=3D0) at ../../binutils-gdb/gdb/tui/tui-winsource.c:107 #5 0x0000000000474147 in tui_show_symtab_source (gdbarch=3Dgdbarch@entry=3D0x271f920, s=3Ds@entry=3D0x25cf840, line=3D..., noerror=3Dnoerror@entry=3D0) at ../../binutils-gdb/gdb/tui/tui-source.c:328 #6 0x0000000000477f63 in tui_update_source_windows_with_addr (gdbarch=3D0x271f920, addr=3D79676) at ../../binutils-gdb/gdb/tui/tui-winsource.c:156 #7 0x000000000047801a in tui_display_main () at ../../binutils-gdb/gdb/tui/tui-winsource.c:56 #8 0x00000000005dd80d in generic_observer_notify (args=3D0x7ffd6a7b4270, subject=3D) at ../../binutils-gdb/gdb/observer.c:167 #9 observer_notify_new_objfile (objfile=3Dobjfile@entry=3D0x0) at ./observer.inc:582 #10 0x0000000000621d1e in clear_symtab_users (add_flags=3D..., add_flags@entry=3D...) at ../../binutils-gdb/gdb/symfile.c:2957 #11 0x0000000000624807 in reread_symbols () at ../../binutils-gdb/gdb/symfile.c:2694 #12 0x0000000000624a02 in load_command (arg=3D0x0, from_tty=3D1) at ../../binutils-gdb/gdb/symfile.c:1835 #13 0x00000000004589f9 in cmd_func (cmd=3D, args=3D, from_tty=3D) at ../../binutils-gdb/gdb/cli/cli-decode.c:1902 #14 0x0000000000650c70 in execute_command (p=3D, p@entry=3D0= x2539730 "", from_tty=3D1) at ../../binutils-gdb/gdb/top.c:675 #15 0x000000000057247c in command_handler (command=3D0x2539730 "") at ../../binutils-gdb/gdb/event-top.c:590 #16 0x0000000000572798 in command_line_handler (rl=3D) at ../../binutils-gdb/gdb/event-top.c:780 #17 0x0000000000571a2c in gdb_rl_callback_handler (rl=3D0x254be30 "") at ../../binutils-gdb/gdb/event-top.c:213 #18 0x00000000006d06e3 in rl_callback_read_char () at ../../binutils-gdb/readline/callback.c:220 #19 0x000000000057195e in gdb_rl_callback_read_char_wrapper_noexcept () at ../../binutils-gdb/gdb/event-top.c:175 #20 0x00000000005719d9 in gdb_rl_callback_read_char_wrapper (client_data=3D) at ../../binutils-gdb/gdb/event-top.c:192 #21 0x0000000000571f60 in stdin_event_handler (error=3D, client_data=3D0x2340df0) at ../../binutils-gdb/gdb/event-top.c:518 #22 0x0000000000570d5d in gdb_wait_for_event (block=3Dblock@entry=3D1) at ../../binutils-gdb/gdb/event-loop.c:859 #23 0x0000000000570eb2 in gdb_do_one_event () at ../../binutils-gdb/gdb/event-loop.c:347 #24 0x000000000057100e in gdb_do_one_event () at ../../binutils-gdb/gdb/event-loop.c:304 #25 start_event_loop () at ../../binutils-gdb/gdb/event-loop.c:371 #26 0x00000000005c8038 in captured_command_loop (data=3Ddata@entry=3D0x0) at ../../binutils-gdb/gdb/main.c:325 #27 0x00000000005730e3 in catch_errors (func=3Dfunc@entry=3D0x5c8010 , func_args=3Dfunc_args@entry=3D0x0, errstring=3Derrstring@entry=3D0x80c1b0 "", mask=3Dmask@entry=3DRETURN_MASK_= ALL) at ../../binutils-gdb/gdb/exceptions.c:236 #28 0x00000000005c8ef6 in captured_main (data=3D0x7ffd6a7b47b0) at ../../binutils-gdb/gdb/main.c:1150 #29 gdb_main (args=3Dargs@entry=3D0x7ffd6a7b48f0) at ../../binutils-gdb/gdb/main.c:1160 #30 0x000000000040e015 in main (argc=3D, argv=3D) at ../../binutils-gdb/gdb/gdb.c:32 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21706-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 22:40:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78418 invoked by alias); 2 Aug 2017 22:40:18 -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 78390 invoked by uid 48); 2 Aug 2017 22:40:17 -0000 From: "ihkose at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Wed, 02 Aug 2017 22:40: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ihkose at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 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: 2017-q3/txt/msg00143.txt.bz2 Content-length: 13778 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 --- Comment #10 from Ismail --- =E2=94=821030=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20 =E2=94=82 =E2=94=821031 int=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=82 =E2=94=821032 find_and_open_source (const char *filename,=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=82 =E2=94=821033 const char *dirname,=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=82 =E2=94=821034 char **fullname)=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=82 =E2=94=821035 {=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=82 ............. =20=20 =E2=94=8C=E2=94=80=E2=94=80../../binutils-gdb/gdb/source.c=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80 =E2=94=821052 xfree (*fullname);=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 =E2=94=821053 *fullname =3D rewritten_fullname;=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821054 }=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821055=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 =E2=94=821056 result =3D gdb_open_cloexec (*fullname, OPEN_MODE= , 0);=20=20=20=20=20=20=20=20=20=20 =E2=94=821057 if (result >=3D 0)=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 =E2=94=821058 {=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821059 char *lpath =3D gdb_realpath (*fullname);=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821060=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 =E2=94=821061 xfree (*fullname);=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 =E2=94=821062 *fullname =3D lpath;=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20 =E2=94=821063 return result;=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20 =E2=94=821064 }=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821065=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 =E2=94=821066 /* Didn't work -- free old one, try again. */=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821067 xfree (*fullname);=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20 =E2=94=821068 *fullname =3D NULL;=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 =E2=94=821069 }=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821070=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 =E2=94=821071 cleanup =3D make_cleanup (null_cleanup, NULL);=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821072=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 =E2=94=821073 if (dirname !=3D NULL)=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 =E2=94=821074 {=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821075 /* If necessary, rewrite the compilation director= y name according=20=20=20=20=20=20=20=20 =E2=94=821076 to the source path substitution rules specifie= d by the user. */=20=20=20=20=20=20 =E2=94=821077=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 =E2=94=821078 char *rewritten_dirname =3D rewrite_source_path (= dirname);=20=20=20=20=20=20 =E2=94=821079=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 =E2=94=821080 if (rewritten_dirname !=3D NULL)=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20 =E2=94=821081 {=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821082 make_cleanup (xfree, rewritten_dirname);=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821083 dirname =3D rewritten_dirname;=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821084 }=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821085=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 =E2=94=821086 /* Replace a path entry of $cdir with the compila= tion directory=20=20=20=20=20=20=20=20=20=20 =E2=94=821087 name. */=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821088 #define cdir_len 5=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20 =E2=94=821089 /* We cast strstr's result in case an ANSIhole ha= s made it const,=20=20=20=20=20=20=20=20 =E2=94=821090 which produces a "required warning" when assig= ned to a nonconst. */=20=20 =E2=94=821091 p =3D (char *) strstr (source_path, "$cdir");=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821092 if (p && (p =3D=3D path || p[-1] =3D=3D DIRNAME_S= EPARATOR)=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821093 && (p[cdir_len] =3D=3D DIRNAME_SEPARATOR || p= [cdir_len] =3D=3D '\0'))=20=20=20=20=20=20=20=20 =E2=94=821094 {=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821095 int len;=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821096=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 =E2=94=821097 path =3D (char *)=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20 >=E2=94=821098 alloca (strlen (source_path) + 1 + strlen (= dirname) + 1); /*CRASHES HERE */=20=20=20=20 =E2=94=821099 len =3D p - source_path;=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 =E2=94=821100 strncpy (path, source_path, len); /* Befo= re $cdir */=20=20 =E2=94=821101 strcpy (path + len, dirname); /* new = stuff */=20=20=20=20=20 =E2=94=821102 strcat (path + len, source_path + len + cdir_= len); /* After=20=20=20=20=20=20=20 =E2=94=821103=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20 $cdir */=20=20=20=20 =E2=94=821104 }=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =E2=94=821105 }=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =20=20 =E2=94=94=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80 multi-thre Thread 0x7f03cf6957 In: find_and_open_source=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 #20 0x00000000005719d9 in gdb_rl_callback_read_char_wrapper (client_ #21 0x0000000000571f60 in stdin_event_handler (error=3D #22 0x0000000000570d5d in gdb_wait_for_event (block=3Dblock@entry=3D1) a #23 0x0000000000570eb2 in gdb_do_one_event () at ../../binutils-gdb/ #24 0x000000000057100e in gdb_do_one_event () at ../../binutils-gdb/ #25 start_event_loop () at ../../binutils-gdb/gdb/event-loop.c:371 #26 0x00000000005c8038 in captured_command_loop (data=3Ddata@entry=3D0x0 #27 0x00000000005730e3 in catch_errors (func=3Dfunc@entry=3D0x5c8010 to continue, or q to quit--- #29 gdb_main (args=3Dargs@entry=3D0x7ffd6a7b48f0) at ../../binutils-gdb/ #30 0x000000000040e015 in main (argc=3D, argv=3D>From gdb-prs-return-21707-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 22:49:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 6498 invoked by alias); 2 Aug 2017 22:49:29 -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 5620 invoked by uid 48); 2 Aug 2017 22:49:28 -0000 From: "ihkose at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Wed, 02 Aug 2017 22:49: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ihkose at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 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: 2017-q3/txt/msg00144.txt.bz2 Content-length: 279 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 --- Comment #11 from Ismail --- Let me try to debug the issue. Perhaps I may figure out the issue and send a patch. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21708-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 23:00:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 119673 invoked by alias); 2 Aug 2017 23:00:00 -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 119634 invoked by uid 48); 2 Aug 2017 23:00:00 -0000 From: "guillaume at morinfr dot org" To: gdb-prs@sourceware.org Subject: [Bug c++/20020] GDB segfault on printing objects Date: Wed, 02 Aug 2017 23:00: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: guillaume at morinfr dot org 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: 2017-q3/txt/msg00145.txt.bz2 Content-length: 2007 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20020 --- Comment #5 from Guillaume Morin --- (In reply to Keith Seitz from comment #3) > I tried your test case (using gcc 7.0-20160916 (experimental) -- the gdb = c++ > compile branch) and did not reproduce the crash. I will try building > something newer. Can you give me the exact compiler version you are using? This is Debian's gcc 7.1.0-10 (from testing) Using built-in specs. COLLECT_GCC=3Dg++-7 COLLECT_LTO_WRAPPER=3D/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper OFFLOAD_TARGET_NAMES=3Dnvptx-none OFFLOAD_TARGET_DEFAULT=3D1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion=3D'Debian 7.1.0-10' --with-bugurl=3Dfile:///usr/share/doc/gcc-7/README.Bugs --enable-languages=3Dc,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=3D/u= sr --with-gcc-major-version-only --program-suffix=3D-7 --program-prefix=3Dx86_64-linux-gnu- --enable-shared --enable-linker-build-= id --libexecdir=3D/usr/lib --without-included-gettext --enable-threads=3Dposix --libdir=3D/usr/lib --enable-nls --with-sysroot=3D/ --enable-clocale=3Dgnu --enable-libstdcxx-debug --enable-libstdcxx-time=3Dyes --with-default-libstdcxx-abi=3Dnew --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=3Dauto --enable-multiarch --disable-werror --with-arch-32=3Di686 --with-abi=3Dm64 --with-multilib-list=3Dm32,m64,mx32 --enable-multilib --with-tune=3Dgeneric --enable-offload-targets=3Dnvptx-none --without-cuda-driver --enable-checking=3Drelease --build=3Dx86_64-linux-gnu --host=3Dx86_64-linu= x-gnu --target=3Dx86_64-linux-gnu Thread model: posix gcc version 7.1.0 (Debian 7.1.0-10) I tested in a Debian testing chroot and reproduced it without any issues. S= o I believe it should be easy for you to reproduce with a similar version --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21709-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 23:03:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4244 invoked by alias); 2 Aug 2017 23:03:45 -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 4214 invoked by uid 48); 2 Aug 2017 23:03:44 -0000 From: "guillaume at morinfr dot org" To: gdb-prs@sourceware.org Subject: [Bug c++/21892] value of constexpr variable is "" (no optimization) Date: Wed, 02 Aug 2017 23:03: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: guillaume at morinfr dot org 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: cc 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: 2017-q3/txt/msg00146.txt.bz2 Content-length: 704 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21892 Guillaume Morin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guillaume at morinfr dot o= rg --- Comment #1 from Guillaume Morin --- Just a note: I get *optimized out* with c++14 (the default), not c++17 So you want to compile with "g++-7 -g -o main main.cpp" to reproduce this b= ug.=20 If you add -std=3Dc++17, you're reproducing the segfault in c++/20020 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21710-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 02 23:34:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 18156 invoked by alias); 2 Aug 2017 23:34:54 -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 18127 invoked by uid 48); 2 Aug 2017 23:34:54 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21893] template_argument(0) gives syntax error Date: Wed, 02 Aug 2017 23:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00147.txt.bz2 Content-length: 676 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21893 --- Comment #1 from Tom Tromey --- This happens because rustc doesn't emit DW_AT_template_type_param for the HashMap type. Then it interacts with a weird gdb/python thing -- in earlier times gcc also did not emit this template information, so the first iteration of this python layer code hacked around the omission by parsing the C++ name and extracting the type names. This code remains, so it still tries to do this as a fallback. I think this is apropos: https://github.com/rust-lang/rust/issues/9224 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21711-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 03 09:59:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 112272 invoked by alias); 3 Aug 2017 09:59:49 -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 112239 invoked by uid 48); 3 Aug 2017 09:59:48 -0000 From: "vuvova at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/13326] Need support for C++ method call for a gdb.Value object from within python Date: Thu, 03 Aug 2017 09:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.3 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vuvova at gmail dot com 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: cc 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: 2017-q3/txt/msg00148.txt.bz2 Content-length: 693 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13326 vuvova at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vuvova at gmail dot com --- Comment #1 from vuvova at gmail dot com --- Same for TYPE_CODE_INTERNAL_FUNCTION: (gdb) pi a=3Dgdb.parse_and_eval('$_streq') (gdb) pi print a.type.code =3D=3D gdb.TYPE_CODE_INTERNAL_FUNCTION True (gdb) pi a("1","2") Python Exception Value is not callable (not TYPE_CODE_FUNC).: --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21712-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 03 14:27:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 82793 invoked by alias); 3 Aug 2017 14:27:01 -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 82254 invoked by uid 48); 3 Aug 2017 14:27:00 -0000 From: "guillaume at morinfr dot org" To: gdb-prs@sourceware.org Subject: [Bug c++/21892] value of constexpr variable is "" (no optimization) Date: Thu, 03 Aug 2017 14:27: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: guillaume at morinfr dot org 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: 2017-q3/txt/msg00149.txt.bz2 Content-length: 404 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21892 --- Comment #2 from Guillaume Morin --- To be 100% clear with the c++/20020 segfault fixed and c++17, you get "{sta= tic a =3D }" With c++14, you get "{static a =3D }" --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21713-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 03 19:44:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20600 invoked by alias); 3 Aug 2017 19:44:29 -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 20195 invoked by uid 48); 3 Aug 2017 19:44:28 -0000 From: "guillaume at morinfr dot org" To: gdb-prs@sourceware.org Subject: [Bug c++/20020] GDB segfault on printing objects Date: Thu, 03 Aug 2017 19:44: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: guillaume at morinfr dot org 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: 2017-q3/txt/msg00150.txt.bz2 Content-length: 297 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20020 --- Comment #6 from Guillaume Morin --- Note: https://sourceware.org/bugzilla/show_bug.cgi?id=3D20607 is probably t= he same bug --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21715-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 03 23:16:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23747 invoked by alias); 3 Aug 2017 23:16:09 -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 23713 invoked by uid 48); 3 Aug 2017 23:16:08 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug python/21436] frame filter should allow duplicated underlying frames Date: Thu, 03 Aug 2017 23:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: WAITING 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: 2017-q3/txt/msg00152.txt.bz2 Content-length: 302 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21436 --- Comment #3 from Tom Tromey --- > So do you have a smaller test case? Nope, I'm afraid not. I will see if I can make a dummy one. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21714-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 03 23:16:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23459 invoked by alias); 3 Aug 2017 23:16:03 -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 23331 invoked by uid 48); 3 Aug 2017 23:15:54 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug python/21213] garbarge collector eats gdb.selected_thread() Date: Thu, 03 Aug 2017 23:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_status cf_reconfirmed_on cc everconfirmed 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: 2017-q3/txt/msg00151.txt.bz2 Content-length: 786 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21213 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-08-03 CC| |tromey at sourceware dot o= rg Ever confirmed|0 |1 --- Comment #1 from Tom Tromey --- This does look like the correct fix. I suggest following the gdb contribution instructions to send the patch in. The instructions are in the source tree. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21716-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 04 00:47:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 10424 invoked by alias); 4 Aug 2017 00:47:27 -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 9580 invoked by uid 48); 4 Aug 2017 00:47:26 -0000 From: "jrmuizel at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/21893] template_argument(0) gives syntax error Date: Fri, 04 Aug 2017 00:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jrmuizel at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00153.txt.bz2 Content-length: 316 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21893 --- Comment #2 from Jeff Muizelaar --- https://github.com/rust-lang/rust/issues/9224 seems to suggest that rustc is emitting DW_AT_template_type_param --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21717-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 04 18:43:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 86826 invoked by alias); 4 Aug 2017 18:43:31 -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 86554 invoked by uid 48); 4 Aug 2017 18:43:30 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21906] New: "nexti" command behaves as "stepi" when remote debugging Date: Fri, 04 Aug 2017 18:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00154.txt.bz2 Content-length: 1984 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21906 Bug ID: 21906 Summary: "nexti" command behaves as "stepi" when remote debugging Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: remote Assignee: unassigned at sourceware dot org Reporter: b7.10110111 at gmail dot com Target Milestone: --- This reproduces with i386 and x86_64 hosts and i386 as well as ARM remote targets. Here's a sample session with i386 host and remote with GDB 8.0.50.20170804-= git: gdb -q -ex 'target remote eeepc:9999' -ex 'x/3i $pc' -ex ni -ex ni Remote debugging using eeepc:9999 warning: while parsing target description (at line 24): Missing end value warning: Could not load XML target description; ignoring Reading /bin/true from remote target... warning: File transfers from remote targets can be slow. Use "set sysroot" = to access files locally instead. Reading /bin/true from remote target... Reading symbols from target:/bin/true...Reading /bin/.debug/true from remote target... (no debugging symbols found)...done. Reading /lib/ld-linux.so.2 from remote target... Reading /lib/ld-linux.so.2 from remote target... Reading symbols from target:/lib/ld-linux.so.2...Reading /lib/ld-2.19.so fr= om remote target... Reading /lib/.debug/ld-2.19.so from remote target... (no debugging symbols found)...done. 0xb7fdf0d0 in ?? () from target:/lib/ld-linux.so.2 =3D> 0xb7fdf0d0: mov eax,esp 0xb7fdf0d2: call 0xb7fe2790 0xb7fdf0d7: mov edi,eax 0xb7fdf0d2 in ?? () from target:/lib/ld-linux.so.2 0xb7fe2790 in ?? () from target:/lib/ld-linux.so.2 Note that the call to 0xb7fe2790 has been entered as if the last command was "stepi" instead of "ni". Instead, the last line of output should have had 0xb7fdf0d7 as address, not 0xb7fe2790. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21718-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 04 21:31:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 106158 invoked by alias); 4 Aug 2017 21:31:57 -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 106111 invoked by uid 48); 4 Aug 2017 21:31:57 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/21907] New: Dn/Qn registers are printed wrongly by "info reg" on a system with NEON support Date: Fri, 04 Aug 2017 21:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00155.txt.bz2 Content-length: 1806 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21907 Bug ID: 21907 Summary: Dn/Qn registers are printed wrongly by "info reg" on a system with NEON support Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: b7.10110111 at gmail dot com Target Milestone: --- Tested on remotely-debugged program on Lenovo A328. To reproduce, run this command: arm-unknown-linux-gnueabihf-gdb -q -ex 'target remote 192.168.0.235:9999' -= ex 'p $d0' -ex 'info reg d0' Then it outputs: $1 =3D { u8 =3D {49, 105, 110, 47, 116, 114, 117, 101},=20 u16 =3D {26929, 12142, 29300, 25973},=20 u32 =3D {795765041, 1702195828},=20 u64 =3D 7310875413443406129,=20 f32 =3D {2.16833454e-10, 7.24431922e+22},=20 f64 =3D 5.5621884095669346e+180 } d0 { u8 =3D {0x31, 0x69, 0x6e, 0x2f, 0x74, 0x72, 0x75, 0x65},=20 u16 =3D {0x6931, 0x2f6e, 0x7274, 0x6575},=20 u32 =3D {0x2f6e6931, 0x65757274},=20 u64 =3D 0x657572742f6e6931,=20 f32 =3D {0x0, 0x0},=20 f64 =3D 0x8000000000000000 } Notice how the first case ("p" command) is OK, while the second (info reg) gives wrong values for f32 and f64. Looks like they are first converted to integers, and then printed in hex format. They should at the very least not= be converted, and additionally maybe printed in natural format as well as raw. Similar pattern is with $q0-$q15 registers. Data from /proc/cpuinfo: Processor : ARMv7 Processor rev 3 (v7l) Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls v= fpv4 idiva idivt --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21719-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 05 21:49:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41459 invoked by alias); 5 Aug 2017 21:49:21 -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 38474 invoked by uid 48); 5 Aug 2017 21:49:19 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21893] template_argument(0) gives syntax error Date: Sat, 05 Aug 2017 21:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00156.txt.bz2 Content-length: 1070 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21893 --- Comment #3 from Tom Tromey --- (In reply to Jeff Muizelaar from comment #2) > https://github.com/rust-lang/rust/issues/9224 seems to suggest that rustc= is > emitting DW_AT_template_type_param Not always. Consider this test (from that bug): pub struct Generic(T); pub struct Normal(i32); fn main () { let generic =3D Generic(10); let normal =3D Normal(10); generic; normal; } Here the DWARF for Generic is just: <2><81>: Abbrev Number: 6 (DW_TAG_structure_type) <82> DW_AT_name : (indirect string, offset: 0x6e): Generic <86> DW_AT_byte_size : 4 <87> Unknown AT value: 88: 4 <3><88>: Abbrev Number: 7 (DW_TAG_member) <89> DW_AT_name : (indirect string, offset: 0x66): __0 <8d> DW_AT_type : <0xa8> <91> Unknown AT value: 88: 4 <92> DW_AT_data_member_location: 0 <3><93>: Abbrev Number: 0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21720-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 05 22:01:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 45419 invoked by alias); 5 Aug 2017 22:01:34 -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 45050 invoked by uid 48); 5 Aug 2017 22:01:33 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/21185] add i128 and u128 support to rust Date: Sat, 05 Aug 2017 22:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q3/txt/msg00157.txt.bz2 Content-length: 304 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21185 --- Comment #12 from Tom Tromey --- Printing got fixed in bug 16225, but I think I want to leave this one open to implement arithmetic. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21721-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 07 07:54:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 104177 invoked by alias); 7 Aug 2017 07:54:43 -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 104112 invoked by uid 48); 7 Aug 2017 07:54:43 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21755] No "step" event Date: Mon, 07 Aug 2017 07:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: pmuldoon at redhat dot com 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: bug_status cf_reconfirmed_on cc everconfirmed bug_severity 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: 2017-q3/txt/msg00158.txt.bz2 Content-length: 804 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21755 Phil Muldoon changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-08-07 CC| |pmuldoon at redhat dot com Ever confirmed|0 |1 Severity|normal |enhancement --- Comment #1 from Phil Muldoon --- Inferior control is not yet implemented in GDB Python unfortunately.=20 Hopefully, that will change in the future. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21722-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 07 10:35:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 38935 invoked by alias); 7 Aug 2017 10:35:13 -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 38896 invoked by uid 48); 7 Aug 2017 10:35:12 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/13326] Need support for C++ method call for a gdb.Value object from within python Date: Mon, 07 Aug 2017 10:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.3 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pmuldoon at redhat dot com 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: cc 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: 2017-q3/txt/msg00159.txt.bz2 Content-length: 1706 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13326 Phil Muldoon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmuldoon at redhat dot com --- Comment #2 from Phil Muldoon --- I looked at the code and, indeed, class method invocation is barred. I susp= ect the reason for this is two-fold. Currently, in GDB we evaluate all the hairy C++ stuff in the evaluation parser. The Python inferior function call stuff just calls "call_function_by_hand". This causes, firstly, the separation fr= om the "this" reference which is passed as a parameter to the function. If you remove the restriction in the code, GDB will complain about an incorrect nu= mber of arguments because the hidden "this" argument is missing. Secondly, all of the extra "shaping" for the function call is missing like overload resoluti= on.=20 So feature missing confirmed. I'm not sure when it will be worked on as it = is a non-trivial issue. Perhaps when the C++ification progresses to the evaluati= on parser it might be possible without duplicating large amounts of code. There is a workaround available. You can use gdb.parse_and_eval to get the value by using it to call the function in question. This uses the evaluation parser and correctly sets up for the C++ function call. So something like: python f =3D gdb.parse_and_eval("someObject.someFunction()")=20 This will call that function and return the value back to GDB as a Python value. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21723-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 07 10:49:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35596 invoked by alias); 7 Aug 2017 10:49:04 -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 35553 invoked by uid 48); 7 Aug 2017 10:49:02 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21755] No "step" event Date: Mon, 07 Aug 2017 10:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: pmuldoon at redhat dot com 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: 2017-q3/txt/msg00160.txt.bz2 Content-length: 512 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21755 --- Comment #2 from Phil Muldoon --- Oops I do apologize, this was about stepping events, not actual stepping. W= e do have both "stop" and "continue" events. There is indeed no concrete step ev= ent. But I suspect a step would just emit a "continue" then "stop" event anyway? https://www.sourceware.org/gdb/onlinedocs/gdb.html#Events-In-Python --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21724-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 07 14:54:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 120926 invoked by alias); 7 Aug 2017 14:54:09 -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 120333 invoked by uid 48); 7 Aug 2017 14:54:08 -0000 From: "leszek at swirski dot co.uk" To: gdb-prs@sourceware.org Subject: [Bug symtab/20899] "dwarf2_string_attr" does not check for "DW_FORM_GNU_str_index" Date: Mon, 07 Aug 2017 14:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: leszek at swirski dot co.uk 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00161.txt.bz2 Content-length: 633 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20899 Lech Swirski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Lech Swirski --- Fix merged in http://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommit;h=3D16= eb6b2db49e6cf2fdca56efd37689fcc170cd37 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21725-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 07 16:03:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 111460 invoked by alias); 7 Aug 2017 16:03:27 -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 111429 invoked by uid 55); 7 Aug 2017 16:03:26 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21886] Compressed MIPS code debugging impossible due to memory breakpoint misplacement Date: Mon, 07 Aug 2017 16:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: macro@linux-mips.org X-Bugzilla-Target-Milestone: 8.0.1 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: 2017-q3/txt/msg00162.txt.bz2 Content-length: 1940 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21886 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Maciej W. Rozycki : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dba7b109b296f= eac8cf8cab74db5f824dfa631610 commit ba7b109b296feac8cf8cab74db5f824dfa631610 Author: Maciej W. Rozycki Date: Mon Aug 7 17:02:04 2017 +0100 PR breakpoints/21886: mem-break: Fix breakpoint insertion location Fix a commit cd6c3b4ffc4e ("New gdbarch methods breakpoint_kind_from_pc and sw_breakpoint_from_kind") regression and restore the use of `->placed_address' rather than `->reqstd_address' as the location for a memory breakpoint to be inserted at. Previously `gdbarch_breakpoint_from_pc' was used that made that adjustment in `default_memory_insert_breakpoint' from the preinitialized value, however with the said commit that call is gone, so the passed `->placed_address' has to be used for the initialization. The regression manifests itself as the inability to debug any MIPS/Linux compressed ISA dynamic executable as GDB corrupts the dynamic loader with one of its implicit breakpoints, causing the program to crash, as seen for example with the `mips-linux-gnu' target, o32 ABI, MIPS16 code, and the gdb.base/advance.exp test case: (gdb) continue Continuing. Program received signal SIGBUS, Bus error. _dl_debug_initialize (ldbase=3D0, ns=3D0) at dl-debug.c:51 51 r =3D &_r_debug; (gdb) FAIL: gdb.base/advance.exp: Can't run to main gdb/ PR breakpoints/21886 * mem-break.c (default_memory_insert_breakpoint): Use `->placed_address' rather than `->reqstd_address' for the breakpoint location. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21726-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 07 16:07:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 56983 invoked by alias); 7 Aug 2017 16:07:34 -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 54910 invoked by uid 48); 7 Aug 2017 16:07:33 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21436] frame filter should allow duplicated underlying frames Date: Mon, 07 Aug 2017 16:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pmuldoon at redhat dot com X-Bugzilla-Status: WAITING 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: attachments.created 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: 2017-q3/txt/msg00163.txt.bz2 Content-length: 444 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21436 --- Comment #4 from Phil Muldoon --- Created attachment 10323 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10323&action=3Ded= it Dummy frame testcase I hope this helps. This was my rough/scratch testcase for setting up nested/multiple nested/assumed dummy frames. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21727-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 00:07:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 18527 invoked by alias); 8 Aug 2017 00:07:25 -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 18496 invoked by uid 48); 8 Aug 2017 00:07:24 -0000 From: "chrisj at rtems dot org" To: gdb-prs@sourceware.org Subject: [Bug sim/20863] gdb-7.12 powerpc-rtems4.12-gdb does not build on FreeBSD. Date: Tue, 08 Aug 2017 00:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: chrisj at rtems dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jhb at FreeBSD dot org X-Bugzilla-Target-Milestone: 8.0.1 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: 2017-q3/txt/msg00164.txt.bz2 Content-length: 1508 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20863 --- Comment #2 from Chris Johns --- This issue also happens on Windows when building on MSYS2: ../sim/ppc/libsim.a(sim_calls.o): In function `sim_io_read_stdin': D:\opt\rtems\rsb.git\rtems\build\prg7xwm1\build\sim\ppc/../../../gdb-7.12/s= im/ppc/sim_calls.c:302: undefined reference to `error' ../sim/ppc/libsim.a(sim_calls.o): In function `sim_io_write_stdout': D:\opt\rtems\rsb.git\rtems\build\prg7xwm1\build\sim\ppc/../../../gdb-7.12/s= im/ppc/sim_calls.c:320: undefined reference to `error' ../sim/ppc/libsim.a(sim_calls.o): In function `sim_io_write_stderr': D:\opt\rtems\rsb.git\rtems\build\prg7xwm1\build\sim\ppc/../../../gdb-7.12/s= im/ppc/sim_calls.c:339: undefined reference to `error' ../sim/ppc/libsim.a(sim_calls.o): In function `sim_io_printf_filtered': D:\opt\rtems\rsb.git\rtems\build\prg7xwm1\build\sim\ppc/../../../gdb-7.12/s= im/ppc/sim_calls.c:358: undefined reference to `error' ../sim/ppc/libsim.a(sim_calls.o): In function `sim_load': D:\opt\rtems\rsb.git\rtems\build\prg7xwm1\build\sim\ppc/../../../gdb-7.12/s= im/ppc/sim_calls.c:105: undefined reference to `error' ../sim/ppc/libsim.a(sim_calls.o):D:\opt\rtems\rsb.git\rtems\build\prg7xwm1\= build\sim\ppc/../../../gdb-7.12/sim/ppc/sim_calls.c:125: more undefined references to `error' follow Also tracked in RTEMS under https://devel.rtems.org/ticket/2990#comment:13 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21728-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 09:50:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 80402 invoked by alias); 8 Aug 2017 09:50: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 80293 invoked by uid 48); 8 Aug 2017 09:50:51 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21558] symtab.fullname() can't handle directories with Unicode characters Date: Tue, 08 Aug 2017 09:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pmuldoon at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00165.txt.bz2 Content-length: 539 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21558 Phil Muldoon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmuldoon at redhat dot com --- Comment #1 from Phil Muldoon --- Do you have a test case (file name I can create) that triggers this error? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21729-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 09:52:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107240 invoked by alias); 8 Aug 2017 09:52:15 -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 107166 invoked by uid 48); 8 Aug 2017 09:52:14 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21366] Python script causes GDB core dump Date: Tue, 08 Aug 2017 09:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pmuldoon at redhat dot com X-Bugzilla-Status: WAITING 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: cc 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: 2017-q3/txt/msg00166.txt.bz2 Content-length: 552 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21366 Phil Muldoon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmuldoon at redhat dot com --- Comment #4 from Phil Muldoon --- Can you submit the patch, following the posting guidelines, to the gdb-patc= hes@ list? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21730-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 09:53:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109050 invoked by alias); 8 Aug 2017 09:53:56 -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 109023 invoked by uid 48); 8 Aug 2017 09:53:55 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/20624] gdb.Value doesn't support Python floordiv operator, // Date: Tue, 08 Aug 2017 09:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pmuldoon at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00167.txt.bz2 Content-length: 546 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20624 Phil Muldoon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmuldoon at redhat dot com --- Comment #6 from Phil Muldoon --- What's the status of your patch, Jonathan? Have you submitted it to gdb-patches@? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21731-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 09:54:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 110753 invoked by alias); 8 Aug 2017 09:54:45 -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 110725 invoked by uid 48); 8 Aug 2017 09:54:44 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21007] Expose breaking with regular expressions on the Python API Date: Tue, 08 Aug 2017 09:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: pmuldoon at redhat dot com 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: bug_status cf_reconfirmed_on cc everconfirmed 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: 2017-q3/txt/msg00168.txt.bz2 Content-length: 672 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21007 Phil Muldoon changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-08-08 CC| |pmuldoon at redhat dot com Ever confirmed|0 |1 --- Comment #1 from Phil Muldoon --- I'll add it to the todo on my list. Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21732-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 09:56:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 26259 invoked by alias); 8 Aug 2017 09:56:40 -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 26222 invoked by uid 48); 8 Aug 2017 09:56:39 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/18439] lazy string value method ignores length Date: Tue, 08 Aug 2017 09:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pmuldoon at redhat dot com X-Bugzilla-Status: WAITING 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: bug_status cc 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: 2017-q3/txt/msg00169.txt.bz2 Content-length: 549 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18439 Phil Muldoon changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING CC| |pmuldoon at redhat dot com --- Comment #2 from Phil Muldoon --- Can I close this bug, Doug? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21733-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 09:57:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27889 invoked by alias); 8 Aug 2017 09:57:25 -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 27855 invoked by uid 48); 8 Aug 2017 09:57:24 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/17728] gdb.LazyString is confused by typedefs Date: Tue, 08 Aug 2017 09:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pmuldoon at redhat dot com X-Bugzilla-Status: WAITING 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: bug_status cc 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: 2017-q3/txt/msg00170.txt.bz2 Content-length: 550 https://sourceware.org/bugzilla/show_bug.cgi?id=3D17728 Phil Muldoon changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING CC| |pmuldoon at redhat dot com --- Comment #3 from Phil Muldoon --- Can we close this bug, Doug? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21734-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 10:04:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 48101 invoked by alias); 8 Aug 2017 10:04:28 -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 47880 invoked by uid 48); 8 Aug 2017 10:04:27 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21196] Build is broken with Python < 2.7 Date: Tue, 08 Aug 2017 10:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: pmuldoon at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00171.txt.bz2 Content-length: 531 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21196 Phil Muldoon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmuldoon at redhat dot com --- Comment #1 from Phil Muldoon --- I've brought the issue up with the community on gdb@sourceware.org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21735-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 12:23:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 57690 invoked by alias); 8 Aug 2017 12:23:42 -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 57661 invoked by uid 48); 8 Aug 2017 12:23:41 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21196] Build is broken with Python < 2.7 Date: Tue, 08 Aug 2017 12:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: pmuldoon at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00172.txt.bz2 Content-length: 334 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21196 --- Comment #2 from Phil Muldoon --- The consensus is that 2.6 now builds cleanly. If you encounter further issu= es, please reopen the bug and we'll look at it again. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21736-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 12:25:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 58993 invoked by alias); 8 Aug 2017 12:25:05 -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 58946 invoked by uid 48); 8 Aug 2017 12:25:04 -0000 From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21196] Build is broken with Python < 2.7 Date: Tue, 08 Aug 2017 12:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: pmuldoon at redhat 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00173.txt.bz2 Content-length: 509 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21196 Phil Muldoon changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Phil Muldoon --- Closed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21737-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 12:26:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 62596 invoked by alias); 8 Aug 2017 12:26:59 -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 62546 invoked by uid 48); 8 Aug 2017 12:26:58 -0000 From: "jwakely.gcc at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/20624] gdb.Value doesn't support Python floordiv operator, // Date: Tue, 08 Aug 2017 12:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jwakely.gcc at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00174.txt.bz2 Content-length: 331 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20624 --- Comment #7 from Jonathan Wakely --- I don't think I ever addressed all the comments in the https://sourceware.org/ml/gdb-patches/2016-09/msg00220.html thread. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21738-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 12:59:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 47454 invoked by alias); 8 Aug 2017 12:59:19 -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 45993 invoked by uid 48); 8 Aug 2017 12:59:18 -0000 From: "hap.ddup at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21925] New: [onlinedocs] Error syntax: show set startup-with-shell Date: Tue, 08 Aug 2017 12:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hap.ddup at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00175.txt.bz2 Content-length: 933 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21925 Bug ID: 21925 Summary: [onlinedocs] Error syntax: show set startup-with-shell Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: hap.ddup at gmail dot com Target Milestone: --- Please fix the following command syntax: Error: (gdb) show set startup-with-shell Undefined show command: "set startup-with-shell". Try "help show". Success: (gdb) show startup-with-shell=20 Use of shell to start subprocesses is on. -------- Error Location: 1. https://sourceware.org/gdb/current/onlinedocs/gdb/Starting.html#Starting 2. http://sourceware.org/gdb/current/onlinedocs/gdb.pdf.gz --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21739-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 14:55:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49090 invoked by alias); 8 Aug 2017 14:55:58 -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 48864 invoked by uid 48); 8 Aug 2017 14:55:56 -0000 From: "joel.sherrill at oarcorp dot com" To: gdb-prs@sourceware.org Subject: [Bug sim/20863] gdb-7.12 powerpc-rtems4.12-gdb does not build on FreeBSD. Date: Tue, 08 Aug 2017 14:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: joel.sherrill at oarcorp dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jhb at FreeBSD dot org X-Bugzilla-Target-Milestone: 8.0.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q3/txt/msg00176.txt.bz2 Content-length: 668 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20863 Joel Sherrill changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joel.sherrill at oarcorp d= ot com --- Comment #3 from Joel Sherrill --- A patch was proposed in this thread https://sourceware.org/ml/gdb-patches/2016-11/msg00760.html by John Baldwin. Any chance of reaching a conclusion on it so psim builds on FreeBSD? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21740-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 16:59:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 116472 invoked by alias); 8 Aug 2017 16:59:56 -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 116431 invoked by uid 48); 8 Aug 2017 16:59:55 -0000 From: "dje at google dot com" To: gdb-prs@sourceware.org Subject: [Bug python/18439] lazy string value method ignores length Date: Tue, 08 Aug 2017 16:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00177.txt.bz2 Content-length: 543 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18439 dje at google dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |FIXED --- Comment #3 from dje at google dot com --- (In reply to Phil Muldoon from comment #2) > Can I close this bug, Doug? Indeed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21741-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 20:46:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 14461 invoked by alias); 8 Aug 2017 20:46:11 -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 14430 invoked by uid 48); 8 Aug 2017 20:46:10 -0000 From: "dominik.b.czarnota+bugzilla at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21927] New: Searching memory on remote target fails Date: Tue, 08 Aug 2017 20:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dominik.b.czarnota+bugzilla at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00178.txt.bz2 Content-length: 4849 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21927 Bug ID: 21927 Summary: Searching memory on remote target fails Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: dominik.b.czarnota+bugzilla at gmail dot com Target Milestone: --- Hey, There is a bug when searching memory on remote targets. At least that is what happened for me on some x86-64 binaries. My setup can be seen at the end of the post. You can see the bug on this asciinema cast which connects to remote target hosted as `gdbserver localhost:4444 /bin/ls`: https://asciinema.org/a/o4ZCjQ7MRwyIKDx6uZHCcQCU9 This can be reproduced using a super simple hello world binary: ``` #include int main() { puts("Hello world"); } ``` That is compiled as `gcc main.c` (gcc version and file properties below). Then starting a gdbserver as `gdbserver localhost:4444 ./a.out` and then in another console: ``` $ gdb ./a.out -q Reading symbols from ./a.out...(no debugging symbols found)...done. (gdb) target remote localhost:4444 Remote debugging using localhost:4444 Reading /lib64/ld-linux-x86-64.so.2 from remote target... warning: File transfers from remote targets can be slow. Use "set sysroot" = to access files locally instead. Reading /lib64/ld-linux-x86-64.so.2 from remote target... Reading symbols from target:/lib64/ld-linux-x86-64.so.2...(no debugging sym= bols found)...done. 0x00007feb9f0adcc0 in _start () from target:/lib64/ld-linux-x86-64.so.2 (gdb) b main Breakpoint 1 at 0x10000067e (gdb) c Continuing. Reading /usr/lib/libc.so.6 from remote target... Breakpoint 1, 0x000000010000067e in main () (gdb) x/4i $rip =3D> 0x10000067e : lea 0x9f(%rip),%rdi # 0x1000007= 24 0x100000685 : callq 0x100000550 0x10000068a : mov $0x0,%eax 0x10000068f : pop %rbp (gdb) ni 0x0000000100000685 in main () (gdb) i r rdi rdi 0x100000724 4294969124 (gdb) x/s 0x100000724 0x100000724: "Hello world" (gdb) find 0x100000700, +0x50, "Hello" Pattern not found. (gdb) find 0x100000700, +200, "ello" Pattern not found. (gdb)=20 (gdb) py import gdb; print(gdb.selected_inferior().search_memory(0x10000070= 0, 500, "Hello")) 4294969124 (gdb) p/x 4294969124 $1 =3D 0x100000724 (gdb) find 0x100000700, +500, "Hello" Pattern not found. ``` As you can see, the pattern is not found with `find` command and it really = *is there*. On the other hand it was found by Python API - which is weird to me because= I started digging over this bug due to `gdb.selected_inferior().search_memory` not being able to find my address. Here is another asciicinema - for /bin/ls - showing that the Python's `.search_memory` can show something weird as well: https://asciinema.org/a/yAiyeTuagKL4r8CQ7FkMA4xJ5 As it returned an address which is unacessible. Below you can see my gdb version. ``` $ gdb --version GNU gdb (GDB) 8.0 // (...) $ gdbserver --version GNU gdbserver (GDB) 8.0 // (...) $ gdb (gdb) py import sys; print(sys.version) 3.6.2 (default, Jul 20 2017, 03:52:27)=20 [GCC 7.1.1 20170630] $ gdb --configuration This GDB was configured as follows: configure --host=3Dx86_64-pc-linux-gnu --target=3Dx86_64-pc-linux-gnu --with-auto-load-dir=3D$debugdir:$datadir/auto-load --with-auto-load-safe-path=3D$debugdir:$datadir/auto-load --with-expat --with-gdb-datadir=3D/usr/share/gdb (relocatable) --with-jit-reader-dir=3D/usr/lib/gdb (relocatable) --without-libunwind-ia64 --with-lzma --with-python=3D/usr (relocatable) --with-guile --with-separate-debug-dir=3D/usr/lib/debug (relocatable) --with-system-gdbinit=3D/etc/gdb/gdbinit --without-babeltrace ("Relocatable" means the directory can be moved with the GDB installation tree, and GDB will still find it.) ``` My gcc version: ``` $ gcc --version gcc (GCC) 7.1.1 20170630 // (...) ``` The result `a.out` file properties: ``` $ file a.out=20 a.out: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=3D6401e4473f83c5f4d6d5bffa691a69119ae86977, not stripped $ checksec -f a.out RELRO STACK CANARY NX PIE RPATH=20=20= =20=20=20 RUNPATH FORTIFY Fortified Fortifiable FILE Partial RELRO No canary found NX enabled PIE enabled No RPATH = No RUNPATH No 0 0 a.out ``` Thanks, Disconnect3d --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21742-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 08 21:18:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107966 invoked by alias); 8 Aug 2017 21:18:35 -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 107910 invoked by uid 48); 8 Aug 2017 21:18:35 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21927] Searching memory on remote target fails Date: Tue, 08 Aug 2017 21:18: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00179.txt.bz2 Content-length: 411 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21927 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.marchi at ericsson d= ot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21743-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 09 08:18:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 119412 invoked by alias); 9 Aug 2017 08:18:15 -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 118265 invoked by uid 48); 9 Aug 2017 08:18:13 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F Date: Wed, 09 Aug 2017 08:18: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: 7.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 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: 2017-q3/txt/msg00180.txt.bz2 Content-length: 609 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21873 --- Comment #12 from Yao Qi --- (In reply to Ismail from comment #11) > Let me try to debug the issue. Perhaps I may figure out the issue and sen= d a > patch. dirname points to a garbage address. valgrind or address sanitizer is good= at finding such problems, you can either 1) run arm-none-eabi-gdb with valgrind, like 'valgrind ./gdb/gdb', 2) or rebuild gdb with address sanitizer, $ make CXXFLAGS=3D"-O0 -g3 -fsanitize=3Daddress" gdb --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21744-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 09 16:14:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 54273 invoked by alias); 9 Aug 2017 16:14:15 -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 54234 invoked by uid 48); 9 Aug 2017 16:14:14 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/13590] always display addresses in "info var" output Date: Wed, 09 Aug 2017 16:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: cc 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: 2017-q3/txt/msg00181.txt.bz2 Content-length: 741 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13590 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #3 from Pedro Alves --- > (gdb) p &foo.c::foo <<< is there a syntax for that? > A syntax error in expression, near `::foo'. yes there is, it's: (gdb) p 'foo.c'::foo $1 =3D 0 "watch 'foo.c'::foo", "disassemble 'foo.c'::function" etc. works too.=20 Basically, everywhere gdb accepts an expression. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21745-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 09 16:18:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 71719 invoked by alias); 9 Aug 2017 16:18:59 -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 71684 invoked by uid 48); 9 Aug 2017 16:18:58 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/13590] always display addresses in "info var" output Date: Wed, 09 Aug 2017 16:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q3/txt/msg00182.txt.bz2 Content-length: 274 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13590 --- Comment #4 from Pedro Alves --- For reference: https://sourceware.org/gdb/onlinedocs/gdb/Variables.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21747-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 09 19:34:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 61906 invoked by alias); 9 Aug 2017 19:34:11 -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 61758 invoked by uid 48); 9 Aug 2017 19:34:10 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/19436] C++11 ABI tag does not work Date: Wed, 09 Aug 2017 19:34: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: keiths at redhat dot com 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: cc 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: 2017-q3/txt/msg00184.txt.bz2 Content-length: 516 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19436 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ks132 at yandex dot ru --- Comment #4 from Keith Seitz --- *** Bug 18601 has been marked as a duplicate of this bug. *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21746-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 09 19:34:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 61692 invoked by alias); 9 Aug 2017 19:34:10 -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 61658 invoked by uid 48); 9 Aug 2017 19:34:09 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/18601] Can't set breakpoint on function with abi_tag attribute Date: Wed, 09 Aug 2017 19:34: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: 7.9 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00183.txt.bz2 Content-length: 967 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18601 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Keith Seitz --- (In reply to Keith Seitz from comment #1) > I hope to be working up a formal fix for this in the coming week, but I'd > like to mention a few things, including a workaround. That didn't happen, but the cxx-improvements patch which I reviewed should help. That was reported in c++/19436, where there's been more discussion (a= nd a link to the patch series). Let's close this bug and track progress there. *** This bug has been marked as a duplicate of bug 19436 *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21748-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 11 08:35:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 67620 invoked by alias); 11 Aug 2017 08:35:33 -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 64121 invoked by uid 55); 11 Aug 2017 08:35:32 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/14100] internal-error: frame_cleanup_after_sniffer: Assertion `frame->prologue_cache == NULL' failed. Date: Fri, 11 Aug 2017 08:35: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 7.5 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: 2017-q3/txt/msg00185.txt.bz2 Content-length: 1470 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14100 --- Comment #5 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Yao Qi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dbe7d3cd5f131= 96dd070978aa48c2832c351c25b6 commit be7d3cd5f13196dd070978aa48c2832c351c25b6 Author: Yao Qi Date: Fri Aug 11 09:30:02 2017 +0100 Reset *THIS_CACHE in frame_unwind_try_unwinder in case of exception It is required that unwinder->sniffer should set *this_cache to NULL if the unwinder is not applicable or exception is thrown, so 78ac5f831692f70b841044961069e50d4ba6a76f adds clear_pointer_cleanup to = set *this_cache to NULL in case of exception in order to fix PR 14100. https://sourceware.org/ml/gdb-patches/2012-08/msg00075.html This patch removes that clear_pointer_cleanup, and catch all exception = in the caller of unwinder->sniffer. In case of exception, reset *this_cas= e. gdb: 2017-08-11 Yao Qi * dwarf2-frame.c (clear_pointer_cleanup): Remove. (dwarf2_frame_cache): Remove reset_cache_cleanup. (dwarf2_frame_cache): * frame-unwind.c (frame_unwind_try_unwinder): Catch RETURN_MASK_ALL and set *this_case to NULL. * frame-unwind.h: Update comments. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21749-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 11 09:50:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 120399 invoked by alias); 11 Aug 2017 09:50:18 -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 120291 invoked by uid 55); 11 Aug 2017 09:50:11 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21886] Compressed MIPS code debugging impossible due to memory breakpoint misplacement Date: Fri, 11 Aug 2017 09:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: macro@linux-mips.org X-Bugzilla-Target-Milestone: 8.0.1 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: 2017-q3/txt/msg00186.txt.bz2 Content-length: 2021 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21886 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The gdb-8.0-branch branch has been updated by Maciej W. Rozycki : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Db3e687f4c5e2= bd847ea0608fd8960820f3efbda3 commit b3e687f4c5e2bd847ea0608fd8960820f3efbda3 Author: Maciej W. Rozycki Date: Fri Aug 11 10:40:06 2017 +0100 PR breakpoints/21886: mem-break: Fix breakpoint insertion location Fix a commit cd6c3b4ffc4e ("New gdbarch methods breakpoint_kind_from_pc and sw_breakpoint_from_kind") regression and restore the use of `->placed_address' rather than `->reqstd_address' as the location for a memory breakpoint to be inserted at. Previously `gdbarch_breakpoint_from_pc' was used that made that adjustment in `default_memory_insert_breakpoint' from the preinitialized value, however with the said commit that call is gone, so the passed `->placed_address' has to be used for the initialization. The regression manifests itself as the inability to debug any MIPS/Linux compressed ISA dynamic executable as GDB corrupts the dynamic loader with one of its implicit breakpoints, causing the program to crash, as seen for example with the `mips-linux-gnu' target, o32 ABI, MIPS16 code, and the gdb.base/advance.exp test case: (gdb) continue Continuing. Program received signal SIGBUS, Bus error. _dl_debug_initialize (ldbase=3D0, ns=3D0) at dl-debug.c:51 51 r =3D &_r_debug; (gdb) FAIL: gdb.base/advance.exp: Can't run to main gdb/ PR breakpoints/21886 * mem-break.c (default_memory_insert_breakpoint): Use `->placed_address' rather than `->reqstd_address' for the breakpoint location. (cherry picked from commit ba7b109b296feac8cf8cab74db5f824dfa631610) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21751-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 11 14:26:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 119973 invoked by alias); 11 Aug 2017 14:25:59 -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 118042 invoked by uid 48); 11 Aug 2017 14:25:56 -0000 From: "macro@linux-mips.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21886] Compressed MIPS code debugging impossible due to memory breakpoint misplacement Date: Fri, 11 Aug 2017 14:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: macro@linux-mips.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: macro@linux-mips.org X-Bugzilla-Target-Milestone: 8.0.1 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00188.txt.bz2 Content-length: 537 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21886 Maciej W. Rozycki changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |FIXED --- Comment #4 from Maciej W. Rozycki --- Fixed in master and 8.0, closing bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21750-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 11 14:25:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109810 invoked by alias); 11 Aug 2017 14:25:39 -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 109447 invoked by uid 48); 11 Aug 2017 14:25:39 -0000 From: "macro@linux-mips.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21886] Compressed MIPS code debugging impossible due to memory breakpoint misplacement Date: Fri, 11 Aug 2017 14:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: macro@linux-mips.org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: macro@linux-mips.org X-Bugzilla-Target-Milestone: 8.0.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status 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: 2017-q3/txt/msg00187.txt.bz2 Content-length: 481 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21886 Maciej W. Rozycki changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |WAITING --- Comment #3 from Maciej W. Rozycki --- Fixed in master and 8.0, closing bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21752-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 11 19:23:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 51280 invoked by alias); 11 Aug 2017 19:23:45 -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 51247 invoked by uid 48); 11 Aug 2017 19:23:43 -0000 From: "dominik.b.czarnota+bugzilla at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21927] Searching memory on remote target fails Date: Fri, 11 Aug 2017 19:23: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dominik.b.czarnota+bugzilla at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00189.txt.bz2 Content-length: 929 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21927 Disconnect3d changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Disconnect3d --- The bug I am mainly pointing at in here is invalid. Actually the `find` command works perfectly BUT its documentation and short help (`help find`) could be improved. The Python API search is broken on remote targets (and the workaround for i= t is to `set remote search-memory-packet off`). I will post two seperate bug reports for those - with better description and minimal example. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21753-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 11 19:43:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41744 invoked by alias); 11 Aug 2017 19:43:41 -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 41720 invoked by uid 48); 11 Aug 2017 19:43:40 -0000 From: "dominik.b.czarnota+bugzilla at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21945] New: Improve find command string search Date: Fri, 11 Aug 2017 19:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: dominik.b.czarnota+bugzilla at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00190.txt.bz2 Content-length: 2149 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21945 Bug ID: 21945 Summary: Improve find command string search Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: dominik.b.czarnota+bugzilla at gmail dot com Target Milestone: --- Hey, It is pretty hard to find "part of string" using `find` command. See an example below (the prompt/plugin I use doesn't change anything here). So I am debugging /bin/ls binary when it is in its entry point (_start function). We have got a "/bin/ls" string on 0x7fffffffdabe: ``` pwndbg> x/s 0x7fffffffdabe 0x7fffffffdabe: "/bin/ls" ``` This is actually a null-terminated string. Finding all of it works fine: ``` pwndbg> find 0x7fffffffdabe, +100, "/bin/ls" 0x7fffffffdabe 1 pattern found. ``` Lets try to find just a part of it: ``` pwndbg> find 0x7fffffffdabe, +500, "/bin/" Pattern not found. ``` It doesn't work. Why? The manual - https://sourceware.org/gdb/onlinedocs/gdb/Searching-Memory.html - states it perfectly: > All values are interpreted in the current language. > This means, for example, that if the current source language is C/C++ the= n searching for the string =E2=80=9Chello=E2=80=9D includes the trailing = =E2=80=99\0=E2=80=99. So one way to find it is to find it by characters: find 0x7fffffffdabe, +500, '/','b','i','n' Or using a cast to truncate null-terminator: find 0x7fffffffdabe, +500, {char[5]}"/bin/" It would be nice to do one of two: 1. Change the current logic so null terminator wouldn't be explicitly added= - this is how it works when searching with Python GDB API: ``` pwndbg> search "/bin/ls"pwndbg> py import gdb; print("%x" % gdb.selected_inferior().search_memory(0x7fffffffdabe, 500, "/bin/")) 7fffffffdabe ``` 2. Change both manual and `help find` result to add this information about null-terminated strings and the possibility how to search for a string. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21754-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 11 20:02:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109947 invoked by alias); 11 Aug 2017 20:02:31 -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 109910 invoked by uid 48); 11 Aug 2017 20:02:30 -0000 From: "dominik.b.czarnota+bugzilla at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21946] New: Python API search_memory remote targets bug Date: Fri, 11 Aug 2017 20:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dominik.b.czarnota+bugzilla at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00191.txt.bz2 Content-length: 3191 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21946 Bug ID: 21946 Summary: Python API search_memory remote targets bug Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: dominik.b.czarnota+bugzilla at gmail dot com Target Milestone: --- Hey, There is a bug with `gdb.selected_inferior().search_memory(startaddr, size, searchfor)` returning wrong results in some cases for remote targets. To reproduce: 1. In first console launch `gdbserver localhost:4444 /bin/ls` 2. In second console fire: ``` $ gdb /bin/ls Reading symbols from /bin/ls...(no debugging symbols found)...done. (gdb) target remote localhost:4444 Remote debugging using localhost:4444 Reading /lib64/ld-linux-x86-64.so.2 from remote target... warning: File transfers from remote targets can be slow. Use "set sysroot" = to access files locally instead. Reading /lib64/ld-linux-x86-64.so.2 from remote target... Reading symbols from target:/lib64/ld-linux-x86-64.so.2...(no debugging sym= bols found)...done. 0x00007ff8582a6cc0 in _start () from target:/lib64/ld-linux-x86-64.so.2 (gdb) info proc mappings process 11537 Mapped address spaces: Start Addr End Addr Size Offset objfile 0x400000 0x41f000 0x1f000 0x0 /usr/bin/ls 0x61e000 0x620000 0x2000 0x1e000 /usr/bin/ls 0x620000 0x621000 0x1000 0x0 [heap] 0x7ff8582a6000 0x7ff8582c9000 0x23000 0x0 /usr/lib/ld-2.25.so 0x7ff8584c4000 0x7ff8584c7000 0x3000 0x0 [vvar] 0x7ff8584c7000 0x7ff8584c9000 0x2000 0x0 [vdso] 0x7ff8584c9000 0x7ff8584cb000 0x2000 0x23000 /usr/lib/ld-2.25.so 0x7ff8584cb000 0x7ff8584cc000 0x1000 0x0=20 0x7ffffffdd000 0x7ffffffff000 0x22000 0x0 [stack] 0xffffffffff600000 0xffffffffff601000 0x1000 0x0 [vsyscall] (gdb) #grab stack startaddr & size (gdb) py import gdb; print("0x%x" % gdb.selected_inferior().search_memory(0x7ffffffdd000, 0x22000, "bin/")) 0x7f23050a3390 (gdb) # the address is invalid? (gdb) x/s 0x7f23050a3390 0x7f23050a3390: (gdb) x/xg 0x7f23050a3390 0x7f23050a3390: Cannot access memory at address 0x7f23050a3390 (gdb) set remote search-memory-packet off (gdb) py import gdb; print("0x%x" % gdb.selected_inferior().search_memory(0x7ffffffdd000, 0x22000, "bin/")) 0x7fffffffdaba (gdb) x/s 0x7fffffffdaba 0x7fffffffdaba: "bin/ls" (gdb)=20 ``` Basically it seems that when the `remote search-memory-packet` parameter is enabled, the search results are wrong. I am not aware what does this option introduce, but it seems it is a good workaround. My GDB/Python version can be seen below: ``` pwndbg> version Gdb: GNU gdb (GDB) 8.0 Python: 3.6.2 (default, Jul 20 2017, 03:52:27) [GCC 7.1.1 20170630] Pwndbg: 1.0.0 build: f481201 ``` --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21755-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 11 20:19:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 60355 invoked by alias); 11 Aug 2017 20:19:14 -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 60325 invoked by uid 48); 11 Aug 2017 20:19:13 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21946] Python API search_memory remote targets bug Date: Fri, 11 Aug 2017 20:19: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00192.txt.bz2 Content-length: 1052 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21946 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- > I am not aware what does this option introduce, but it seems it is a good workaround. That option disables the "qSearch:memory" remote serial protocol packet. I= .e., when the option is on, GDB sends the pattern to GDBserver, GDBserver does t= he searching, and returns back the result to GDB. When the option is off, GDB falls back to search memory itself, by reading memory blocks out of the rem= ote target's memory. The latter is much slower. "qSearch:memory" is thus an optimization. Look for qSearch:memory at: https://sourceware.org/gdb/onlinedocs/gdb/General-Query-Packets.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21756-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 11 20:36:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 62380 invoked by alias); 11 Aug 2017 20:36:13 -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 62354 invoked by uid 48); 11 Aug 2017 20:36:12 -0000 From: "alexlindsay239 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21947] New: Memory leak coming from obstack Date: Fri, 11 Aug 2017 20:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: alexlindsay239 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00193.txt.bz2 Content-length: 1916 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21947 Bug ID: 21947 Summary: Memory leak coming from obstack Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: alexlindsay239 at gmail dot com Target Milestone: --- If I run `gdb ./hello_world` through valgrind, I get (among some other leak= s): =3D=3D32024=3D=3D 20,320 bytes in 5 blocks are definitely lost in loss reco= rd 11,413 of 11,460 =3D=3D32024=3D=3D at 0x4C2DE31: malloc (vg_replace_malloc.c:299) =3D=3D32024=3D=3D by 0x3C3725: xmalloc (common-utils.c:44) =3D=3D32024=3D=3D by 0x734C20: call_chunkfun (obstack.c:94) =3D=3D32024=3D=3D by 0x734CE3: _obstack_begin_worker (obstack.c:141) =3D=3D32024=3D=3D by 0x734DED: _obstack_begin (obstack.c:164) =3D=3D32024=3D=3D by 0x21A289: auto_obstack::auto_obstack() (gdb_obstack= .h:70) =3D=3D32024=3D=3D by 0x4FC649: objfile_per_bfd_storage::objfile_per_bfd_= storage() (objfiles.h:188) =3D=3D32024=3D=3D by 0x4F87EC: get_objfile_bfd_data(objfile*, bfd*) (obj= files.c:157) =3D=3D32024=3D=3D by 0x4F95D6: allocate_objfile(bfd*, char const*, enum_flags) (objfiles.c:420) =3D=3D32024=3D=3D by 0x561F24: symbol_file_add_with_addrs(bfd*, char con= st*, enum_flags, section_addr_info*, enum_flags, objfile*) (symfile.c:1158) =3D=3D32024=3D=3D by 0x56228B: symbol_file_add_from_bfd(bfd*, char const= *, enum_flags, section_addr_info*, enum_flags, objfile*) (symfile.c:1268) =3D=3D32024=3D=3D by 0x5458FB: solib_read_symbols(so_list*, enum_flags) (solib.c:707) Perhaps this is purely a libiberty bug? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21757-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 11 20:38:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66356 invoked by alias); 11 Aug 2017 20:38:50 -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 66334 invoked by uid 48); 11 Aug 2017 20:38:49 -0000 From: "alexlindsay239 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21947] Memory leak coming from obstack Date: Fri, 11 Aug 2017 20:38: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: alexlindsay239 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc cf_gcchost 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: 2017-q3/txt/msg00194.txt.bz2 Content-length: 478 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21947 Alex Lindsay changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexlindsay239 at gmail do= t com Host| |x86_64-pc-linux-gnu --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21758-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 12 07:01:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 118207 invoked by alias); 12 Aug 2017 07:01:54 -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 105865 invoked by uid 48); 12 Aug 2017 07:01:29 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/21948] New: stepi works wrongly with mixed 16- and 32-bit thumb instructions Date: Sat, 12 Aug 2017 07:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00195.txt.bz2 Content-length: 2154 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21948 Bug ID: 21948 Summary: stepi works wrongly with mixed 16- and 32-bit thumb instructions Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: b7.10110111 at gmail dot com Target Milestone: --- I compile a simple "Hello, world" C program with the following command: armv5te-unknown-linux-gnueabi-gcc hello.c -o test-thumb -mthumb Then I start it as gdb -ex 'tb *(main+0)' -ex r -ex 'info reg cpsr' -ex 'disp/i $pc' -ex 'disa= s/r $pc,+12' ./test-thumb and get this: Temporary breakpoint 1, main () at hello.c:4 4 { cpsr 0x60000030 1610612784 1: x/i $pc =3D> 0x103f0
: push {r7, lr} Dump of assembler code from 0x103f0 to 0x103fc: =3D> 0x000103f0 : 80 b5 push {r7, lr} 0x000103f2 : 00 af add r7, sp, #0 0x000103f4 : 03 4b ldr r3, [pc, #12] ; (0x10404 ) 0x000103f6 : 18 1c adds r0, r3, #0 0x000103f8 : ff f7 4c ff bl 0x10294 End of assembler dump. After that I do `si` 4 times, and the program exits, although it should have just reached 0x000103f8 =E2=80=94 call to puts@plt: (gdb) si 0x000103f2 4 { 1: x/i $pc =3D> 0x103f2 : add r7, sp, #0 (gdb)=20 5 printf("Hello, ARM\n"); 1: x/i $pc =3D> 0x103f4 : ldr r3, [pc, #12] ; (0x10404 ) (gdb)=20 0x000103f6 5 printf("Hello, ARM\n"); 1: x/i $pc =3D> 0x103f6 : adds r0, r3, #0 (gdb)=20 [Inferior 1 (process 10808) exited normally] Tested on Raspberry Pi Model B on Raspbian Jessie, here're parts of /proc/cpuinfo: model name : ARMv6-compatible processor rev 7 (v6l) Features : half thumb fastmult vfp edsp java tls=20 Hardware : BCM2835 Reproduces with GDB 8.0 as well as 8.0.50.20170811-git. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21759-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 12 16:33:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 73222 invoked by alias); 12 Aug 2017 16:33:50 -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 73187 invoked by uid 48); 12 Aug 2017 16:33:49 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21925] [onlinedocs] Error syntax: show set startup-with-shell Date: Sat, 12 Aug 2017 16:33: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00196.txt.bz2 Content-length: 405 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21925 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21760-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 12 16:49:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64070 invoked by alias); 12 Aug 2017 16:49:42 -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 63921 invoked by uid 55); 12 Aug 2017 16:49:35 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21925] [onlinedocs] Error syntax: show set startup-with-shell Date: Sat, 12 Aug 2017 16:49: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00197.txt.bz2 Content-length: 1025 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21925 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dca145713f354= ebd5e45ddf393ead46782d1f8b1e commit ca145713f354ebd5e45ddf393ead46782d1f8b1e Author: Sergio Durigan Junior Date: Sat Aug 12 12:46:03 2017 -0400 Fix typo on documentation ("show set startup-with-shell") The documentation was erroneously saying that there is a command named "show set startup-with-shell", while the correct version is "show startup-with-shell". This commit fixes obvious mistake. gdb/doc/ChangeLog: 2017-08-12 Sergio Durigan Junior PR gdb/21925 * gdb.texinfo (Starting) : Fix typo ("show set..."). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21761-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 12 16:50:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68241 invoked by alias); 12 Aug 2017 16:50:16 -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 68212 invoked by uid 48); 12 Aug 2017 16:50:16 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21925] [onlinedocs] Error syntax: show set startup-with-shell Date: Sat, 12 Aug 2017 16:50: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00198.txt.bz2 Content-length: 526 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21925 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Sergio Durigan Junior --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21762-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 12 21:27:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 57154 invoked by alias); 12 Aug 2017 21:27:49 -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 57085 invoked by uid 48); 12 Aug 2017 21:27:49 -0000 From: "noloader at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system Date: Sat, 12 Aug 2017 21:27: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: 6.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: noloader at gmail 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: 7.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q3/txt/msg00199.txt.bz2 Content-length: 596 https://sourceware.org/bugzilla/show_bug.cgi?id=3D10833 Jeffrey Walton changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |noloader at gmail dot com --- Comment #17 from Jeffrey Walton --- Mee too: Program OK outside debugger, SIGILL under debugger when stepping?, https://stackoverflow.com/q/45649778. Thanks ks1322 . --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21763-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 12 21:32:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3789 invoked by alias); 12 Aug 2017 21:32:17 -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 117178 invoked by uid 48); 12 Aug 2017 21:32:03 -0000 From: "noloader at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system Date: Sat, 12 Aug 2017 21:32: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: 6.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: noloader at gmail 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: 7.1 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: 2017-q3/txt/msg00200.txt.bz2 Content-length: 726 https://sourceware.org/bugzilla/show_bug.cgi?id=3D10833 --- Comment #18 from Jeffrey Walton --- (In reply to ChrisD from comment #15) > Sorry, I forgot to update this bug. This turned out to be a bug in the Li= nux > kernel. It's been fixed since at least kernel 2.6.39. The problem never > appeared again with any newer kernel. Gdb works fine on any multi-core ARM > CPU. Comment 11 probably diagnosed this problem correctly. Please close t= he > bug. Chris, what version of GDB is this fixed under? I'm experiencing it under b= oth 3.4.113-bananian and 4.1.15-ti-rt-r40-beaglebone kernels, but GDB may be too old. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21764-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 12 21:49:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79387 invoked by alias); 12 Aug 2017 21:49:01 -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 79259 invoked by uid 48); 12 Aug 2017 21:48:52 -0000 From: "noloader at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system Date: Sat, 12 Aug 2017 21:49: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: 6.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: noloader at gmail 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: 7.1 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: 2017-q3/txt/msg00201.txt.bz2 Content-length: 652 https://sourceware.org/bugzilla/show_bug.cgi?id=3D10833 --- Comment #19 from Jeffrey Walton --- (In reply to Jeffrey Walton from comment #17) > Me too: Program OK outside debugger, SIGILL under debugger when stepping?, > https://stackoverflow.com/q/45649778. Thanks ks1322 . Here are a couple of downstream Debian bugs: * GDB Crash due to GDB/Kernel generated SIGILL, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D871952. * SIGILL when stepping through application on armhf, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D852854 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21765-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Aug 13 17:20:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 93488 invoked by alias); 13 Aug 2017 17:20:40 -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 92323 invoked by uid 48); 13 Aug 2017 17:20:38 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21954] New: "run" stops too early with detach-on-fork=off Date: Sun, 13 Aug 2017 17:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00202.txt.bz2 Content-length: 2121 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21954 Bug ID: 21954 Summary: "run" stops too early with detach-on-fork=3Doff Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- Consider this program: #include int main () { if (fork () =3D=3D 0) { sleep(10); } return 0; } Start gdb. "set detach-on-fork off". Then "run". What I expect to happen is that I will get a gdb prompt back when both inferiors have stopped. My reason for this is that it seems more "shell-like", but also because I think a process exit shouldn't be a stop-worth event, at least not (1) when other processes are running, or (2) there isn't a "catch exit" in place (which is a hypothetical command but seems like a decent idea). What actually happens is that I get a prompt after the parent exits. Then, in all-stop, the other inferior is attached, but stopped. In non-stop, the child process continues to run in the background. This patch works ok for non-stop but I don't really know if it makes sense. And, it doesn't work for all-stop, presumably because the child has already been stopped at this point, and nothing restarts it. diff --git a/gdb/infrun.c b/gdb/infrun.c index d6723fd..c51bec6 100644 --- a/gdb/infrun.c +++ b/gdb/infrun.c @@ -5128,7 +5128,12 @@ Cannot fill $_exitsignal with the correct signal number.\n")); gdb_flush (gdb_stdout); target_mourn_inferior (inferior_ptid); stop_print_frame =3D 0; - stop_waiting (ecs); + /* In multi-inferior, there might still be other processes + running. Only stop waiting if everything has exited. */ + if (have_live_inferiors ()) + prepare_to_wait (ecs); + else + stop_waiting (ecs); return; /* The following are the only cases in which we keep going; --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21766-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 14 16:18:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 113707 invoked by alias); 14 Aug 2017 16:18:15 -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 111032 invoked by uid 55); 14 Aug 2017 16:18:12 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21675] Regression since 8.0 printing has changed format for decimal/octal/others Date: Mon, 14 Aug 2017 16:18: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q3/txt/msg00203.txt.bz2 Content-length: 1672 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21675 --- Comment #8 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dd6382fffde99= 214ce4aee99a208ddb703c647008 commit d6382fffde99214ce4aee99a208ddb703c647008 Author: Tom Tromey Date: Tue Jul 11 06:40:40 2017 -0600 Fix two regressions in scalar printing PR gdb/21675 points out a few regressions in scalar printing. One type of regression is due to not carrying over the old handling of floating point printing -- where a format like "/d" causes a floating point number to first be cast to a signed integer. This patch restores this behavior. The other regression is a longstanding bug in print_octal_chars: one of the constants was wrong. This patch fixes the constant and adds static asserts to help catch this sort of error. ChangeLog 2017-08-14 Tom Tromey PR gdb/21675 * valprint.c (LOW_ZERO): Change value to 034. (print_octal_chars): Add static_asserts for octal constants. * printcmd.c (print_scalar_formatted): Add 'd' case. testsuite/ChangeLog 2017-08-14 Tom Tromey PR gdb/21675: * gdb.base/printcmds.exp (test_radices): New function. * gdb.dwarf2/var-access.exp: Use p/u, not p/d. * gdb.base/sizeof.exp (check_valueof): Use p/d. * lib/gdb.exp (get_integer_valueof): Use p/d. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21767-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 14 16:19:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 75257 invoked by alias); 14 Aug 2017 16:19:55 -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 74582 invoked by uid 48); 14 Aug 2017 16:19:53 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21675] Regression since 8.0 printing has changed format for decimal/octal/others Date: Mon, 14 Aug 2017 16:19: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-q3/txt/msg00204.txt.bz2 Content-length: 570 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21675 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED Target Milestone|--- |8.1 --- Comment #9 from Tom Tromey --- Fix checked in. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21768-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 15 12:52:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 39612 invoked by alias); 15 Aug 2017 12:52:54 -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 38139 invoked by uid 48); 15 Aug 2017 12:52:52 -0000 From: "jonah at kichwacoders dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21954] New: unset entire environment no longer works (regression since GDB 8.0) Date: Tue, 15 Aug 2017 12:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jonah at kichwacoders dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00205.txt.bz2 Content-length: 3635 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21954 Bug ID: 21954 Summary: unset entire environment no longer works (regression since GDB 8.0) Product: gdb Version: 8.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jonah at kichwacoders dot com Target Milestone: --- doing 'unset env' no longer clears the whole environment. Compare GDB 8.0 (first) and current master (second) in the example below. I did a git bisect and believe it was "C++ify gdb/common/environ.c" https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommit;h=3D9= a6c7d9c021cfeb290d76584db7a01e57e7c3d4e that introduced the regression $ gdb -q -ex 'unset env' -ex 'run' /usr/bin/env < /dev/null Reading symbols from /usr/bin/env...(no debugging symbols found)...done. Delete all environment variables? (y or n) [answered Y; input not from terminal] Starting program: /usr/bin/env=20 PWD=3D/scratch/gdb/binutils-gdb SHLVL=3D0 [Inferior 1 (process 24267) exited normally] (gdb) quit $ ./gdb/gdb -q -ex 'unset env' -ex 'run' /usr/bin/env < /dev/null Python Exception No module named gdb:=20 ./gdb/gdb: warning:=20 Could not load the Python gdb module from `/usr/local/share/gdb/python'. Limited Python support is available from the _gdb module. Suggest passing --data-directory=3D/path/to/gdb/data-directory. Reading symbols from /usr/bin/env...(no debugging symbols found)...done. Delete all environment variables? (y or n) [answered Y; input not from terminal] Starting program: /usr/bin/env=20 LS_COLORS=3Drs=3D0:di=3D01;34:ln=3D01;36:mh=3D00:pi=3D40;33:so=3D01;35:do= =3D01;35:bd=3D40;33;01:cd=3D40;33;01:or=3D40;31;01:mi=3D00:su=3D37;41:sg=3D= 30;43:ca=3D30;41:tw=3D30;42:ow=3D34;42:st=3D37;44:ex=3D01;32:*.tar=3D01;31:= *.tgz=3D01;31:*.arc=3D01;31:*.arj=3D01;31:*.taz=3D01;31:*.lha=3D01;31:*.lz4= =3D01;31:*.lzh=3D01;31:*.lzma=3D01;31:*.tlz=3D01;31:*.txz=3D01;31:*.tzo=3D0= 1;31:*.t7z=3D01;31:*.zip=3D01;31:*.z=3D01;31:*.Z=3D01;31:*.dz=3D01;31:*.gz= =3D01;31:*.lrz=3D01;31:*.lz=3D01;31:*.lzo=3D01;31:*.xz=3D01;31:*.zst=3D01;3= 1:*.tzst=3D01;31:*.bz2=3D01;31:*.bz=3D01;31:*.tbz=3D01;31:*.tbz2=3D01;31:*.= tz=3D01;31:*.deb=3D01;31:*.rpm=3D01;31:*.jar=3D01;31:*.war=3D01;31:*.ear=3D= 01;31:*.sar=3D01;31:*.rar=3D01;31:*.alz=3D01;31:*.ace=3D01;31:*.zoo=3D01;31= :*.cpio=3D01;31:*.7z=3D01;31:*.rz=3D01;31:*.cab=3D01;31:*.jpg=3D01;35:*.jpe= g=3D01;35:*.mjpg=3D01;35:*.mjpeg=3D01;35:*.gif=3D01;35:*.bmp=3D01;35:*.pbm= =3D01;35:*.pgm=3D01;35:*.ppm=3D01;35:*.tga=3D01;35:*.xbm=3D01;35:*.xpm=3D01= ;35:*.tif=3D01;35:*.tiff=3D01;35:*.png=3D01;35:*.svg=3D01;35:*.svgz=3D01;35= :*.mng=3D01;35:*.pcx=3D01;35:*.mov=3D01;35:*.mpg=3D01;35:*.mpeg=3D01;35:*.m= 2v=3D01;35:*.mkv=3D01;35:*.webm=3D01;35:*.ogm=3D01;35:*.mp4=3D01;35:*.m4v= =3D01;35:*.mp4v=3D01;35:*.vob=3D01;35:*.qt=3D01;35:*.nuv=3D01;35:*.wmv=3D01= ;35:*.asf=3D01;35:*.rm=3D01;35:*.rmvb=3D01;35:*.flc=3D01;35:*.avi=3D01;35:*= .fli=3D01;35:*.flv=3D01;35:*.gl=3D01;35:*.dl=3D01;35:*.xcf=3D01;35:*.xwd=3D= 01;35:*.yuv=3D01;35:*.cgm=3D01;35:*.emf=3D01;35:*.ogv=3D01;35:*.ogx=3D01;35= :*.aac=3D00;36:*.au=3D00;36:*.flac=3D00;36:*.m4a=3D00;36:*.mid=3D00;36:*.mi= di=3D00;36:*.mka=3D00;36:*.mp3=3D00;36:*.mpc=3D00;36:*.ogg=3D00;36:*.ra=3D0= 0;36:*.wav=3D00;36:*.oga=3D00;36:*.opus=3D00;36:*.spx=3D00;36:*.xspf=3D00;3= 6: LESSCLOSE=3D/usr/bin/lesspipe %s %s XDG_MENU_PREFIX=3Dxfce- -- snip-- --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21769-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 15 12:54:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 95962 invoked by alias); 15 Aug 2017 12:54:29 -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 81692 invoked by uid 48); 15 Aug 2017 12:54:25 -0000 From: "jonah at kichwacoders dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21954] unset entire environment no longer works (regression since GDB 8.0) Date: Tue, 15 Aug 2017 17:09: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: 8.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jonah at kichwacoders dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00206.txt.bz2 Content-length: 585 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21954 Jonah Graham changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #1 from Jonah Graham --- Hi Sergio, I have added you to the CC list as you were the author of the co= mmit I identified. I hope that is ok. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21770-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 15 17:09:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 111317 invoked by alias); 15 Aug 2017 17:09:42 -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 106328 invoked by uid 48); 15 Aug 2017 17:09:12 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21954] unset entire environment no longer works (regression since GDB 8.0) Date: Tue, 15 Aug 2017 17:55: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: 8.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed 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: 2017-q3/txt/msg00207.txt.bz2 Content-length: 689 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21954 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-08-15 Assignee|unassigned at sourceware dot org |sergiodj at redhat = dot com Ever confirmed|0 |1 --- Comment #2 from Sergio Durigan Junior --- Thanks, I'll look into this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21771-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 15 17:55:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122895 invoked by alias); 15 Aug 2017 17:55:21 -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 122110 invoked by uid 55); 15 Aug 2017 17:55:18 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21954] unset entire environment no longer works (regression since GDB 8.0) Date: Tue, 15 Aug 2017 17:55: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: 8.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: 2017-q3/txt/msg00208.txt.bz2 Content-length: 1528 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21954 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D206726fbfdd5= 21fbb184daedb71b85030453bf0b commit 206726fbfdd521fbb184daedb71b85030453bf0b Author: Sergio Durigan Junior Date: Tue Aug 15 13:49:18 2017 -0400 Fix PR gdb/21954: make 'unset environment' work again When I made commit 9a6c7d9c021cfeb290d76584db7a01e57e7c3d4e, which C++-fied gdb/common/environ.[ch], I mistakenly altered the behaviour of the 'unset environment' command. This command, which should delete all environment variables, is now resetting the list of variables to the state they were when GDB was started. This commit fixes this regression, and also adds a test on gdb.base/environ.exp which really checks if 'unset environment' worked. gdb/ChangeLog: 2017-08-15 Sergio Durigan Junior PR gdb/21954 * infcmd.c (unset_environment_command): Use the 'clear' method on the environment instead of resetting it. gdb/testsuite/ChangeLog: 2017-08-15 Sergio Durigan Junior PR gdb/21954 * gdb.base/environ.exp: Add test to check if 'unset environment' works. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21772-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 15 17:55:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4017 invoked by alias); 15 Aug 2017 17:55:41 -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 1949 invoked by uid 48); 15 Aug 2017 17:55:38 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21954] unset entire environment no longer works (regression since GDB 8.0) Date: Tue, 15 Aug 2017 18:04: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: 8.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00209.txt.bz2 Content-length: 526 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21954 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Sergio Durigan Junior --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21773-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 15 18:04:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 123596 invoked by alias); 15 Aug 2017 18:04:27 -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 123090 invoked by uid 48); 15 Aug 2017 18:03:47 -0000 From: "msebor at gmail dot com" To: gdb-prs@sourceware.org Subject: =?UTF-8?B?W0J1ZyBidWlsZC8yMTc3M10gYmludXRpbHMtZ2RiL2dkYi9jb21tb24vdmVj?= =?UTF-8?B?Lmg6MTA4NTozMTogZXJyb3I6IOKAmHZvaWQqIG1lbWNweSh2b2lkKiwgY29u?= =?UTF-8?B?c3Qgdm9pZCosIHNpemVfdCnigJkgY29weWluZyBhbiBvYmplY3Qgb2Ygbm9u?= =?UTF-8?B?LXRyaXZpYWwgdHlwZSDigJhidHJhY2VfaW5zbl9zIHtha2Egc3RydWN0IGJ0?= =?UTF-8?B?cmFjZV9pbnNufeKAmSBmcm9tIGFuIGFycmF5IG9mIOKAmGJ0cmFjZV9pbnNu?= =?UTF-8?B?X3MgWzFdIHtha2Egc3RydWN0IGJ0cmFjZV9pbnNuIFsxXX3igJkgWy1XZXJy?= =?UTF-8?B?b3I9Y2xhc3MtbQ==?= Date: Wed, 16 Aug 2017 09:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00210.txt.bz2 Content-length: 1127 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21773 Martin Sebor changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msebor at gmail dot com --- Comment #1 from Martin Sebor --- The errors were discussed on gcc-patches, along with a trivial patch for th= em: https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00299.html The solution might need to be guarded if GDB is meant to compile with C++ 98 compiler. Like so: index ddfcddf..f344c4b 100644 --- a/gdb/common/enum-flags.h +++ b/gdb/common/enum-flags.h @@ -116,9 +116,13 @@ private: public: /* Allow default construction. */ +#if __cplusplus >=3D 201103L + enum_flags () =3D default; +#else enum_flags () : m_enum_value ((enum_type) 0) {} +#endif /* If you get an error saying these two overloads are ambiguous, then you tried to mix values of different enum types. */ --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21774-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 16 09:40:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36300 invoked by alias); 16 Aug 2017 09:40:56 -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 35167 invoked by uid 48); 16 Aug 2017 09:40:55 -0000 From: "jonah at kichwacoders dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21954] unset entire environment no longer works (regression since GDB 8.0) Date: Wed, 16 Aug 2017 09:47: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: 8.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jonah at kichwacoders dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com 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: 2017-q3/txt/msg00211.txt.bz2 Content-length: 321 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21954 --- Comment #5 from Jonah Graham --- (In reply to Sergio Durigan Junior from comment #4) > Fixed. Thanks, this fixed our failing tests in Eclipse CDT! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21775-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 16 09:57:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 96501 invoked by alias); 16 Aug 2017 09:47:50 -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 76379 invoked by uid 48); 16 Aug 2017 09:47:30 -0000 From: "jonah at kichwacoders dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21675] Regression since 8.0 printing has changed format for decimal/octal/others Date: Wed, 16 Aug 2017 13:07: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jonah at kichwacoders dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q3/txt/msg00212.txt.bz2 Content-length: 501 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21675 --- Comment #8 from Jonah Graham --- Thanks for fixing this, the test failures in Eclipse CDT are now resolved. PS due to https://sourceware.org/ml/overseers/2017-q3/msg00065.html some comments are missing in this bug: https://sourceware.org/ml/gdb-prs/2017-q3/msg00203.html https://sourceware.org/ml/gdb-prs/2017-q3/msg00204.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21776-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 16 13:07:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 59895 invoked by alias); 16 Aug 2017 13:07:05 -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 58611 invoked by uid 48); 16 Aug 2017 13:07:03 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21675] Regression since 8.0 printing has changed format for decimal/octal/others Date: Thu, 17 Aug 2017 02:11: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-q3/txt/msg00213.txt.bz2 Content-length: 623 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21675 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED Target Milestone|--- |8.1 --- Comment #9 from Tom Tromey --- Thanks for posting those links. The bug is fixed, I'm closing this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21777-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 17 02:11:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 22026 invoked by alias); 17 Aug 2017 02:11:48 -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 21456 invoked by uid 48); 17 Aug 2017 02:11:47 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug threads/19471] unexpected stop in multi-inferior debugging Date: Thu, 17 Aug 2017 13:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q3/txt/msg00214.txt.bz2 Content-length: 1945 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19471 --- Comment #5 from Tom Tromey --- I tripped over this again -- in fact I re-reported it, but the bug was lost in the sourceware disk corruption. This patch seems to fix the problem but I tend to doubt it is correct. I haven't tested some scenarios, like one process exiting while stepping in another; in fact I only tried this test program: #include int main () { if (fork () =3D=3D 0) { sleep(10); } return 0; } Here's the patch so far: diff --git a/gdb/infrun.c b/gdb/infrun.c index c51bec6..1416a48 100644 --- a/gdb/infrun.c +++ b/gdb/infrun.c @@ -5127,13 +5127,32 @@ Cannot fill $_exitsignal with the correct signal number.\n")); gdb_flush (gdb_stdout); target_mourn_inferior (inferior_ptid); - stop_print_frame =3D 0; /* In multi-inferior, there might still be other processes running. Only stop waiting if everything has exited. */ if (have_live_inferiors ()) - prepare_to_wait (ecs); + { + if (!(non_stop && target_is_non_stop_p ())) + { + struct inferior *inf; + + ALL_NON_EXITED_INFERIORS (inf) + { + thread_info *tp =3D any_live_thread_of_process (inf->pid); + inferior_ptid =3D tp->ptid; + set_current_inferior (inf); + target_terminal_inferior (); + target_resume (RESUME_ALL, 0, GDB_SIGNAL_0); + target_commit_resume (); + break; + } + } + prepare_to_wait (ecs); + } else - stop_waiting (ecs); + { + stop_print_frame =3D 0; + stop_waiting (ecs); + } return; /* The following are the only cases in which we keep going; --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21778-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 17 13:51:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 46255 invoked by alias); 17 Aug 2017 13:49:41 -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 19309 invoked by uid 48); 17 Aug 2017 13:49:15 -0000 From: "mattn.jp at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21963] New: gdb can't work on winpty Date: Fri, 18 Aug 2017 02:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mattn.jp at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00215.txt.bz2 Content-length: 1155 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21963 Bug ID: 21963 Summary: gdb can't work on winpty Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: mattn.jp at gmail dot com Target Milestone: --- Hi. On Windows, when type ^X^A gdb open tui mode. And it seems that gdb open CONOUT$ without FILE_SHARE_WRITE mode. https://github.com/bminor/binutils-gdb/blob/0749542484129e77a30f1089d6d6711= 97be5035f/gdb/windows-nat.c#L2059-L2060 So when I try to run gdb with tui mode, winpty fail to open CONOUT$. https://github.com/rprichard/winpty/blob/e7c63efbbdac5a3e4cf9434728ebfcc72b= 92a53b/src/agent/Win32ConsoleBuffer.cc#L39 I could reproduce with following operation. 1. open vim.exe or gvim.exe 2. :terminal on vim 3. start gdb 4. type ^X^A I don't make sure but I guess add FILE_SHARE_WRITE into the mode will fix t= his issue. Regards. Yasuhiro Matsumoto --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21779-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 18 02:12:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 56395 invoked by alias); 18 Aug 2017 02:12:02 -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 56369 invoked by uid 48); 18 Aug 2017 02:12:01 -0000 From: "jfhart085 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21969] New: watchpoint break not triggered on reverse continue Date: Fri, 18 Aug 2017 08:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jfhart085 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q3/txt/msg00216.txt.bz2 Content-length: 1220 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21969 Bug ID: 21969 Summary: watchpoint break not triggered on reverse continue Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: jfhart085 at gmail dot com Target Milestone: --- Created attachment 10351 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10351&action=3Ded= it utl1.c - test program with deliberate stack overwrite bash-3.2$ uname -a Linux DellXPS 4.10.0 #1 SMP Thu Apr 13 09:55:54 EDT 2017 x86_64 GNU/Linux build utl1.c as follows:=20 gcc -Wall -Wno-unused-but-set-variable -g utl1.c -o0 -o utl1 # forward continue - watch break triggered gdb utl1 c-x 2 b *main # break on 1st main() instruction run record watch -l *((long *)$sp) continue # reverse continue - watch break not triggered gdb utl1 c-x 2 b *main # break on 1st main() instruction b *main+41 # break on retq instruction run record continue watch -l *((long *)$sp) reverse-continue --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21780-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 18 08:31:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 119281 invoked by alias); 18 Aug 2017 08:31:46 -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 119241 invoked by uid 55); 18 Aug 2017 08:31:45 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tdep/21818] disassemble with v5TE remote: Assertion `info->mach == bfd_get_mach (exec_bfd)' failed. Date: Sat, 19 Aug 2017 17:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.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: 2017-q3/txt/msg00217.txt.bz2 Content-length: 1308 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21818 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Yao Qi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3De60eb2880368= b4e4752577c626ab0dadf0499cb5 commit e60eb2880368b4e4752577c626ab0dadf0499cb5 Author: Yao Qi Date: Fri Aug 18 09:30:12 2017 +0100 [ARM] Mark USER_SPECIFIED_MACHINE_TYPE in disassemble_info.flags opcodes/arm-dis.c:print_insn may update disassemble_info.mach to bfd_mach_arm_unknown unless USER_SPECIFIED_MACHINE_TYPE is marked. When default_print_insn is called for the first time, disassemble_info.mach is correctly set in GDB, but arm-dis.c:print_insn sets it to bfd_mach_arm_unknown. Then, when default_print_insn is called again (in a loop), it triggers the assert. The patch fixes the assert by marking USER_SPECIFIED_MACHINE_TYPE so th= at opcodes won't reset disassemble_info.mach. gdb: 2017-08-18 Yao Qi PR tdep/21818 * arm-tdep.c (gdb_print_insn_arm): Mark USER_SPECIFIED_MACHINE_TYPE if exec_bfd isn't NULL. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21781-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 19 17:31:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 11743 invoked by alias); 19 Aug 2017 17:31:54 -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 11702 invoked by uid 48); 19 Aug 2017 17:31:52 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug threads/17545] no obvious way to associate threads with processes Date: Sat, 19 Aug 2017 17:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: tromey at sourceware dot org 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: 7.11 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-q3/txt/msg00218.txt.bz2 Content-length: 788 https://sourceware.org/bugzilla/show_bug.cgi?id=3D17545 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |7.11 --- Comment #1 from Tom Tromey --- This was fixed by the per-inferior thread ids patch: commit 5d5658a1d3c3eb2a09c03f2f0662a1c01963c869 Author: Pedro Alves Date: Wed Jan 13 10:56:07 2016 +0000 Per-inferior/Inferior-qualified thread IDs ... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21782-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 19 17:58:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 34443 invoked by alias); 19 Aug 2017 17:58:37 -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 34400 invoked by uid 48); 19 Aug 2017 17:58:35 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug threads/19471] unexpected stop in multi-inferior debugging Date: Sat, 19 Aug 2017 18:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q3/txt/msg00219.txt.bz2 Content-length: 1041 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19471 --- Comment #6 from Tom Tromey --- That was the wrong patch, but it has the bits from the earlier missing patch in the context, so you can reconstruct it ok from there. Anyway, that patch causes an assertion failure if you also "set schedule-multiple on". The new call to target_resume(RESUME_ALL,...) calls down to linux-nat.c, ending up in x86_linux_update_debug_registers, which does=20 gdb_assert (lwp_is_stopped (lwp)); I am not sure how this code is intended to work. Like, I would have thought that the "target_resume" call would do the right thing; that is, that the backends would take care to only resume things which are resumable. So, maybe I could fix this in linux_nat_resume= ... but if this isn't generally how targets are supposed to work, then=20 maybe the correct fix is in the caller, to have it only resume threads that are not already running. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21784-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 19 18:09:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49283 invoked by alias); 19 Aug 2017 18:09:16 -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 49240 invoked by uid 48); 19 Aug 2017 18:09:15 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/13463] bad multi-inferior behavior with breakpoint resetting Date: Sat, 19 Aug 2017 18:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: cc 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: 2017-q3/txt/msg00221.txt.bz2 Content-length: 638 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13463 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --- Comment #6 from Tom Tromey --- This bug seems to depend on non-stop. When I apply the patches from bug 19471, and just use "detach-on-fork off" and "schedule-multiple on",=20 I can set breakpoints ok. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21785-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 19 18:09:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49722 invoked by alias); 19 Aug 2017 18:09: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 49681 invoked by uid 48); 19 Aug 2017 18:09:51 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/17543] could not set breakpoint in multi-inferior case Date: Sat, 19 Aug 2017 18:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00222.txt.bz2 Content-length: 578 https://sourceware.org/bugzilla/show_bug.cgi?id=3D17543 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Tom Tromey --- Duplicate. *** This bug has been marked as a duplicate of bug 13463 *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21783-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 19 18:03:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41223 invoked by alias); 19 Aug 2017 18:03:24 -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 40727 invoked by uid 48); 19 Aug 2017 18:03:24 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug threads/19471] unexpected stop in multi-inferior debugging Date: Sat, 19 Aug 2017 18:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q3/txt/msg00220.txt.bz2 Content-length: 630 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19471 --- Comment #7 from Tom Tromey --- This seems to help: diff --git a/gdb/linux-nat.c b/gdb/linux-nat.c index 4124318..bd91744 100644 --- a/gdb/linux-nat.c +++ b/gdb/linux-nat.c @@ -1557,6 +1557,9 @@ static void linux_resume_one_lwp_throw (struct lwp_info *lp, int step, enum gdb_signal signo) { + if (!lwp_is_stopped (lp)) + return; + lp->step =3D step; /* stop_pc doubles as the PC the LWP had when it was last resumed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21786-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Aug 19 18:09:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49869 invoked by alias); 19 Aug 2017 18:09:55 -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 49739 invoked by uid 48); 19 Aug 2017 18:09:53 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/13463] bad multi-inferior behavior with breakpoint resetting Date: Sun, 20 Aug 2017 03:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q3/txt/msg00223.txt.bz2 Content-length: 265 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13463 --- Comment #7 from Tom Tromey --- *** Bug 17543 has been marked as a duplicate of this bug. *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21787-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Aug 20 03:50:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 111231 invoked by alias); 20 Aug 2017 03:50:17 -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 111192 invoked by uid 48); 20 Aug 2017 03:50:15 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/13457] `catch syscall' doesn't work for parent after `fork' is called Date: Sun, 20 Aug 2017 11:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q3/txt/msg00224.txt.bz2 Content-length: 972 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13457 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --- Comment #4 from Tom Tromey --- The theory in bug 17549, and in linespec, is that breakpoints should apply to all inferiors. However, for "catch syscall", there is the additional wrinkle that the syscall tables are OS- and architecture-dependent. Maybe syscall catching should be per-architecture? Right now it is per-inferior, but this seems a bit incorrect. Another possibility might be to have a given "catch syscall" automatically apply to any inferior where the arguments are valid (re-translating syscall names as appropriate). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21788-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Aug 20 11:17:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 100683 invoked by alias); 20 Aug 2017 11:17:03 -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 100569 invoked by uid 48); 20 Aug 2017 11:17:00 -0000 From: "ciro.santilli at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug server/21979] New: Make show args show CLI arguments passed via gdbserver Date: Sun, 20 Aug 2017 11:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: ciro.santilli at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00225.txt.bz2 Content-length: 884 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21979 Bug ID: 21979 Summary: Make show args show CLI arguments passed via gdbserver Product: gdb Version: 7.11 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: server Assignee: unassigned at sourceware dot org Reporter: ciro.santilli at gmail dot com Target Milestone: --- Current behavior is a bit confusing: gdbserver :1234 ./prog.out arg0 arg1 gdb -ex 'target remote :1234' ./prog.out Then: (gdb) b main (gdb) c (gdb) show args Argument list to give program being debugged when it is started is "" (gdb) print argc $1 =3D 3 Would require sending the arguments over the protocol I expect. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21789-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Aug 20 11:18:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 102323 invoked by alias); 20 Aug 2017 11:18:48 -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 102279 invoked by uid 48); 20 Aug 2017 11:18:45 -0000 From: "ciro.santilli at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug server/21980] New: Make "show args" show arguments passed through the CLI to gdbserver Date: Sun, 20 Aug 2017 11:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ciro.santilli at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00226.txt.bz2 Content-length: 912 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21980 Bug ID: 21980 Summary: Make "show args" show arguments passed through the CLI to gdbserver Product: gdb Version: 7.11 Status: UNCONFIRMED Severity: normal Priority: P2 Component: server Assignee: unassigned at sourceware dot org Reporter: ciro.santilli at gmail dot com Target Milestone: --- Current behavior is a bit confusing: gdbserver :1234 ./prog.out arg0 arg1 gdb -ex 'target remote :1234' ./prog.out Then: (gdb) b main (gdb) c (gdb) show args Argument list to give program being debugged when it is started is "" (gdb) print argc $1 =3D 3 Would require sending the arguments over the protocol I expect. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21790-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Aug 20 11:33:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 119564 invoked by alias); 20 Aug 2017 11:33:15 -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 118497 invoked by uid 48); 20 Aug 2017 11:33:13 -0000 From: "ciro.santilli at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug server/21981] New: Document on --help and man that gdbserver --multi can take the program and CLI arguments as arguments Date: Sun, 20 Aug 2017 11:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ciro.santilli at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00227.txt.bz2 Content-length: 1526 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21981 Bug ID: 21981 Summary: Document on --help and man that gdbserver --multi can take the program and CLI arguments as arguments Product: gdb Version: 7.11 Status: UNCONFIRMED Severity: normal Priority: P2 Component: server Assignee: unassigned at sourceware dot org Reporter: ciro.santilli at gmail dot com Target Milestone: --- gdbserver --help says: Usage: gdbserver [OPTIONS] COMM PROG [ARGS ...] gdbserver [OPTIONS] --attach COMM PID gdbserver [OPTIONS] --multi COMM however it should likely be: gdbserver [OPTIONS] --multi COMM [PROG [ARGS ...]] since --multi can take either PROG or ARGS: gdbserver --multi :1234 ./prog.out a b gdb -ex 'target extended-remote :1234' ./prog.out Then: (gdb) b main (gdb) c (gdb) show args Argument list to give program being debugged when it is started is "" (gdb) print argc $1 =3D 3 and that behavior is very useful (you can have a single alias that either r= uns the program without GDB, or appends "gdbserver" before the command).=20 The only annoyance is that the arguments only work for the first run, unlik= e an explicit "set args" on host, but maybe that should be solved with: https://sourceware.org/bugzilla/show_bug.cgi?id=3D21980 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21792-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Aug 20 12:57:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 126112 invoked by alias); 20 Aug 2017 12:57:26 -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 126019 invoked by uid 48); 20 Aug 2017 12:57:20 -0000 From: "schwab@linux-m68k.org" To: gdb-prs@sourceware.org Subject: [Bug server/21979] Make show args show CLI arguments passed via gdbserver Date: Sun, 20 Aug 2017 12:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: schwab@linux-m68k.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00229.txt.bz2 Content-length: 565 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21979 Andreas Schwab changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Andreas Schwab --- dup *** This bug has been marked as a duplicate of bug 21980 *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21791-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Aug 20 11:37:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4006 invoked by alias); 20 Aug 2017 11:37:17 -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 3945 invoked by uid 48); 20 Aug 2017 11:37:12 -0000 From: "ciro.santilli at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug server/21980] Make "show args" show arguments passed through the CLI to gdbserver Date: Sun, 20 Aug 2017 12:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ciro.santilli at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00228.txt.bz2 Content-length: 391 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21980 --- Comment #1 from Ciro Santilli --- And while we are at it, also make args persist for --multi across runs: currently it is only used for the first one. See also: https://sourceware.org/bugzilla/show_bug.cgi?id=3D21981 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21793-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Aug 20 12:57:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 126529 invoked by alias); 20 Aug 2017 12:57:34 -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 126117 invoked by uid 48); 20 Aug 2017 12:57:26 -0000 From: "schwab@linux-m68k.org" To: gdb-prs@sourceware.org Subject: [Bug server/21980] Make "show args" show arguments passed through the CLI to gdbserver Date: Sun, 20 Aug 2017 14:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: schwab@linux-m68k.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00230.txt.bz2 Content-length: 262 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21980 --- Comment #2 from Andreas Schwab --- *** Bug 21979 has been marked as a duplicate of this bug. *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21794-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Aug 20 14:04:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 99339 invoked by alias); 20 Aug 2017 14:04:44 -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 99305 invoked by uid 48); 20 Aug 2017 14:04:43 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/17549] catch load seems to be inferior-specific Date: Sun, 20 Aug 2017 14:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q3/txt/msg00231.txt.bz2 Content-length: 363 https://sourceware.org/bugzilla/show_bug.cgi?id=3D17549 --- Comment #4 from Tom Tromey --- It looks like this might be as simple as clearing the new breakpoint's "pspace" member in add_solib_catchpoint. At least that works for me in initial testing. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21795-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Aug 20 14:27:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 60135 invoked by alias); 20 Aug 2017 14:27:53 -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 60083 invoked by uid 48); 20 Aug 2017 14:27:49 -0000 From: "ciro.santilli at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug server/21980] Make "show args" show arguments passed through the CLI to gdbserver Date: Mon, 21 Aug 2017 05:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ciro.santilli at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00232.txt.bz2 Content-length: 256 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21980 --- Comment #3 from Ciro Santilli --- Sorry, the site or my internet was a bit shaky. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21796-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 21 05:38:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 106603 invoked by alias); 21 Aug 2017 05:38:04 -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 103581 invoked by uid 48); 21 Aug 2017 05:37:42 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21852] Remote run without specifying a local binary crashes GDB Date: Mon, 21 Aug 2017 10:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com 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: 2017-q3/txt/msg00233.txt.bz2 Content-length: 295 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21852 --- Comment #3 from Sergio Durigan Junior --- I have a fix for this. I'm writing the commit message + testcase, will post soon. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21797-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 21 10:37:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109687 invoked by alias); 21 Aug 2017 10:37:14 -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 109399 invoked by uid 55); 21 Aug 2017 10:37:14 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/19487] Result of call to __errno_location() is truncated to 32 bit on amd64 Date: Mon, 21 Aug 2017 11:02: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.10 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q3/txt/msg00234.txt.bz2 Content-length: 4612 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19487 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dbf223d3e808e= 6fec9ee165d3d48beb74837796de commit bf223d3e808e6fec9ee165d3d48beb74837796de Author: Pedro Alves Date: Mon Aug 21 11:34:32 2017 +0100 Handle function aliases better (PR gdb/19487, errno printing) (Ref: https://sourceware.org/ml/gdb/2017-06/msg00048.html) This patch improves GDB support for function aliases defined with __attribute__ alias. For example, in the test added by this commit, there is no reference to "func_alias" in the debug info at all, only to "func"'s definition: $ nm ./testsuite/outputs/gdb.base/symbol-alias/symbol-alias | grep " func" 00000000004005ae t func 00000000004005ae T func_alias $ readelf -w ./testsuite/outputs/gdb.base/symbol-alias/symbol-alias | = grep func -B 1 -A 8 <1>: Abbrev Number: 5 (DW_TAG_subprogram) DW_AT_name : (indirect string, offset: 0x111): func DW_AT_decl_file : 1 DW_AT_decl_line : 27 DW_AT_prototyped : 1 DW_AT_type : <0xf8> DW_AT_low_pc : 0x4005ae DW_AT_high_pc : 0xb DW_AT_frame_base : 1 byte block: 9c=20=20=20=20=20=20=20=20 (DW_OP_call_frame_cfa) DW_AT_GNU_all_call_sites: 1 So all GDB knows about "func_alias" is from the minsym (elf symbol): (gdb) p func_alias $1 =3D {} 0x4005ae (gdb) ptype func_alias type =3D int () (gdb) p func $2 =3D {struct S *(void)} 0x4005ae (gdb) ptype func type =3D struct S { int field1; int field2; } *(void) The result is that calling func_alias from the command line produces incorrect results. This is similar (though not exactly the same) to the glibc errno/__errno_location/__GI___errno_location situation. On glibc, errno is defined like this: extern int *__errno_location (void); #define errno (*__errno_location ()) with __GI___errno_location being an internal alias for __errno_location. On my system's libc (F23), I do see debug info for __errno_location, in the form of name vs linkage name: <1><95a5>: Abbrev Number: 18 (DW_TAG_subprogram) <95a6> DW_AT_external : 1 <95a6> DW_AT_name : (indirect string, offset: 0x2c26): __errno_location <95aa> DW_AT_decl_file : 1 <95ab> DW_AT_decl_line : 24 <95ac> DW_AT_linkage_name: (indirect string, offset: 0x2c21): __GI___errno_location <95b0> DW_AT_prototyped : 1 <95b0> DW_AT_type : <0x9206> <95b4> DW_AT_low_pc : 0x20f40 <95bc> DW_AT_high_pc : 0x11 <95c4> DW_AT_frame_base : 1 byte block: 9c=20=20=20=20=20=20 (DW_OP_call_frame_cfa) <95c6> DW_AT_GNU_all_call_sites: 1 however that doesn't matter in practice, because GDB doesn't record demangled names anyway, and so we end up with the exact same situation covered by the testcase. So the fix is to make the expression parser find a debug symbol for the same address as the just-found minsym, when a lookup by name didn't find a debug symbol by name. We now get: (gdb) p func_alias $1 =3D {struct S *(void)} 0x4005ae (gdb) p __errno_location $2 =3D {int *(void)} 0x7ffff6e92830 <__errno_location> I've made the test exercise variable aliases too, for completeness. Those already work correctly, because unlike for function aliases, GCC emits debug information for variable aliases. Tested on GNU/Linux. gdb/ChangeLog: 2017-08-21 Pedro Alves PR gdb/19487 * c-exp.y (variable production): Handle function aliases. * minsyms.c (msymbol_is_text): New function. * minsyms.h (msymbol_is_text): Declare. * symtab.c (find_function_alias_target): New function. * symtab.h (find_function_alias_target): Declare. gdb/testsuite/ChangeLog: 2017-08-21 Pedro Alves PR gdb/19487 * gdb.base/symbol-alias.c: New. * gdb.base/symbol-alias2.c: New. * gdb.base/symbol-alias.exp: New. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21798-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 21 11:02:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109900 invoked by alias); 21 Aug 2017 11:02:19 -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 108588 invoked by uid 48); 21 Aug 2017 11:02:18 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/19487] Result of call to __errno_location() is truncated to 32 bit on amd64 Date: Mon, 21 Aug 2017 14:48: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.10 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q3/txt/msg00235.txt.bz2 Content-length: 507 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19487 --- Comment #7 from Pedro Alves --- The original issue should be fixed, provided you have glibc debug info installed. There's a follow up series pending that will improve things further, by stopping GDB from silently assuming that functions without debug info have type "int ()": https://sourceware.org/ml/gdb-patches/2017-07/msg00137.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21799-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 21 14:49:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 71908 invoked by alias); 21 Aug 2017 14:48:59 -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 71689 invoked by uid 48); 21 Aug 2017 14:48:55 -0000 From: "jon at beniston dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21985] New: set inferior-tty doesn't work for remote or sim targets Date: Mon, 21 Aug 2017 16:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jon at beniston dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q3/txt/msg00236.txt.bz2 Content-length: 1279 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21985 Bug ID: 21985 Summary: set inferior-tty doesn't work for remote or sim targets Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jon at beniston dot com Target Milestone: --- Created attachment 10356 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10356&action=3Ded= it Potential fix The set inferior-tty command doesn't work for remote or sim targets. (That = is, remote targets using remote-fileio to have the IO appear on the debug host). This is a shame as Eclipse (and potentially other front-ends) use this comm= and to separate the windows used for target IO and the gdb console. This theref= ore doesn't currently work for remote and sim targets. The attached patch adds support for this command in remote-fileio.c and remote-sim.c. Reads/writes from/to stdin/stdout are redirected to the tty. This may not be the idea way to implement this within GDB, but it does get = it working with Eclipse. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21800-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 21 16:01:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 115852 invoked by alias); 21 Aug 2017 16:01:11 -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 115509 invoked by uid 48); 21 Aug 2017 16:00:52 -0000 From: "jon at beniston dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21985] set inferior-tty doesn't work for remote or sim targets Date: Mon, 21 Aug 2017 16:17: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jon at beniston dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.isobsolete attachments.created 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: 2017-q3/txt/msg00237.txt.bz2 Content-length: 592 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21985 jon at beniston dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #10356|0 |1 is obsolete| | --- Comment #1 from jon at beniston dot com --- Created attachment 10357 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10357&action=3Ded= it Add stderr support for sim target --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21801-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 21 16:17:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 83677 invoked by alias); 21 Aug 2017 16:17:19 -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 83640 invoked by uid 48); 21 Aug 2017 16:17:17 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/19471] unexpected stop in multi-inferior debugging Date: Mon, 21 Aug 2017 16:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q3/txt/msg00238.txt.bz2 Content-length: 515 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19471 --- Comment #8 from Pedro Alves --- IWBN if we had some sort of "catch inferior-exit" / "catch exit" catchpoint, which you'd use to stop when an inferior exits. If we had that, switching = to not stopping by default would be an even easier sell. With such a catchpoint, we could then do things like "catch exit if $_exitc= ode !=3D 0", for example. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21802-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 21 16:29:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 29490 invoked by alias); 21 Aug 2017 16:29:55 -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 29461 invoked by uid 48); 21 Aug 2017 16:29:54 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/19471] unexpected stop in multi-inferior debugging Date: Mon, 21 Aug 2017 20:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q3/txt/msg00239.txt.bz2 Content-length: 1310 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19471 --- Comment #9 from Pedro Alves --- > That was the wrong patch, but it has the bits from the earlier missing > patch in the context, so you can reconstruct it ok from there. Actually, I'm confused on what would the patch look like. In all-stop (not fake all-stop-on-top-of-non-stop, e.g., against gdbserver)= , we need to issue one resume only, because once you send a resume request to the target, you can't send another until the target stops again. I don't think you should be calling target_resume at that level. It bypass= es layers of thread-is-resumed state private to infrun. You should probably be calling resume or keep_going. If an inferior exited while we were trying to step some thread of another inferior, we need to switch back to that thread instead of some other random thread. That's why you see several: if (!switch_back_to_stepped_thread (ecs)) keep_going (ecs); in infrun.c. In this case, we probably need to do something like: if (!switch_back_to_stepped_thread (ecs)) { // pick any random live thread and switch to it. keep_going (ecs); } return; --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21803-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 21 20:19:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 71655 invoked by alias); 21 Aug 2017 20:19:39 -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 71624 invoked by uid 48); 21 Aug 2017 20:19:38 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug threads/19471] unexpected stop in multi-inferior debugging Date: Tue, 22 Aug 2017 18:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q3/txt/msg00240.txt.bz2 Content-length: 927 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19471 --- Comment #10 from Tom Tromey --- (In reply to Pedro Alves from comment #9) > Actually, I'm confused on what would the patch look like. Given the below, probably not a big deal :) > in infrun.c. In this case, we probably need to do something like: >=20 > if (!switch_back_to_stepped_thread (ecs)) > { > // pick any random live thread and switch to it. > keep_going (ecs); > } > return; Thanks, that makes sense. I figured I had to call keep_going, but that failed; it doesn't switch back to a random live thread. But maybe I can do this by hand by resetting the proper members of "ecs"? Also it wasn't clear to me if we would want a stop in some situations, like "nexting and then the process dies". --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21804-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 22 18:19:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 67906 invoked by alias); 22 Aug 2017 18:19:29 -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 67861 invoked by uid 48); 22 Aug 2017 18:19:28 -0000 From: "psmith at gnu dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/14678] GDB 7.5 fails to build unless makeinfo is installed Date: Tue, 22 Aug 2017 18:31: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.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: psmith at gnu dot org X-Bugzilla-Status: WAITING 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: 2017-q3/txt/msg00241.txt.bz2 Content-length: 1363 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14678 --- Comment #3 from psmith at gnu dot org --- I'm still seeing this with GDB 8.0 using the tar.xz package from ftp.gnu.or= g. $ mkdir obj $ cd obj $ ../gdb-8.0/configure ... checking for makeinfo... no obj/gdb-8.0/missing: 81: obj/gdb-8.0/missing: makeinfo: not found ... checking for makeinfo... obj/gdb-8.0/missing makeinfo --split-size=3D5000000 configure: WARNING: *** Makeinfo is missing. Info documentation will not be built. $ make $ make install ... mv GDBvn.new GDBvn.texi /usr/src/cc/gdb-7.5/missing makeinfo --split-size=3D5000000 --split-size=3D= 5000000=20 -I /usr/src/cc/gdb-7.5/gdb/doc/../../readline/doc -I /usr/src/cc/gdb-7.5/gdb/doc/../mi -I /usr/src/cc/gdb-7.5/gdb/doc \ -o gdb.info /usr/src/cc/gdb-7.5/gdb/doc/gdb.texinfo WARNING: `makeinfo' is missing on your system. You should only need it if you modified a `.texi' or `.texinfo' file, or any other file indirectly affecting the aspect of the manual. The spurious call might also be the consequence of using a buggy `make' (AIX, DU, IRIX). You might want to install the `Texinfo' package or the `GNU make' package. Grab either from any GNU archive site. make[7]: *** [gdb.info] Error 1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21805-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 22 18:31:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 115039 invoked by alias); 22 Aug 2017 18:31:19 -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 95147 invoked by uid 48); 22 Aug 2017 18:30:28 -0000 From: "psmith at gnu dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/14678] GDB 7.5 fails to build unless makeinfo is installed Date: Tue, 22 Aug 2017 19:04: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.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: psmith at gnu dot org X-Bugzilla-Status: WAITING 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: 2017-q3/txt/msg00242.txt.bz2 Content-length: 1460 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14678 --- Comment #4 from psmith at gnu dot org --- Sorry I pasted the wrong cut buffer into my comment above: the error messag= es refer to gdb-8.0 not gdb-7.5: if test -z "-I ../gdb-8.0/gdb/doc/../../readline/doc"; then \ echo "@set SYSTEM_READLINE" >> ./GDBvn.new; \ fi if [ -n "" ]; then \ echo "@set SYSTEM_GDBINIT " >> ./GDBvn.new; \ fi mv GDBvn.new GDBvn.texi ../gdb-8.0/missing makeinfo --split-size=3D5000000 --split-size=3D5000000 = -I ../gdb-8.0/gdb/doc/../../readline/doc -I ../gdb-8.0/gdb/doc/../mi -I ../gdb-8.0/gdb/doc \ -o gdb.info ../gdb-8.0/gdb/doc/gdb.texinfo ../gdb-8.0/missing: 81: ../gdb-8.0/missing: makeinfo: not found WARNING: 'makeinfo' is missing on your system. You should only need it if you modified a '.texi' file, or any other file indirectly affecting the aspect of the manual. You might want to install the Texinfo package: The spurious makeinfo call might also be the consequence of using a buggy 'make' (AIX, DU, IRIX), in which case you might want to install GNU make: make[5]: *** [Makefile:503: gdb.info] Error 127 I'm not sure if I'm supposed to change the status of this bug myself and if= so what I should change it to... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21806-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 22 19:04:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109888 invoked by alias); 22 Aug 2017 19:04:35 -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 109825 invoked by uid 48); 22 Aug 2017 19:04:33 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/14678] GDB 7.5 fails to build unless makeinfo is installed Date: Tue, 22 Aug 2017 19:42: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.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_status 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: 2017-q3/txt/msg00243.txt.bz2 Content-length: 548 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14678 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW --- Comment #5 from Pedro Alves --- Paul, please feel free to edit the bug status. I had set it to waiting in comment #1 waiting for your response. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21807-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 22 19:42:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 70904 invoked by alias); 22 Aug 2017 19:42:24 -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 70781 invoked by uid 48); 22 Aug 2017 19:42:23 -0000 From: "psmith at gnu dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/14678] GDB 7.5 fails to build unless makeinfo is installed Date: Wed, 23 Aug 2017 21:29: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.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: psmith at gnu dot org 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: 2017-q3/txt/msg00244.txt.bz2 Content-length: 301 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14678 --- Comment #6 from psmith at gnu dot org --- Oops sorry; I dpn't have much to add beyond what Aaro said: you need to run "make install" to see the issue. Cheers! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21808-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 23 21:29:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 98643 invoked by alias); 23 Aug 2017 21:29:29 -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 97917 invoked by uid 55); 23 Aug 2017 21:29:27 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug remote/21852] Remote run without specifying a local binary crashes GDB Date: Wed, 23 Aug 2017 21:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q3/txt/msg00245.txt.bz2 Content-length: 2338 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21852 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D87215ad1651c= a3094d813eae06233fd7259b37e5 commit 87215ad1651ca3094d813eae06233fd7259b37e5 Author: Sergio Durigan Junior Date: Tue Aug 22 08:52:44 2017 -0400 Fix PR remote/21852: Remote run without specifying a local binary crash= es GDB There is an assertion that is triggering when we start GDB and instruct it to debug a remote inferior, but don't provide a local binary, like: ./gdb -nx -q --data-directory=3Ddata-directory -ex "tar ext :1234" \ -ex "set remote exec-file /bin/ls" -ex r In this case, when calling exec_file_locate_attach to locate the inferior, GDB is incorrectly resetting the breakpoints without a thread/inferior even running, which causes an assertion to be triggered: binutils-gdb/gdb/thread.c:1609: internal-error: scoped_restore_current_thread::scoped_restore_current_thread(): Assertion `= tp !=3D NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) This happens because add_current_inferior_and_thread (on remote.c) is breaking an invariant: making inferior_ptid point to a non-existing thread and then calling common code, which in this case is breakpoint_re_set. The fix is to make sure that inferior_ptid points to null_ptid if there is no thread present. A testcase is provided. Regtested on buildbot. gdb/ChangeLog: 2017-08-23 Pedro Alves PR remote/21852 * remote.c (add_current_inferior_and_thread): Set inferior_ptid to null_ptid and switch to thread without reading the registers after adding the inferior. gdb/testsuite/ChangeLog: 2017-08-23 Sergio Durigan Junior PR remote/21852 * gdb.server/normal.c: New file, copied from gdb.base. * gdb.server/run-without-local-binary.exp: New file. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21809-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 23 21:31:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 10968 invoked by alias); 23 Aug 2017 21:31:20 -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 127156 invoked by uid 48); 23 Aug 2017 21:31:13 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21852] Remote run without specifying a local binary crashes GDB Date: Wed, 23 Aug 2017 22:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00246.txt.bz2 Content-length: 526 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21852 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Sergio Durigan Junior --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21810-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 23 22:03:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 112684 invoked by alias); 23 Aug 2017 22:03:25 -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 111606 invoked by uid 48); 23 Aug 2017 22:03:25 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug threads/19471] unexpected stop in multi-inferior debugging Date: Wed, 23 Aug 2017 22:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q3/txt/msg00247.txt.bz2 Content-length: 898 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19471 --- Comment #11 from Tom Tromey --- > IWBN if we had some sort of "catch inferior-exit" / "catch exit" catchpoi= nt, which you'd use to stop when an inferior exits. If we had that, switching = to not stopping by default would be an even easier sell. I started one once. It's in my github, on the catch-exit branch. It worked by using PTRACE_O_TRACEEXIT, so not exactly the same thing. I suppose on systems without that, it could fall back to target-waitkind-ba= sed stops. It would need quite a bit of work now. And, I never wrote the gdbserver or remote protocol parts. > You should probably be calling resume or keep_going. I tried what you suggested and it works, but I don't really know if it's correct or even close. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21811-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 23 22:12:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 81204 invoked by alias); 23 Aug 2017 22:12:38 -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 80735 invoked by uid 48); 23 Aug 2017 22:12:37 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/19471] unexpected stop in multi-inferior debugging Date: Thu, 24 Aug 2017 07:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q3/txt/msg00248.txt.bz2 Content-length: 1638 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19471 --- Comment #12 from Pedro Alves --- (In reply to Tom Tromey from comment #11) > > IWBN if we had some sort of "catch inferior-exit" / "catch exit" catchp= oint, > which you'd use to stop when an inferior exits. If we had that, switching > to not stopping by default would be an even easier sell. >=20 > I started one once. It's in my github, on the catch-exit branch. >=20 > It worked by using PTRACE_O_TRACEEXIT, so not exactly the same thing. > I suppose on systems without that, it could fall back to > target-waitkind-based > stops. That must have been for intercepting the exits before the process really ex= its? Sort of like "catch syscall exit"? Maybe so that you could still inspect memory?=20=20 What I was suggesting instead was just to have a way to have GDB stop after= the inferior dies, on TARGET_WAITIND_EXITED/TARGET_WAITIND_SIGNALED. I.e., it'= d be totally an infrun.c/breakpoint.c thing, no target backend change necessary = at all. >=20 > It would need quite a bit of work now. And, I never wrote the gdbserver > or remote protocol parts. >=20 > > You should probably be calling resume or keep_going. >=20 > I tried what you suggested and it works, but I don't really know > if it's correct or even close. Next step would be testcases, exercising the several different scenarios, I think. all-stop/non-stop X single-process/multi-process X single-thread X multi-threaded X set schedule-multiple on/off X set scheduler-locking on/of= f, etc. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21812-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 24 07:46:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 77194 invoked by alias); 24 Aug 2017 07:46:13 -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 77153 invoked by uid 48); 24 Aug 2017 07:46:12 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/21852] Remote run without specifying a local binary crashes GDB Date: Thu, 24 Aug 2017 10:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson 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: 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: 2017-q3/txt/msg00249.txt.bz2 Content-length: 259 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21852 --- Comment #6 from Simon Marchi --- I haven't had time to look at it yet, but thanks! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21813-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 24 10:12:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 121117 invoked by alias); 24 Aug 2017 10:12:04 -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 119103 invoked by uid 48); 24 Aug 2017 10:12:02 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21555] "error re-setting breakpoint" on PIE executables Date: Thu, 24 Aug 2017 14:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.0.1 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00250.txt.bz2 Content-length: 501 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21555 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Yao Qi --- Close it again. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21814-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 24 14:29:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 26128 invoked by alias); 24 Aug 2017 14:29:29 -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 26099 invoked by uid 48); 24 Aug 2017 14:29:28 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/22002] New: GDB assertion on -gdwarf-5 -fdebug-types-section Date: Thu, 24 Aug 2017 14:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00251.txt.bz2 Content-length: 933 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22002 Bug ID: 22002 Summary: GDB assertion on -gdwarf-5 -fdebug-types-section Product: gdb Version: 8.0 Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Target Milestone: --- Debuggees compiled with -gdwarf-5 -fdebug-types-section now crash GDB such = as: (gdb) break 60 dwarf2read.c:9516: internal-error: void setup_type_unit_groups(die_info*, dwarf2_cu*): Assertion `per_cu->is_debug_types' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) FAIL: gdb.cp/pr17132.exp: setting breakpoint at 60 (GDB internal error) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21815-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 24 14:31:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27447 invoked by alias); 24 Aug 2017 14:31:11 -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 27367 invoked by uid 48); 24 Aug 2017 14:31:08 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/22002] Assertion on debuggee built with -gdwarf-5 -fdebug-types-section Date: Thu, 24 Aug 2017 14:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan.kratochvil at redhat dot com X-Bugzilla-Target-Milestone: 8.0.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution assigned_to target_milestone short_desc 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: 2017-q3/txt/msg00252.txt.bz2 Content-length: 1091 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22002 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jan.kratochvil at redhat d= ot com Resolution|--- |FIXED Assignee|unassigned at sourceware dot org |jan.kratochvil at r= edhat dot com Target Milestone|--- |8.0.1 Summary|GDB assertion on -gdwarf-5 |Assertion on debuggee built |-fdebug-types-section |with -gdwarf-5 | |-fdebug-types-section --- Comment #1 from Jan Kratochvil --- Checked in: f1902523c9b7941775a2c64af89de0f111b8924c master 06f84c95a2d88d03c1c231bfd436ac9d225d6615 gdb-8.0-branch --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21816-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 24 14:38:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 22610 invoked by alias); 24 Aug 2017 14:38:41 -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 22586 invoked by uid 48); 24 Aug 2017 14:38:40 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/22003] New: Incompatibility with -gdwarf-5 - DW_FORM_implicit_const Date: Thu, 24 Aug 2017 14:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00253.txt.bz2 Content-length: 1158 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22003 Bug ID: 22003 Summary: Incompatibility with -gdwarf-5 - DW_FORM_implicit_const Product: gdb Version: 8.0 Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Target Milestone: --- DWARF-5 implemented in 8.0 has a bug: -gdwarf-4: ptype logical type =3D const char [2] (gdb) PASS: gdb.base/constvars.exp: ptype logical -gdwarf-5: ptype logical type =3D const char [] (gdb) FAIL: gdb.base/constvars.exp: ptype logical <2><2fc>: Abbrev Number: 1 (DW_TAG_variable) <2fd> DW_AT_name : (indirect string, offset: 0x2eb): logical <301> DW_AT_decl_file : 1 1 DW_TAG_variable [no children] DW_AT_name DW_FORM_strp DW_AT_decl_file DW_FORM_implicit_const: 1 During symbol reading, invalid attribute class or form for 'DW_FORM_implicit_const' in '(null)'. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21817-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 24 14:40:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 101943 invoked by alias); 24 Aug 2017 14:40:56 -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 101261 invoked by uid 55); 24 Aug 2017 14:40:55 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/22003] Incompatibility with -gdwarf-5 - DW_FORM_implicit_const Date: Thu, 24 Aug 2017 14:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q3/txt/msg00254.txt.bz2 Content-length: 1562 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22003 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Jan Kratochvil : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D663c44ac4d43= 36e99c282705b1d289b365b273d3 commit 663c44ac4d4336e99c282705b1d289b365b273d3 Author: Jan Kratochvil Date: Thu Aug 24 16:39:11 2017 +0200 DWARF-5 Fix DW_FORM_implicit_const -gdwarf-4: ptype logical type =3D const char [2] (gdb) PASS: gdb.base/constvars.exp: ptype logical -gdwarf-5: ptype logical type =3D const char [] (gdb) FAIL: gdb.base/constvars.exp: ptype logical <2><2fc>: Abbrev Number: 1 (DW_TAG_variable) <2fd> DW_AT_name : (indirect string, offset: 0x2eb): logic= al <301> DW_AT_decl_file : 1 1 DW_TAG_variable [no children] DW_AT_name DW_FORM_strp DW_AT_decl_file DW_FORM_implicit_const: 1 During symbol reading, invalid attribute class or form for 'DW_FORM_implicit_const' in '(null)'. gdb/ChangeLog 2017-08-24 Jan Kratochvil PR symtab/22003 * dwarf2read.c (dwarf2_const_value_attr, dump_die_shallow) (dwarf2_get_attr_constant_value, dwarf2_fetch_constant_bytes) (skip_form_bytes, attr_form_is_constant): Handle DW_FORM_implicit_const. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21818-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 24 14:42:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 13554 invoked by alias); 24 Aug 2017 14:42:32 -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 13413 invoked by uid 55); 24 Aug 2017 14:42:31 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/22003] Incompatibility with -gdwarf-5 - DW_FORM_implicit_const Date: Thu, 24 Aug 2017 14:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q3/txt/msg00255.txt.bz2 Content-length: 1568 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22003 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The gdb-8.0-branch branch has been updated by Jan Kratochvil : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Df74f69f45570= ced87b9f778983a63157b551a129 commit f74f69f45570ced87b9f778983a63157b551a129 Author: Jan Kratochvil Date: Thu Aug 24 16:39:11 2017 +0200 DWARF-5 Fix DW_FORM_implicit_const -gdwarf-4: ptype logical type =3D const char [2] (gdb) PASS: gdb.base/constvars.exp: ptype logical -gdwarf-5: ptype logical type =3D const char [] (gdb) FAIL: gdb.base/constvars.exp: ptype logical <2><2fc>: Abbrev Number: 1 (DW_TAG_variable) <2fd> DW_AT_name : (indirect string, offset: 0x2eb): logic= al <301> DW_AT_decl_file : 1 1 DW_TAG_variable [no children] DW_AT_name DW_FORM_strp DW_AT_decl_file DW_FORM_implicit_const: 1 During symbol reading, invalid attribute class or form for 'DW_FORM_implicit_const' in '(null)'. gdb/ChangeLog 2017-08-24 Jan Kratochvil PR symtab/22003 * dwarf2read.c (dwarf2_const_value_attr, dump_die_shallow) (dwarf2_get_attr_constant_value, dwarf2_fetch_constant_bytes) (skip_form_bytes, attr_form_is_constant): Handle DW_FORM_implicit_const. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21819-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 24 14:43:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 14692 invoked by alias); 24 Aug 2017 14:43:49 -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 14618 invoked by uid 48); 24 Aug 2017 14:43:43 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/22003] Incompatibility with -gdwarf-5 - DW_FORM_implicit_const Date: Fri, 25 Aug 2017 06:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan.kratochvil at redhat dot com X-Bugzilla-Target-Milestone: 8.0.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution assigned_to target_milestone 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: 2017-q3/txt/msg00256.txt.bz2 Content-length: 759 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22003 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jan.kratochvil at redhat d= ot com Resolution|--- |FIXED Assignee|unassigned at sourceware dot org |jan.kratochvil at r= edhat dot com Target Milestone|--- |8.0.1 --- Comment #3 from Jan Kratochvil --- Checked in. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21820-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 25 06:37:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31593 invoked by alias); 25 Aug 2017 06:37:24 -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 30970 invoked by uid 48); 25 Aug 2017 06:37:23 -0000 From: "westion717 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/16841] virtual inheritance via typedef cannot find base Date: Fri, 25 Aug 2017 09:43: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: westion717 at gmail dot com 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: cc 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: 2017-q3/txt/msg00257.txt.bz2 Content-length: 737 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16841 Zeson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |westion717 at gmail dot com --- Comment #5 from Zeson --- How about the progress of this bug? I found it still exists in gdb 8.0. typedef struct { int x; } A; struct C : A { int y; }; int main() { C c; return 55; } gdb a.out ptype C::x Internal error: non-aggregate type to value_struct_elt_for_reference --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21821-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 25 09:43:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 1632 invoked by alias); 25 Aug 2017 09:43:03 -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 1315 invoked by uid 48); 25 Aug 2017 09:43:02 -0000 From: "lassi.niemisto at wapice dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21603] powerpc-linux-gnu-gdb throws internal error on remote debugging: 'gdbarch!=NULL' failed Date: Fri, 25 Aug 2017 09:44: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lassi.niemisto at wapice dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00258.txt.bz2 Content-length: 789 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21603 Lassi Niemist=C3=B6 changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lassi.niemisto at wapice d= ot com --- Comment #1 from Lassi Niemist=C3=B6 = --- I get the same with: * MPC8309E * Debugged SW compiled with GCC 4.8.2 -ggdb3 * Remote debugging or core dump analysis * Custom GDB 8.0 build with --enable-targets=3Dpowerpc-linux,powerpc-freebsd,powerpc-elf,powerpc-eabi Attaching a sample binary and sample core file for easy recreation. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21822-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 25 09:44:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4232 invoked by alias); 25 Aug 2017 09:44: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 4175 invoked by uid 48); 25 Aug 2017 09:44:41 -0000 From: "lassi.niemisto at wapice dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21603] powerpc-linux-gnu-gdb throws internal error on remote debugging: 'gdbarch!=NULL' failed Date: Fri, 25 Aug 2017 09:46: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lassi.niemisto at wapice dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q3/txt/msg00259.txt.bz2 Content-length: 363 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21603 --- Comment #2 from Lassi Niemist=C3=B6 = --- Created attachment 10364 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10364&action=3Ded= it Core file created by running on PowerPC --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21823-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 25 09:46:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 5930 invoked by alias); 25 Aug 2017 09:46:18 -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 5867 invoked by uid 48); 25 Aug 2017 09:46:16 -0000 From: "lassi.niemisto at wapice dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21603] powerpc-linux-gnu-gdb throws internal error on remote debugging: 'gdbarch!=NULL' failed Date: Fri, 25 Aug 2017 09:47: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lassi.niemisto at wapice dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q3/txt/msg00260.txt.bz2 Content-length: 357 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21603 --- Comment #3 from Lassi Niemist=C3=B6 = --- Created attachment 10365 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10365&action=3Ded= it Crashing demo program for PowerPC --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21824-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 25 09:47:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 7743 invoked by alias); 25 Aug 2017 09:47:36 -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 7698 invoked by uid 48); 25 Aug 2017 09:47:35 -0000 From: "lassi.niemisto at wapice dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21603] powerpc-linux-gnu-gdb throws internal error on remote debugging: 'gdbarch!=NULL' failed Date: Fri, 25 Aug 2017 12:43: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lassi.niemisto at wapice dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q3/txt/msg00261.txt.bz2 Content-length: 367 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21603 --- Comment #4 from Lassi Niemist=C3=B6 = --- Created attachment 10366 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10366&action=3Ded= it Source code for the crashing sample program --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21825-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 25 12:43:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64125 invoked by alias); 25 Aug 2017 12:43:58 -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 63270 invoked by uid 48); 25 Aug 2017 12:43:57 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/22006] New: Missing MI event when the "return" command is used Date: Fri, 25 Aug 2017 15:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00262.txt.bz2 Content-length: 805 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22006 Bug ID: 22006 Summary: Missing MI event when the "return" command is used Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: mi Assignee: unassigned at sourceware dot org Reporter: simon.marchi at ericsson dot com Target Milestone: --- When the users returns from a function manually with the "return" command, nothing is printed on the MI UIs that would let the front-ends know that the thread is now stopped somewhere else. The return command can come from a separate CLI ui, -interpreter-exec or CLI-in-MI, it's all the same. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21826-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 25 15:58:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 123107 invoked by alias); 25 Aug 2017 15:58:30 -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 123053 invoked by uid 48); 25 Aug 2017 15:58:29 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug threads/19471] unexpected stop in multi-inferior debugging Date: Fri, 25 Aug 2017 16:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q3/txt/msg00263.txt.bz2 Content-length: 314 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19471 --- Comment #13 from Tom Tromey --- > And, I never wrote the gdbserver or remote protocol parts. It turns out I did, just not the docs or tests. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21827-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 25 16:49:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 93040 invoked by alias); 25 Aug 2017 16:48:56 -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 80961 invoked by uid 48); 25 Aug 2017 16:48:46 -0000 From: "thopre01 at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22010] New: PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Date: Fri, 25 Aug 2017 17:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thopre01 at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00264.txt.bz2 Content-length: 1277 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22010 Bug ID: 22010 Summary: PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: thopre01 at gcc dot gnu.org Target Milestone: --- Hi, Following commit d6382fffde99214ce4aee99a208ddb703c647008 the following test regressed on arm-none-eabi targets: PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Having investigated a bit, I found the following behavior to be surprising: (gdb) print (unsigned char) '\377'=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20 $5 =3D 255 '\377' (gdb) print /d ((unsigned char) '\377')=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 $7 =3D -1 I would expect printing 255 as a decimal integer to give 255 but here it gi= ves -1. It seems to be ignoring the cast. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21828-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 25 17:51:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122141 invoked by alias); 25 Aug 2017 17:51:02 -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 121088 invoked by uid 48); 25 Aug 2017 17:51:01 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22010] PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Date: Fri, 25 Aug 2017 18:37: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: cc 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: 2017-q3/txt/msg00265.txt.bz2 Content-length: 902 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22010 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- The manual says: @item d Print as integer in signed decimal. @item u Print as integer in unsigned decimal. Note "signed". This was discussed at: https://sourceware.org/ml/gdb-patches/2017-07/msg00182.html What does the failure look like, exactly? Note that get_integer_valueof is also documented as explicitly returning a signed decimal: # Retrieve the value of EXP in the inferior, as a signed decimal value # (using "print /d"). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21829-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 25 18:37:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 55891 invoked by alias); 25 Aug 2017 18:37:59 -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 55859 invoked by uid 48); 25 Aug 2017 18:37:57 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22010] PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Date: Fri, 25 Aug 2017 20:20: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q3/txt/msg00266.txt.bz2 Content-length: 1816 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22010 --- Comment #2 from Pedro Alves --- I think I see the problem: set signof_byte [get_integer_valueof "'\\377'" -1] set signof_char [get_integer_valueof "(int) (char) -1" -1] set signof_signed_char [get_integer_valueof "(int) (signed char) -1" -1] set signof_unsigned_char [get_integer_valueof "(int) (unsigned char) -1" -= 1] check_valueof "'\\377'" ${signof_byte} check_valueof "(int) (char) -1" ${signof_char} check_valueof "(int) (signed char) -1" ${signof_signed_char} check_valueof "(int) (unsigned char) -1" ${signof_unsigned_char} Note there's no '(int)' cast in the 'get_integer_valueof \\377' test, unlike the other tests. At first sight, that should be OK, because=20 char literals in C are supposed to be int, unlike in C++. However, GDB gets that wrong (bug 19973): (gdb) ptype typeof ('\377') type =3D char (gdb) p sizeof ('\377') $5 =3D 1 If GDB realized that '\\377' really were an int, then: - if gdb thought that char is signed, that'd result in '(int) (signed char) 0xff' =3D> -1. - if gdb thought that char was unsigned, then that would result in '(int) (unsigned char) 0xff' =3D> 0xff. Probably changing the test to do: - set signof_byte [get_integer_valueof "'\\377'" -1] + set signof_byte [get_integer_valueof "(int) '\\377'" -1] would work around this. Alternatively, change the .exp to do: - set signof_byte [get_integer_valueof "'\\377'" -1] + set signed_char_lit [get_integer_valueof "'\\377' < 0" -1] - check_valueof "'\\377'" ${signof_byte} + check_valueof "'\\377' < 0" ${signed_char_lit} etc. instead, and the test .c file to match: - value =3D '\377'; + value =3D '\377' < 0; --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21830-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 25 20:20:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 114030 invoked by alias); 25 Aug 2017 20:20:56 -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 113997 invoked by uid 48); 25 Aug 2017 20:20:56 -0000 From: "psmith at gnu dot org" To: gdb-prs@sourceware.org Subject: [Bug c++/22013] New: Default value in template argument list breaks RTTI lookup Date: Fri, 25 Aug 2017 20:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: psmith at gnu dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q3/txt/msg00267.txt.bz2 Content-length: 1855 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22013 Bug ID: 22013 Summary: Default value in template argument list breaks RTTI lookup Product: gdb Version: 8.0 Status: NEW Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: psmith at gnu dot org Target Milestone: --- Created attachment 10370 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10370&action=3Ded= it Source file for reproducer While trying to access one of my types, I am getting "warning: RTTI symbol = not found for class ...". This is because one of the template parameters has a default value, and the type is found if you omit the default value but not if you include it. And, the Python type seems to want to include it. Attached find a file tvtest.cpp. To reproduce the problem: $ g++ -Wall -ggdb3 -o tvtest tvtest.cpp $ gdb tvtest ... (gdb) br 49 Breakpoint 1 at 0x989: file tvtest.cpp, line 49. (gdb) run Breakpoint 1, main (argc=3D1, argv=3D0x7fffffffe638) at tvtest.cpp:52 52 return iim.container.tree->_depth; (gdb) p iim.container.tree->_depth warning: RTTI symbol not found for class 'TreeVector::ValueWrapper>::Tree' $1 =3D 3 (gdb) python print str(gdb.parse_and_eval("iim")["container"]["tree"].type) TreeVector::ValueWrapper>::Tree * Note that the type of the container is TreeVector::ValueWrapper>::Tree (without the default templa= te argument) but when I try to use GDB to examine the contents of that type, G= DB tries to lookup TreeVector::ValueWrapper>::Tree (with= the default argument) and fails. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21831-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 25 20:21:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 115152 invoked by alias); 25 Aug 2017 20:21:36 -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 115123 invoked by uid 48); 25 Aug 2017 20:21:36 -0000 From: "psmith at gnu dot org" To: gdb-prs@sourceware.org Subject: [Bug c++/22013] Default value in template argument list breaks RTTI lookup Date: Fri, 25 Aug 2017 20:22: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: psmith at gnu dot org 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: 2017-q3/txt/msg00268.txt.bz2 Content-length: 247 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22013 --- Comment #1 from psmith at gnu dot org --- FYI I've tried this with GCC 6.2 and 7.2, and GDB 7.11 and 8.0. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21832-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Aug 25 20:22:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 118164 invoked by alias); 25 Aug 2017 20:22:56 -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 118129 invoked by uid 48); 25 Aug 2017 20:22:53 -0000 From: "psmith at gnu dot org" To: gdb-prs@sourceware.org Subject: [Bug c++/22013] Default value in template argument list breaks RTTI lookup Date: Mon, 28 Aug 2017 13:38: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: psmith at gnu dot org 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: 2017-q3/txt/msg00269.txt.bz2 Content-length: 230 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22013 --- Comment #2 from psmith at gnu dot org --- On GNU/Linux x86_64 (sorry for spammy udpates) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21833-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 28 13:38:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 105078 invoked by alias); 28 Aug 2017 13:38:01 -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 105025 invoked by uid 48); 28 Aug 2017 13:38:00 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug sim/20863] gdb-7.12 powerpc-rtems4.12-gdb does not build on FreeBSD. Date: Mon, 28 Aug 2017 14:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jhb at FreeBSD dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc target_milestone 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: 2017-q3/txt/msg00270.txt.bz2 Content-length: 786 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20863 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brobecker at gnat dot com Target Milestone|8.0.1 |--- --- Comment #4 from Joel Brobecker --- We use the "Target Milestone" field when the GDB group has decided that the= PR must be fixed for that release. Since this is not an 8.0.x regression, I do= not consider this issue as being required for the 8.0.1 release, and therefore removed the target milestone. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21834-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 28 14:23:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 96631 invoked by alias); 28 Aug 2017 14:23:43 -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 96244 invoked by uid 48); 28 Aug 2017 14:23:42 -0000 From: "joel.sherrill at oarcorp dot com" To: gdb-prs@sourceware.org Subject: [Bug sim/20863] gdb-7.12 powerpc-rtems4.12-gdb does not build on FreeBSD. Date: Mon, 28 Aug 2017 14:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: joel.sherrill at oarcorp dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jhb at FreeBSD 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: 2017-q3/txt/msg00271.txt.bz2 Content-length: 302 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20863 --- Comment #5 from Joel Sherrill --- This was a regression that appeared in 7.12. Isn't that enough to include i= t in an 8.0.1? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21835-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 28 14:36:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 111474 invoked by alias); 28 Aug 2017 14:36:43 -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 110889 invoked by uid 55); 28 Aug 2017 14:36:42 -0000 From: "brobecker at adacore dot com" To: gdb-prs@sourceware.org Subject: [Bug sim/20863] gdb-7.12 powerpc-rtems4.12-gdb does not build on FreeBSD. Date: Mon, 28 Aug 2017 14:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at adacore dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jhb at FreeBSD 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: 2017-q3/txt/msg00272.txt.bz2 Content-length: 782 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20863 --- Comment #6 from brobecker at adacore dot com --- > This was a regression that appeared in 7.12. Isn't that enough to > include it in an 8.0.1? If the fix is accepted and deemed safe for backporting, then yes, absolutely. We also typically give a bit of extra time to those actively working on fixing a bug they would really like to be fixed when they can show a plan to have the bug fixed relatively quickly. However, since this isn't an 8.0 -> 8.0.1 regression, an 8.0.1 release without the fix wouldn't make the situation worse for that particular issue. So it's unfair in that case to block everyone else while hoping someone fixes it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21836-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 28 14:42:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122295 invoked by alias); 28 Aug 2017 14:42:48 -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 119457 invoked by uid 48); 28 Aug 2017 14:42:47 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug sim/20863] gdb-7.12 powerpc-rtems4.12-gdb does not build on FreeBSD. Date: Mon, 28 Aug 2017 14:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jhb at FreeBSD dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jhb at FreeBSD 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: 2017-q3/txt/msg00273.txt.bz2 Content-length: 694 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20863 --- Comment #7 from jhb at FreeBSD dot org --- To be clear, there is a fix that hass been posted multiple times to gdb-patches@ since November of 2016, it is just waiting on a reviewer / approver. Pedro agreed to the approach used in the patch when this issue w= as first raised in a thread on gdb@ back in November (and asked me to then sub= mit the patch to gdb-patches@ for review). The issue here is that I can't get anyone to approve the patch, not that a fix isn't available. I had marked = it as a milestone in the hopes of resolving the impasse. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21837-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 28 14:51:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 45698 invoked by alias); 28 Aug 2017 14:51:22 -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 45006 invoked by uid 48); 28 Aug 2017 14:51:21 -0000 From: "joel.sherrill at oarcorp dot com" To: gdb-prs@sourceware.org Subject: [Bug sim/20863] gdb-7.12 powerpc-rtems4.12-gdb does not build on FreeBSD. Date: Mon, 28 Aug 2017 20:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: joel.sherrill at oarcorp dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jhb at FreeBSD 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: 2017-q3/txt/msg00274.txt.bz2 Content-length: 327 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20863 --- Comment #8 from Joel Sherrill --- I pinged Mike Frysinger about this PR since he was the one who commented on= the email thread and isn't on this PR. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21838-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 28 20:57:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127107 invoked by alias); 28 Aug 2017 20:57:33 -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 127081 invoked by uid 48); 28 Aug 2017 20:57:32 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/22021] New: Multi-arch exec fails with a remote target Date: Mon, 28 Aug 2017 21:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00275.txt.bz2 Content-length: 965 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22021 Bug ID: 22021 Summary: Multi-arch exec fails with a remote target Product: gdb Version: 8.0 Status: NEW Severity: normal Priority: P2 Component: remote Assignee: unassigned at sourceware dot org Reporter: simon.marchi at ericsson dot com Target Milestone: --- Starting with gdb 8.0, this test fails: $ make check RUNTESTFLAGS=3D"--target_board=3Dnative-extended-gdbserver" TESTS=3D"gdb.multi/multi-arch-exec.exp" ... # of unexpected failures 1 In gdb.log, when trying to "continue" across the exec: (gdb) continue Continuing. Truncated register 50 in remote 'g' packet Truncated register 50 in remote 'g' packet More details in this thread: https://sourceware.org/ml/gdb-patches/2017-08/threads.html#00488 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21839-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Aug 28 21:26:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 118984 invoked by alias); 28 Aug 2017 21:26:19 -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 118952 invoked by uid 48); 28 Aug 2017 21:26:19 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug exp/21827] Regression: gdb command lookup became case-sensitive; but definitions are forced into lowercase Date: Tue, 29 Aug 2017 07:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson 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 cc resolution 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: 2017-q3/txt/msg00276.txt.bz2 Content-length: 724 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21827 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |simon.marchi at ericsson d= ot com Resolution|--- |FIXED --- Comment #3 from Simon Marchi --- Fixed by https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommit;h=3Df= d437cbc432d5421492a5b0e371750de104cce93 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21840-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 29 07:29:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4346 invoked by alias); 29 Aug 2017 07:29:34 -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 3608 invoked by uid 48); 29 Aug 2017 07:29:33 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug exp/21827] Regression: gdb command lookup became case-sensitive; but definitions are forced into lowercase Date: Tue, 29 Aug 2017 09:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat 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: 8.0.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc target_milestone 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: 2017-q3/txt/msg00277.txt.bz2 Content-length: 752 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21827 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brobecker at gnat dot com Target Milestone|--- |8.0.1 --- Comment #4 from Joel Brobecker --- Also pushed to the gdb-8.0-branch in time for the 8.0.1 release. So adjusti= ng the target milestone accordingly. https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommit;h=3D9= 5eeca3bccb6121c201183e21cb5fc39a6b711a2 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21841-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 29 09:27:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 118044 invoked by alias); 29 Aug 2017 09:27:36 -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 117864 invoked by uid 48); 29 Aug 2017 09:27:34 -0000 From: "thopre01 at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22010] PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Date: Tue, 29 Aug 2017 10:51: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thopre01 at gcc dot gnu.org 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: 2017-q3/txt/msg00278.txt.bz2 Content-length: 1003 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22010 --- Comment #3 from Thomas Preud'homme --- Hi Pedro, To answer your first question, the failure looks like this: print /d '\377'^M $21 =3D -1^M (gdb) PASS: gdb.base/sizeof.exp: get integer valueof "'\377'" (-1) (...) next^M 116 value =3D (int) (char) -1;^M (gdb) p /d value^M $25 =3D 255^M (gdb) FAIL: gdb.base/sizeof.exp: check valueof "'\377'" As to your second answer, I don't understand how the missing integer cast w= ould be a problem since both the get_integer_valueof and check_valueof are consistent with one another, ie. they don't cast. Besides, my example shows that printing an expression equal to 355 as an integer value gives -1 which doesn't make sense. If (unsigned char) '\377' is equal to 355, then printing this with /d should yield 355 as well since 355 can be represented as an integer. Best regards. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21842-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 29 10:51:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68529 invoked by alias); 29 Aug 2017 10:51:35 -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 68505 invoked by uid 48); 29 Aug 2017 10:51:34 -0000 From: "rcopley at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22024] New: Internal error Date: Tue, 29 Aug 2017 18:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rcopley at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00279.txt.bz2 Content-length: 3162 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22024 Bug ID: 22024 Summary: Internal error Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: rcopley at gmail dot com Target Milestone: --- A GDB internal error happened while I was investigating Emacs bug 28268 (see "https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D28268"). My emacs image is compiled with "-O0 -g -ggdb". Note Emacs has its own ".gdbinit", see "http://git.savannah.gnu.org/cgit/emacs.git/tree/src/.gdbin= it". I ran Emacs under GDB in a Windows 7 command prompt, triggered the Emacs cr= ash in #28268 (visit git repo, open Git GUI via Magit by typing "C-x g ! g", cl= ose Git GUI, type "C-g", Emacs crashes), then entered "thread apply all bt full= ". The output: Thread 1 received signal SIGTRAP, Trace/breakpoint trap. 0x000007fefcb831f3 in KERNELBASE!DebugBreak () from C:\Windows\system32\KernelBase.dll (gdb) thread apply all bt full Thread 126 (Thread 3644.0x2bcc): #0 0x0000000076e7bd7a in ntdll!ZwWaitForSingleObject () from C:\Windows\SYSTEM32\ntdll.dll No symbol table info available. #1 0x000007fefcb510ac in WaitForSingleObjectEx () from C:\Windows\system32\KernelBase.dll No symbol table info available. #2 0x000000040027c83b in reader_thread (arg=3D0x401bca480 ) at w32proc.c:1140 cp =3D 0x401bca480 #3 0x0000000076d259cd in KERNEL32!BaseThreadInitThunk () from C:\Windows\system32\kernel32.dll No symbol table info available. #4 0x0000000076e5a561 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll No symbol table info available. #5 0x0000000000000000 in ?? () No symbol table info available. Backtrace stopped: previous frame inner to this frame (corrupt stack?) [Thread 3644.0x1a90 exited with code 2] [Thread 3644.0x2bcc exited with code 2] [Thread 3644.0x25d0 exited with code 2] [Thread 3644.0x5e4 exited with code 2] [Inferior 1 (process 3644) exited with code 02] ../../gdb-8.0/gdb/infcall.c:1154: internal-error: value* call_function_by_hand_dummy(value*, int, valu e**, void (*)(void*, int), void*): Assertion `tp->thread_fsm =3D=3D &sm->thread_fsm' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] This is a bug, please report it. For instructions, see: . ../../gdb-8.0/gdb/infcall.c:1154: internal-error: value* call_function_by_hand_dummy(value*, int, valu e**, void (*)(void*, int), void*): Assertion `tp->thread_fsm =3D=3D &sm->thread_fsm' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] This application has requested the Runtime to terminate it in an unusual wa= y. Please contact the application's support team for more information. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21843-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 29 18:21:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109387 invoked by alias); 29 Aug 2017 18:21:48 -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 109357 invoked by uid 48); 29 Aug 2017 18:21:47 -0000 From: "danielgutson at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22033] New: tell the user that the stack was exceeded Date: Tue, 29 Aug 2017 18:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: danielgutson at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00280.txt.bz2 Content-length: 867 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22033 Bug ID: 22033 Summary: tell the user that the stack was exceeded Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: danielgutson at gmail dot com Target Milestone: --- Valgrind shows "=3D=3D9392=3D=3D Stack overflow in thread #1: can't grow st= ack to 0xffe801000" A similar hint provided by gdb when the inferior segfaults would be very useful. Of course issuing "bt" shows a very large backtrace, but if there are many functions involved in the infinite recursion, telling the actual issue migh= t be very difficult. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21844-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Aug 29 18:37:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 105294 invoked by alias); 29 Aug 2017 18:37:00 -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 105271 invoked by uid 48); 29 Aug 2017 18:36:59 -0000 From: "rcopley at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22024] Internal error Date: Wed, 30 Aug 2017 04:54: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rcopley at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00281.txt.bz2 Content-length: 1248 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22024 --- Comment #1 from rcopley at gmail dot com --- Apparently, this GDB internal error happens if GDB is run in a Windows 7 or Windows 10 command prompt, and does not happen if GDB is run in an MSYS com= mand prompt. Here is a more easily reproducible recipe, assuming you have installed MSYS2 and Git For Windows. See the discussion at the Emacs bug report I mentioned before for the background. ;; Clone the Emacs repository and check out a tree that ;; features the desired Emacs crash git clone git://git.sv.gnu.org/emacs.git git checkout -b gdb-bug-22024 b65cb981cc ;; Build Emacs in an MSYS2 mingw64 shell: ./autogen.sh ./configure --config-cache "CFLAGS=3D-O0 -g3 -ggdb" make -j4 ;; Increase the "4"; but just "-j" will be painful. ;; Debug Emacs in a Windows command prompt: gdb --quiet -ex run --args src/emacs.exe -Q -eval \ "(start-process \"git gui\" \"*git gui*\" \ \"C:\\\\Program Files\\\\Git\\\\cmd\\\\Git-GUI.exe\")" ;; In Emacs, type "C-g" several times until Emacs shows ;; its abort dialog. Click "Yes" to make Emacs SIGINT ;; itself. ;; In GDB: thread apply all bt ;; GDB crashes. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21845-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 30 04:54:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 34047 invoked by alias); 30 Aug 2017 04:54:05 -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 34012 invoked by uid 48); 30 Aug 2017 04:54:05 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22010] PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Date: Wed, 30 Aug 2017 04:56: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com 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: cc 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: 2017-q3/txt/msg00282.txt.bz2 Content-length: 1113 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22010 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com, | |tromey at sourceware dot o= rg --- Comment #4 from Sergio Durigan Junior --- Worth mentioning: I've also noticed this test failing on BuildBot. Accordi= ng to the logs, the first commit that introduced this regression is: commit d6382fffde99214ce4aee99a208ddb703c647008=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 Author: Tom Tromey =20=20=20=20=20=20=20=20=20=20=20=20 Date: Tue Jul 11 06:40:40 2017 -0600=20=20=20=20=20=20=20=20=20 Fix two regressions in scalar printing=20=20=20=20=20 I'm adding Tom to the Cc list of this bug just in case. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21846-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 30 04:56:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 37981 invoked by alias); 30 Aug 2017 04:56:04 -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 37949 invoked by uid 48); 30 Aug 2017 04:56:04 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22010] PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Date: Wed, 30 Aug 2017 14:09: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com 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: 2017-q3/txt/msg00283.txt.bz2 Content-length: 422 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22010 --- Comment #5 from Sergio Durigan Junior --- Ops, sorry, a brain fart prevented me from seeing that Thomas had already f= ound the commit that introduced the regression. Well, at least this served to p= rove that one can reasonably rely on BuildBot! ;) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21847-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 30 14:09:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 5857 invoked by alias); 30 Aug 2017 14:09:05 -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 5826 invoked by uid 48); 30 Aug 2017 14:09:05 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22010] PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Date: Wed, 30 Aug 2017 15:14: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q3/txt/msg00284.txt.bz2 Content-length: 1906 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22010 --- Comment #6 from Pedro Alves --- (In reply to Thomas Preud'homme from comment #3) > To answer your first question, the failure looks like this: >=20 > print /d '\377'^M > $21 =3D -1^M > (gdb) PASS: gdb.base/sizeof.exp: get integer valueof "'\377'" (-1) >=20 > (...) >=20 > next^M > 116 value =3D (int) (char) -1;^M > (gdb) p /d value^M > $25 =3D 255^M > (gdb) FAIL: gdb.base/sizeof.exp: check valueof "'\377'" >=20 >=20 > As to your second answer, I don't understand how the missing integer cast > would be a problem since both the get_integer_valueof and check_valueof a= re > consistent with one another, ie. they don't cast. Besides, my example sho= ws > that printing an expression equal to 355 as an integer value gives -1 whi= ch > doesn't make sense. If (unsigned char) '\377' is equal to 355, then print= ing > this with /d should yield 355 as well since 355 can be represented as an > integer. Depends on the size of the "integer". If it were an "int", then yes. But the "integer" in question is a "char", which has sizeof =3D=3D 1. So "p /d (unsigned char) 0xff" is the same as "p (signed char) 0xff", like: "p /d (unsigned char) 0xff"=20 =3D=3D> "p (signed typeof ((unsigned char) 0xff) 0xff =3D> -1 Similarly: "p /d (unsigned int) 0xffffffff" =3D=3D> -1 "p /d (unsigned short) 0xffff" =3D=3D> -1 [unsigned short] "p /d (unsigned long long) 0xffffffffffffffff" =3D=3D> -1 I think that's a reasonable behavior, that mirrors the /u behavior naturall= y.=20 Like: (gdb) p /u 0xffffffffffffffff $1 =3D 18446744073709551615 and not: (gdb) p /u 0xffffffffffffffff $2 =3D 4294967295 (which would be what you'd get if "/u =3D=3D interpret as unsigned integer"= meant interpret as "unsigned int".) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21848-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 30 15:14:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 57554 invoked by alias); 30 Aug 2017 15:14:41 -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 56172 invoked by uid 48); 30 Aug 2017 15:14:41 -0000 From: "thopre01 at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22010] PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Date: Wed, 30 Aug 2017 19:12: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thopre01 at gcc dot gnu.org 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: 2017-q3/txt/msg00285.txt.bz2 Content-length: 1617 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22010 --- Comment #7 from Thomas Preud'homme --- (In reply to Pedro Alves from comment #6) > (In reply to Thomas Preud'homme from comment #3) > > To answer your first question, the failure looks like this: > >=20 > > print /d '\377'^M > > $21 =3D -1^M > > (gdb) PASS: gdb.base/sizeof.exp: get integer valueof "'\377'" (-1) > >=20 > > (...) > >=20 > > next^M > > 116 value =3D (int) (char) -1;^M > > (gdb) p /d value^M > > $25 =3D 255^M > > (gdb) FAIL: gdb.base/sizeof.exp: check valueof "'\377'" > >=20 > >=20 > > As to your second answer, I don't understand how the missing integer ca= st > > would be a problem since both the get_integer_valueof and check_valueof= are > > consistent with one another, ie. they don't cast. Besides, my example s= hows > > that printing an expression equal to 355 as an integer value gives -1 w= hich > > doesn't make sense. If (unsigned char) '\377' is equal to 355, then pri= nting > > this with /d should yield 355 as well since 355 can be represented as an > > integer. >=20 > Depends on the size of the "integer". If it were an "int", then yes. But > the "integer" in question is a "char", which has sizeof =3D=3D 1. > So "p /d (unsigned char) 0xff" is the same as "p (signed char) 0xff", lik= e: > "p /d (unsigned char) 0xff"=20 > =3D=3D> "p (signed typeof ((unsigned char) 0xff) 0xff > =3D> -1 Oh I see, didn't realize it was dependent on the type of the expression. Th= anks for the explanation. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21849-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 30 19:12:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 32034 invoked by alias); 30 Aug 2017 19:12:27 -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 31969 invoked by uid 48); 30 Aug 2017 19:12:27 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22046] New: Regression on older kernels for T (stopped) processes Date: Wed, 30 Aug 2017 19:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00286.txt.bz2 Content-length: 1755 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22046 Bug ID: 22046 Summary: Regression on older kernels for T (stopped) processes Product: gdb Version: 8.0 Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Target Milestone: --- On <=3DRHEL6 hosts Fedora/RHEL GDB started to 'kill -STOP' all processes it detached. Even those not originally T-stopped. This is a Fedora-specific patch which is based on upstream GDB's PROC_STATE_STOPPED state. I believe (I did not verify) this patch did regress it: commit d617208bb06bd461b52ce041d89f7127e3044762 Author: Pedro Alves Date: Mon Jul 25 12:42:17 2016 +0100=20=20=20 linux-procfs: Introduce enum proc_state As originally there was strstr() but now there is strcmp() and so the missi= ng trailing '\n' no longer matches. The Bug was found by Michal Kolar. Reproducibility: $ gdb -p $PID (gdb) quit $ ... Actual results: =3D=3D=3D RHEL6.9 x86_64 # scl enable devtoolset-7 bash RHEL6.9 x86_64 # which gdb /opt/rh/devtoolset-7/root/usr/bin/gdb RHEL6.9 x86_64 # ./testcase.sh 24737 pts/0 S+ 0:00 /bin/sleep 4 24737 pts/0 T+ 0:00 /bin/sleep 4 RHEL6.9 x86_64 # =3D=3D=3D Expected results: =3D=3D=3D RHEL6.9 x86_64 # which gdb /usr/bin/gdb RHEL6.9 x86_64 # ./testcase.sh 24708 pts/0 S+ 0:00 /bin/sleep 4 24708 pts/0 S+ 0:00 /bin/sleep 4 ./testcase.sh: line 20: kill: (24708) - No such process RHEL6.9 x86_64 # =3D=3D=3D Tested: 5b86dbf4549af98c4428da4764182e03f22c58ab --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21850-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 30 19:13:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 33442 invoked by alias); 30 Aug 2017 19:13:11 -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 33372 invoked by uid 48); 30 Aug 2017 19:13:11 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22046] Regression on older kernels for T (stopped) processes Date: Wed, 30 Aug 2017 19:14: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan.kratochvil at redhat dot com X-Bugzilla-Target-Milestone: 8.0.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc assigned_to target_milestone 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: 2017-q3/txt/msg00287.txt.bz2 Content-length: 617 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22046 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |jan.kratochvil at redhat d= ot com Assignee|unassigned at sourceware dot org |jan.kratochvil at r= edhat dot com Target Milestone|--- |8.0.1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21851-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 30 19:14:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 39068 invoked by alias); 30 Aug 2017 19:14:48 -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 39045 invoked by uid 48); 30 Aug 2017 19:14:47 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22046] Regression on older kernels for T (stopped) processes Date: Wed, 30 Aug 2017 22:10: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan.kratochvil at redhat dot com X-Bugzilla-Target-Milestone: 8.0.1 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: 2017-q3/txt/msg00288.txt.bz2 Content-length: 332 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22046 --- Comment #1 from Jan Kratochvil --- [patch+8.0.1] Fix T-stopped detach regression on old kernels https://sourceware.org/ml/gdb-patches/2017-08/msg00532.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21852-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Aug 30 22:10:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 125264 invoked by alias); 30 Aug 2017 22:10:30 -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 125231 invoked by uid 48); 30 Aug 2017 22:10:30 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22010] PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Date: Thu, 31 Aug 2017 20:33: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: 2017-q3/txt/msg00289.txt.bz2 Content-length: 408 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22010 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |tromey at sourcewar= e dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21853-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 31 20:33:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 58972 invoked by alias); 31 Aug 2017 20:33:50 -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 58946 invoked by uid 48); 31 Aug 2017 20:33:49 -0000 From: "mdennis at merfer dot net" To: gdb-prs@sourceware.org Subject: [Bug python/21460] SIGTERM received under finalize_python() causes segmentation fault Date: Thu, 31 Aug 2017 21:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mdennis at merfer dot net X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00290.txt.bz2 Content-length: 390 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21460 mdennis changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mdennis at merfer dot net --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21854-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Aug 31 21:21:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 59994 invoked by alias); 31 Aug 2017 21:21:11 -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 59974 invoked by uid 48); 31 Aug 2017 21:21:11 -0000 From: "goeran at uddeborg dot se" To: gdb-prs@sourceware.org Subject: [Bug gdb/22056] New: Breakpoint conditions takes precedence over ignore counts, contrary to documentation Date: Fri, 01 Sep 2017 00:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: goeran at uddeborg dot se X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q3/txt/msg00291.txt.bz2 Content-length: 3394 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22056 Bug ID: 22056 Summary: Breakpoint conditions takes precedence over ignore counts, contrary to documentation Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: goeran at uddeborg dot se Target Milestone: --- Created attachment 10382 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10382&action=3Ded= it Test case In the documentation node gdb =E2=86=92 Stopping =E2=86=92 Breakpoints =E2= =86=92 Condition it says: If a breakpoint has a positive ignore count and a condition, the condition is not checked. Once the ignore count reaches zero, GDB resumes checking the condition. That does not seem to reflect the actual behaviour. GDB does not seem to decrement the ignore count unless the condition is met. To illustrate, download the attached test case c.c, and then do mimmi$$ cc -g c.c -o c mimmi$$ gdb c GNU gdb (GDB) Fedora 8.0-24.fc26 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copyi= ng" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from c...done. (gdb) b f if x<100 Breakpoint 1 at 0x40048e: file c.c, line 5. (gdb) r Starting program: /home/g=C3=B6ran/c=20 Missing separate debuginfos, use: dnf debuginfo-install glibc-2.25-7.fc26.x86_64 Breakpoint 1, f (x=3D1) at c.c:5 5 i +=3D x; (gdb) continue 3 Will ignore next 2 crossings of breakpoint 1. Continuing. Breakpoint 1, f (x=3D4) at c.c:5 5 i +=3D x; Behaviour: When doing "continue 3", I would expect the calls of "f(100)" on lines 11 a= nd 12 to be ignored. The condition is false, but the documentation says that should not be checked as long as there is an ignore count. Then the condit= ion makes the execution pass the third call of "f(100)" too, and execution shou= ld stop when reaching the call of "f(2)" on line 14. But as can be seen, the execution isn't stopped until the call of "f(4)" on line 16. That makes me believe the ignore count is only decremented when t= he condition is met, that is for the calls of "f(2)" and "f(3)". It isn't obvious to me if the implementation or the documentation is "corre= ct". I guess changing the documentation to agree with the implementation would cause the least surprises out ther. Environment: Fedora Linux gdb-8.0-24.fc26.x86_64 (Side note: I believe I reported this to the mailing list a long time ago. = I guess that report was lost.) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21855-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 01 00:39:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 22200 invoked by alias); 1 Sep 2017 00:39:48 -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 22171 invoked by uid 48); 1 Sep 2017 00:39:48 -0000 From: "stephen.kim at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/21695] Loss of line info Date: Fri, 01 Sep 2017 04:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: stephen.kim at oracle dot com 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: cc 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: 2017-q3/txt/msg00292.txt.bz2 Content-length: 868 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21695 Stephen Kim changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stephen.kim at oracle dot = com --- Comment #1 from Stephen Kim --- My employer assigned a few engineers to GNU toolchains so that we make some contribution to the projects. I am one of the engineers, and would like to start with this bug. As it does not seem that I can assign this bug to myse= lf, I am leaving this comment here. I would like to take a look at this bug, and will see if this is in my area or not. If it is, I will do my best to fix t= his bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21856-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 01 04:17:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36195 invoked by alias); 1 Sep 2017 04:17:06 -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 36015 invoked by uid 55); 1 Sep 2017 04:17:06 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22046] Regression on older kernels for T (stopped) processes Date: Fri, 01 Sep 2017 04:19: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan.kratochvil at redhat dot com X-Bugzilla-Target-Milestone: 8.0.1 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: 2017-q3/txt/msg00293.txt.bz2 Content-length: 2150 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22046 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Jan Kratochvil : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D5c811d30d12b= 6f7c6c6f4ce6d03408d987154548 commit 5c811d30d12b6f7c6c6f4ce6d03408d987154548 Author: Jan Kratochvil Date: Fri Sep 1 06:13:40 2017 +0200 PR gdb/22046: Fix T-stopped detach regression on old Linux kernels On <=3DRHEL6 hosts Fedora/RHEL GDB started to 'kill -STOP' all processe= s it detached. Even those not originally T-stopped. This is a Fedora-speci= fic patch which is based on upstream GDB's PROC_STATE_STOPPED state. I believe (I did not verify) this patch did regress it: commit d617208bb06bd461b52ce041d89f7127e3044762 Author: Pedro Alves Date: Mon Jul 25 12:42:17 2016 +0100 linux-procfs: Introduce enum proc_state As originally there was strstr() but now there is strcmp() and so the missing trailing '\n' no longer matches. The Bug was found by Michal Kolar. Reproducibility: $ gdb -p $PID (gdb) quit $ ... Actual results: =3D=3D=3D RHEL6.9 x86_64 # scl enable devtoolset-7 bash RHEL6.9 x86_64 # which gdb /opt/rh/devtoolset-7/root/usr/bin/gdb RHEL6.9 x86_64 # ./testcase.sh 24737 pts/0 S+ 0:00 /bin/sleep 4 24737 pts/0 T+ 0:00 /bin/sleep 4 RHEL6.9 x86_64 # =3D=3D=3D Expected results: =3D=3D=3D RHEL6.9 x86_64 # which gdb /usr/bin/gdb RHEL6.9 x86_64 # ./testcase.sh 24708 pts/0 S+ 0:00 /bin/sleep 4 24708 pts/0 S+ 0:00 /bin/sleep 4 ./testcase.sh: line 20: kill: (24708) - No such process RHEL6.9 x86_64 # =3D=3D=3D gdb/ChangeLog 2017-09-01 Jan Kratochvil PR gdb/22046 * nat/linux-procfs.c (parse_proc_status_state): Fix PROC_STATE_STOP= PED detection. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21857-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 01 04:19:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 47250 invoked by alias); 1 Sep 2017 04:19:40 -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 47230 invoked by uid 55); 1 Sep 2017 04:19:40 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22046] Regression on older kernels for T (stopped) processes Date: Fri, 01 Sep 2017 04:23: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan.kratochvil at redhat dot com X-Bugzilla-Target-Milestone: 8.0.1 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: 2017-q3/txt/msg00294.txt.bz2 Content-length: 2156 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22046 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The gdb-8.0-branch branch has been updated by Jan Kratochvil : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dc247e38d78a9= 8f85066e4a61032ee742d08a0579 commit c247e38d78a98f85066e4a61032ee742d08a0579 Author: Jan Kratochvil Date: Fri Sep 1 06:13:40 2017 +0200 PR gdb/22046: Fix T-stopped detach regression on old Linux kernels On <=3DRHEL6 hosts Fedora/RHEL GDB started to 'kill -STOP' all processe= s it detached. Even those not originally T-stopped. This is a Fedora-speci= fic patch which is based on upstream GDB's PROC_STATE_STOPPED state. I believe (I did not verify) this patch did regress it: commit d617208bb06bd461b52ce041d89f7127e3044762 Author: Pedro Alves Date: Mon Jul 25 12:42:17 2016 +0100 linux-procfs: Introduce enum proc_state As originally there was strstr() but now there is strcmp() and so the missing trailing '\n' no longer matches. The Bug was found by Michal Kolar. Reproducibility: $ gdb -p $PID (gdb) quit $ ... Actual results: =3D=3D=3D RHEL6.9 x86_64 # scl enable devtoolset-7 bash RHEL6.9 x86_64 # which gdb /opt/rh/devtoolset-7/root/usr/bin/gdb RHEL6.9 x86_64 # ./testcase.sh 24737 pts/0 S+ 0:00 /bin/sleep 4 24737 pts/0 T+ 0:00 /bin/sleep 4 RHEL6.9 x86_64 # =3D=3D=3D Expected results: =3D=3D=3D RHEL6.9 x86_64 # which gdb /usr/bin/gdb RHEL6.9 x86_64 # ./testcase.sh 24708 pts/0 S+ 0:00 /bin/sleep 4 24708 pts/0 S+ 0:00 /bin/sleep 4 ./testcase.sh: line 20: kill: (24708) - No such process RHEL6.9 x86_64 # =3D=3D=3D gdb/ChangeLog 2017-09-01 Jan Kratochvil PR gdb/22046 * nat/linux-procfs.c (parse_proc_status_state): Fix PROC_STATE_STOP= PED detection. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21858-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 01 04:23:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 121114 invoked by alias); 1 Sep 2017 04:23:50 -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 121072 invoked by uid 48); 1 Sep 2017 04:23:49 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22046] Regression on older kernels for T (stopped) processes Date: Fri, 01 Sep 2017 05:11: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan.kratochvil at redhat dot com X-Bugzilla-Target-Milestone: 8.0.1 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00295.txt.bz2 Content-length: 524 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22046 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Jan Kratochvil --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21859-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 01 05:11:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 112624 invoked by alias); 1 Sep 2017 05:11:20 -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 112560 invoked by uid 48); 1 Sep 2017 05:11:20 -0000 From: "anwilli5 at ncsu dot edu" To: gdb-prs@sourceware.org Subject: [Bug tui/9765] Scrolling to end of program in asm layout is broken Date: Fri, 01 Sep 2017 09:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 6.50 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: anwilli5 at ncsu dot edu X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q3/txt/msg00296.txt.bz2 Content-length: 667 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9765 anwilli5 at ncsu dot edu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anwilli5 at ncsu dot edu --- Comment #3 from anwilli5 at ncsu dot edu --- This happens for me as well (with gdb 8.0) except that gdb aborts with error message "(gdb) terminate called after throwing an instance of 'gdb_exception_RETURN_MASK_ERROR'" instead of just getting into a bad state= as described by Pedro. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21860-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 01 09:38:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94957 invoked by alias); 1 Sep 2017 09:38:30 -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 94927 invoked by uid 48); 1 Sep 2017 09:38:29 -0000 From: "thopre01 at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/21695] Loss of line info Date: Fri, 01 Sep 2017 12:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thopre01 at gcc dot gnu.org 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: 2017-q3/txt/msg00297.txt.bz2 Content-length: 1007 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21695 --- Comment #2 from Thomas Preud'homme --- (In reply to Stephen Kim from comment #1) > My employer assigned a few engineers to GNU toolchains so that we make so= me > contribution to the projects. I am one of the engineers, and would like to > start with this bug. As it does not seem that I can assign this bug to > myself, I am leaving this comment here. I would like to take a look at th= is > bug, and will see if this is in my area or not. If it is, I will do my be= st > to fix this bug. Hi Stephen, First of all thank you for proposing your help here, that's much appreciate= d. You'll find more info on how to contribute at [1]. As to assigning bugzilla ticket, I believe this is only possible once you get commit approval, at le= ast that's how it work in GCC bugzilla. [1] https://sourceware.org/gdb/contribute/ Best regards. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21861-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 01 12:13:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88526 invoked by alias); 1 Sep 2017 12:13:27 -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 88445 invoked by uid 48); 1 Sep 2017 12:13:26 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/9765] Scrolling to end of program in asm layout is broken Date: Fri, 01 Sep 2017 15:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: 6.50 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 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: 2017-q3/txt/msg00298.txt.bz2 Content-length: 425 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9765 --- Comment #4 from Pedro Alves --- Sounds like we're letting C++ exceptions cross ncurses (in this case the me= mory error exception). We can't, because it's a C library that may have not been built with unwind info. [we had a similar problem with readline]. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21862-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 01 15:29:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 74737 invoked by alias); 1 Sep 2017 15:29:33 -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 74531 invoked by uid 48); 1 Sep 2017 15:29:33 -0000 From: "koutheir at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22063] New: infrun.c:5570: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed. Date: Fri, 01 Sep 2017 15:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: koutheir at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00299.txt.bz2 Content-length: 3398 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22063 Bug ID: 22063 Summary: infrun.c:5570: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed. Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: critical Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: koutheir at gmail dot com Target Milestone: --- New UI allocated GNU gdb (GDB) 8.0 [copyright-notice-removed] (gdb) 0x0000007fb7fd3d00 in _start () from [path]/sysroots/aarch64-poky-linux/lib/ld-linux-aarch64.so.1=20=20=20=20=20= =20 Temporary breakpoint 4, main (argc=3D13, argv=3D0x7ffffffa88) at [path]/jdk/src/share/bin/main.c:95 95 int margc =3D -1; sha Reading symbols from [path]/jdk/lib/aarch64/jli/libjli.so...done. Reading symbols from [path]/sysroots/aarch64-poky-linux/lib/libc.so.6...don= e. Reading symbols from [path]/sysroots/aarch64-poky-linux/lib/.debug/libc-2.24.so...done. Reading symbols from [path]/sysroots/aarch64-poky-linux/lib/libdl.so.2...do= ne. Reading symbols from [path]/sysroots/aarch64-poky-linux/lib/.debug/libdl-2.24.so...done. Reading symbols from [path]/sysroots/aarch64-poky-linux/lib/libpthread.so.0...done. Reading symbols from [path]/sysroots/aarch64-poky-linux/lib/.debug/libpthread-2.24.so...done. (gdb) c Continuing. Breakpoint 1, JLI_Launch (argc=3D0, argv=3D0x411118, jargc=3D1, jargv=3D0x0, appclassc=3D1, appclassv=3D0x0, fullversion=3D0x400ab0 "[data-removed]", dotversion=3D0x400aa8 "1.8", pname=3D0x400a90 "java", lname=3D0x400a98 "ope= njdk", javaargs=3D0 '\000', cpwildcard=3D1 '\001', javaw=3D0 '\000', ergo=3D0) at [path]/jdk/src/share/bin/java.c:304 304 return JVMInit(&ifn, threadStackSize, argc, argv, mode, what, r= et); (gdb) sha Reading symbols from [path]/hotspot/linux_aarch64_compiler1/debug/libjvm.so...done. Reading symbols from [path]/hotspot/linux_aarch64_compiler1/debug/libjvm.debuginfo...done. Reading symbols from [path]/sysroots/aarch64-poky-linux/usr/lib/libstdc++.so.6...done. Reading symbols from [path]/sysroots/aarch64-poky-linux/usr/lib/.debug/libstdc++.so.6.0.22...don= e. Reading symbols from [path]/sysroots/aarch64-poky-linux/lib/libm.so.6...don= e. Reading symbols from [path]/sysroots/aarch64-poky-linux/lib/.debug/libm-2.24.so...done. Reading symbols from [path]/sysroots/aarch64-poky-linux/lib/libgcc_s.so.1...done. Reading symbols from [path]/sysroots/aarch64-poky-linux/lib/.debug/libgcc_s.so.1...done. (gdb) c Continuing. [New Thread 3445.3448] infrun.c:5570: internal-error: int finish_step_over(execution_control_state= *): Assertion `ecs->event_thread->control.trap_expected' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) n This is a bug, please report it. For instructions, see: . infrun.c:5570: internal-error: int finish_step_over(execution_control_state= *): Assertion `ecs->event_thread->control.trap_expected' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) y Command aborted. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21863-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 01 15:30:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27213 invoked by alias); 1 Sep 2017 15:30:38 -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 26407 invoked by uid 48); 1 Sep 2017 15:30:38 -0000 From: "koutheir at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22063] infrun.c:5570: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed. Date: Sun, 03 Sep 2017 00:14: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: koutheir at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00300.txt.bz2 Content-length: 400 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22063 Koutheir Attouchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |koutheir at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21864-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Sep 03 00:14:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127540 invoked by alias); 3 Sep 2017 00:14:22 -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 127514 invoked by uid 48); 3 Sep 2017 00:14:22 -0000 From: "Hsiangkai at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21698] Stepping from python interface broken? Date: Sun, 03 Sep 2017 00:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: Hsiangkai at gmail dot com 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: cc 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: 2017-q3/txt/msg00301.txt.bz2 Content-length: 906 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21698 Hsiangkai Wang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Hsiangkai at gmail dot com --- Comment #1 from Hsiangkai Wang --- Currently, current_ui->prompt_state will keep PROMPTED value under python interface. Synchronous commands will behave like asynchronous commands and GDB will raise an exception while checking thread state before executing synchronouse commands in ensure_not_running(). Initialize current_ui->prompt_state to PROMPT_NEEDED in execute_gdb_command() to ensure synchronous commands will complete before next command under python interface. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21865-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Sep 03 00:34:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 5637 invoked by alias); 3 Sep 2017 00:34:22 -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 5613 invoked by uid 48); 3 Sep 2017 00:34:22 -0000 From: "Hsiangkai at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21698] Stepping from python interface broken? Date: Sun, 03 Sep 2017 17:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: Hsiangkai at gmail dot com 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: 2017-q3/txt/msg00302.txt.bz2 Content-length: 889 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21698 --- Comment #2 from Hsiangkai Wang --- I have prepared a patch for this bug. However, I am not sure is it reasonab= le to change prompt_state in execute_gdb_command() or not. Any comments? --- gdb/python/python.c | 1 + 1 file changed, 1 insertion(+) diff --git a/gdb/python/python.c b/gdb/python/python.c index c53e10f..49b5eff 100644 --- a/gdb/python/python.c +++ b/gdb/python/python.c @@ -589,6 +589,7 @@ execute_gdb_command (PyObject *self, PyObject *args, PyObject *kw) struct interp *interp; scoped_restore save_async =3D make_scoped_restore (¤t_ui->asyn= c, 0); + current_ui->prompt_state =3D PROMPT_NEEDED; scoped_restore save_uiout =3D make_scoped_restore (¤t_uiout); -- --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21866-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Sep 03 17:51:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 114682 invoked by alias); 3 Sep 2017 17:51:57 -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 114658 invoked by uid 48); 3 Sep 2017 17:51:57 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21969] watchpoint break not triggered on reverse continue Date: Sun, 03 Sep 2017 18:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_status cf_reconfirmed_on cc everconfirmed 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: 2017-q3/txt/msg00303.txt.bz2 Content-length: 871 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21969 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-09-03 CC| |simon.marchi at ericsson d= ot com Ever confirmed|0 |1 --- Comment #1 from Simon Marchi --- Thanks for reporting. I see the same behavior, hardware watchpoints don't trigger in reverse execution or in replay. As a workaround, you can use "s= et can-use-hw-watchpoints 0" to force the use of software watchpoints. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21867-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Sep 03 18:51:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 62201 invoked by alias); 3 Sep 2017 18:51:07 -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 61606 invoked by uid 48); 3 Sep 2017 18:51:06 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21506] python execute(to_string=True) no longer captures certain output since e7ea3ec7 Date: Sun, 03 Sep 2017 18:54: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_status cf_reconfirmed_on cc everconfirmed 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: 2017-q3/txt/msg00304.txt.bz2 Content-length: 1156 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21506 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-09-03 CC| |tromey at sourceware dot o= rg Ever confirmed|0 |1 --- Comment #1 from Tom Tromey --- I've also noticed this when using my python gdb gui --=20 the gui uses to_string=3DTrue for some commands to suppress output, but gdb still emits the output anyway now. For example in my case it happens in tui_on_normal_stop, which calls print_stop_event for each UI. I'm not sure what can be done about this. if nothing, it's worth noting that the output is sub-par as well: (top) 30 args.argv =3D argv; 31 args.interpreter_p =3D INTERP_CONSOLE; ... that is, it doesn't try to erase the prompt first. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21868-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Sep 03 18:54:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 77073 invoked by alias); 3 Sep 2017 18:54:50 -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 77041 invoked by uid 48); 3 Sep 2017 18:54:50 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22010] PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Date: Sun, 03 Sep 2017 19:00: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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: 2017-q3/txt/msg00305.txt.bz2 Content-length: 393 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22010 --- Comment #8 from Tom Tromey --- Created attachment 10391 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10391&action=3Ded= it patch Can you try this patch? It was hard to tell from the buildbot if this worked. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21869-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Sep 03 19:00:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 96239 invoked by alias); 3 Sep 2017 19:00:42 -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 95425 invoked by uid 48); 3 Sep 2017 19:00:41 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22010] PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Date: Mon, 04 Sep 2017 13:21: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q3/txt/msg00306.txt.bz2 Content-length: 370 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22010 --- Comment #9 from Sergio Durigan Junior --- Kind of "out of topic" here, but do you think it'd make sense to also list = FAIL -> PASS on buildbot? I think it'd make it easier to spot regression fixes. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21870-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Sep 04 13:21:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 37959 invoked by alias); 4 Sep 2017 13:21:35 -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 37358 invoked by uid 48); 4 Sep 2017 13:21:34 -0000 From: "anprice at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/17346] i386 record: Missing AVX Date: Mon, 04 Sep 2017 15:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: anprice at redhat dot com 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: cc 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: 2017-q3/txt/msg00307.txt.bz2 Content-length: 393 https://sourceware.org/bugzilla/show_bug.cgi?id=3D17346 Andy Price changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anprice at redhat dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21871-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Sep 04 15:09:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 93269 invoked by alias); 4 Sep 2017 15:09:53 -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 93241 invoked by uid 48); 4 Sep 2017 15:09:52 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug record/22081] New: i386 record: doesn't support syscall number 318 = getrandom Date: Tue, 05 Sep 2017 03:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00308.txt.bz2 Content-length: 1015 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22081 Bug ID: 22081 Summary: i386 record: doesn't support syscall number 318 =3D getrandom Product: gdb Version: 8.0 Status: NEW Severity: normal Priority: P2 Component: record Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Target Milestone: --- $ gdb -ex 'set env LD_BIND_NOW=3D1' -ex start -ex record -ex c --args pytho= n3 Process record and replay target doesn't support syscall number 318 Process record: failed to record execution log. Program stopped. 0x00007ffff6ba41a1 in getrandom (buffer=3D0x7ffff7dd5ba0 <_Py_HashSecret>, length=3D24, flags=3D1) at ../sysdeps/unix/sysv/linux/getrandom.c:30 30 return SYSCALL_CANCEL (getrandom, buffer, length, flags); Fedora 26 x86_64 gdb-8.0-24.fc26.x86_64 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21872-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 05 03:49:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127467 invoked by alias); 5 Sep 2017 03:49:59 -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 127437 invoked by uid 55); 5 Sep 2017 03:49:59 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug sim/20863] gdb-7.12 powerpc-rtems4.12-gdb does not build on FreeBSD. Date: Tue, 05 Sep 2017 10:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jhb at FreeBSD 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: 2017-q3/txt/msg00309.txt.bz2 Content-length: 1419 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20863 --- Comment #9 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by John Baldwin : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D625ce09c1cfb= 557725310f602ee66ac1475d780e commit 625ce09c1cfb557725310f602ee66ac1475d780e Author: John Baldwin Date: Mon Sep 4 19:53:50 2017 -0700 Define an error function in the PPC simulator library. Previously this used the error function from GDB directly when linked against GDB instead of the error method in the host callbacks structure. This was exposed via a link error when GDB was converted to C++. The error function invokes the error callback similar to sim_io_error. Note that there are also error functions in sim/ppc/main.c and sim/ppc/misc.c. The ppc libsim.a expects each consumer to provide several symbols used by the library including "error". sim-calls.c provides these symbols when the library is linked into gdb. The dgen, igen, tmp-filter, tmp-ld-decode, tmp-ld-cache, and tmp-ld-insn programs use the functions from misc.c. psim uses the functions from main.c. sim/ppc/ChangeLog: PR sim/20863 * sim_calls.c (error): New function. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21873-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 05 10:53:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 60494 invoked by alias); 5 Sep 2017 10:53: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 60466 invoked by uid 48); 5 Sep 2017 10:53:23 -0000 From: "dudu.arbel at ilrd dot co.il" To: gdb-prs@sourceware.org Subject: [Bug compile/22084] New: unexpected padding in a struct Date: Tue, 05 Sep 2017 11:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: compile X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dudu.arbel at ilrd dot co.il X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00310.txt.bz2 Content-length: 879 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22084 Bug ID: 22084 Summary: unexpected padding in a struct Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: compile Assignee: unassigned at sourceware dot org Reporter: dudu.arbel at ilrd dot co.il Target Milestone: --- There is an unexpected padding (of 2 bytes) between x and y in the following struct. This causes it to be of size 12 bytes, although 8 bytes should be enough. This behavior seems inconsistent to many other examples (e.g - reducing x s= ize to 15, eliminates the padding) typedef struct { unsigned int x:16; unsigned int y:17; unsigned short z; } XXX; --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21874-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 05 11:43:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 48880 invoked by alias); 5 Sep 2017 11:43:02 -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 48858 invoked by uid 55); 5 Sep 2017 11:43:02 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug sim/20863] gdb-7.12 powerpc-rtems4.12-gdb does not build on FreeBSD. Date: Tue, 05 Sep 2017 11:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jhb at FreeBSD 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: 2017-q3/txt/msg00311.txt.bz2 Content-length: 1428 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20863 --- Comment #10 from cvs-commit at gcc dot gnu.org --- The gdb-8.0-branch branch has been updated by John Baldwin : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D6854bcdfba43= dd3a2058565bbf85868c9914bf39 commit 6854bcdfba43dd3a2058565bbf85868c9914bf39 Author: John Baldwin Date: Mon Sep 4 19:53:50 2017 -0700 Define an error function in the PPC simulator library. Previously this used the error function from GDB directly when linked against GDB instead of the error method in the host callbacks structure. This was exposed via a link error when GDB was converted to C++. The error function invokes the error callback similar to sim_io_error. Note that there are also error functions in sim/ppc/main.c and sim/ppc/misc.c. The ppc libsim.a expects each consumer to provide several symbols used by the library including "error". sim-calls.c provides these symbols when the library is linked into gdb. The dgen, igen, tmp-filter, tmp-ld-decode, tmp-ld-cache, and tmp-ld-insn programs use the functions from misc.c. psim uses the functions from main.c. sim/ppc/ChangeLog: PR sim/20863 * sim_calls.c (error): New function. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21875-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 05 11:43:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 50500 invoked by alias); 5 Sep 2017 11:43:54 -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 50472 invoked by uid 48); 5 Sep 2017 11:43:54 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug sim/20863] gdb-7.12 powerpc-rtems4.12-gdb does not build on FreeBSD. Date: Tue, 05 Sep 2017 11:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jhb at FreeBSD dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jhb at FreeBSD dot org X-Bugzilla-Target-Milestone: 8.0.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-q3/txt/msg00312.txt.bz2 Content-length: 555 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20863 jhb at FreeBSD dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED Target Milestone|--- |8.0.1 --- Comment #11 from jhb at FreeBSD dot org --- Fix merged to 8.0 branch for 8.0.1. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21876-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 05 11:45:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53772 invoked by alias); 5 Sep 2017 11:45:42 -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 53732 invoked by uid 48); 5 Sep 2017 11:45:41 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug python/21698] Stepping from python interface broken? Date: Tue, 05 Sep 2017 11:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: cc 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: 2017-q3/txt/msg00313.txt.bz2 Content-length: 791 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21698 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org --- Comment #3 from Yao Qi --- (In reply to Hsiangkai Wang from comment #2) > I have prepared a patch for this bug. However, I am not sure is it > reasonable to change prompt_state in execute_gdb_command() or not. Any > comments? gdb-patches@sourceware.org is the right place to discuss patches, so post your patch there. You can ask something you are not sure about there. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21877-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 05 11:58:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 77764 invoked by alias); 5 Sep 2017 11:58:02 -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 77729 invoked by uid 48); 5 Sep 2017 11:58:02 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug compile/22084] unexpected padding in a struct Date: Tue, 05 Sep 2017 12:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: compile X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00314.txt.bz2 Content-length: 587 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22084 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org --- Comment #1 from Yao Qi --- Can you provide more information? like how do you "compile" the example? N= ote that different ABIs have different requirements on padding. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21878-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 05 12:03:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 83076 invoked by alias); 5 Sep 2017 12:03:10 -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 83055 invoked by uid 48); 5 Sep 2017 12:03:09 -0000 From: "dudu.arbel at ilrd dot co.il" To: gdb-prs@sourceware.org Subject: [Bug compile/22084] unexpected padding in a struct Date: Tue, 05 Sep 2017 13:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: compile X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dudu.arbel at ilrd dot co.il X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00315.txt.bz2 Content-length: 765 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22084 --- Comment #2 from Dudu --- I use gcc.=20 the whole file to compile is: #include "stdio.h" typedef struct { unsigned int x:16; unsigned int y:17; unsigned short z; } XXX; int main()=20 {=20 XXX x =3D {0}; x.x =3D 65536-1; x.y =3D 2*65536-1; x.z =3D 65536-1; char *p =3D (char*)&x; printf("1st byte is=3D%d\n", *p++); printf("2nd byte is=3D%d\n", *p++); printf("3rd byte is=3D%d\n", *p++); printf("\nsize of xxx=3D%ld\n", sizeof(XXX)); } the output is: -1 (ok), -1 (ok), 0 (!? - wrong padding) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21879-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 05 13:20:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 32415 invoked by alias); 5 Sep 2017 13:20:22 -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 31898 invoked by uid 48); 5 Sep 2017 13:20:22 -0000 From: "Hsiangkai at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21698] Stepping from python interface broken? Date: Tue, 05 Sep 2017 15:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: Hsiangkai at gmail dot com 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: 2017-q3/txt/msg00316.txt.bz2 Content-length: 743 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21698 --- Comment #4 from Hsiangkai Wang --- (In reply to Yao Qi from comment #3) > (In reply to Hsiangkai Wang from comment #2) > > I have prepared a patch for this bug. However, I am not sure is it > > reasonable to change prompt_state in execute_gdb_command() or not. Any > > comments? >=20 > gdb-patches@sourceware.org is the right place to discuss patches, so post > your patch there. You can ask something you are not sure about there. Thanks for your reminding. I have sent a patch to gdb-patches@sourceware.o= rg for review. https://patchwork.sourceware.org/patch/22595/ --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21880-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 05 15:13:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 65295 invoked by alias); 5 Sep 2017 15:13:58 -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 64750 invoked by uid 48); 5 Sep 2017 15:13:58 -0000 From: "thopre01 at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22010] PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Date: Tue, 05 Sep 2017 15:54: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thopre01 at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q3/txt/msg00317.txt.bz2 Content-length: 412 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22010 --- Comment #10 from Thomas Preud'homme --- (In reply to Tom Tromey from comment #8) > Created attachment 10391 [details] > patch >=20 > Can you try this patch? > It was hard to tell from the buildbot if this worked. Yep, works. Best regards. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21881-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 05 15:54:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36926 invoked by alias); 5 Sep 2017 15:54:26 -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 36679 invoked by uid 48); 5 Sep 2017 15:54:26 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug compile/22084] unexpected padding in a struct Date: Wed, 06 Sep 2017 09:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: compile X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00318.txt.bz2 Content-length: 571 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22084 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Yao Qi --- It is definitely not a GDB bug. If you think GCC is wrong, report it gcc bugzilla. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21882-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 06 09:57:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27615 invoked by alias); 6 Sep 2017 09:57:14 -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 27584 invoked by uid 48); 6 Sep 2017 09:57:14 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/21695] Loss of line info Date: Wed, 06 Sep 2017 10:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: cc 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: 2017-q3/txt/msg00319.txt.bz2 Content-length: 723 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21695 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #3 from Pedro Alves --- Stephen, I've given editbugs privileges to your account and to the accounts= of a a couple of your colleagues that I recognized as contributing upstream recently. Welcome on board! Another URL to look at is: https://sourceware.org/gdb/wiki/ContributionChecklist --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21883-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 06 10:18:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 26527 invoked by alias); 6 Sep 2017 10:18:50 -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 26505 invoked by uid 48); 6 Sep 2017 10:18:49 -0000 From: "thopre01 at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/22091] New: PASS->FAIL: gdb.arch/thumb2-it.exp Date: Wed, 06 Sep 2017 11:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thopre01 at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00320.txt.bz2 Content-length: 1051 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22091 Bug ID: 22091 Summary: PASS->FAIL: gdb.arch/thumb2-it.exp Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: thopre01 at gcc dot gnu.org Target Milestone: --- Hi, Many gdb.arch/thumb2-it.exp tests regressed after 7022349d5c86bae74b49225515f42d2e221bd368. As one would expect, errors are of the form: 'it_1' has unknown return type; cast the call to its declared return type (gdb) FAIL: gdb.arch/thumb2-it.exp: it_1, call stepi 41 bx lr @ Thumb-2 OK (gdb) FAIL: gdb.arch/thumb2-it.exp: it_1, stepi 0 continue Continuing. [Inferior 1 (Remote target) exited normally] I guess either the assembly should be enhanced with some debug info or the = exp file changed to cast calls as suggested. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21884-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 06 11:58:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 123932 invoked by alias); 6 Sep 2017 11:58:27 -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 123464 invoked by uid 48); 6 Sep 2017 11:58:27 -0000 From: "paveld500 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22092] New: GdbServer fails to build for host "aarch64-linux-gnu" Date: Wed, 06 Sep 2017 12:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: paveld500 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q3/txt/msg00321.txt.bz2 Content-length: 2529 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22092 Bug ID: 22092 Summary: GdbServer fails to build for host "aarch64-linux-gnu" Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: paveld500 at gmail dot com Target Milestone: --- Created attachment 10398 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10398&action=3Ded= it make error log 1. Which version of gdb is used? gdb 8.0 2. How to reproduce the issue? 1. Got to gdb-8.0/gdb/gdbsrver/ folder 2. execute command in bash: "./configure --host=3Daarch64-linux-gnu CC=3Daarch64-linux-gnu-gcc" 3. Start "make" 4. Receive the following output: See attachment. 3. What version of aarch64-linux-gnu-gcc was used? Using built-in specs. COLLECT_GCC=3Daarch64-linux-gnu-gcc COLLECT_LTO_WRAPPER=3D/usr/lib/gcc-cross/aarch64-linux-gnu/6/lto-wrapper Target: aarch64-linux-gnu Configured with: ../src/configure -v --with-pkgversion=3D'Ubuntu/Linaro 6.3.0-12ubuntu2' --with-bugurl=3Dfile:///usr/share/doc/gcc-6/README.Bugs --enable-languages=3Dc,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=3D/u= sr --program-suffix=3D-6 --enable-shared --enable-linker-build-id --libexecdir=3D/usr/lib --without-included-gettext --enable-threads=3Dposix --libdir=3D/usr/lib --enable-nls --with-sysroot=3D/ --enable-clocale=3Dgnu --enable-libstdcxx-debug --enable-libstdcxx-time=3Dyes --with-default-libstdcxx-abi=3Dnew --enable-gnu-unique-object --disable-libquadmath --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=3Dgtk --enable-gtk-cairo --with-java-home=3D/usr/lib/jvm/java-1.5.0-gcj-6-arm64-cross/jre --enable-java-home --with-jvm-root-dir=3D/usr/lib/jvm/java-1.5.0-gcj-6-arm64-cross --with-jvm-jar-dir=3D/usr/lib/jvm-exports/java-1.5.0-gcj-6-arm64-cross --with-arch-directory=3Daarch64 --with-ecj-jar=3D/usr/share/java/eclipse-ec= j.jar --disable-libgcj --enable-multiarch --enable-fix-cortex-a53-843419 --disable-werror --enable-checking=3Drelease --build=3Dx86_64-linux-gnu --host=3Dx86_64-linux-gnu --target=3Daarch64-linux-gnu --program-prefix=3Daarch64-linux-gnu- --includedir=3D/usr/aarch64-linux-gnu= /include Thread model: posix gcc version 6.3.0 20170406 (Ubuntu/Linaro 6.3.0-12ubuntu2)=20 Expected behavior: no errors and build passes. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21885-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 06 12:08:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 57732 invoked by alias); 6 Sep 2017 12:08:45 -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 54471 invoked by uid 48); 6 Sep 2017 12:08:43 -0000 From: "paveld500 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22092] GdbServer fails to build for host "aarch64-linux-gnu" Date: Wed, 06 Sep 2017 13:02: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: paveld500 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00322.txt.bz2 Content-length: 43705 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22092 --- Comment #1 from pavel --- Output of configure command: checking whether to enable maintainer-specific portions of Makefiles... no checking for aarch64-linux-gnu-gcc... aarch64-linux-gnu-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables...=20 checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether aarch64-linux-gnu-gcc accepts -g... yes checking for aarch64-linux-gnu-gcc option to accept ISO C89... none needed checking for aarch64-linux-gnu-g++... no checking for aarch64-linux-gnu-c++... no checking for aarch64-linux-gnu-gpp... no checking for aarch64-linux-gnu-aCC... no checking for aarch64-linux-gnu-CC... no checking for aarch64-linux-gnu-cxx... no checking for aarch64-linux-gnu-cc++... no checking for aarch64-linux-gnu-cl.exe... no checking for aarch64-linux-gnu-FCC... no checking for aarch64-linux-gnu-KCC... no checking for aarch64-linux-gnu-RCC... no checking for aarch64-linux-gnu-xlC_r... no checking for aarch64-linux-gnu-xlC... no checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking how to run the C preprocessor... aarch64-linux-gnu-gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking build system type... x86_64-pc-linux-gnu checking host system type... aarch64-unknown-linux-gnu checking target system type... aarch64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking for aarch64-linux-gnu-ar... aarch64-linux-gnu-ar checking for aarch64-linux-gnu-ranlib... aarch64-linux-gnu-ranlib checking whether g++ supports C++11 features by default... yes checking for ANSI C header files... (cached) yes checking dependency style of aarch64-linux-gnu-gcc... gcc3 =3D=3D=3D configuring in build-gnulib-gdbserver (/home/pavel/harman/gdb-8.0/gdb/gdbserver/build-gnulib-gdbserver) configure: running /bin/bash .././../gnulib/configure --disable-option-chec= king '--prefix=3DNONE' '--host=3Daarch64-linux-gnu' 'CC=3Daarch64-linux-gnu-gcc' 'host_alias=3Daarch64-linux-gnu' --cache-file=3D/dev/null --srcdir=3D.././.= ./gnulib checking whether to enable maintainer-specific portions of Makefiles... no checking for aarch64-linux-gnu-gcc... aarch64-linux-gnu-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables...=20 checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether aarch64-linux-gnu-gcc accepts -g... yes checking for aarch64-linux-gnu-gcc option to accept ISO C89... none needed checking how to run the C preprocessor... aarch64-linux-gnu-gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking whether _XOPEN_SOURCE should be defined... no checking for Minix Amsterdam compiler... no checking for aarch64-linux-gnu-ar... aarch64-linux-gnu-ar checking for aarch64-linux-gnu-ranlib... aarch64-linux-gnu-ranlib checking build system type... x86_64-pc-linux-gnu checking host system type... aarch64-unknown-linux-gnu checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking for aarch64-linux-gnu-gcc... (cached) aarch64-linux-gnu-gcc checking whether we are using the GNU C compiler... (cached) yes checking whether aarch64-linux-gnu-gcc accepts -g... (cached) yes checking for aarch64-linux-gnu-gcc option to accept ISO C89... (cached) none needed checking target system type... aarch64-unknown-linux-gnu checking for working alloca.h... yes checking for alloca... yes checking for canonicalize_file_name... yes checking for getcwd... yes checking for readlink... yes checking for realpath... yes checking for btowc... yes checking for isblank... yes checking for iswctype... yes checking for mbsrtowcs... yes checking for mempcpy... yes checking for wmemchr... yes checking for wmemcpy... yes checking for wmempcpy... yes checking for gettimeofday... yes checking for symlink... yes checking for lstat... yes checking for mbsinit... yes checking for mbrtowc... yes checking for mprotect... yes checking for link... yes checking for iswcntrl... yes checking whether // is distinct from /... unknown, assuming no checking whether realpath works... guessing yes checking for sys/param.h... yes checking for dirent.h... yes checking for wctype.h... yes checking for sys/time.h... yes checking for sys/socket.h... yes checking for limits.h... yes checking for wchar.h... yes checking for stdint.h... (cached) yes checking for inttypes.h... (cached) yes checking for unistd.h... (cached) yes checking for math.h... yes checking for sys/mman.h... yes checking for sys/stat.h... (cached) yes checking for features.h... yes checking whether the preprocessor supports include_next... yes checking whether system header files limit the line length... no checking for complete errno.h... yes checking for mbstate_t... yes checking whether frexp() can be used without linking with libm... yes checking whether alarm is declared... yes checking whether long double and double are the same... no checking for C/C++ restrict keyword... __restrict checking for struct timeval... yes checking for wide-enough struct timeval.tv_sec member... yes checking whether gettimeofday is declared without a macro... yes checking whether limits.h has ULLONG_WIDTH etc.... no checking for unsigned long long int... yes checking for long long int... yes checking whether stdint.h conforms to C99... yes checking whether stdint.h predates C++11... no checking whether stdint.h has UINTMAX_WIDTH etc.... no checking whether imaxabs is declared without a macro... yes checking whether imaxdiv is declared without a macro... yes checking whether strtoimax is declared without a macro... yes checking whether strtoumax is declared without a macro... yes checking for inttypes.h... (cached) yes checking whether the inttypes.h PRIxNN macros are broken... no checking where to find the exponent in a 'double'... word 1 bit 20 checking whether byte ordering is bigendian... (cached) no checking for nl_langinfo and CODESET... yes checking for working fcntl.h... cross-compiling checking whether getc_unlocked is declared... yes checking whether we are using the GNU C Library >=3D 2.1 or uClibc... yes checking whether lstat correctly handles trailing slash... guessing yes checking whether malloc, realloc, calloc are POSIX compliant... yes checking for stdlib.h... (cached) yes checking for GNU libc compatible malloc... yes checking for a traditional japanese locale... none checking for a transitional chinese locale... none checking for a french Unicode locale... none checking for a traditional french locale... none checking for mmap... yes checking for MAP_ANONYMOUS... yes checking whether memchr works... guessing no checking whether memmem is declared... yes checking for memmem... yes checking whether memmem works... guessing yes checking for sigset_t... yes checking for pid_t... yes checking for uid_t in sys/types.h... yes checking for stdbool.h that conforms to C99... yes checking for _Bool... yes checking for wchar_t... yes checking whether ffsl is declared without a macro... yes checking whether ffsll is declared without a macro... yes checking whether memmem is declared without a macro... yes checking whether mempcpy is declared without a macro... yes checking whether memrchr is declared without a macro... yes checking whether rawmemchr is declared without a macro... yes checking whether stpcpy is declared without a macro... yes checking whether stpncpy is declared without a macro... yes checking whether strchrnul is declared without a macro... yes checking whether strdup is declared without a macro... yes checking whether strncat is declared without a macro... yes checking whether strndup is declared without a macro... yes checking whether strnlen is declared without a macro... yes checking whether strpbrk is declared without a macro... yes checking whether strsep is declared without a macro... yes checking whether strcasestr is declared without a macro... yes checking whether strtok_r is declared without a macro... yes checking whether strerror_r is declared without a macro... yes checking whether strsignal is declared without a macro... yes checking whether strverscmp is declared without a macro... yes checking whether strtok_r is declared... (cached) yes checking whether stat file-mode macros are broken... no checking for mode_t... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for struct timespec in ... yes checking whether uses 'inline' correctly... yes checking for wint_t... yes checking for alloca as a compiler built-in... yes checking whether alphasort is declared without a macro... yes checking whether closedir is declared without a macro... yes checking whether dirfd is declared without a macro... yes checking whether fdopendir is declared without a macro... yes checking whether opendir is declared without a macro... yes checking whether readdir is declared without a macro... yes checking whether rewinddir is declared without a macro... yes checking whether scandir is declared without a macro... yes checking for dirfd... yes checking whether dirfd is declared... (cached) yes checking whether dirfd is a macro... no checking whether // is distinct from /... (cached) unknown, assuming no checking for flexible array member... yes checking whether conversion from 'int' to 'long double' works... guessing y= es checking for working GNU fnmatch... guessing no checking whether isblank is declared... yes checking whether isblank is declared... (cached) yes checking whether frexp works... guessing yes checking whether frexpl is declared... yes checking whether frexpl() can be used without linking with libm... yes checking whether frexpl works... guessing yes checking whether gettimeofday clobbers localtime buffer... guessing no checking for gettimeofday with POSIX signature... almost checking whether INT32_MAX < INTMAX_MAX... yes checking whether INT64_MAX =3D=3D LONG_MAX... yes checking whether UINT32_MAX < UINTMAX_MAX... yes checking whether UINT64_MAX =3D=3D ULONG_MAX... yes checking whether isnan(double) can be used without linking with libm... yes checking whether isnan(long double) can be used without linking with libm... yes checking whether isnanl works... guessing yes checking whether NAN macro works... yes checking whether HUGE_VAL works... yes checking whether acosf is declared without a macro... yes checking whether acosl is declared without a macro... yes checking whether asinf is declared without a macro... yes checking whether asinl is declared without a macro... yes checking whether atanf is declared without a macro... yes checking whether atanl is declared without a macro... yes checking whether cbrt is declared without a macro... yes checking whether cbrtf is declared without a macro... yes checking whether cbrtl is declared without a macro... yes checking whether ceilf is declared without a macro... yes checking whether ceill is declared without a macro... yes checking whether copysign is declared without a macro... yes checking whether copysignf is declared without a macro... yes checking whether copysignl is declared without a macro... yes checking whether cosf is declared without a macro... yes checking whether cosl is declared without a macro... yes checking whether coshf is declared without a macro... yes checking whether expf is declared without a macro... yes checking whether expl is declared without a macro... yes checking whether exp2 is declared without a macro... yes checking whether exp2f is declared without a macro... yes checking whether exp2l is declared without a macro... yes checking whether expm1 is declared without a macro... yes checking whether expm1f is declared without a macro... yes checking whether expm1l is declared without a macro... yes checking whether fabsf is declared without a macro... yes checking whether fabsl is declared without a macro... yes checking whether floorf is declared without a macro... yes checking whether floorl is declared without a macro... yes checking whether fma is declared without a macro... yes checking whether fmaf is declared without a macro... yes checking whether fmal is declared without a macro... yes checking whether fmod is declared without a macro... yes checking whether fmodf is declared without a macro... yes checking whether fmodl is declared without a macro... yes checking whether frexpf is declared without a macro... yes checking whether frexpl is declared without a macro... yes checking whether hypotf is declared without a macro... yes checking whether hypotl is declared without a macro... yes checking whether ilogb is declared without a macro... yes checking whether ilogbf is declared without a macro... yes checking whether ilogbl is declared without a macro... yes checking whether ldexpf is declared without a macro... yes checking whether ldexpl is declared without a macro... yes checking whether log is declared without a macro... yes checking whether logf is declared without a macro... yes checking whether logl is declared without a macro... yes checking whether log10 is declared without a macro... yes checking whether log10f is declared without a macro... yes checking whether log10l is declared without a macro... yes checking whether log1p is declared without a macro... yes checking whether log1pf is declared without a macro... yes checking whether log1pl is declared without a macro... yes checking whether log2 is declared without a macro... yes checking whether log2f is declared without a macro... yes checking whether log2l is declared without a macro... yes checking whether logb is declared without a macro... yes checking whether logbf is declared without a macro... yes checking whether logbl is declared without a macro... yes checking whether modf is declared without a macro... yes checking whether modff is declared without a macro... yes checking whether modfl is declared without a macro... yes checking whether powf is declared without a macro... yes checking whether remainder is declared without a macro... yes checking whether remainderf is declared without a macro... yes checking whether remainderl is declared without a macro... yes checking whether rint is declared without a macro... yes checking whether rintf is declared without a macro... yes checking whether rintl is declared without a macro... yes checking whether round is declared without a macro... yes checking whether roundf is declared without a macro... yes checking whether roundl is declared without a macro... yes checking whether sinf is declared without a macro... yes checking whether sinl is declared without a macro... yes checking whether sinhf is declared without a macro... yes checking whether sqrtf is declared without a macro... yes checking whether sqrtl is declared without a macro... yes checking whether tanf is declared without a macro... yes checking whether tanl is declared without a macro... yes checking whether tanhf is declared without a macro... yes checking whether trunc is declared without a macro... yes checking whether truncf is declared without a macro... yes checking whether truncl is declared without a macro... yes checking whether mbrtowc handles incomplete characters... guessing yes checking whether mbrtowc works as well as mbtowc... guessing yes checking whether mbrtowc handles a NULL pwc argument... guessing yes checking whether mbrtowc handles a NULL string argument... guessing yes checking whether mbrtowc has a correct return value... guessing yes checking whether mbrtowc returns 0 when parsing a NUL character... guessing= yes checking whether mbrtowc works on empty input... guessing no checking whether the C locale is free of encoding errors... guessing no checking whether mbrtowc handles incomplete characters... (cached) guessing= yes checking whether mbrtowc works as well as mbtowc... (cached) guessing yes checking whether mbrtowc handles incomplete characters... (cached) guessing= yes checking whether mbrtowc works as well as mbtowc... (cached) guessing yes checking whether mbsrtowcs works... guessing yes checking bp-sym.h usability... no checking bp-sym.h presence... no checking for bp-sym.h... no checking whether memmem works in linear time... guessing yes checking for memmem... (cached) yes checking whether memmem works... (cached) guessing yes checking for rawmemchr... yes checking whether readlink signature is correct... yes checking whether readlink handles trailing slash correctly... guessing yes checking whether rename honors trailing slash on destination... guessing yes checking whether rename honors trailing slash on source... guessing yes checking whether rename manages hard links correctly... guessing yes checking whether rename manages existing destinations correctly... guessing= yes checking whether rmdir works... guessing yes checking for volatile sig_atomic_t... yes checking for sighandler_t... yes checking whether pthread_sigmask is declared without a macro... yes checking whether sigaction is declared without a macro... yes checking whether sigaddset is declared without a macro... yes checking whether sigdelset is declared without a macro... yes checking whether sigemptyset is declared without a macro... yes checking whether sigfillset is declared without a macro... yes checking whether sigismember is declared without a macro... yes checking whether sigpending is declared without a macro... yes checking whether sigprocmask is declared without a macro... yes checking for ssize_t... yes checking whether stat handles trailing slashes on directories... guessing y= es checking whether stat handles trailing slashes on files... guessing yes checking for max_align_t... yes checking whether NULL can be used in arbitrary expressions... yes checking which flavor of printf attribute matches inttypes macros... system checking whether dprintf is declared without a macro... yes checking whether fpurge is declared without a macro... no checking whether fseeko is declared without a macro... yes checking whether ftello is declared without a macro... yes checking whether getdelim is declared without a macro... yes checking whether getline is declared without a macro... yes checking whether gets is declared without a macro... no checking whether pclose is declared without a macro... yes checking whether popen is declared without a macro... yes checking whether renameat is declared without a macro... yes checking whether snprintf is declared without a macro... yes checking whether tmpfile is declared without a macro... yes checking whether vdprintf is declared without a macro... yes checking whether vsnprintf is declared without a macro... yes checking whether _Exit is declared without a macro... yes checking whether atoll is declared without a macro... yes checking whether canonicalize_file_name is declared without a macro... yes checking whether getloadavg is declared without a macro... yes checking whether getsubopt is declared without a macro... yes checking whether grantpt is declared without a macro... yes checking whether initstate is declared without a macro... yes checking whether initstate_r is declared without a macro... yes checking whether mkdtemp is declared without a macro... yes checking whether mkostemp is declared without a macro... yes checking whether mkostemps is declared without a macro... yes checking whether mkstemp is declared without a macro... yes checking whether mkstemps is declared without a macro... yes checking whether posix_openpt is declared without a macro... yes checking whether ptsname is declared without a macro... yes checking whether ptsname_r is declared without a macro... yes checking whether qsort_r is declared without a macro... yes checking whether random is declared without a macro... yes checking whether random_r is declared without a macro... yes checking whether realpath is declared without a macro... yes checking whether rpmatch is declared without a macro... yes checking whether secure_getenv is declared without a macro... yes checking whether setenv is declared without a macro... yes checking whether setstate is declared without a macro... yes checking whether setstate_r is declared without a macro... yes checking whether srandom is declared without a macro... yes checking whether srandom_r is declared without a macro... yes checking whether strtod is declared without a macro... yes checking whether strtoll is declared without a macro... yes checking whether strtoull is declared without a macro... yes checking whether unlockpt is declared without a macro... yes checking whether unsetenv is declared without a macro... yes checking for strchrnul... yes checking whether strchrnul works... guessing yes checking for strtok_r... yes checking whether strtok_r works... guessing no checking for nlink_t... yes checking whether fchmodat is declared without a macro... yes checking whether fstat is declared without a macro... yes checking whether fstatat is declared without a macro... yes checking whether futimens is declared without a macro... yes checking whether lchmod is declared without a macro... yes checking whether lstat is declared without a macro... yes checking whether mkdirat is declared without a macro... yes checking whether mkfifo is declared without a macro... yes checking whether mkfifoat is declared without a macro... yes checking whether mknod is declared without a macro... yes checking whether mknodat is declared without a macro... yes checking whether stat is declared without a macro... yes checking whether utimensat is declared without a macro... yes checking whether chdir is declared without a macro... yes checking whether chown is declared without a macro... yes checking whether dup is declared without a macro... yes checking whether dup2 is declared without a macro... yes checking whether dup3 is declared without a macro... yes checking whether environ is declared without a macro... yes checking whether euidaccess is declared without a macro... yes checking whether faccessat is declared without a macro... yes checking whether fchdir is declared without a macro... yes checking whether fchownat is declared without a macro... yes checking whether fdatasync is declared without a macro... yes checking whether fsync is declared without a macro... yes checking whether ftruncate is declared without a macro... yes checking whether getcwd is declared without a macro... yes checking whether getdomainname is declared without a macro... yes checking whether getdtablesize is declared without a macro... yes checking whether getgroups is declared without a macro... yes checking whether gethostname is declared without a macro... yes checking whether getlogin is declared without a macro... yes checking whether getlogin_r is declared without a macro... yes checking whether getpagesize is declared without a macro... yes checking whether getusershell is declared without a macro... yes checking whether setusershell is declared without a macro... yes checking whether endusershell is declared without a macro... yes checking whether group_member is declared without a macro... yes checking whether isatty is declared without a macro... yes checking whether lchown is declared without a macro... yes checking whether link is declared without a macro... yes checking whether linkat is declared without a macro... yes checking whether lseek is declared without a macro... yes checking whether pipe is declared without a macro... yes checking whether pipe2 is declared without a macro... yes checking whether pread is declared without a macro... yes checking whether pwrite is declared without a macro... yes checking whether readlink is declared without a macro... yes checking whether readlinkat is declared without a macro... yes checking whether rmdir is declared without a macro... yes checking whether sethostname is declared without a macro... yes checking whether sleep is declared without a macro... yes checking whether symlink is declared without a macro... yes checking whether symlinkat is declared without a macro... yes checking whether ttyname_r is declared without a macro... yes checking whether unlink is declared without a macro... yes checking whether unlinkat is declared without a macro... yes checking whether usleep is declared without a macro... yes checking whether btowc is declared without a macro... yes checking whether wctob is declared without a macro... yes checking whether mbsinit is declared without a macro... yes checking whether mbrtowc is declared without a macro... yes checking whether mbrlen is declared without a macro... yes checking whether mbsrtowcs is declared without a macro... yes checking whether mbsnrtowcs is declared without a macro... yes checking whether wcrtomb is declared without a macro... yes checking whether wcsrtombs is declared without a macro... yes checking whether wcsnrtombs is declared without a macro... yes checking whether wcwidth is declared without a macro... yes checking whether wmemchr is declared without a macro... yes checking whether wmemcmp is declared without a macro... yes checking whether wmemcpy is declared without a macro... yes checking whether wmemmove is declared without a macro... yes checking whether wmemset is declared without a macro... yes checking whether wcslen is declared without a macro... yes checking whether wcsnlen is declared without a macro... yes checking whether wcscpy is declared without a macro... yes checking whether wcpcpy is declared without a macro... yes checking whether wcsncpy is declared without a macro... yes checking whether wcpncpy is declared without a macro... yes checking whether wcscat is declared without a macro... yes checking whether wcsncat is declared without a macro... yes checking whether wcscmp is declared without a macro... yes checking whether wcsncmp is declared without a macro... yes checking whether wcscasecmp is declared without a macro... yes checking whether wcsncasecmp is declared without a macro... yes checking whether wcscoll is declared without a macro... yes checking whether wcsxfrm is declared without a macro... yes checking whether wcsdup is declared without a macro... yes checking whether wcschr is declared without a macro... yes checking whether wcsrchr is declared without a macro... yes checking whether wcscspn is declared without a macro... yes checking whether wcsspn is declared without a macro... yes checking whether wcspbrk is declared without a macro... yes checking whether wcsstr is declared without a macro... yes checking whether wcstok is declared without a macro... yes checking whether wcswidth is declared without a macro... yes checking whether iswcntrl works... guessing yes checking for towlower... yes checking for wctype_t... yes checking for wctrans_t... yes checking whether wctype is declared without a macro... yes checking whether iswctype is declared without a macro... yes checking whether wctrans is declared without a macro... yes checking whether towctrans is declared without a macro... yes checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for aarch64-linux-gnu-strip... aarch64-linux-gnu-strip checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking for style of include used by make... GNU checking dependency style of aarch64-linux-gnu-gcc... gcc3 checking whether ln -s works... yes checking for aarch64-linux-gnu-ranlib... (cached) aarch64-linux-gnu-ranlib checking for aarch64-linux-gnu-ar... (cached) aarch64-linux-gnu-ar configure: creating ./config.status config.status: creating Makefile config.status: creating import/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing default commands =3D=3D=3D configuring in build-libiberty-gdbserver (/home/pavel/harman/gdb-8.0/gdb/gdbserver/build-libiberty-gdbserver) configure: running /bin/bash .././../../libiberty/configure --disable-option-checking '--prefix=3DNONE' '--host=3Daarch64-linux-gnu' 'CC=3Daarch64-linux-gnu-gcc' 'host_alias=3Daarch64-linux-gnu' --cache-file=3D/dev/null --srcdir=3D.././../../libiberty checking whether to enable maintainer-specific portions of Makefiles... no checking for makeinfo... makeinfo checking for perl... perl checking build system type... x86_64-pc-linux-gnu checking host system type... aarch64-unknown-linux-gnu checking for aarch64-linux-gnu-ar... aarch64-linux-gnu-ar checking for aarch64-linux-gnu-ranlib... aarch64-linux-gnu-ranlib checking whether to install libiberty headers and static library... no configure: target_header_dir =3D=20 checking for aarch64-linux-gnu-gcc... aarch64-linux-gnu-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables...=20 checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether aarch64-linux-gnu-gcc accepts -g... yes checking for aarch64-linux-gnu-gcc option to accept ISO C89... none needed checking how to run the C preprocessor... aarch64-linux-gnu-gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking whether aarch64-linux-gnu-gcc supports -W... yes checking whether aarch64-linux-gnu-gcc supports -Wall... yes checking whether aarch64-linux-gnu-gcc supports -Wwrite-strings... yes checking whether aarch64-linux-gnu-gcc supports -Wc++-compat... yes checking whether aarch64-linux-gnu-gcc supports -Wstrict-prototypes... yes checking whether aarch64-linux-gnu-gcc supports -Wshadow=3Dlocal... no checking whether aarch64-linux-gnu-gcc supports -pedantic ... yes checking whether aarch64-linux-gnu-gcc and cc understand -c and -o together= ... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking whether byte ordering is bigendian... no checking for a BSD-compatible install... /usr/bin/install -c checking for sys/file.h... yes checking for sys/param.h... yes checking for limits.h... yes checking for stdlib.h... (cached) yes checking for malloc.h... yes checking for string.h... (cached) yes checking for unistd.h... (cached) yes checking for strings.h... (cached) yes checking for sys/time.h... yes checking for time.h... yes checking for sys/resource.h... yes checking for sys/stat.h... (cached) yes checking for sys/mman.h... yes checking for fcntl.h... yes checking for alloca.h... yes checking for sys/pstat.h... no checking for sys/sysmp.h... no checking for sys/sysinfo.h... yes checking for machine/hal_sysinfo.h... no checking for sys/table.h... no checking for sys/sysctl.h... yes checking for sys/systemcfg.h... no checking for stdint.h... (cached) yes checking for stdio_ext.h... yes checking for process.h... no checking for sys/prctl.h... yes checking for sys/wait.h that is POSIX.1 compatible... yes checking whether time.h and sys/time.h may both be included... yes checking whether errno must be declared... no checking size of int... 4 checking size of long... 8 checking size of size_t... 8 checking for long long... yes checking size of long long... 8 checking for a 64-bit type... uint64_t checking for intptr_t... yes checking for uintptr_t... yes checking for ssize_t... yes checking for pid_t... yes checking for library containing strerror... none required checking for asprintf... yes checking for atexit... yes checking for basename... yes checking for bcmp... yes checking for bcopy... yes checking for bsearch... yes checking for bzero... yes checking for calloc... yes checking for clock... yes checking for ffs... yes checking for getcwd... yes checking for getpagesize... yes checking for gettimeofday... yes checking for index... yes checking for insque... yes checking for memchr... yes checking for memcmp... yes checking for memcpy... yes checking for memmem... yes checking for memmove... yes checking for mempcpy... yes checking for memset... yes checking for mkstemps... yes checking for putenv... yes checking for random... yes checking for rename... yes checking for rindex... yes checking for setenv... yes checking for snprintf... yes checking for sigsetmask... yes checking for stpcpy... yes checking for stpncpy... yes checking for strcasecmp... yes checking for strchr... yes checking for strdup... yes checking for strncasecmp... yes checking for strndup... yes checking for strnlen... yes checking for strrchr... yes checking for strstr... yes checking for strtod... yes checking for strtol... yes checking for strtoul... yes checking for strtoll... yes checking for strtoull... yes checking for strverscmp... yes checking for tmpnam... yes checking for vasprintf... yes checking for vfprintf... yes checking for vprintf... yes checking for vsnprintf... yes checking for vsprintf... yes checking for waitpid... yes checking for setproctitle... no checking whether alloca needs Cray hooks... no checking stack direction for C alloca... 0 checking for vfork.h... no checking for fork... yes checking for vfork... yes checking for working fork... cross checking for working vfork... (cached) yes checking for _doprnt... no checking for sys_errlist... yes checking for sys_nerr... yes checking for sys_siglist... yes checking for external symbol _system_configuration... no checking for __fsetlocking... yes checking for canonicalize_file_name... yes checking for dup3... yes checking for getrlimit... yes checking for getrusage... yes checking for getsysinfo... no checking for gettimeofday... (cached) yes checking for on_exit... yes checking for psignal... yes checking for pstat_getdynamic... no checking for pstat_getstatic... no checking for realpath... yes checking for setrlimit... yes checking for sbrk... yes checking for spawnve... no checking for spawnvpe... no checking for strerror... yes checking for strsignal... yes checking for sysconf... yes checking for sysctl... no checking for sysmp... no checking for table... no checking for times... yes checking for wait3... yes checking for wait4... yes checking whether basename is declared... yes checking whether ffs is declared... yes checking whether asprintf is declared... yes checking whether vasprintf is declared... yes checking whether snprintf is declared... yes checking whether vsnprintf is declared... yes checking whether calloc is declared... yes checking whether getenv is declared... yes checking whether getopt is declared... yes checking whether malloc is declared... yes checking whether realloc is declared... yes checking whether sbrk is declared... yes checking whether strtol is declared... yes checking whether strtoul is declared... yes checking whether strtoll is declared... yes checking whether strtoull is declared... yes checking whether strverscmp is declared... yes checking whether strnlen is declared... yes checking whether canonicalize_file_name must be declared... no checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... (cached) yes checking for working mmap... no checking for working strncmp... yes configure: creating ./config.status config.status: creating Makefile config.status: creating testsuite/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing default commands checking sgtty.h usability... yes checking sgtty.h presence... yes checking for sgtty.h... yes checking termio.h usability... yes checking termio.h presence... yes checking for termio.h... yes checking termios.h usability... yes checking termios.h presence... yes checking for termios.h... yes checking sys/reg.h usability... no checking sys/reg.h presence... no checking for sys/reg.h... no checking for string.h... (cached) yes checking proc_service.h usability... no checking proc_service.h presence... no checking for proc_service.h... no checking sys/procfs.h usability... yes checking sys/procfs.h presence... yes checking for sys/procfs.h... yes checking linux/elf.h usability... yes checking linux/elf.h presence... yes checking for linux/elf.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking signal.h usability... yes checking signal.h presence... yes checking for signal.h... yes checking sys/file.h usability... yes checking sys/file.h presence... yes checking for sys/file.h... yes checking sys/ioctl.h usability... yes checking sys/ioctl.h presence... yes checking for sys/ioctl.h... yes checking netinet/in.h usability... yes checking netinet/in.h presence... yes checking for netinet/in.h... yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking netdb.h usability... yes checking netdb.h presence... yes checking for netdb.h... yes checking netinet/tcp.h usability... yes checking netinet/tcp.h presence... yes checking for netinet/tcp.h... yes checking arpa/inet.h usability... yes checking arpa/inet.h presence... yes checking for arpa/inet.h... yes checking for pid_t... yes checking vfork.h usability... no checking vfork.h presence... no checking for vfork.h... no checking for fork... yes checking for vfork... yes checking for working fork... cross checking for working vfork... (cached) yes checking for getauxval... yes checking for pread... yes checking for pwrite... yes checking for pread64... yes checking for setns... yes checking for ANSI C header files... (cached) yes checking for working alloca.h... yes checking for alloca... yes checking for nl_langinfo and CODESET... yes checking linux/perf_event.h usability... yes checking linux/perf_event.h presence... yes checking for linux/perf_event.h... yes checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for memory.h... (cached) yes checking for signal.h... (cached) yes checking sys/resource.h usability... yes checking sys/resource.h presence... yes checking for sys/resource.h... yes checking for sys/socket.h... (cached) yes checking sys/syscall.h usability... yes checking sys/syscall.h presence... yes checking for sys/syscall.h... yes checking sys/un.h usability... yes checking sys/un.h presence... yes checking for sys/un.h... yes checking sys/wait.h usability... yes checking sys/wait.h presence... yes checking for sys/wait.h... yes checking thread_db.h usability... yes checking thread_db.h presence... yes checking for thread_db.h... yes checking wait.h usability... yes checking wait.h presence... yes checking for wait.h... yes checking for fdwalk... no checking for getrlimit... yes checking for pipe... yes checking for pipe2... yes checking for socketpair... yes checking for sigaction... yes checking whether strerror is declared... yes checking whether strstr is declared... yes checking for sigsetjmp... yes checking sys/ptrace.h usability... yes checking sys/ptrace.h presence... yes checking for sys/ptrace.h... yes checking ptrace.h usability... no checking ptrace.h presence... no checking for ptrace.h... no checking whether ptrace is declared... yes checking return type of ptrace... long checking types of arguments for ptrace... enum __ptrace_request,int,long,lo= ng checking for ust... no checking compiler warning flags... -Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-b= ody -Wunused-but-set-parameter -Wunused-but-set-variable -Wno-sign-compare -Wno-narrowing -Wformat-nonliteral=20 checking for dladdr... yes checking for long long... yes checking size of long long... 8 checking whether basename is declared... yes checking whether ffs is declared... yes checking whether asprintf is declared... yes checking whether vasprintf is declared... yes checking whether snprintf is declared... yes checking whether vsnprintf is declared... yes checking whether strtol is declared... yes checking whether strtoul is declared... yes checking whether strtoll is declared... yes checking whether strtoull is declared... yes checking whether strverscmp is declared... yes checking whether strerror is declared... (cached) yes checking whether perror is declared... yes checking whether vasprintf is declared... (cached) yes checking whether vsnprintf is declared... (cached) yes checking for struct stat.st_blocks... yes checking for struct stat.st_blksize... yes checking for struct user_regs_struct.fs_base... no checking for struct user_regs_struct.gs_base... no checking for socklen_t... yes checking for Elf32_auxv_t... yes checking for Elf64_auxv_t... yes checking for PTRACE_GETREGS... no checking for PTRACE_GETFPXREGS... no checking for lwpid_t in sys/procfs.h... yes checking for psaddr_t in sys/procfs.h... yes checking for prgregset_t in sys/procfs.h... yes checking for prfpregset_t in sys/procfs.h... yes checking for elf_fpregset_t in sys/procfs.h... yes checking for dlopen in -ldl... yes checking for the dynamic export flag... -Wl,--dynamic-list checking for TD_VERSION... yes checking whether the target supports __sync_*_compare_and_swap... yes checking whether ADDR_NO_RANDOMIZE is declared... yes configure: creating ./config.status config.status: creating Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depdir commands --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21886-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 06 13:02:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 83756 invoked by alias); 6 Sep 2017 13:02:48 -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 83397 invoked by uid 48); 6 Sep 2017 13:02:47 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug testsuite/22091] PASS->FAIL: gdb.arch/thumb2-it.exp Date: Wed, 06 Sep 2017 13:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: cc 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: 2017-q3/txt/msg00323.txt.bz2 Content-length: 729 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22091 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- Casts is the simplest. Can you give it a try? Assuming the function retur= ns nothing, then something like this should work: - gdb_test "call ${func}()" "Breakpoint.*@ Setup.*" "$func, call" + gdb_test "call (void) ${func}()" "Breakpoint.*@ Setup.*" "$func, call" --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21887-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 06 13:37:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94598 invoked by alias); 6 Sep 2017 13:37:46 -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 94559 invoked by uid 48); 6 Sep 2017 13:37:46 -0000 From: "thopre01 at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/22091] PASS->FAIL: gdb.arch/thumb2-it.exp Date: Wed, 06 Sep 2017 13:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thopre01 at gcc dot gnu.org 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: 2017-q3/txt/msg00324.txt.bz2 Content-length: 627 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22091 --- Comment #2 from Thomas Preud'homme --- (In reply to Pedro Alves from comment #1) > Casts is the simplest. Can you give it a try? Assuming the function > returns nothing, then something like this should work: >=20 > - gdb_test "call ${func}()" "Breakpoint.*@ Setup.*" "$func, call" > + gdb_test "call (void) ${func}()" "Breakpoint.*@ Setup.*" "$func, cal= l" It works on the condition that the call to it_breakpoints below is also cas= t. Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21888-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 06 13:51:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 37735 invoked by alias); 6 Sep 2017 13:51:16 -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 37132 invoked by uid 48); 6 Sep 2017 13:51:15 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug testsuite/22091] PASS->FAIL: gdb.arch/thumb2-it.exp Date: Wed, 06 Sep 2017 14:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: 2017-q3/txt/msg00325.txt.bz2 Content-length: 303 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22091 --- Comment #3 from Pedro Alves --- Could you send the resulting patch to gdb-patches? With a ChangeLog entry,= it should be good to go. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21889-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 06 14:48:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 39176 invoked by alias); 6 Sep 2017 14:48:34 -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 35481 invoked by uid 48); 6 Sep 2017 14:48:15 -0000 From: "thopre01 at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/22091] PASS->FAIL: gdb.arch/thumb2-it.exp Date: Wed, 06 Sep 2017 16:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thopre01 at gcc dot gnu.org 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: 2017-q3/txt/msg00326.txt.bz2 Content-length: 381 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22091 --- Comment #4 from Thomas Preud'homme --- (In reply to Pedro Alves from comment #3) > Could you send the resulting patch to gdb-patches? With a ChangeLog entr= y, > it should be good to go. Absolutely, will do. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21890-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 06 16:35:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 28200 invoked by alias); 6 Sep 2017 16:35:35 -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 28147 invoked by uid 48); 6 Sep 2017 16:35:35 -0000 From: "alfedotov at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22098] New: failed to build with mingw 5.1.0 Date: Wed, 06 Sep 2017 17:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: alfedotov at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00327.txt.bz2 Content-length: 3999 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22098 Bug ID: 22098 Summary: failed to build with mingw 5.1.0 Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: alfedotov at gmail dot com Target Milestone: --- gcc version 5.1.0 20150422 (Fedora MinGW 5.1.0-2.fc22) (GCC) ../../src_gdb/gdb/arm-linux-tdep.c:394:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } }; ^ ../../src_gdb/gdb/arm-linux-tdep.c:394:1: error: narrowing conversion of '-= 1ll' from 'LONGEST {aka long long int}' to 'ULONGEST {aka long long unsigned int= }' inside { } ../../src_gdb/gdb/arm-linux-tdep.c:404:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } }; ^ ../../src_gdb/gdb/arm-linux-tdep.c:404:1: error: narrowing conversion of '-= 1ll' from 'LONGEST {aka long long int}' to 'ULONGEST {aka long long unsigned int= }' inside { } ../../src_gdb/gdb/arm-linux-tdep.c:415:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } }; ^ ../../src_gdb/gdb/arm-linux-tdep.c:415:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } ../../src_gdb/gdb/arm-linux-tdep.c:415:1: error: narrowing conversion of '-= 1ll' from 'LONGEST {aka long long int}' to 'ULONGEST {aka long long unsigned int= }' inside { } ../../src_gdb/gdb/arm-linux-tdep.c:426:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } }; ^ ../../src_gdb/gdb/arm-linux-tdep.c:426:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } ../../src_gdb/gdb/arm-linux-tdep.c:426:1: error: narrowing conversion of '-= 1ll' from 'LONGEST {aka long long int}' to 'ULONGEST {aka long long unsigned int= }' inside { } ../../src_gdb/gdb/arm-linux-tdep.c:438:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } }; ^ ../../src_gdb/gdb/arm-linux-tdep.c:438:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } ../../src_gdb/gdb/arm-linux-tdep.c:438:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } ../../src_gdb/gdb/arm-linux-tdep.c:438:1: error: narrowing conversion of '-= 1ll' from 'LONGEST {aka long long int}' to 'ULONGEST {aka long long unsigned int= }' inside { } ../../src_gdb/gdb/arm-linux-tdep.c:450:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } }; ^ ../../src_gdb/gdb/arm-linux-tdep.c:450:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } ../../src_gdb/gdb/arm-linux-tdep.c:450:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } ../../src_gdb/gdb/arm-linux-tdep.c:450:1: error: narrowing conversion of '-= 1ll' from 'LONGEST {aka long long int}' to 'ULONGEST {aka long long unsigned int= }' inside { } ../../src_gdb/gdb/arm-linux-tdep.c:461:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } }; ^ ../../src_gdb/gdb/arm-linux-tdep.c:461:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } ../../src_gdb/gdb/arm-linux-tdep.c:461:1: error: narrowing conversion of '-= 1ll' from 'LONGEST {aka long long int}' to 'ULONGEST {aka long long unsigned int= }' inside { } ../../src_gdb/gdb/arm-linux-tdep.c:472:1: error: narrowing conversion of '-= 1' from 'int' to 'ULONGEST {aka long long unsigned int}' inside { } }; ^ --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21892-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 06 17:13:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 104248 invoked by alias); 6 Sep 2017 17:13:27 -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 104204 invoked by uid 55); 6 Sep 2017 17:13:26 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22010] PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Date: Wed, 06 Sep 2017 17:13: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q3/txt/msg00329.txt.bz2 Content-length: 1215 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22010 --- Comment #11 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D5aec60eb2f6f= 0905bfc76f5949fd5d55c6a10f10 commit 5aec60eb2f6f0905bfc76f5949fd5d55c6a10f10 Author: Tom Tromey Date: Wed Aug 30 16:12:56 2017 -0600 Cast char constant to int in sizeof.exp PR gdb/22010 concerns a regression I introduced with the scalar printing changes. The bug is that this code in sizeof.exp: set signof_byte [get_integer_valueof "'\\377'" -1] can incorrectly compute sizeof_byte. One underlying problem here is that gdb's C parser doesn't treat a char constant as an int (this is PR 19973). However, it seems good to have an immediate fix for the regression. The simplest is to cast to an int here. testsuite/ChangeLog 2017-09-05 Tom Tromey PR gdb/22010: * gdb.base/sizeof.exp (check_valueof): Cast char constant to int. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21891-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 06 17:13:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 104210 invoked by alias); 6 Sep 2017 17:13:27 -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 104161 invoked by uid 55); 6 Sep 2017 17:13:26 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/19973] gdb prints sizeof a char literal as 1 when the language is C Date: Wed, 06 Sep 2017 17:13: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.10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q3/txt/msg00328.txt.bz2 Content-length: 1214 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19973 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D5aec60eb2f6f= 0905bfc76f5949fd5d55c6a10f10 commit 5aec60eb2f6f0905bfc76f5949fd5d55c6a10f10 Author: Tom Tromey Date: Wed Aug 30 16:12:56 2017 -0600 Cast char constant to int in sizeof.exp PR gdb/22010 concerns a regression I introduced with the scalar printing changes. The bug is that this code in sizeof.exp: set signof_byte [get_integer_valueof "'\\377'" -1] can incorrectly compute sizeof_byte. One underlying problem here is that gdb's C parser doesn't treat a char constant as an int (this is PR 19973). However, it seems good to have an immediate fix for the regression. The simplest is to cast to an int here. testsuite/ChangeLog 2017-09-05 Tom Tromey PR gdb/22010: * gdb.base/sizeof.exp (check_valueof): Cast char constant to int. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21893-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 06 17:13:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 105617 invoked by alias); 6 Sep 2017 17:13:57 -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 105587 invoked by uid 48); 6 Sep 2017 17:13:57 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22010] PASS->FAIL: gdb.base/sizeof.exp: check valueof "'\377'" Date: Thu, 07 Sep 2017 06:17: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-q3/txt/msg00330.txt.bz2 Content-length: 562 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22010 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |8.1 --- Comment #12 from Tom Tromey --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21894-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Sep 07 06:17:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 5302 invoked by alias); 7 Sep 2017 06:17:28 -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 5254 invoked by uid 48); 7 Sep 2017 06:17:28 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/22021] Multi-arch exec fails with a remote target Date: Thu, 07 Sep 2017 09:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson 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: 8.0.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-q3/txt/msg00331.txt.bz2 Content-length: 650 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22021 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |8.0.1 --- Comment #1 from Simon Marchi --- Fixed by this series: https://sourceware.org/ml/gdb-patches/2017-08/msg00503.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21895-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Sep 07 09:01:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 112132 invoked by alias); 7 Sep 2017 09:01:39 -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 83197 invoked by uid 48); 7 Sep 2017 09:00:57 -0000 From: "alfedotov at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/22098] failed to build with mingw 5.1.0 Date: Thu, 07 Sep 2017 10:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: alfedotov at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: component 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: 2017-q3/txt/msg00332.txt.bz2 Content-length: 1159 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22098 Alexander Fedotov changed: What |Removed |Added ---------------------------------------------------------------------------- Component|gdb |build --- Comment #1 from Alexander Fedotov --- Environment is: Fedora 4.4.14-200.fc22.x86_64 #1 SMP Fri Jun 24 21:19:33 UTC 2016 x86_64 x8= 6_64 x86_64 GNU/Linux gcc version 5.1.0 20150422 (Fedora MinGW 5.1.0-2.fc22) (GCC) ../../src_gdb/gdb/aarch64-tdep.c: In function 'VEC_CORE_ADDR* aarch64_software_single_step(regcache*)': ../../src_gdb/gdb/aarch64-tdep.c:2428:34: error: narrowing conversion of '-= 1' from 'int' to 'CORE_ADDR {aka long long unsigned int}' inside { } CORE_ADDR breaks[2] =3D { -1, -1 }; ^ ../../src_gdb/gdb/aarch64-tdep.c:2428:34: error: narrowing conversion of '-= 1' from 'int' to 'CORE_ADDR {aka long long unsigned int}' inside { } Makefile:1876: recipe for target 'aarch64-tdep.o' failed --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21896-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Sep 07 10:48:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 130628 invoked by alias); 7 Sep 2017 10:48:37 -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 130581 invoked by uid 48); 7 Sep 2017 10:48:33 -0000 From: "sven.c.dack at sky dot com" To: gdb-prs@sourceware.org Subject: [Bug build/22102] New: 32-bit gdb build fails with undefined reference to amd64_create_target_description Date: Thu, 07 Sep 2017 12:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: sven.c.dack at sky dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00333.txt.bz2 Content-length: 37874 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22102 Bug ID: 22102 Summary: 32-bit gdb build fails with undefined reference to amd64_create_target_description Product: gdb Version: HEAD Status: UNCONFIRMED Severity: critical Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: sven.c.dack at sky dot com Target Milestone: --- Current binutils fails to build gdb on 32-bit (i686-pc-linux-gnu) with undefined reference to amd64_create_target_description. The same source bui= lds just fine on 64-bit however. The BFD_VERSION_DATE is 20170907. The last working version of gdb for 32-bit that I have is 8.0.50.20170831-g= it. The failure seems to have been introduced only recently. g++ -pipe -O3 -march=3Dnative -fomit-frame-pointer -fno-checking -flto -ffat-lto-objects -flto-partition=3Dbalanced -static-libstdc++ -static-li= bgcc -Wl,-O1,--hash-style=3Dgnu,--enable-new-dtags,-z,combreloc,-z,noexecstack,-= z,relro,-z,now -fno-checking -pipe -O3 -march=3Dnative -fomit-frame-pointer -fno-checking = -flto -ffat-lto-objects -flto-partition=3Dbalanced \ -o gdb gdb.o amd64-tdep.o amd64-linux-tdep.o i386-tdep.o i386.o i386-linux-tdep.o glibc-tdep.o i387-tdep.o solib-svr4.o symfile-mem.o linux-tdep.o linux-record.o ser-base.o ser-unix.o ser-pipe.o ser-tcp.o inf-ptrace.o fork-child.o fork-inferior.o proc-service.o linux-thread-db.o linux-nat.o linux-osdata.o linux-fork.o linux-procfs.o linux-ptrace.o linux-waitpid.o linux-personality.o linux-namespaces.o x86-nat.o x86-dregs.= o=20=20=20 i386-linux-nat.o x86-linux-nat.o linux-btrace.o=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 x86-linux.o x86-linux-dregs.o ax-gdb.o ax-general.o ctf.o dcache.o remote.o remote-fileio.o remote-notif.o tracefile.o tracefile-tfile.o tracepoint.o=20 cli-cmds.o cli-decode.o cli-dump.o cli-interp.o cli-logging.o cli-script.o cli-setshow.o cli-utils.o mi-cmd-break.o mi-cmd-catch.o mi-cmd-disas.o mi-cmd-env.o mi-cmd-file.o mi-cmd-info.o mi-cmd-stack.o mi-cmd-target.o mi-cmd-var.o mi-cmds.o mi-console.o mi-getopt.o mi-interp.o mi-main.o mi-ou= t.o mi-parse.o mi-symbol-cmds.o tui.o tui-command.o tui-data.o tui-disasm.o tui-file.o tui-hooks.o tui-interp.o tui-io.o tui-layout.o tui-out.o tui-reg= s.o tui-source.o tui-stack.o tui-win.o tui-windata.o tui-wingeneral.o tui-winsource.o py-arch.o py-auto-load.o py-block.o py-bpevent.o py-breakpoint.o py-cmd.o py-continueevent.o py-event.o py-evtregistry.o py-evts.o py-exitedevent.o py-finishbreakpoint.o py-frame.o py-framefilter.o py-function.o py-gdb-readline.o py-inferior.o py-infevents.o py-infthread.o py-instruction.o py-lazy-string.o py-linetable.o py-newobjfileevent.o py-objfile.o py-param.o py-prettyprint.o py-progspace.o py-record.o py-record-btrace.o py-record-full.o py-signalevent.o py-stopevent.o py-symb= ol.o py-symtab.o py-threadevent.o py-type.o py-unwind.o py-utils.o py-value.o py-varobj.o py-xmethods.o python.o guile.o scm-arch.o scm-auto-load.o scm-block.o scm-breakpoint.o scm-cmd.o scm-disasm.o scm-exception.o scm-fra= me.o scm-gsmob.o scm-iterator.o scm-lazy-string.o scm-math.o scm-objfile.o scm-param.o scm-ports.o scm-pretty-print.o scm-progspace.o scm-safe-call.o scm-string.o scm-symbol.o scm-symtab.o scm-type.o scm-utils.o scm-value.o elfread.o stap-probe.o dtrace-probe.o posix-hdep.o posix-strerror.o array-view-selftests.o environ-selftests.o function-view-selftests.o offset-type-selftests.o optional-selftests.o ptid-selftests.o scoped_restore-selftests.o ada-exp.o c-exp.o cp-name-parser.o d-exp.o f-exp= .o go-exp.o m2-exp.o p-exp.o rust-exp.o ada-lang.o ada-tasks.o ada-typeprint.o ada-valprint.o ada-varobj.o addrmap.o agent.o annotate.o arch-utils.o auto-load.o auxv.o bcache.o bfd-target.o block.o blockframe.o break-catch-s= ig.o break-catch-syscall.o break-catch-throw.o breakpoint.o btrace.o btrace-comm= on.o buffer.o build-id.o buildsym.o c-lang.o c-typeprint.o c-valprint.o c-varobj= .o charset.o cleanups.o cli-out.o coff-pe-read.o coffread.o common-agent.o common-debug.o common-exceptions.o job-control.o common-regcache.o common-utils.o complaints.o completer.o continuations.o copying.o corefile.o corelow.o cp-abi.o cp-namespace.o cp-support.o cp-valprint.o d-lang.o d-namespace.o d-valprint.o dbxread.o debug.o demangle.o dfp.o dictionary.o disasm.o disasm-selftests.o doublest.o dummy-frame.o dwarf2-frame.o dwarf2-frame-tailcall.o dwarf2expr.o dwarf2loc.o dwarf2read.o environ.o errors.o eval.o event-loop.o event-top.o exceptions.o exec.o expprint.o extension.o f-lang.o f-typeprint.o f-valprint.o fileio.o filename-seen-cach= e.o filestuff.o filesystem.o findcmd.o findvar.o format.o frame.o frame-base.o frame-unwind.o gcore.o gdb_bfd.o gdb-dlfcn.o gdb_obstack.o gdb_regex.o gdb_usleep.o gdb_vecs.o gdbarch.o gdbarch-selftests.o gdbtypes.o gnu-v2-abi= .o gnu-v3-abi.o go-lang.o go-typeprint.o go-valprint.o inf-child.o inf-loop.o infcall.o infcmd.o inferior.o infrun.o inline-frame.o interps.o jit.o language.o linespec.o location.o m2-lang.o m2-typeprint.o m2-valprint.o macrocmd.o macroexp.o macroscope.o macrotab.o main.o maint.o mdebugread.o mem-break.o memattr.o memory-map.o memrange.o mi-common.o minidebug.o minsy= ms.o mipsread.o namespace.o new-op.o objc-lang.o objfiles.o observer.o opencl-la= ng.o osabi.o osdata.o p-lang.o p-typeprint.o p-valprint.o parse.o print-utils.o printcmd.o probe.o progspace.o progspace-and-thread.o prologue-value.o psymtab.o ptid.o record.o record-btrace.o record-full.o regcache.o reggroup= s.o registry.o reverse.o rsp-low.o run-time-clock.o rust-lang.o selftest.o selftest-arch.o sentinel-frame.o ser-event.o serial.o signals.o signals-state-save-restore.o skip.o solib.o solib-target.o source.o stabsre= ad.o stack.o std-regs.o symfile.o symfile-debug.o symmisc.o symtab.o target.o target-dcache.o target-descriptions.o target-memory.o thread.o thread-fsm.o tid-parse.o top.o trad-frame.o tramp-frame.o typeprint.o ui-file.o ui-out.o user-regs.o utils.o utils-selftests.o valarith.o valops.o valprint.o value.o varobj.o vec.o version.o waitstatus.o xml-builtin.o xml-support.o xml-sysca= ll.o xml-tdesc.o xml-utils.o compile.o compile-c-support.o compile-c-symbols.o compile-c-types.o compile-loc2c.o compile-object-load.o compile-object-run.o inflow.o init.o \ ../readline/libreadline.a ../opcodes/libopcodes.a ../bfd/libbfd.a -L./../zlib -lz ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a=20= =20=20 -ldl -ldl -lncurses -lm -ldl -L/home/sven/gnu32/lib -lguile-2.0 -lgc -lpth= read -ldl -lutil -lm -lpython2.7 -lexpat /home/sven/gnu32/lib/liblzma.so -Wl,-rp= ath -Wl,/home/sven/gnu32/lib ../libiberty/libiberty.a=20 build-gnulib/import/libgnu.a /home/sven/gnu32/lib/libiconv.so -Wl,-rpath -Wl,/home/sven/gnu32/lib -ldl -Wl,--dynamic-list=3D/dev/shm/build-pkg-18379/src/binutils-master/gdb/proc-= service.list /dev/shm/build-pkg-18379/src/binutils-master/gold/gdb-index.cc: In member function 'visit_children': /dev/shm/build-pkg-18379/src/binutils-master/gold/gdb-index.cc:404:1: warni= ng: stack usage might be unbounded [-Wstack-usage=3D] Gdb_index_info_reader::visit_children(Dwarf_die* parent, Dwarf_die* contex= t) ^ /dev/shm/build-pkg-18379/src/binutils-master/libiberty/cp-demangle.c: In function 'd_demangle': /dev/shm/build-pkg-18379/src/binutils-master/libiberty/cp-demangle.c:6274:1: warning: stack usage might be unbounded [-Wstack-usage=3D] d_demangle (const char *mangled, int options, size_t *palc) ^ /dev/shm/build-pkg-18379/src/binutils-master/gold/layout.cc: In member func= tion 'make_output_section': /dev/shm/build-pkg-18379/src/binutils-master/gold/output.h:4758:18: warning: 'addr' may be used uninitialized in this function [-Wmaybe-uninitialized] this->paddr_ =3D paddr; ^ /dev/shm/build-pkg-18379/src/binutils-master/gold/layout.cc:1952:12: note: 'addr' was declared here uint64_t addr; ^ /dev/shm/build-pkg-18379/src/binutils-master/gold/gdb-index.cc: In member function 'visit_children': /dev/shm/build-pkg-18379/src/binutils-master/gold/gdb-index.cc:404:1: warni= ng: stack usage might be unbounded [-Wstack-usage=3D] Gdb_index_info_reader::visit_children(Dwarf_die* parent, Dwarf_die* contex= t) ^ /dev/shm/build-pkg-18379/src/binutils-master/gold/gold.cc: In member functi= on 'run': /dev/shm/build-pkg-18379/src/binutils-master/gold/output.h:4758:18: warning: 'addr' may be used uninitialized in this function [-Wmaybe-uninitialized] this->paddr_ =3D paddr; ^ /dev/shm/build-pkg-18379/src/binutils-master/gold/layout.cc:1952:12: note: 'addr' was declared here uint64_t addr; ^ /dev/shm/build-pkg-18379/src/binutils-master/gold/layout.cc: In member func= tion 'make_output_section': /dev/shm/build-pkg-18379/src/binutils-master/gold/output.h:4758:18: warning: 'addr' may be used uninitialized in this function [-Wmaybe-uninitialized] this->paddr_ =3D paddr; ^ /dev/shm/build-pkg-18379/src/binutils-master/gold/layout.cc:1952:12: note: 'addr' was declared here uint64_t addr; ^ /dev/shm/build-pkg-18379/src/binutils-master/libiberty/cp-demangle.c: In function 'is_ctor_or_dtor': /dev/shm/build-pkg-18379/src/binutils-master/libiberty/cp-demangle.c:6480:1: warning: stack usage might be unbounded [-Wstack-usage=3D] is_ctor_or_dtor (const char *mangled, ^ /dev/shm/build-pkg-18379/src/binutils-master/libiberty/cp-demangle.c: In function 'd_demangle': /dev/shm/build-pkg-18379/src/binutils-master/libiberty/cp-demangle.c:6274:1: warning: stack usage might be unbounded [-Wstack-usage=3D] d_demangle (const char *mangled, int options, size_t *palc) ^ make[4]: Leaving directory '/dev/shm/build-pkg-18379/build/binutils-master/gold' make[3]: Leaving directory '/dev/shm/build-pkg-18379/build/binutils-master/gold' make[2]: Leaving directory '/dev/shm/build-pkg-18379/build/binutils-master/gold' /dev/shm/build-pkg-18379/src/binutils-master/gdb/nat/linux-btrace.h:85:8: warning: type 'struct btrace_target_info' violates the C++ One Definition R= ule [-Wodr] struct btrace_target_info ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/remote.c:13103:8: note: a different type is defined in another translation unit struct btrace_target_info ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/nat/linux-btrace.h:102:5: note: the first difference of corresponding definitions is field 'variant' } variant; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/remote.c:13103:8: note: a = type with different number of fields is defined in another translation unit struct btrace_target_info ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/linux-thread-db.c:254:8: warning: type 'struct private_thread_info' violates the C++ One Definition = Rule [-Wodr] struct private_thread_info ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/remote.c:450:8: note: a different type is defined in another translation unit struct private_thread_info ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/linux-thread-db.c:257:22: note: the first difference of corresponding definitions is field 'dying' unsigned int dying:1; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/remote.c:452:9: note: a fi= eld with different name is defined in another translation unit char *extra; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/linux-thread-db.c:1166:8: warning: type 'struct callback_data' violates the C++ One Definition Rule [-Wodr] struct callback_data ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/cli/cli-dump.c:391:8: note= : a different type is defined in another translation unit struct callback_data { ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/linux-thread-db.c:1168:26: note: the first difference of corresponding definitions is field 'info' struct thread_db_info *info; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/cli/cli-dump.c:392:13: not= e: a field with different name is defined in another translation unit CORE_ADDR load_offset; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/python/py-prettyprint.c:32= :6: warning: type 'string_repr_result' violates the C++ One Definition Rule [-W= odr] enum string_repr_result ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/guile/scm-pretty-print.c:3= 4:6: note: an enum with different value name is defined in another translation u= nit enum string_repr_result ^ ada-exp.c:283:7: warning: type 'union YYSTYPE' violates the C++ One Definit= ion Rule [-Wodr] union YYSTYPE ^ c-exp.c:273:7: note: a different type is defined in another translation unit union YYSTYPE ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/ada-exp.y:129:7: note: the first difference of corresponding definitions is field 'typed_val' } typed_val; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/c-exp.y:89:7: note: a field with different name is defined in another translation unit } typed_val_int; ^ ada-exp.c:502:7: warning: type 'union yyalloc' violates the C++ One Definit= ion Rule [-Wodr] union yyalloc ^ c-exp.c:521:7: note: a different type is defined in another translation unit union yyalloc ^ ada-exp.c:505:11: note: the first difference of corresponding definitions is field 'yyvs_alloc' YYSTYPE yyvs_alloc; ^ c-exp.c:524:11: note: a field of same name but different type is defined in another translation unit YYSTYPE yyvs_alloc; ^ ada-exp.c:305:23: note: type 'union YYSTYPE' should match type 'union YYSTY= PE' typedef union YYSTYPE YYSTYPE; ^ c-exp.c:310:23: note: the incompatible type is defined here typedef union YYSTYPE YYSTYPE; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/c-exp.y:2862:3: warning: t= ype 'struct token_and_value' violates the C++ One Definition Rule [-Wodr] } token_and_value; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/d-exp.y:1332:3: note: a different type is defined in another translation unit } token_and_value; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/c-exp.y:2861:11: note: the first difference of corresponding definitions is field 'value' YYSTYPE value; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/d-exp.y:1331:11: note: a f= ield of same name but different type is defined in another translation unit YYSTYPE value; ^ c-exp.c:310:23: note: type 'union YYSTYPE' should match type 'union YYSTYPE' typedef union YYSTYPE YYSTYPE; ^ d-exp.c:265:23: note: the incompatible type is defined here typedef union YYSTYPE YYSTYPE; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/c-exp.y:2284:8: warning: t= ype 'struct token' violates the C++ One Definition Rule [-Wodr] struct token ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/d-exp.y:958:8: note: a different type is defined in another translation unit struct token ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/c-exp.y:2289:15: note: the first difference of corresponding definitions is field 'flags' token_flags flags; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/d-exp.y:958:8: note: a type with different number of fields is defined in another translation unit struct token ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/dbxread.c:70:8: warning: t= ype 'struct symloc' violates the C++ One Definition Rule [-Wodr] struct symloc ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/mdebugread.c:89:8: note: a different type is defined in another translation unit struct symloc ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/dbxread.c:75:9: note: the first difference of corresponding definitions is field 'ldsymoff' int ldsymoff; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/mdebugread.c:92:9: note: a field with different name is defined in another translation unit int fdr_idx; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/dwarf2read.c:1444:8: warni= ng: type 'struct nextfield' violates the C++ One Definition Rule [-Wodr] struct nextfield ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/stabsread.c:57:8: note: a different type is defined in another translation unit struct nextfield ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/dwarf2read.c:1447:7: note:= the first difference of corresponding definitions is field 'accessibility' int accessibility; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/stabsread.c:64:7: note: a field with different name is defined in another translation unit int visibility; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/dwarf2read.c:1474:8: warni= ng: type 'struct field_info' violates the C++ One Definition Rule [-Wodr] struct field_info ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/stabsread.c:81:8: note: a different type is defined in another translation unit struct field_info ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/dwarf2read.c:1477:23: note: the first difference of corresponding definitions is field 'fields' struct nextfield *fields, *baseclasses; ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/stabsread.c:83:23: note: a field with different name is defined in another translation unit struct nextfield *list; ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/dpd/decimal32.c:5= 3:13: warning: type of 'decDigitsFromDPD' does not match original declaration [-Wlto-type-mismatch] extern void decDigitsFromDPD(decNumber *, const uInt *, Int); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/dpd/decimal128.c:= 52:13: warning: type of 'decDigitsFromDPD' does not match original declaration [-Wlto-type-mismatch] extern void decDigitsFromDPD(decNumber *, const uInt *, Int); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/dpd/decimal64.c:7= 41:6: note: 'decDigitsFromDPD' was previously declared here void decDigitsFromDPD(decNumber *dn, const uInt *sour, Int declets) { ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/dpd/decimal64.c:7= 41:6: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/dpd/decimal32.c:5= 2:13: warning: type of 'decDigitsToDPD' does not match original declaration [-Wlto-type-mismatch] extern void decDigitsToDPD(const decNumber *, uInt *, Int); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/dpd/decimal128.c:= 53:13: warning: type of 'decDigitsToDPD' does not match original declaration [-Wlto-type-mismatch] extern void decDigitsToDPD(const decNumber *, uInt *, Int); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/dpd/decimal64.c:6= 15:6: note: 'decDigitsToDPD' was previously declared here void decDigitsToDPD(const decNumber *dn, uInt *targ, Int shift) { ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/dpd/decimal64.c:6= 15:6: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:179:1= 6: warning: type of 'decNumberZero' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberZero(decNumber *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:179:1= 6: warning: type of 'decNumberZero' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberZero(decNumber *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:179:1= 6: warning: type of 'decNumberZero' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberZero(decNumber *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:3582:= 13: note: 'decNumberZero' was previously declared here decNumber * decNumberZero(decNumber *dn) { ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:3582:= 13: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:150:1= 5: warning: type of 'decNumberPlus' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberPlus(decNumber *, const decNumber *, decContext *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:150:1= 5: warning: type of 'decNumberPlus' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberPlus(decNumber *, const decNumber *, decContext *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:150:1= 5: warning: type of 'decNumberPlus' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberPlus(decNumber *, const decNumber *, decContext *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:1875:= 13: note: 'decNumberPlus' was previously declared here decNumber * decNumberPlus(decNumber *res, const decNumber *rhs, ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:1875:= 13: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:118:1= 5: warning: type of 'decNumberFromString' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberFromString(decNumber *, const char *, decContext *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:118:1= 5: warning: type of 'decNumberFromString' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberFromString(decNumber *, const char *, decContext *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:118:1= 5: warning: type of 'decNumberFromString' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberFromString(decNumber *, const char *, decContext *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:489:1= 3: note: 'decNumberFromString' was previously declared here decNumber * decNumberFromString(decNumber *dn, const char chars[], ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:489:1= 3: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:120:1= 4: warning: type of 'decNumberToEngString' does not match original declaration [-Wlto-type-mismatch] char * decNumberToEngString(const decNumber *, char *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:120:1= 4: warning: type of 'decNumberToEngString' does not match original declaration [-Wlto-type-mismatch] char * decNumberToEngString(const decNumber *, char *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:120:1= 4: warning: type of 'decNumberToEngString' does not match original declaration [-Wlto-type-mismatch] char * decNumberToEngString(const decNumber *, char *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:464:8: note: 'decNumberToEngString' was previously declared here char * decNumberToEngString(const decNumber *dn, char *string){ ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:464:8: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:119:1= 4: warning: type of 'decNumberToString' does not match original declaration [-Wlto-type-mismatch] char * decNumberToString(const decNumber *, char *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:119:1= 4: warning: type of 'decNumberToString' does not match original declaration [-Wlto-type-mismatch] char * decNumberToString(const decNumber *, char *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.h:119:1= 4: warning: type of 'decNumberToString' does not match original declaration [-Wlto-type-mismatch] char * decNumberToString(const decNumber *, char *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:459:8: note: 'decNumberToString' was previously declared here char * decNumberToString(const decNumber *dn, char *string){ ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:459:8: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/readline/rlprivate.h:278:12: warning: type of '_rl_isearch_callback' does not match original declaration [-Wlto-type-mismatch] extern int _rl_isearch_callback PARAMS((_rl_search_cxt *)); ^ /dev/shm/build-pkg-18379/src/binutils-master/readline/isearch.c:686:1: note: '_rl_isearch_callback' was previously declared here _rl_isearch_callback (cxt) ^ /dev/shm/build-pkg-18379/src/binutils-master/readline/isearch.c:686:1: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/readline/rlprivate.h:433:24: warning: type of '_rl_iscxt' does not match original declaration [-Wlto-type-mismatch] extern _rl_search_cxt *_rl_iscxt; ^ /dev/shm/build-pkg-18379/src/binutils-master/readline/rlprivate.h:99:3: not= e: type 'struct _rl_search_cxt' should match type 'struct _rl_search_cxt' } _rl_search_cxt; ^ /dev/shm/build-pkg-18379/src/binutils-master/readline/isearch.c:60:17: note: '_rl_iscxt' was previously declared here _rl_search_cxt *_rl_iscxt =3D 0; ^ /dev/shm/build-pkg-18379/src/binutils-master/readline/isearch.c:60:17: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/readline/rlprivate.h:321:12: warning: type of '_rl_nsearch_callback' does not match original declaration [-Wlto-type-mismatch] extern int _rl_nsearch_callback PARAMS((_rl_search_cxt *)); ^ /dev/shm/build-pkg-18379/src/binutils-master/readline/search.c:435:1: note: '_rl_nsearch_callback' was previously declared here _rl_nsearch_callback (cxt) ^ /dev/shm/build-pkg-18379/src/binutils-master/readline/search.c:435:1: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/readline/rlprivate.h:466:24: warning: type of '_rl_nscxt' does not match original declaration [-Wlto-type-mismatch] extern _rl_search_cxt *_rl_nscxt; ^ /dev/shm/build-pkg-18379/src/binutils-master/readline/rlprivate.h:99:3: not= e: type 'struct _rl_search_cxt' should match type 'struct _rl_search_cxt' } _rl_search_cxt; ^ /dev/shm/build-pkg-18379/src/binutils-master/readline/search.c:55:17: note: '_rl_nscxt' was previously declared here _rl_search_cxt *_rl_nscxt =3D 0; ^ /dev/shm/build-pkg-18379/src/binutils-master/readline/search.c:55:17: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/gdb/../libdecnumber/decNumber.= h:130:15: warning: type of 'decNumberCompare' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberCompare(decNumber *, const decNumber *, const decNu= mber *, decContext *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:864:1= 3: note: 'decNumberCompare' was previously declared here decNumber * decNumberCompare(decNumber *res, const decNumber *lhs, ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:864:1= 3: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/gdb/../libdecnumber/decNumber.= h:128:15: warning: type of 'decNumberAdd' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberAdd(decNumber *, const decNumber *, const decNumber= *, decContext *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:770:1= 3: note: 'decNumberAdd' was previously declared here decNumber * decNumberAdd(decNumber *res, const decNumber *lhs, ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:770:1= 3: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/gdb/../libdecnumber/decNumber.= h:162:15: warning: type of 'decNumberSubtract' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberSubtract(decNumber *, const decNumber *, const decNumber *, decContext *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:3139:= 13: note: 'decNumberSubtract' was previously declared here decNumber * decNumberSubtract(decNumber *res, const decNumber *lhs, ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:3139:= 13: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/gdb/../libdecnumber/decNumber.= h:147:15: warning: type of 'decNumberMultiply' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberMultiply(decNumber *, const decNumber *, const decNumber *, decContext *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:1905:= 13: note: 'decNumberMultiply' was previously declared here decNumber * decNumberMultiply(decNumber *res, const decNumber *lhs, ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:1905:= 13: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/gdb/../libdecnumber/decNumber.= h:134:15: warning: type of 'decNumberDivide' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberDivide(decNumber *, const decNumber *, const decNum= ber *, decContext *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:991:1= 3: note: 'decNumberDivide' was previously declared here decNumber * decNumberDivide(decNumber *res, const decNumber *lhs, ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:991:1= 3: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/gdb/../libdecnumber/decNumber.= h:151:15: warning: type of 'decNumberPower' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberPower(decNumber *, const decNumber *, const decNumb= er *, decContext *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:1942:= 13: note: 'decNumberPower' was previously declared here decNumber * decNumberPower(decNumber *res, const decNumber *lhs, ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:1942:= 13: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/gdb/../libdecnumber/decNumber.= h:117:15: warning: type of 'decNumberFromUInt32' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberFromUInt32(decNumber *, uint32_t); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:358:1= 3: note: 'decNumberFromUInt32' was previously declared here decNumber * decNumberFromUInt32(decNumber *dn, uInt uin) { ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:358:1= 3: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/gdb/../libdecnumber/decNumber.= h:116:15: warning: type of 'decNumberFromInt32' does not match original declaration [-Wlto-type-mismatch] decNumber * decNumberFromInt32(decNumber *, int32_t); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:345:1= 3: note: 'decNumberFromInt32' was previously declared here decNumber * decNumberFromInt32(decNumber *dn, Int in) { ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/decNumber.c:345:1= 3: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/gdb/../libdecnumber/dpd/decima= l32.h:92:15: warning: type of 'decimal32ToNumber' does not match original declaration [-Wlto-type-mismatch] decNumber * decimal32ToNumber(const decimal32 *, decNumber *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/bid/decimal32.c:8= 7:1: note: 'decimal32ToNumber' was previously declared here decimal32ToNumber (const decimal32 *bid32, decNumber *dn) ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/bid/decimal32.c:8= 7:1: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/gdb/../libdecnumber/dpd/decima= l64.h:94:15: warning: type of 'decimal64ToNumber' does not match original declaration [-Wlto-type-mismatch] decNumber * decimal64ToNumber(const decimal64 *, decNumber *); ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/bid/decimal64.c:8= 7:1: note: 'decimal64ToNumber' was previously declared here decimal64ToNumber (const decimal64 *bid64, decNumber *dn) ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/bid/decimal64.c:8= 7:1: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/gdb/../libdecnumber/dpd/decima= l32.h:90:15: warning: type of 'decimal32FromNumber' does not match original declaration [-Wlto-type-mismatch] decimal32 * decimal32FromNumber(decimal32 *, const decNumber *, ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/bid/decimal32.c:5= 8:1: note: 'decimal32FromNumber' was previously declared here decimal32FromNumber (decimal32 *d32, const decNumber *dn, ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/bid/decimal32.c:5= 8:1: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/gdb/../libdecnumber/dpd/decima= l64.h:92:15: warning: type of 'decimal64FromNumber' does not match original declaration [-Wlto-type-mismatch] decimal64 * decimal64FromNumber(decimal64 *, const decNumber *, ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/bid/decimal64.c:5= 8:1: note: 'decimal64FromNumber' was previously declared here decimal64FromNumber (decimal64 *d64, const decNumber *dn, ^ /dev/shm/build-pkg-18379/src/binutils-master/libdecnumber/bid/decimal64.c:5= 8:1: note: code may be misoptimized unless -fno-strict-aliasing is used /dev/shm/build-pkg-18379/src/binutils-master/gdb/maint.c:704:12: warning: t= ype of 'main' does not match original declaration [-Wlto-type-mismatch] extern int main (); ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/gdb.c:24:1: note: type mismatch in parameter 1 main (int argc, char **argv) ^ /dev/shm/build-pkg-18379/src/binutils-master/gdb/gdb.c:24:1: note: type 'in= t' should match type 'void' /dev/shm/build-pkg-18379/src/binutils-master/gdb/gdb.c:24:1: note: 'main' w= as previously declared here In function 'tui_set_locator_fullname', inlined from 'tui_show_disassem_and_update_source' at /dev/shm/build-pkg-18379/src/binutils-master/gdb/tui/tui-stack.c:346:28, inlined from '_Z35tui_update_source_windows_with_addrP7gdbarchy.part.1'= at /dev/shm/build-pkg-18379/src/binutils-master/gdb/tui/tui-winsource.c:149:40, inlined from 'tui_update_source_windows_with_addr': /dev/shm/build-pkg-18379/src/binutils-master/gdb/tui/tui.c:570:10: warning: 'strncat': specified bound between 2147487746 and 4294967295 exceeds maxim= um object size 2147483647 [-Wstringop-overflow=3D] strncat (buf, item_to_add, (buflen - strlen (buf))); ^ /tmp/ccUhQauM.ltrans0.ltrans.o: In function `amd64_x32_linux_init_abi(gdbarch_info, gdbarch*) [clone .lto_priv.3305]': :(.text+0x290c9): undefined reference to `amd64_create_target_description(unsigned long long, bool, bool)' /tmp/ccUhQauM.ltrans0.ltrans.o: In function `amd64_linux_init_abi(gdbarch_i= nfo, gdbarch*) [clone .lto_priv.3304]': :(.text+0x29999): undefined reference to `amd64_create_target_description(unsigned long long, bool, bool)' /tmp/ccUhQauM.ltrans0.ltrans.o: In function `amd64_linux_core_read_description(gdbarch*, target_ops*, bfd*)': :(.text+0x29c98): undefined reference to `amd64_create_target_description(unsigned long long, bool, bool)' /tmp/ccUhQauM.ltrans20.ltrans.o: In function `initialize_all_files()': :(.text+0x13ff0): undefined reference to `amd64_create_target_description(unsigned long long, bool, bool)' :(.text+0x1728e): undefined reference to `amd64_create_target_description(unsigned long long, bool, bool)' /tmp/ccUhQauM.ltrans20.ltrans.o::(.text+0x172d4): more undefined references to `amd64_create_target_description(unsigned long long, bool, bo= ol)' follow collect2: error: ld returned 1 exit status make[2]: *** [Makefile:2248: gdb] Error 1 make[2]: Leaving directory '/dev/shm/build-pkg-18379/build/binutils-master/= gdb' make[1]: *** [Makefile:10741: all-gdb] Error 2 make[1]: Leaving directory '/dev/shm/build-pkg-18379/build/binutils-master' make: *** [Makefile:850: all] Error 2 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21897-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Sep 07 12:10:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 5787 invoked by alias); 7 Sep 2017 12:10:06 -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 5757 invoked by uid 48); 7 Sep 2017 12:10:04 -0000 From: "sven.c.dack at sky dot com" To: gdb-prs@sourceware.org Subject: [Bug build/22102] 32-bit gdb build fails with undefined reference to amd64_create_target_description Date: Fri, 08 Sep 2017 22:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: sven.c.dack at sky dot com X-Bugzilla-Status: UNCONFIRMED 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: cf_gcctarget 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: 2017-q3/txt/msg00334.txt.bz2 Content-length: 611 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22102 Sven changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |i686-pc-linux-gnu --- Comment #1 from Sven --- The bug seems to have been introduced with commit 22916b0786336394bf84f68ba71875ac3cd48fea (HEAD) Author: Yao Qi Date: Tue Sep 5 09:54:54 2017 +0100 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21898-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 08 22:20:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 129830 invoked by alias); 8 Sep 2017 22:20:32 -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 129027 invoked by uid 48); 8 Sep 2017 22:20:32 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug python/15622] no "new thread" event Date: Fri, 08 Sep 2017 23:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to 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: 2017-q3/txt/msg00335.txt.bz2 Content-length: 488 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15622 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg Assignee|unassigned at sourceware dot org |tromey at sourcewar= e dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21899-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 08 23:30:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 51567 invoked by alias); 8 Sep 2017 23:30:53 -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 51460 invoked by uid 48); 8 Sep 2017 23:30:53 -0000 From: "temp4746 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/16622] set sysroot remote: is not enough for set debug-file-directory Date: Mon, 11 Sep 2017 02:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: temp4746 at gmail dot com 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: cc 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: 2017-q3/txt/msg00336.txt.bz2 Content-length: 1057 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16622 temp4746 at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |temp4746 at gmail dot com --- Comment #1 from temp4746 at gmail dot com --- There are probably multiple causes for this not working. One is that the colon character is used as a separator for debug-file-direc= tory so instead of search for "target:/usr/lib/debug/<...>" it will search for "target/<...>" and "/usr/lib/debug/<...>" locally. And since the directory to search for a symbol file for a remote file alrea= dy has a "target:" prefix (if I understood the code correctly), than it will be looking for /usr/lib/debug/target:/.../<...> locally anyhow. The "target:" prefix will be in the middle of the path. A newer gdb with "set debug separate-debug-file 1" can help show what is go= ing on. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21900-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Sep 11 02:15:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 120481 invoked by alias); 11 Sep 2017 02:15:38 -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 120372 invoked by uid 48); 11 Sep 2017 02:15:33 -0000 From: "stephen.kim at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/21695] Loss of line info Date: Mon, 11 Sep 2017 02:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: stephen.kim at oracle dot com 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: 2017-q3/txt/msg00337.txt.bz2 Content-length: 2563 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21695 --- Comment #4 from Stephen Kim --- Hi, all,=20 I could not reproduce this bug. Here are my configurations: I have an Ubuntu box: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety It comes up with a binary package for the cross compiler: $ arm-none-eabi-gcc --version arm-none-eabi-gcc (15:4.9.3+svn231177-1) 4.9.3 20150529 (prerelease) Copyright (C) 2014 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I think I configured my GDB with the options in this bug report, and the version is: $ ./gdb --version GNU gdb (GDB) 8.0.50.20170908-git The test case was from: https://bugs.launchpad.net/gcc-arm-embedded/+bug/1700646 There was a batch file as far as I remember it. I made a bash script from i= t as follows: $ cat ./build.sh=20 #!/bin/bash arm-none-eabi-gcc -O0 -fno-common -fpie -ffunction-sections -fdata-sections -Wall -mcpu=3Dcortex-m0 -mthumb -mfloat-abi=3Dsoft -g3 -T"linker_script.ld" -Wl,-Map,gdb_test.map,--gc-sections,-emain -nostdlib main.c -o gdb_test2.elf arm-none-eabi-objcopy --output-target binary gdb_test2.elf gdb_test2.bin Then, I did what is described in this bug report: $ ./gdb GNU gdb (GDB) 8.0.50.20170908-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=3Dx86_64-linux-gnu --target=3Darm-none-e= abi". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) add-symbol-file ./gdb_test2.elf 0x1fff0000 add symbol table from file "./gdb_test2.elf" at .text_addr =3D 0x1fff0000 The bug was not reproducible. Would you check if the bug is gone in the 8..50-20170908 GDB? Otherwise, I guess the difference would be the compiler= we used. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21901-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Sep 11 02:44:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 57510 invoked by alias); 11 Sep 2017 02:44:03 -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 57476 invoked by uid 48); 11 Sep 2017 02:44:02 -0000 From: "stephen.kim at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug testsuite/19127] func sum and func print_average fail in dbx.exp Date: Mon, 11 Sep 2017 02:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: stephen.kim at oracle dot com 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: cc 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: 2017-q3/txt/msg00338.txt.bz2 Content-length: 595 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19127 Stephen Kim changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stephen.kim at oracle dot = com --- Comment #1 from Stephen Kim --- It seems to me that nobody has taken this bug yet. As I would like to work = on this bug, I am leaving this comment here. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21902-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Sep 11 02:48:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88965 invoked by alias); 11 Sep 2017 02:48:49 -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 88936 invoked by uid 48); 11 Sep 2017 02:48:48 -0000 From: "stephen.kim at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/21695] Loss of line info Date: Mon, 11 Sep 2017 20:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: stephen.kim at oracle dot com 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: 2017-q3/txt/msg00339.txt.bz2 Content-length: 489 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21695 --- Comment #5 from Stephen Kim --- (y or n) y Reading symbols from ./gdb_test2.elf...done. (gdb) br main Breakpoint 1 at 0x1fff0000 I cannot modify my comments. The add-symbol-file command asked a "yes or no" question above. I answered "y" to it, and was able to set a break point with the address of main, I believe. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21903-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Sep 11 20:27:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36331 invoked by alias); 11 Sep 2017 20:27:40 -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 36302 invoked by uid 55); 11 Sep 2017 20:27:40 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug python/15622] no "new thread" event Date: Mon, 11 Sep 2017 20:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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: 2017-q3/txt/msg00340.txt.bz2 Content-length: 2444 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15622 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D7c96f8c1dae0= 23c7d0b1cabc5e50c4d18fd06960 commit 7c96f8c1dae023c7d0b1cabc5e50c4d18fd06960 Author: Tom Tromey Date: Tue Sep 5 12:07:00 2017 -0600 Add new_inferior, inferior_deleted, and new_thread events This adds a few new events to gdb's Python layer: new_inferior, inferior_deleted, and new_thread. I wanted to be able to add a combined inferior/thread display window to my GUI, and I needed a few events to make this work. This is PR python/15622. ChangeLog 2017-09-11 Tom Tromey PR python/15622: * NEWS: Add entry. * python/python.c (do_start_initialization): Initialize new event types. * python/python-internal.h (gdbpy_initialize_new_inferior_event) (gdbpy_initialize_inferior_deleted_event) (gdbpy_initialize_new_thread_event): Declare. * python/py-threadevent.c (create_thread_event_object): Add option "thread" parameter. * python/py-inferior.c (new_thread_event_object_type) (new_inferior_event_object_type) (inferior_deleted_event_object_type): Declare. (python_new_inferior, python_inferior_deleted): New functions. (add_thread_object): Emit new_thread event. (gdbpy_initialize_inferior): Attach new functions to corresponding observers. (new_thread, new_inferior, inferior_deleted): Define new event types. * python/py-evts.c (gdbpy_initialize_py_events): Add new registries. * python/py-events.h (events_object) : New fields. * python/py-event.h (create_thread_event_breakpoint): Add optional "thread" parameter. doc/ChangeLog 2017-09-11 Tom Tromey * python.texi (Events In Python): Document new events. testsuite/ChangeLog 2017-09-11 Tom Tromey * gdb.python/py-infthread.exp: Add tests for new_thread event. * gdb.python/py-inferior.exp: Add tests for new inferior events. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21904-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Sep 11 20:31:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 43481 invoked by alias); 11 Sep 2017 20:31:41 -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 43452 invoked by uid 48); 11 Sep 2017 20:31:41 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug python/15622] no "new thread" event Date: Tue, 12 Sep 2017 00:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-q3/txt/msg00341.txt.bz2 Content-length: 561 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15622 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |8.1 --- Comment #3 from Tom Tromey --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21905-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 12 00:03:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 114541 invoked by alias); 12 Sep 2017 00:03:03 -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 114357 invoked by uid 48); 12 Sep 2017 00:03:03 -0000 From: "weimin.pan at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21870] aarch64: Leftover uncleared debug registers Date: Tue, 12 Sep 2017 14:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: weimin.pan at oracle dot com 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: cc 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: 2017-q3/txt/msg00342.txt.bz2 Content-length: 1447 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21870 weimin.pan at oracle dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |weimin.pan at oracle dot c= om --- Comment #1 from weimin.pan at oracle dot com --- Looks like it's the kernel that set these control registers with non-zero values. To experiment and verify the new register contents, just added a PTRACE_GETREGSET call, immediately following the PTRACE_SETREGSET call in aarch64_linux_set_debug_regs(). Register contents for the PTRACE_SETREGSET call: gdb) p/x regs $3 =3D {dbg_info =3D 0x0, pad =3D 0x0, dbg_regs =3D {{addr =3D 0x0, ctrl = =3D 0x0, pad =3D 0x0} }} 588 if (ptrace (PTRACE_SETREGSET, tid, (gdb) n 596 if (ptrace (PTRACE_GETREGSET, tid, NT_ARM_HW_WATCH, &iov) =3D=3D 0) (gdb) n 598 regs.dbg_regs[0].addr, regs.dbg_regs[0].ctrl); After the PTRACE_GETREGSET call: (gdb) p/x regs $4 =3D {dbg_info =3D 0x604, pad =3D 0x0, dbg_regs =3D {{addr =3D 0x0, ctrl = =3D 0x1fc, pad =3D 0x0}, {addr =3D 0x0, ctrl =3D 0x1fc, pad =3D 0x0}, {addr =3D = 0x0, ctrl =3D 0x1fc, pad =3D 0x0}, {addr =3D 0x0, ctrl =3D 0x1fc, pad =3D = 0x0}, { addr =3D 0x0, ctrl =3D 0x0, pad =3D 0x0} }} --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21906-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 12 14:33:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 85087 invoked by alias); 12 Sep 2017 14:33:36 -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 85057 invoked by uid 48); 12 Sep 2017 14:33:35 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug cli/16238] "show user" doesn't complete properly Date: Thu, 14 Sep 2017 17:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: cc 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: 2017-q3/txt/msg00343.txt.bz2 Content-length: 541 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16238 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --- Comment #1 from Tom Tromey --- Tripped over this again, went to file a bug, and saw that I already had. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21907-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Sep 14 17:21:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 33855 invoked by alias); 14 Sep 2017 17:21:12 -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 33584 invoked by uid 48); 14 Sep 2017 17:21:12 -0000 From: "aboya at igalia dot com" To: gdb-prs@sourceware.org Subject: [Bug server/22137] New: gdbserver crashes on hosts with pkru register Date: Thu, 14 Sep 2017 17:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: aboya at igalia dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00344.txt.bz2 Content-length: 1304 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22137 Bug ID: 22137 Summary: gdbserver crashes on hosts with pkru register Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: server Assignee: unassigned at sourceware dot org Reporter: aboya at igalia dot com Target Milestone: --- How to reproduce (as a Bash snippet): cat > /tmp/a.c < int main(int argc, char** argv) { puts("hi\n"); return 0; } EOF gcc -g -O0 -o /tmp/a /tmp/a.c gdbserver localhost:5000 /tmp/a & gdb -q /tmp/a <>From gdb-prs-return-21908-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Sep 14 17:53:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79386 invoked by alias); 14 Sep 2017 17:53:04 -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 79348 invoked by uid 48); 14 Sep 2017 17:53:04 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug server/22137] gdbserver crashes on hosts with pkru register Date: Thu, 14 Sep 2017 19:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00345.txt.bz2 Content-length: 478 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22137 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com, | |walfred.tedeschi at intel = dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21909-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Sep 14 19:52:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 24606 invoked by alias); 14 Sep 2017 19:52:48 -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 24578 invoked by uid 48); 14 Sep 2017 19:52:47 -0000 From: "Jim_Muchow at Dell dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/20020] GDB segfault on printing objects Date: Fri, 15 Sep 2017 19:59: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: Jim_Muchow at Dell dot com 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: cc 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: 2017-q3/txt/msg00346.txt.bz2 Content-length: 2417 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20020 Jim Muchow changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Jim_Muchow at Dell dot com --- Comment #7 from Jim Muchow --- This is very interesting; I thought it was only me that experienced this. I have been looking into this issue, off and on (tho' mostly off) for some months. I have found that it can be avoided in our situation, by running "s= et print static-members off" either by hand or in .gdbinit. While I agree with Thilo's approach below of testing for a NULL-pointer bef= ore calling cp_print_static_field(), it seems to me that this may not actually = fix the problem - and perhaps cause another. I was concerned with the latter case because if gdb was unable to find a variable (in the call to value_static_field()), then perhaps it is better to crash (perhaps using gdb_assert())? This call to value_static_field() after= all occurs in a for-loop and so perhaps the problem worsens ignoring by the NULL-pointer? Maybe? I defer to Thilo's experience in this regard; if the f= ix seems to work with no side effect, great. I bring up the problem of something else being the real source of the probl= em because I found in my cases that GDB was trying to reference a variable tha= t I couldn't even find (ie, the cause of the NULL-pointer). In my case there wa= s a C++ template: template class BlockHolder { ... static const uns32 DEBUGLOG_ENUM_LOGALL =3D 0xFFFFFFFF; } During investigation, I discovered that the symbol is not even present in t= he output of "objdump -t /binary_unstripped". I made the assumption that= the symbol was a prime candidate to be optimized out since it is static, const,= and with a predefined value. I also assumed that if I used a debug build, that = the symbol was more likely to be found. Oddly, it wasn't. In short, this looks like a situation in which the compiler/linker have conspired, so to speak, against gdb. I'm not really sure there is anything = that can be done in this situation except add various conditionals like Thilo's = to avoid the problem. Regards, Jim Muchow --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21910-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 15 19:59:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 82170 invoked by alias); 15 Sep 2017 19:59:54 -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 82148 invoked by uid 48); 15 Sep 2017 19:59:54 -0000 From: "bgraham at technosofteng dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22143] New: gdb dies in E2 Studio Date: Sun, 17 Sep 2017 15:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: bgraham at technosofteng dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00347.txt.bz2 Content-length: 1550 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22143 Bug ID: 22143 Summary: gdb dies in E2 Studio Product: gdb Version: unknown Status: UNCONFIRMED Severity: critical Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: bgraham at technosofteng dot com Target Milestone: --- See console output below. [338 ssp\src\framework\el\tx\tx_src\synergy\tx_thread_schedule.c: No such file or directory. Thread 1.1] #1 stopped. _skip_vfp_restore () at ssp\src\framework\el\tx\tx_src\synergy\tx_thread_schedule.c:338 ../../ARM_python_GDB/gdb/inline-frame.c:169: internal-error: inline_frame_this_id: Assertion `frame_id_p (*this_id)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] This is a bug, please report it. For instructions, see: . ../../ARM_python_GDB/gdb/inline-frame.c:169: internal-error: inline_frame_this_id: Assertion `frame_id_p (*this_id)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] This application has requested the Runtime to terminate it in an unusual wa= y. Please contact the application's support team for more information. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21911-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Sep 17 15:37:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 104008 invoked by alias); 17 Sep 2017 15:37:15 -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 103981 invoked by uid 48); 17 Sep 2017 15:37:15 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug python/18621] No "frame change" event Date: Mon, 18 Sep 2017 21:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: OBSOLETE 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00348.txt.bz2 Content-length: 658 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18621 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |OBSOLETE --- Comment #2 from Tom Tromey --- It seems to me that any sort of frame-changed event could only be triggered before a prompt. So, anybody needing this could synthesize it pretty easily. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21912-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Sep 18 21:01:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 6427 invoked by alias); 18 Sep 2017 21:01:34 -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 4123 invoked by uid 48); 18 Sep 2017 21:01:33 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug build/22102] 32-bit gdb build fails with undefined reference to amd64_create_target_description Date: Tue, 19 Sep 2017 00:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00349.txt.bz2 Content-length: 775 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22102 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org --- Comment #2 from Yao Qi --- (In reply to Sven from comment #1) > The bug seems to have been introduced with >=20 > commit 22916b0786336394bf84f68ba71875ac3cd48fea (HEAD) > Author: Yao Qi > Date: Tue Sep 5 09:54:54 2017 +0100 The build failure should be fixed by this patch, https://sourceware.org/ml/gdb-patches/2017-09/msg00403.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21913-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 19 00:33:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 8461 invoked by alias); 19 Sep 2017 00:33:00 -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 8416 invoked by uid 48); 19 Sep 2017 00:33:00 -0000 From: "liuluping1 at huawei dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/9055] gdb segment fault with core dumped Date: Wed, 20 Sep 2017 13:18: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: 6.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: liuluping1 at huawei dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q3/txt/msg00350.txt.bz2 Content-length: 399 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9055 liuluping changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |liuluping1 at huawei dot c= om --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21914-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 20 13:18:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 69579 invoked by alias); 20 Sep 2017 13:18:29 -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 69552 invoked by uid 48); 20 Sep 2017 13:18:28 -0000 From: "walfred.tedeschi at intel dot com" To: gdb-prs@sourceware.org Subject: [Bug server/22137] gdbserver crashes on hosts with pkru register Date: Wed, 20 Sep 2017 13:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: walfred.tedeschi at intel dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q3/txt/msg00351.txt.bz2 Content-length: 414 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22137 --- Comment #1 from Walfred Tedeschi --- Created attachment 10433 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10433&action=3Ded= it Previous commiter did not regenerated the dat files. Partially added to Master branch by Yao. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21915-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 20 13:19:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 71132 invoked by alias); 20 Sep 2017 13:19:11 -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 71093 invoked by uid 48); 20 Sep 2017 13:19:08 -0000 From: "walfred.tedeschi at intel dot com" To: gdb-prs@sourceware.org Subject: [Bug server/22137] gdbserver crashes on hosts with pkru register Date: Thu, 21 Sep 2017 00:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: walfred.tedeschi at intel dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q3/txt/msg00352.txt.bz2 Content-length: 288 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22137 --- Comment #2 from Walfred Tedeschi --- Bug is confirmed. Patch should fix the issue. Thanks and regards, /Fred --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21916-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Sep 21 00:01:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4957 invoked by alias); 21 Sep 2017 00:01:53 -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 4925 invoked by uid 48); 21 Sep 2017 00:01:52 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/14186] const volatile is ignored for TYPE_INSTANCE Date: Thu, 21 Sep 2017 16:27: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: palves at redhat dot com 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: cc 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: 2017-q3/txt/msg00353.txt.bz2 Content-length: 1544 https://sourceware.org/bugzilla/show_bug.cgi?id=3D14186 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #3 from Pedro Alves --- Keith informed me today that I fixed this PR with this patch: https://sourceware.org/ml/gdb-patches/2017-07/msg00147.html commit 3693fdb3c8ec14bd8ecb4ebb39e4384b330a2999 Author: Pedro Alves AuthorDate: Mon Sep 4 20:21:16 2017 +0100 Make "p S::method() const::static_var" work too Somehow I completely managed to overlook that that caused: KPASS: gdb.cp/cpexprs.exp: p CV::m(int) const (PRMS c++/14186) KPASS: gdb.cp/cpexprs.exp: p CV::m(int) volatile (PRMS c++/14186) KPASS: gdb.cp/cpexprs.exp: p CV::m(int) const volatile (PRMS c++/14186) It pains me to realize that this had a partially written patch here... There are some similarities, and some differences; In your version from 201= 2, it seems like you avoided touching dwarf2read.c, with the "inexact_match" check in value_struct_elt_for_reference, but I'm not really sure I understa= nd that. And now I'm wondering whether we're missing something in master arou= nd overload resolution, since in the use case I was aiming for [accessing local statics], I was only thinking of exact matches. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21917-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Sep 21 16:27:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 38412 invoked by alias); 21 Sep 2017 16:27:03 -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 38351 invoked by uid 48); 21 Sep 2017 16:27:02 -0000 From: "zontik77 at poczta dot fm" To: gdb-prs@sourceware.org Subject: [Bug threads/22177] New: set detach-on-fork off does not work properly Date: Thu, 21 Sep 2017 16:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: zontik77 at poczta dot fm X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00354.txt.bz2 Content-length: 1156 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22177 Bug ID: 22177 Summary: set detach-on-fork off does not work properly Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: threads Assignee: unassigned at sourceware dot org Reporter: zontik77 at poczta dot fm Target Milestone: --- Even for the simplest fork c program (no shared libs etc.) it is impossible= to turn off detaching processes. After fork with this option set (set detach-on-fork off) there is always the same info from the GDB : ... (gdb) n Single stepping until exit from function fork, which has no line number information. [New process <...> ] Reading symbols from <...> Warning: Cannot insert breakpoint <...>. Cannot access memory at address <...> (gdb) n Cannot find the bound of the current function ... My gcc version : 7.2.0-2 My kernel version: 4.12.13-1 My gdb version :8.0.1-1 Bush fix: downgrading gdb from 8.0.1-1 to 8.0.1 fixed the problem. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21918-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Sep 21 16:30:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 47275 invoked by alias); 21 Sep 2017 16:30:42 -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 47253 invoked by uid 48); 21 Sep 2017 16:30:41 -0000 From: "zontik77 at poczta dot fm" To: gdb-prs@sourceware.org Subject: [Bug threads/22177] set detach-on-fork off does not work properly Date: Fri, 22 Sep 2017 03:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: zontik77 at poczta dot fm X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00355.txt.bz2 Content-length: 389 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22177 dzoker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zontik77 at poczta dot fm --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21919-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 22 03:39:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 108457 invoked by alias); 22 Sep 2017 03:39:47 -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 108431 invoked by uid 48); 22 Sep 2017 03:39:47 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/15828] GDB crashed during process attachment when that process was dumping its own core due to a fault Date: Fri, 22 Sep 2017 09:01: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.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: cc 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: 2017-q3/txt/msg00356.txt.bz2 Content-length: 546 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15828 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jan.kratochvil at redhat d= ot com --- Comment #2 from Jan Kratochvil --- I cannot reproduce it, do you still have it reproducible? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21920-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 22 09:01:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 24851 invoked by alias); 22 Sep 2017 09:01:14 -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 24826 invoked by uid 48); 22 Sep 2017 09:01:14 -0000 From: "ro at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22185] New: Obsolete/remove support for Solaris < 10 Date: Fri, 22 Sep 2017 14:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: ro at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget Message-ID: 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: 2017-q3/txt/msg00357.txt.bz2 Content-length: 1056 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22185 Bug ID: 22185 Summary: Obsolete/remove support for Solaris < 10 Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: ro at gcc dot gnu.org Reporter: ro at gcc dot gnu.org Target Milestone: 8.1 Target: *-*-solaris2.[01], *-*-solaris2.[2-9]* This is tracking bug according to https://sourceware.org/gdb/wiki/Internals%20Obsoleting-code: GCC has obsoleted/removed support for Solaris 9 in GCC 4.9/5 in 2013: https://gcc.gnu.org/gcc-4.9/changes.html https://gcc.gnu.org/ml/gcc-patches/2013-05/msg00728.html While gdb 7.12.1 can still be built (only with --disable-build-with-cxx), t= he=20 8.0 branch and trunk cannot, and it seems a waste of time to even try to ma= ke it work. Therefore, support will be removed for the gdb 8.1 release. Rainer --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21921-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 22 14:45:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 125907 invoked by alias); 22 Sep 2017 14:45:56 -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 125873 invoked by uid 48); 22 Sep 2017 14:45:55 -0000 From: "ro at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22185] Obsolete/remove support for Solaris < 10 Date: Fri, 22 Sep 2017 16: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: ro at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status bug_file_loc 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: 2017-q3/txt/msg00358.txt.bz2 Content-length: 657 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22185 Rainer Orth changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED URL| |https://sourceware.org/ml/g | |db-patches/2017-09/msg00674 | |.html --- Comment #1 from Rainer Orth --- Patch posted. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21922-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 22 16:26:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 103576 invoked by alias); 22 Sep 2017 16:26:35 -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 103529 invoked by uid 48); 22 Sep 2017 16:26:35 -0000 From: "dilyan.palauzov at aegee dot org" To: gdb-prs@sourceware.org Subject: [Bug compile/22188] New: gdb/arm-tdep.c:6449: (rn & 0xe) == 0x1 - tautology Date: Fri, 22 Sep 2017 21:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: compile X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dilyan.palauzov at aegee dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00359.txt.bz2 Content-length: 1442 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22188 Bug ID: 22188 Summary: gdb/arm-tdep.c:6449: (rn & 0xe) =3D=3D 0x1 - tautology Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: compile Assignee: unassigned at sourceware dot org Reporter: dilyan.palauzov at aegee dot org Target Milestone: --- Compiling with GCC 8 I get: binutils-gdb/gdb/arm-tdep.c: In function =E2=80=98int arm_decode_misc_memhint_neon(gdbarch*, uint32_t, regcache*, displaced_step_closure*)=E2=80=99: binutils-gdb/gdb/arm-tdep.c:6449:52: error: bitwise comparison always evalu= ates to false [-Werror=3Dtautological-compare] else if (op1 =3D=3D 0x10 && op2 =3D=3D 0x0 && (rn & 0xe) =3D=3D 0x1) ~~~~~~~~~~~^~~~~~ Indeed (whatever & 0xe) cannot have zero as least significant bit. Likewise binutils-gdb/gdb/rs6000-tdep.c: In function =E2=80=98CORE_ADDR skip_prologu= e(gdbarch*, CORE_ADDR, CORE_ADDR, rs6000_framedata*)=E2=80=99: binutils-gdb/gdb/rs6000-tdep.c:1859:34: error: bitwise comparison always evaluates to false [-Werror=3Dtautological-compare] else if ((op & 0xfc1f016a) =3D=3D 0x7c01016e) ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~ op & 0x....a cannot be 0x....e --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21923-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 22 21:45:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23486 invoked by alias); 22 Sep 2017 21:45:26 -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 23436 invoked by uid 48); 22 Sep 2017 21:45:24 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/22177] set detach-on-fork off does not work properly Date: Sun, 24 Sep 2017 04:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00360.txt.bz2 Content-length: 729 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22177 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #1 from Sergio Durigan Junior --- Thanks for the bug report. There is no "8.0.1-1" release; this is usually an indicative of a distribut= ion version. Are you using a specific GNU/Linux distribution? If yes, can you reproduce the bug using the upstream GDB repository? Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21924-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Sep 24 04:32:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 69490 invoked by alias); 24 Sep 2017 04:32:32 -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 68884 invoked by uid 48); 24 Sep 2017 04:32:31 -0000 From: "ciro.santilli at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/22195] New: Provide a help() method to gdb.Command that overrides the docstring Date: Sun, 24 Sep 2017 13:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: ciro.santilli at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00361.txt.bz2 Content-length: 855 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22195 Bug ID: 22195 Summary: Provide a help() method to gdb.Command that overrides the docstring Product: gdb Version: 7.11.1 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: ciro.santilli at gmail dot com Target Milestone: --- I want to use pythons argparse for command parameter handling after gdb.string_to_argv If I had a method: define help(): that would override the class docstring for: help mycmd I could return: return parser.format_usage() there and everything would be DRY and beautiful. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21925-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Sep 24 13:04:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 128624 invoked by alias); 24 Sep 2017 13:04:13 -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 128039 invoked by uid 48); 24 Sep 2017 13:04:12 -0000 From: "stephen.kim at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug testsuite/19127] func sum and func print_average fail in dbx.exp Date: Sun, 24 Sep 2017 13:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: stephen.kim at oracle dot com 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: 2017-q3/txt/msg00362.txt.bz2 Content-length: 6638 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19127 --- Comment #2 from Stephen Kim --- The last comment was 2015-10-14. As of Sep. 24th 2017 in Tokyo time, I have done the following, and it does not look like the bug is reproducible. If I= am mistaken somewhere, please, let me know. 1. arm-none-eabi-gcc/g++ - Downloaded binaries from https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads 2. gdb a. as of the date above, git clone as follows: git clone git://sourceware.org/git/binutils-gdb.git gdb_arm b. configure'd as follows: mkdir build cd build; ../configure --target=3Darm-none-eabi --with-libexpat --with-lz= ma=3Dno --build=3Dx86_64-linux-gnu --host=3Dx86_64-linux-gnu --with-python=3Dno c. make After 1 and 2 are done, the following command was run and 5 failures were reported: make check RUNTESTFLAGS=3D"CFLAGS_FOR_TARGET=3D'--specs=3Dnosys.specs'=20 gdb.base/dbx.exp" However, when I looked into the gdb.log, it seems like all failures were du= e to that the debugee was not really running. According to the gdb.log from anot= her gdb on and for x86, I tried to run the gdb commands in the test case one by one. Only that I should have added 'target sim' and 'load' command. Please, see below: aion1223@localhost ~/workspace/srcs/gdb_arm/build $=20 /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/../../gdb/gdb -nw= -nx -data-directory /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/../data-directory --dbx GNU gdb (GDB) 8.0.50.20170924-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=3Dx86_64-linux-gnu --target=3Darm-none-e= abi". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) set height 0 (gdb) set width 0 (gdb) use Reinitialize source path to empty? (y or n) y Source directories searched: $cdir:$cwd (gdb) use /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/../../../gdb/test= suite/gdb.base Source directories searched: /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/../../../gdb/test= suite/gdb.base:$cdir:$cwd (gdb) symbol-file /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/outputs/gdb.base/= dbx/dbx Reading symbols from /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/outputs/gdb.base/= dbx/dbx...done. (gdb) exec-file /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/outputs/gdb.base/= dbx/dbx (gdb) stop in main Breakpoint 1 at 0x82d8: file /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/../../../gdb/test= suite/gdb.base/average.c, line 25. (gdb) status Num Type Disp Enb Address What 1 breakpoint keep y 0x000082d8 in main at /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/../../../gdb/test= suite/gdb.base/average.c:25 (gdb) stop at average.c:30 Breakpoint 2 at 0x8300: file /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/../../../gdb/test= suite/gdb.base/average.c, line 30. (gdb) stop in average.c:30 Usage: stop in (gdb) stop at main Usage: stop at (gdb) run Don't know how to run. Try "help target". (gdb) target sim Connected to the simulator. (gdb) load Loading section .init, size 0x18 lma 0x8000 Loading section .text, size 0xa844 lma 0x8018 Loading section .fini, size 0x18 lma 0x1285c Loading section .rodata, size 0x2d5 lma 0x12878 Loading section .ARM.exidx, size 0x8 lma 0x12b50 Loading section .eh_frame, size 0x4 lma 0x12b58 Loading section .init_array, size 0x8 lma 0x22b5c Loading section .fini_array, size 0x4 lma 0x22b64 Loading section .jcr, size 0x4 lma 0x22b68 Loading section .data, size 0x9d8 lma 0x22b70 Start address 0x8130 Transfer rate: 371176 bits in <1 sec. (gdb) run Starting program: /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/outputs/gdb.base/= dbx/dbx=20 Breakpoint 1, main () at /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/../../../gdb/test= suite/gdb.base/average.c:25 25 int first =3D 0, last =3D 0; /* stop-in-main */ (gdb) assign first=3D1 (gdb) print first $1 =3D 1 (gdb) whereis my_list All variables matching regular expression "my_list": File /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/../../../gdb/test= suite/gdb.base/average.c: static int my_list[10]; (gdb) file average.c:1 1 /* This is a sample program for the HP WDB debugger. */ 2=20=20=20=20=20=20=20 3 #include 4 #include 5=20=20=20=20=20=20=20 6 extern int sum(int *, int, int); 7=20=20=20=20=20=20=20 8 #define num 10 9=20=20=20=20=20=20=20 10 static int my_list[num] =3D {3,4,2,0,2,1,8,3,6,7}; (gdb) cont Continuing. Breakpoint 2, main () at /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/../../../gdb/test= suite/gdb.base/average.c:30 30 print_average (my_list, first, last - 3); /* stop-at-call */ (gdb) step print_average (list=3D0x22b74 , low=3D0, high=3D6) at /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/../../../gdb/test= suite/gdb.base/average.c:14 14 int total =3D 0, num_elements =3D 0, average =3D 0; (gdb) func sum 'sum' not within current stack frame. (gdb) stop in sum Breakpoint 3 at 0x833c: file /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/../../../gdb/test= suite/gdb.base/sum.c, line 6. (gdb) cont Continuing. Breakpoint 3, sum (list=3D0x22b74 , low=3D0, high=3D6) at /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/../../../gdb/test= suite/gdb.base/sum.c:6 6 int i =3D 0, s =3D 0; /* stop-in-sum */ (gdb) func print_average #1 0x00008284 in print_average (list=3D0x22b74 , low=3D0, high=3D= 6) at /home/aion1223/workspace/srcs/gdb_arm/build/gdb/testsuite/../../../gdb/test= suite/gdb.base/average.c:15 15 total =3D sum(list, low, high); I believe that the output is as expected. In other words, GDB on and for x86 passes this test case, and the output above seems the same. I am not sure if this bug is reproducible. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21927-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Sep 24 17:10:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 9016 invoked by alias); 24 Sep 2017 17:10:16 -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 8293 invoked by uid 48); 24 Sep 2017 17:10:16 -0000 From: "psppsn96 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/7850] 16 bit real-mode for the i386 Date: Sun, 24 Sep 2017 17:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: psppsn96 at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q3/txt/msg00364.txt.bz2 Content-length: 392 https://sourceware.org/bugzilla/show_bug.cgi?id=3D7850 Kyle Marek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |psppsn96 at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21926-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Sep 24 13:06:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63396 invoked by alias); 24 Sep 2017 13:06:42 -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 63373 invoked by uid 48); 24 Sep 2017 13:06:42 -0000 From: "ciro.santilli at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22198] New: Allow skip -gfi globs to match directories recursively Date: Sun, 24 Sep 2017 17:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: ciro.santilli at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00363.txt.bz2 Content-length: 702 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22198 Bug ID: 22198 Summary: Allow skip -gfi globs to match directories recursively Product: gdb Version: 7.11.1 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: ciro.santilli at gmail dot com Target Milestone: --- E.g., I'd like to do: skip -gfi /usr/include/c++/**/*.h to skip all C++ standard library files, in particular entering unique_ptr. The ** part does not work. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21928-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Sep 24 17:10:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 59310 invoked by alias); 24 Sep 2017 17:10:48 -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 58771 invoked by uid 48); 24 Sep 2017 17:10:47 -0000 From: "jpyeron at pdinc dot us" To: gdb-prs@sourceware.org Subject: [Bug tdep/7850] 16 bit real-mode for the i386 Date: Sun, 24 Sep 2017 17:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jpyeron at pdinc dot us X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q3/txt/msg00365.txt.bz2 Content-length: 390 https://sourceware.org/bugzilla/show_bug.cgi?id=3D7850 Jason Pyeron changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jpyeron at pdinc dot us --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21929-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Sep 24 17:14:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 18451 invoked by alias); 24 Sep 2017 17:14:22 -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 18006 invoked by uid 48); 24 Sep 2017 17:14:22 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/13000] Return value with -batch is always 0 Date: Mon, 25 Sep 2017 12:28: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: jan.kratochvil at redhat dot com 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: cc 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: 2017-q3/txt/msg00366.txt.bz2 Content-length: 413 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13000 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jan.kratochvil at redhat d= ot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21931-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Sep 25 14:36:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 16709 invoked by alias); 25 Sep 2017 14:36:30 -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 15322 invoked by uid 48); 25 Sep 2017 14:36:29 -0000 From: "ro at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug build/22206] New: [8.1 regression] SPARC M7 ADI patches break Solaris build Date: Mon, 25 Sep 2017 14:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget attachments.created Message-ID: 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: 2017-q3/txt/msg00368.txt.bz2 Content-length: 4367 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22206 Bug ID: 22206 Summary: [8.1 regression] SPARC M7 ADI patches break Solaris build Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: ro at gcc dot gnu.org CC: weimin.pan at oracle dot com Target Milestone: --- Target: sparc*-sun-solaris2.* Created attachment 10480 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10480&action=3Ded= it Minimal patch The recent SPARC M7 ADI patches break the gdb build on Solaris/SPARC (which is a total shame: feels like one side of Oracle doesn't care about w= hat the other side is doing ;-(). I'm seeing it on Solaris 10/SPARC, haven't tried 11.3 or 11.4 beta yet: /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c:1876:0: error: "PSR_ICC" redefined [-Werror] #define PSR_ICC 0x00f00000 ^ In file included from /usr/include/v7/sys/privregs.h:24:0, from /usr/include/sys/regset.h:420, from /usr/include/sys/ucontext.h:21, from /usr/include/sys/signal.h:231, from /usr/include/sys/procset.h:23, from /usr/include/sys/wait.h:25, from /usr/include/stdlib.h:21, from build-gnulib/import/stdlib.h:36, from /vol/src/gnu/gdb/gdb/local/gdb/common/common-defs.h:5= 3, from /vol/src/gnu/gdb/gdb/local/gdb/defs.h:28, from /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c:20: /usr/include/v7/sys/psr.h:35:0: note: this is the location of the previous definition #define PSR_ICC 0x00F00000 /* integer condition codes */ ^ /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c:1878:0: error: "PSR_IMPL" redefined [-Werror] #define PSR_IMPL 0xf0000000 ^ In file included from /usr/include/v7/sys/privregs.h:24:0, from /usr/include/sys/regset.h:420, from /usr/include/sys/ucontext.h:21, from /usr/include/sys/signal.h:231, from /usr/include/sys/procset.h:23, from /usr/include/sys/wait.h:25, from /usr/include/stdlib.h:21, from build-gnulib/import/stdlib.h:36, from /vol/src/gnu/gdb/gdb/local/gdb/common/common-defs.h:5= 3, from /vol/src/gnu/gdb/gdb/local/gdb/defs.h:28, from /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c:20: /usr/include/v7/sys/psr.h:41:0: note: this is the location of the previous definition #define PSR_IMPL 0xF0000000 /* implementation */ ^ /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c: In function =E2=80=98int adi= _tag_fd()=E2=80=99: /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c:296:63: error: format =E2=80= =98%d=E2=80=99 expects argument of type =E2=80=98int=E2=80=99, but argument 4 has type =E2= =80=98pid_t {aka long int}=E2=80=99 [-Werror=3Dformat=3D] snprintf (cl_name, sizeof(cl_name), "/proc/%d/adi/tags", pid); ^ /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c: In function =E2=80=98bool adi_is_addr_mapped(CORE_ADDR, std::size_t)=E2=80=99: /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c:314:64: error: format =E2=80= =98%d=E2=80=99 expects argument of type =E2=80=98int=E2=80=99, but argument 4 has type =E2= =80=98pid_t {aka long int}=E2=80=99 [-Werror=3Dformat=3D] snprintf (filename, sizeof filename, "/proc/%d/adi/maps", pid); ^ The attached patch at least allows the build to finish, but there are way more problems with this code (only from a quick inspection): * The Solaris/SPARC codes doesn't make use of/support ADI; it's currently=20 Linux-only. * Some of the new code in sparc64-tdep.c is Linux-specific, although this is supposed to be platform-independent code: ** ADI support in procfs is way different from the way used here, which is Linux-specific. ** Same for ADI support in auxv: none of AT_ADI_BLKSZ, AT_ADI_NBITS, and AT_ADI_UEONADI exist on Solaris, and the latter is unused beside its definition. Rainer --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21930-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Sep 25 12:28:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 45080 invoked by alias); 25 Sep 2017 12:28:22 -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 44368 invoked by uid 48); 25 Sep 2017 12:28:21 -0000 From: "eldar.abusalimov at jetbrains dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/20020] GDB segfault on printing objects Date: Mon, 25 Sep 2017 14:36: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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: eldar.abusalimov at jetbrains dot com 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: cc 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: 2017-q3/txt/msg00367.txt.bz2 Content-length: 466 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20020 Eldar Abusalimov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eldar.abusalimov@jetbrains. | |com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21932-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Sep 25 14:36:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79230 invoked by alias); 25 Sep 2017 14:36:43 -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 77169 invoked by uid 48); 25 Sep 2017 14:36:43 -0000 From: "ro at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug build/22206] [8.1 regression] SPARC M7 ADI patches break Solaris build Date: Tue, 26 Sep 2017 05:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone 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: 2017-q3/txt/msg00369.txt.bz2 Content-length: 368 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22206 Rainer Orth changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21934-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 26 05:48:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 43679 invoked by alias); 26 Sep 2017 05:48:00 -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 43228 invoked by uid 48); 26 Sep 2017 05:47:59 -0000 From: "matthias291999 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22208] Deadlock in watchpoint handling Date: Tue, 26 Sep 2017 05:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: matthias291999 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00371.txt.bz2 Content-length: 415 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22208 Matthias Zimmerman changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthias291999 at gmail do= t com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21933-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 26 05:43:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 54272 invoked by alias); 26 Sep 2017 05:43:09 -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 54076 invoked by uid 48); 26 Sep 2017 05:43:08 -0000 From: "matthias291999 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22208] New: Deadlock in watchpoint handling Date: Tue, 26 Sep 2017 05:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: matthias291999 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00370.txt.bz2 Content-length: 1614 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22208 Bug ID: 22208 Summary: Deadlock in watchpoint handling Product: gdb Version: 7.12 Status: UNCONFIRMED Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: matthias291999 at gmail dot com Target Milestone: --- When i use:: >watch *(long int)$rsp >command >silent >si >end I am also using pwndbg Then ni a few times. Gdb enters a deadlock, polling for something... The stack & registers of the deadlocked process... I am using Ubuntu 17.04 RAX 0xfffffffffffffdfc RBX 0xffffffff RCX 0x7efbf5bf5d70 (__poll_nocancel+7) =E2=97=82=E2=80=94 cmp rax, -0x= fff RDX 0xffffffff RDI 0x565558f4fb60 =E2=97=82=E2=80=94 0x100000003 RSI 0x3 R8 0x7efbf5ebc750 (_IO_stdfile_2_lock) =E2=97=82=E2=80=94 0x0 R9 0x7efbf7fba780 =E2=97=82=E2=80=94 0x7efbf7fba780 R10 0x8 *R11 0x346 R12 0x0 R13 0x5655581c8950 =E2=80=94=E2=96=B8 0x565555e2bcb8 =E2=80=94=E2=96=B8 0= x565555758430 (linux_ptrace_test_ret_to_nx_instr+992351) =E2=97=82=E2=80=94 lea rax, [= rip + 0x6d3881] R14 0x56555580b3a0 =E2=97=82=E2=80=94 push rbx R15 0x565555a73980 =E2=97=82=E2=80=94 add byte ptr [rax], al RBP 0x565555f31db0 =E2=97=82=E2=80=94 0x0 RSP 0x7ffbffffa898 =E2=80=94=E2=96=B8 0x5655557b2f31 =E2=97=82=E2=80=94 c= mp eax, -1 RIP 0x7efbf5bf5d70 (__poll_nocancel+7) =E2=97=82=E2=80=94 cmp rax, -0x= fff --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21935-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 26 05:48:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 43887 invoked by alias); 26 Sep 2017 05:48:00 -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 43240 invoked by uid 48); 26 Sep 2017 05:47:59 -0000 From: "matthias291999 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21328] checkpoint deadlock Date: Tue, 26 Sep 2017 09:10: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.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: matthias291999 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00372.txt.bz2 Content-length: 1090 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21328 Matthias Zimmerman changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthias291999 at gmail do= t com --- Comment #1 from Matthias Zimmerman --- This is not a bug, you have a breakpoint in an area that you later call from gdb, ie >break exit >p exit() >From gdb-prs-return-21936-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 26 09:10:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64317 invoked by alias); 26 Sep 2017 09:10:18 -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 64294 invoked by uid 48); 26 Sep 2017 09:10:17 -0000 From: "t at jujit dot su" To: gdb-prs@sourceware.org Subject: [Bug gdb/22211] New: gdb 8.0.1 x86_64 thread.c:1123: internal-error: void finish_thread_state(ptid_t): Assertion `tp' failed. Date: Tue, 26 Sep 2017 09:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: t at jujit dot su X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q3/txt/msg00373.txt.bz2 Content-length: 9196 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22211 Bug ID: 22211 Summary: gdb 8.0.1 x86_64 thread.c:1123: internal-error: void finish_thread_state(ptid_t): Assertion `tp' failed. Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: t at jujit dot su Target Milestone: --- Created attachment 10485 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10485&action=3Ded= it code and python script to reproduce gdb 8.0.1 arch linux package Linux 4.12.13-1-ARCH #1 SMP PREEMPT Fri Sep 15 06:36:43 UTC 2017 x86_64 GNU/Linux=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 Code and script to reproduce: see attachment or https://github.com/spacejam/gdb-bug Description: Two threads are run one at a time in non-stop mode until they reach a "stop" breakpoint. Then we "run" and gdb crashes when in thread.c at finish_thread_state=20 Crash log: GNU gdb (GDB) 8.0.1=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". seeding with 752097355547 +file target/debug/race warning: Missing auto-load script at offset 0 in section .debug_gdb_scripts of file /home/t/src/gdb-bug/target/debug/race. Use `info auto-load python-scripts [REGEXP]' to list them. +set non-stop on +set confirm off +b src/main.rs:8=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 Breakpoint 1 at 0xf0f2: file src/main.rs, line 8.=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 +r=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 [Thread debugging using libthread_db enabled]=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7ffff6bff700 (LWP 20352)]=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 [New Thread 0x7ffff69fe700 (LWP 20353)]=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 Thread 2 "race" hit Breakpoint 1, race::bad_txn () at src/main.rs:8=20=20= =20=20=20=20=20=20=20=20=20=20=20 8 if A.load(SeqCst) =3D=3D 0 { (gdb) running schedule +d Breakpoint 2 at 0x5555555630f2: file src/main.rs, line 8.=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 Breakpoint 3 at 0x55555556312a: file src/main.rs, line 9.=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 Breakpoint 4 at 0x555555596e71: file /checkout/src/liballoc/boxed.rs, line = 241.=20 Breakpoint 5 at 0x55555556330a: file src/main.rs, line 12.=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 +t 2=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 [Switching to thread 2 (Thread 0x7ffff6bff700 (LWP 20352))] #0 race::bad_txn () at src/main.rs:8=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 8 if A.load(SeqCst) =3D=3D 0 {=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20 +c=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 Selected thread is running.=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 (gdb) thread 2 hit breakpoint at src/main.rs:9=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 +t 2=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 [Switching to thread 2 (Thread 0x7ffff6bff700 (LWP 20352))]=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 #0 race::bad_txn () at src/main.rs:9=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 9 A.fetch_add(10, SeqCst);=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 +c=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 Selected thread is running.=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 (gdb) success!=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 +t 3=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 [Switching to thread 3 (Thread 0x7ffff69fe700 (LWP 20353))]=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 #0 race::bad_txn () at src/main.rs:8=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 8 if A.load(SeqCst) =3D=3D 0 {=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20 +c=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 Selected thread is running.=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 (gdb) restarting execution after running out of valid threads=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 +k=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 +file target/debug/race=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 warning: Missing auto-load script at offset 0 in section .debug_gdb_scripts= =20=20=20=20=20 of file /home/t/src/gdb-bug/target/debug/race. Use `info auto-load python-scripts [REGEXP]' to list them. reseeding with 84716566159 +b src/main.rs:8 Breakpoint 6 at 0xf0f2: file src/main.rs, line 8. +r thread.c:1123: internal-error: void finish_thread_state(ptid_t): Assertion = `tp' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. This is a bug, please report it. For instructions, see: . [1] 20343 abort (core dumped) ./debug.py --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21937-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 26 09:37:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 99782 invoked by alias); 26 Sep 2017 09:37:25 -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 99750 invoked by uid 48); 26 Sep 2017 09:37:25 -0000 From: "ro at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug build/22206] [8.1 regression] SPARC M7 ADI patches break Solaris build Date: Tue, 26 Sep 2017 13:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_file_loc 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: 2017-q3/txt/msg00374.txt.bz2 Content-length: 607 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22206 Rainer Orth changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://sourceware.org/ml/g | |db-patches/2017-09/msg00787 | |.html --- Comment #1 from Rainer Orth --- Minimal patch posted. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21938-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 26 13:01:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94469 invoked by alias); 26 Sep 2017 13:01:30 -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 93358 invoked by uid 55); 26 Sep 2017 13:01:29 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug build/22206] [8.1 regression] SPARC M7 ADI patches break Solaris build Date: Tue, 26 Sep 2017 13:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q3/txt/msg00375.txt.bz2 Content-length: 5388 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22206 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Rainer Orth : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D39b06c208fb7= b7edb98866252cbd05ba0918f666 commit 39b06c208fb7b7edb98866252cbd05ba0918f666 Author: Rainer Orth Date: Tue Sep 26 14:58:53 2017 +0200 Fix gdb 8.1 Solaris/SPARC compilation (PR build/22206) When testing my Solaris < 10 removal patch on Solaris/SPARC, I found that gdb mainline is currently broken there due to the recent SPARC M7 ADI patches: /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c:1876:0: error: "PSR_ICC" redefined [-Werror] #define PSR_ICC 0x00f00000 ^ In file included from /usr/include/v7/sys/privregs.h:24:0, from /usr/include/sys/regset.h:420, from /usr/include/sys/ucontext.h:21, from /usr/include/sys/signal.h:231, from /usr/include/sys/procset.h:23, from /usr/include/sys/wait.h:25, from /usr/include/stdlib.h:21, from build-gnulib/import/stdlib.h:36, from /vol/src/gnu/gdb/gdb/local/gdb/common/common-defs.h:53, from /vol/src/gnu/gdb/gdb/local/gdb/defs.h:28, from /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c:20: /usr/include/v7/sys/psr.h:35:0: note: this is the location of the previ= ous definition #define PSR_ICC 0x00F00000 /* integer condition codes */ ^ /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c:1878:0: error: "PSR_IMPL" redefined [-Werror] #define PSR_IMPL 0xf0000000 ^ In file included from /usr/include/v7/sys/privregs.h:24:0, from /usr/include/sys/regset.h:420, from /usr/include/sys/ucontext.h:21, from /usr/include/sys/signal.h:231, from /usr/include/sys/procset.h:23, from /usr/include/sys/wait.h:25, from /usr/include/stdlib.h:21, from build-gnulib/import/stdlib.h:36, from /vol/src/gnu/gdb/gdb/local/gdb/common/common-defs.h:53, from /vol/src/gnu/gdb/gdb/local/gdb/defs.h:28, from /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c:20: /usr/include/v7/sys/psr.h:41:0: note: this is the location of the previ= ous definition #define PSR_IMPL 0xF0000000 /* implementation */ ^ Comparing Solaris 11.4 and sparc64-tdep.c, there are more inconsistencies: : #define PSR_S 0x00000080 /* supervisor mode */ #define PSR_ICC 0x00F00000 /* integer condition codes = */ #define PSR_VER 0x0F000000 /* mask version */ #define PSR_IMPL 0xF0000000 /* implementation */ #define PSR_RSV 0x000FC000 /* reserved */ sparc64-tdep.c: #define PSR_S 0x00000080 #define PSR_ICC 0x00f00000 #define PSR_VERS 0x0f000000 #define PSR_IMPL 0xf0000000 #define PSR_V8PLUS 0xff000000 #define PSR_XCC 0x000f0000 Apart from the capitalization differences that trip g++, the names differ (PSR_VER vs. PSR_VERS), PSR_XCC is included in Solaris' PSR_RSV, and there's no PSR_V8PLUS on Solaris either. /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c: In function `int adi_tag_fd()': /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c:296:63: error: format `%d' expects argument of type `int', but argument 4 has type `pid_t {aka long in= t}' [-Werror=3Dformat=3D] snprintf (cl_name, sizeof(cl_name), "/proc/%d/adi/tags", pid); ^ /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c: In function `bool adi_is_addr_mapped(CORE_ADDR, std::size_t)': /vol/src/gnu/gdb/gdb/local/gdb/sparc64-tdep.c:314:64: error: format `%d' expects argument of type `int', but argument 4 has type `pid_t {aka long in= t}' [-Werror=3Dformat=3D] snprintf (filename, sizeof filename, "/proc/%d/adi/maps", pid); ^ You cannot always print a pid_t, which can be either int or long on Solaris, as an int. Obviously, the ADI patch which modifies code shared between all SPARC targets, hasn't been tested on anything but Linux/SPARC. The patch below includes the minimal fixes necessary to unbreak the Solaris/SPARC build. However, as detailed in the PR, there's more breakage here: apart from not bothering to implement ADI support on Solaris, the code contains several more changes to shared/common SPARC code that are simply wrong on anything but Linux/SPARC. The patch was tested on sparcv9-sun-solaris2.10 and sparcv9-sun-solaris2.11.4 (build and gdb/gdb gdb/gdb smoke test only). PR build/22206 * sparc64-tdep.c (adi_tag_fd): Print pid as long. (adi_is_addr_mapped): Likewise. (PSR_ICC): Don't redefine. (PSR_IMPL): Likewise. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21939-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 26 13:05:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53259 invoked by alias); 26 Sep 2017 13:05:55 -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 53229 invoked by uid 55); 26 Sep 2017 13:05:55 -0000 From: "ro at CeBiTec dot Uni-Bielefeld.DE" To: gdb-prs@sourceware.org Subject: [Bug build/22206] [8.1 regression] SPARC M7 ADI patches break Solaris build Date: Tue, 26 Sep 2017 13:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q3/txt/msg00376.txt.bz2 Content-length: 422 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22206 --- Comment #3 from Rainer Orth --- The minimal patch has been installed to unbreak the Solaris/SPARC build. I'm leaving the PR open for now to figure out how to properly deal with SPARC M7 ADI support on anything but Linux/SPARC. Rainer --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21940-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 26 13:22:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 59700 invoked by alias); 26 Sep 2017 13:22:00 -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 59661 invoked by uid 55); 26 Sep 2017 13:21:59 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22185] Obsolete/remove support for Solaris < 10 Date: Tue, 26 Sep 2017 13:56: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: ro at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q3/txt/msg00377.txt.bz2 Content-length: 3064 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22185 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Rainer Orth : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D281c44477384= 09888d9659924937da182a65b4e1 commit 281c4447738409888d9659924937da182a65b4e1 Author: Rainer Orth Date: Tue Sep 26 15:19:10 2017 +0200 Remove support for Solaris < 10 (PR gdb/22185) Given that GCC has obsoleted/removed support for Solaris 9 in GCC 4.9/5= in 2013: https://gcc.gnu.org/gcc-4.9/changes.html https://gcc.gnu.org/ml/gcc-patches/2013-05/msg00728.html and the last gdb version that can be compiled with gcc 4.9 is 7.12.1 on= ly when configured with --disable-build-with-cxx, it's time to obsolete/remove support for Solaris < 10. This patch does this, simplifying configure.nat along the way (only a single sol2 configuration with variants for i386 and sparc). Some configure checks for older Solaris versions can go, too, and the c= heck for libthread_db.so.1 removed: * Since Solaris 10, dlopen has moved to libc and libdl.so is just a filter on ld.so.1, so no need to check. * $RDYNAMIC is already handled above (and is a no-op with Solaris ld anyway). Both proc-service.c and sol-thread.c lose support for (Solaris-only) PROC_SERVICE_IS_OLD. The attached revised patch has been tested on sparcv9-sun-solaris2.10, sparcv9-sun-solaris2.11.4, amd64-pc-solaris2.10, amd64-pc-solaris2.11.4, and x86_64-pc-linux-gnu. I've also started an i386-pc-solaris2.9 build to check that it really stops as expected. PR gdb/22185 * configure.host <*-*-solaris2.[01], *-*-solaris2.[2-9]*>: Mark as obsolete. Use gdb_host sol2 for i[34567]86-*-solaris2*, x86_64-*-solaris2*. Remove i386sol2 support. * configure.nat : Remove. : Fold into ... : ... this. Move common settings to default section. Add sol-thread.o. * configure.tgt : Rename to ... : ... this. : Remove. : Remove. * configure.ac: Remove wctype in libw check. (_MSE_INT_H): Don't define on Solaris 7-9. : Remove libthread_db.so.1 check. * configure: Regenerate. * config.in: Regenerate. * proc-service.c: Remove PROC_SERVICE_IS_OLD handling. (gdb_ps_prochandle_t, gdb_ps_read_buf_t, gdb_ps_write_buf_t) (gdb_ps_size_t): Remove. Use base types in users. * sol-thread.c: Likewise, also for gdb_ps_addr_t. * NEWS (Changes since GDB 8.0): Document Solaris 2.0-9 removal. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21941-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 26 13:56:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127151 invoked by alias); 26 Sep 2017 13:56:57 -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 127067 invoked by uid 48); 26 Sep 2017 13:56:56 -0000 From: "ro at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22185] Obsolete/remove support for Solaris < 10 Date: Tue, 26 Sep 2017 19:25: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: ro at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.1 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q3/txt/msg00378.txt.bz2 Content-length: 592 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22185 Rainer Orth changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Rainer Orth --- gdb-announce, gdb FYI posted https://sourceware.org/ml/gdb/2017-09/msg00128.html Closing. Rainer --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21942-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 26 19:25:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 57776 invoked by alias); 26 Sep 2017 19:25:37 -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 57746 invoked by uid 48); 26 Sep 2017 19:25:36 -0000 From: "kevinb at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/22214] New: Cannot view all variables in scope within OpenMP parallel region Date: Tue, 26 Sep 2017 19:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kevinb at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q3/txt/msg00379.txt.bz2 Content-length: 2931 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22214 Bug ID: 22214 Summary: Cannot view all variables in scope within OpenMP parallel region Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: threads Assignee: unassigned at sourceware dot org Reporter: kevinb at redhat dot com Target Milestone: --- Created attachment 10488 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10488&action=3Ded= it Test case demonstrating problem with printing all variables in scope in Ope= nMP program When a breakpoint is placed within a parallel region within an OpenMP progr= am, GDB is unable to print variables which are in scope, but which are not referenced within the parallel region. I've attached an example which I intend to use as a test which I plan to po= st to gdb-patches. (I'm filing this bug so I have a bug id to use for tests w= hich I need to kfail.) This program can be compiled with the following command: gcc -o omp-par-scope -g -fopenmp omp-par-scope.c Debugging it in gdb and placing a breakpoint on the first printf (on line 3= 9) and running to that breakpoint reveals that variable i3 cannot be printed... (gdb) b 39 Breakpoint 1 at 0x400b20: file omp-par-scope.c, line 39. (gdb) run Starting program: omp-par-scope=20 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7ffff73d6700 (LWP 8483)] Breakpoint 1, single_scope._omp_fn.0 () at omp-par-scope.c:39 39 printf ("single_scope: thread_num=3D%d, s1=3D%d, i1=3D%d, s2=3D= %d, i2=3D%d\n", (gdb) print i3 No symbol "i3" in current context. This is what it looks like when it works correctly: (gdb) b 39 Breakpoint 1 at 0x400a6a: file omp-par-scope.c, line 39. (gdb) run Starting program: /mesquite2/sourceware-git/binutils-gdb/gdb/testsuite/gdb.threads/omp-par-sc= ope=20 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7ffff73cb700 (LWP 8504)] [Switching to Thread 0x7ffff73cb700 (LWP 8504)] Thread 2 "omp-par-scope" hit Breakpoint 1, single_scope._omp_fn.0 () at omp-par-scope.c:39 39 printf ("single_scope: thread_num=3D%d, s1=3D%d, i1=3D%d, s2=3D= %d, i2=3D%d\n", (gdb) print i3 $1 =3D 13 Moreover, continuing to the breakpoint again in the second/other thread sho= uld also correctly print i3: (gdb) c Continuing. single_scope: thread_num=3D1, s1=3D-41, i1=3D11, s2=3D202, i2=3D212 [Switching to Thread 0x7ffff7fd9780 (LWP 8500)] Thread 1 "omp-par-scope" hit Breakpoint 1, single_scope._omp_fn.0 () at omp-par-scope.c:39 39 printf ("single_scope: thread_num=3D%d, s1=3D%d, i1=3D%d, s2=3D= %d, i2=3D%d\n", (gdb) print i3 $2 =3D 13 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21943-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 26 19:26:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 58454 invoked by alias); 26 Sep 2017 19:26:05 -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 58429 invoked by uid 48); 26 Sep 2017 19:26:04 -0000 From: "kevinb at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/22214] Cannot view all variables in scope within OpenMP parallel region Date: Tue, 26 Sep 2017 23:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kevinb at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: kevinb at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: 2017-q3/txt/msg00380.txt.bz2 Content-length: 404 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22214 Kevin Buettner changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |kevinb at redhat do= t com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21944-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Sep 26 23:05:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31926 invoked by alias); 26 Sep 2017 23:05:37 -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 31899 invoked by uid 48); 26 Sep 2017 23:05:37 -0000 From: "chrisfriedt at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20981] Dynamic library debugging on MacOS X 10.12 (Sierra) and dyld 15 is broken Date: Wed, 27 Sep 2017 00:00: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: chrisfriedt at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q3/txt/msg00381.txt.bz2 Content-length: 521 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20981 Chris Friedt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chrisfriedt at gmail dot c= om --- Comment #4 from Chris Friedt --- I'm also encountering this on 10.12.6 ... sigh.. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21946-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 27 04:40:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 28840 invoked by alias); 27 Sep 2017 04:40:12 -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 28817 invoked by uid 48); 27 Sep 2017 04:40:11 -0000 From: "grassfedcode at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/22217] New: gdb mi command -thread-list-ids Date: Wed, 27 Sep 2017 04:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: grassfedcode at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00383.txt.bz2 Content-length: 1018 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22217 Bug ID: 22217 Summary: gdb mi command -thread-list-ids Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: mi Assignee: unassigned at sourceware dot org Reporter: grassfedcode at gmail dot com Target Milestone: --- Example output of "-thread-list-ids" is as follows: ^done,thread-ids=3D{thread-id=3D"1",thread-id=3D"2"},current-thread-id=3D"2= ",number-of-threads=3D"2" The problem with this output is that the key "thread-id" is used multiple times. In all other cases, this type of output corresponds to an associative array (Python dictionary, JavaScript object, etc.) with unique keys. In this case, the keys are not distinct. The output *should* be: ^done,thread-ids=3D["1","2"},current-thread-id=3D"2",number-of-threads=3D"2" --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21945-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 27 00:00:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 38981 invoked by alias); 27 Sep 2017 00:00:33 -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 36593 invoked by uid 48); 27 Sep 2017 00:00:31 -0000 From: "alexander.v.shaposhnikov at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22215] New: Triggered assert at dwarf2read.c:10986 elf_section_nr < dwp_file->num_sections Date: Wed, 27 Sep 2017 04:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: alexander.v.shaposhnikov at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00382.txt.bz2 Content-length: 2950 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22215 Bug ID: 22215 Summary: Triggered assert at dwarf2read.c:10986 elf_section_nr < dwp_file->num_sections Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: alexander.v.shaposhnikov at gmail dot com Target Milestone: --- This assert triggers if the section .strtab is the first one=20 (probably, more generally (but i didn't verify that), the same issue can co= me up if .strtab is not the last section. Example:=20 main.cpp: struct Foo { int bar; }; int main() { Foo foo; foo.bar =3D 1; int x =3D foo.bar + 1; return x; } build commands: g++ -fPIC -gsplit-dwarf -g -O0 main.cpp -o main.exe llvm-dwp main.dwo -o main.exe.dwp llvm-dwp (built from LLVM upstream, or, alternatively,=20 5.0 version should work as well)=20 places .strtab section at the beginning of the binary: Section Headers: [Nr] Name Type Address Offset Size EntSize Flags Link Info Align [ 0] NULL 0000000000000000 00000000 0000000000000000 0000000000000000 0 0 0 [ 1] .strtab STRTAB 0000000000000000 000002a0 0000000000000053 0000000000000000 0 0 1 Next one needs to build GDB from the upstream + make sure the patch=20 https://sourceware.org/ml/gdb-patches/2017-09/msg00814.html is included (it fixes a separate issue, otherwise gdb will segfault much earlier). run gdb: gdb and see (gdb) file main.exe Reading symbols from main.exe...dwarf2read.c:10986: internal-error: void dwarf2_locate_common_dwp_sections(bfd*, asection*, void*): Assertion `elf_section_nr < dwp_file->num_sections' failed. A problem internal to GDB has been detected, Some remarks:=20 1. To workaround this issue one can use the following trick:=20 objcopy --remove-section .strtab main.exe.dwp objcopy will remove ".strtab" section but will create a new section ".shstr= tab" and will put it at the end. GDB works fine with the newly created .dwp. 2. It looks like that the value of dwp_file->num_sections is not correct. I didn't dig deep into this issue, b= ut one potential scenario might look as follows (i'm not sure, it's just a gue= ss, might be completely wrong):=20 in the file elf.c, inside the function=20 bfd_section_from_shdr (bfd *abfd, unsigned int shindex), at the line 2242, case SHT_STRTAB:=20 for the section .strtab the function _bfd_elf_make_section_from_shdr is = not called=20 =3D> the function bfd_section_init is not called =3D> abfd->section_coun= t is not incremented. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21947-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 27 04:40:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 29162 invoked by alias); 27 Sep 2017 04:40:35 -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 29141 invoked by uid 48); 27 Sep 2017 04:40:35 -0000 From: "grassfedcode at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/22217] gdb mi command -thread-list-ids produces duplicate keys Date: Wed, 27 Sep 2017 16:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: grassfedcode at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: short_desc 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: 2017-q3/txt/msg00384.txt.bz2 Content-length: 512 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22217 grassfedcode at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|gdb mi command |gdb mi command |-thread-list-ids |-thread-list-ids produces | |duplicate keys --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21948-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 27 16:02:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 14298 invoked by alias); 27 Sep 2017 16:02:07 -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 14276 invoked by uid 48); 27 Sep 2017 16:02:07 -0000 From: "vivi00791 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/22223] New: python event.new_thread does not exist but described in online document Date: Wed, 27 Sep 2017 20:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vivi00791 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00385.txt.bz2 Content-length: 1162 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22223 Bug ID: 22223 Summary: python event.new_thread does not exist but described in online document Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: vivi00791 at gmail dot com Target Milestone: --- gdb-mi output: &"source ./Command/new_thread_trigger.py\n" &"Traceback (most recent call last):\n" &" File \"./Command/new_thread_trigger.py\", line 9, in \n" &" gdb.events.new_thread.connect (new_thread_handler)\n" &"AttributeError: 'module' object has no attribute 'new_thread'\n" source file(new_thread_trigger.py): import gdb def new_thread_handler (event): print("NEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEW Thread!!!!!") gdb.events.new_thread.connect (new_thread_handler) event document: https://sourceware.org/gdb/current/onlinedocs/gdb/Events-In-Python.html#Eve= nts-In-Python --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21949-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 27 20:13:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 14235 invoked by alias); 27 Sep 2017 20:13:20 -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 13798 invoked by uid 48); 27 Sep 2017 20:13:20 -0000 From: "vomlehn at texas dot net" To: gdb-prs@sourceware.org Subject: [Bug gdb/22224] New: Documentation for add-symbol-file could be clarified Date: Wed, 27 Sep 2017 23:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vomlehn at texas dot net X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00386.txt.bz2 Content-length: 907 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22224 Bug ID: 22224 Summary: Documentation for add-symbol-file could be clarified Product: gdb Version: 7.12 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: vomlehn at texas dot net Target Milestone: --- I ran into a piece of code whose .text section began at a higher address th= an another section. The documentation for add-symbol-file implies that the add= ress is that of the file, but it appears as though this is incorrect. When I sup= ply the virtual address of the start of the .text section, things work correctl= y. If my deduction is correct, a clarification of this would be helpful. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21950-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Sep 27 23:09:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 70631 invoked by alias); 27 Sep 2017 23:09:21 -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 70606 invoked by uid 48); 27 Sep 2017 23:09:20 -0000 From: "weimin.pan at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18071] TLS variables can't be resolved on aarch64-linux-gnu Date: Thu, 28 Sep 2017 21:12: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: weimin.pan at oracle dot com 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: cc 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: 2017-q3/txt/msg00387.txt.bz2 Content-length: 623 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18071 weimin.pan at oracle dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |weimin.pan at oracle dot c= om --- Comment #1 from weimin.pan at oracle dot com --- These problems can still be reproduced with upstream gcc/gdb and can be addressed first by having the compiler emit dwarf attribute DW_AT_location for these thread-local variables. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21951-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Sep 28 21:12:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 76068 invoked by alias); 28 Sep 2017 21:12:11 -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 75872 invoked by uid 48); 28 Sep 2017 21:12:10 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Fri, 29 Sep 2017 17:36: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: version 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: 2017-q3/txt/msg00388.txt.bz2 Content-length: 906 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 Adam Stylinski changed: What |Removed |Added ---------------------------------------------------------------------------- Version|7.12.1 |8.0 --- Comment #12 from Adam Stylinski --- (In reply to Keith Seitz from comment #11) > (In reply to Adam Stylinski from comment #10) > > So it's been about 3 months, any luck reproducing this? >=20 > I'm very sorry, I've not been able to work on this for some time, but I do > have plans to investigate this further soon. I just wanted to drop you a > note letting you know that I haven't (completely) forgotten about you/your > problem. Any luck reproducing this? I still see it on gdb 8.0. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21952-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 29 17:36:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 128124 invoked by alias); 29 Sep 2017 17:36:53 -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 128094 invoked by uid 48); 29 Sep 2017 17:36:52 -0000 From: "sillyduckyang at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/22228] New: Arguments shift when print/call (sometimes causing gdb crash) Date: Fri, 29 Sep 2017 17:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sillyduckyang at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q3/txt/msg00389.txt.bz2 Content-length: 3255 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22228 Bug ID: 22228 Summary: Arguments shift when print/call (sometimes causing gdb crash) Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: sillyduckyang at gmail dot com Target Milestone: --- Description: ------------ If a function is returning a inheritance class object, the print/call of that function will have an argument shift. Testcase: --------- #include using namespace std; class Dad { public: Dad(int i): _value(i) {} private: int _value ; }; class Son : public Dad { public: Son() : Dad(777) {} }; class B{ public: Son f(int a, int b, B* c){ cout << this << " " << a << " " << b << " " << c << endl; cout << (this =3D=3D c) << endl; return Son(); } }; int main(){ B* p =3D new B(); p->f(1,2,p); return 0; } How to reproduce: ----------------- Compile the above mentioned testcase=20 (gdb) b main Breakpoint 1 at 0x4009ee: file test.cpp, line 27. (gdb) r Starting program: /home/SillyDuck/bad=20 Breakpoint 1, main () at test.cpp:27 27 B* p =3D new B(); (gdb) n 28 p->f(1,2,p); (gdb) p p->f(1,2,p) 0x7fffffffda00 6376480 1 0x2 0 $1 =3D { =3D {_value =3D 0}, } Environment: ------------ GNU gdb (GDB) 8.0.1 gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)=20 Also appears in the gcc 4.8.3 with gdb 7.12 in CentOS 6.6 (In fact it appears in most linux system) Discussion: ----------- After tracing the src, I think the root problem may be in the gnu-v3-api.c --> gnuv3_pass_by_reference the assembly of test.cpp did not has a pointer passed as the first argument= for the return value. But gdb is somehow inconsist with gcc's behavior... If the function is calling some other function with incorrect "this" pointe= r, it sometimes also crashes the gdb... 00000000004009e6
: 4009e6: 55 push %rbp 4009e7: 48 89 e5 mov %rsp,%rbp 4009ea: 48 83 ec 10 sub $0x10,%rsp 4009ee: bf 01 00 00 00 mov $0x1,%edi 4009f3: e8 d8 fe ff ff callq 4008d0 <_Znwm@plt> 4009f8: 48 89 45 f8 mov %rax,-0x8(%rbp) 4009fc: 48 8b 55 f8 mov -0x8(%rbp),%rdx 400a00: 48 8b 45 f8 mov -0x8(%rbp),%rax 400a04: 48 89 d1 mov %rdx,%rcx 400a07: ba 02 00 00 00 mov $0x2,%edx 400a0c: be 01 00 00 00 mov $0x1,%esi 400a11: 48 89 c7 mov %rax,%rdi 400a14: e8 cf 00 00 00 callq 400ae8 <_ZN1B1fEiiPS_> 400a19: b8 00 00 00 00 mov $0x0,%eax 400a1e: c9 leaveq=20 400a1f: c3 retq=20=20=20 Interesting thing is that if we add a copy constructor in Dad, this problem= is gone... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21953-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 29 17:40:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 16763 invoked by alias); 29 Sep 2017 17:40: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 16738 invoked by uid 48); 29 Sep 2017 17:40:52 -0000 From: "sillyduckyang at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/22228] Arguments shift when print/call (sometimes causing gdb crash) Date: Fri, 29 Sep 2017 19:01: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: sillyduckyang at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc bug_severity 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: 2017-q3/txt/msg00390.txt.bz2 Content-length: 450 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22228 sillyduckyang at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sillyduckyang at gmail dot= com Severity|normal |critical --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21954-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 29 19:01:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 19561 invoked by alias); 29 Sep 2017 19:01:21 -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 19535 invoked by uid 48); 29 Sep 2017 19:01:21 -0000 From: "sillyduckyang at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/22228] Arguments shift when print/call (sometimes causing gdb crash) Date: Sat, 30 Sep 2017 17:37: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: sillyduckyang at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q3/txt/msg00391.txt.bz2 Content-length: 320 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22228 --- Comment #1 from sillyduckyang at gmail dot com --- Created attachment 10492 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10492&action=3Ded= it Arg shift illustration --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21956-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 02 11:16:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 112426 invoked by alias); 2 Oct 2017 11:16:11 -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 112404 invoked by uid 48); 2 Oct 2017 11:16:11 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug cli/22234] New: complaints don't end with newlines Date: Mon, 02 Oct 2017 11:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00000.txt.bz2 Content-length: 1920 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22234 Bug ID: 22234 Summary: complaints don't end with newlines Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: cli Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- I did "set complaints 1" and ran gdb on an executable that has some DWARF issues (see https://github.com/rust-lang/rust/issues/44412). I got output like this: (gdb) file -readnow libxul.so.dbg=20 Reading symbols from libxul.so.dbg...expanding to full symbols...unsupported tag: 'DW_TAG_unspecified_type'...const value length mismatch for 'nsISupports::COMTypeInfo::kIID', got 16, expected 0...C= hild DIE 0x9a0d and its abstract origin 0x9e60 have different parents...cannot g= et low and high bounds for subprogram DIE at 42795....debug_line address at of= fset 0x19c6 is 0 [in module /tmp/libxul.so.dbg]...Member function "~MetaData" (offset 74544) is virtual but the vtable offset is not specified...DW_AT_call_target target DIE has invalid low pc, for referencing DIE 0x1d356 [in module /tmp/libxul.so.dbg]...Multiple children of DIE 0xa8f= 7c refer to DIE 0xa2549 as their abstract origin...location expression too complex...No DW_FORM_block* DW_AT_call_value for DW_TAG_call_site child DIE 0x10ea38 [in module /tmp/libxul.so.dbg]...missing name for subprogram DIE at 9803491...Only single DW_OP_reg or DW_OP_fbreg is supported for DW_FORM_blo= ck* DW_AT_location is supported for DW_TAG_call_site child DIE 0xf8c6ae [in mod= ule /tmp/libxul.so.dbg]...Duplicate PC 0xf1202e for DW_TAG_call_site DIE 0x5d0a= d32 [in module /tmp/libxul.so.dbg]...^CQuit This would be a lot more readable with newlines. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21957-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 02 16:50:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 84873 invoked by alias); 2 Oct 2017 16:50:10 -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 84399 invoked by uid 48); 2 Oct 2017 16:50:10 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/22236] New: string slices print too much Date: Mon, 02 Oct 2017 16:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00001.txt.bz2 Content-length: 787 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22236 Bug ID: 22236 Summary: string slices print too much Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- Consider this program: fn main() { let c =3D "a/b"; let d =3D &c[..1]; println!("done"); } Set a breakpoint on the println and run. Then print "d": (gdb) p d $2 =3D &str { data_ptr: 0x100044280 "a/b\000", length: 1 } Since length is 1 I would expect this to just print "a". --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21958-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 02 17:57:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3257 invoked by alias); 2 Oct 2017 17:57:48 -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 2793 invoked by uid 48); 2 Oct 2017 17:57:48 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/22236] string slices print too much Date: Mon, 02 Oct 2017 17:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: 2017-q4/txt/msg00002.txt.bz2 Content-length: 408 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22236 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |tromey at sourcewar= e dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21959-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 02 18:02:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20252 invoked by alias); 2 Oct 2017 18:02:38 -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 20225 invoked by uid 48); 2 Oct 2017 18:02:38 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/20164] fix string printing in rust Date: Mon, 02 Oct 2017 18:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q4/txt/msg00003.txt.bz2 Content-length: 251 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20164 --- Comment #1 from Tom Tromey --- Special-casing &str is being done in bug 22236. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21960-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 02 20:13:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 13428 invoked by alias); 2 Oct 2017 20:13:42 -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 13318 invoked by uid 48); 2 Oct 2017 20:13:41 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/22236] string slices print too much Date: Mon, 02 Oct 2017 20:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-q4/txt/msg00004.txt.bz2 Content-length: 561 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22236 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |8.1 --- Comment #1 from Tom Tromey --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21961-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 02 20:13:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 13732 invoked by alias); 2 Oct 2017 20:13:43 -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 13634 invoked by uid 55); 2 Oct 2017 20:13:42 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug rust/22236] string slices print too much Date: Mon, 02 Oct 2017 20:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00005.txt.bz2 Content-length: 1296 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22236 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D45320ffa0450= b27e232d933d2a1c6a09d94ac18b commit 45320ffa0450b27e232d933d2a1c6a09d94ac18b Author: Tom Tromey Date: Mon Oct 2 13:55:42 2017 -0600 Fix &str printing in Rust Printing a string slice ("&str") in Rust would print until the terminating \0; but that is incorrect because a slice has a length. This fixes &str printing, and arranges to preserve the type name when slicing a slice, so that printing a slice of an "&str" works as well. This is PR rust/22236. 2017-10-02 Tom Tromey PR rust/22236: * rust-lang.c (rust_val_print_str): New function. (val_print_struct): Call it. (rust_subscript): Preserve name of slice type. 2017-10-02 Tom Tromey PR rust/22236: * gdb.rust/simple.rs (main): New variable "fslice". * gdb.rust/simple.exp: Add slice tests. Update string tests. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21962-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 03 13:14:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23906 invoked by alias); 3 Oct 2017 13:14:15 -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 23881 invoked by uid 48); 3 Oct 2017 13:14:14 -0000 From: "nolange79 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/22242] New: recursive display of variable information Date: Tue, 03 Oct 2017 13:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: nolange79 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q4/txt/msg00006.txt.bz2 Content-length: 1094 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22242 Bug ID: 22242 Summary: recursive display of variable information Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: nolange79 at gmail dot com Target Milestone: --- Created attachment 10502 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10502&action=3Ded= it Code for demonstrating the "infinite print" Seems like the heuristics to prevent recursing into static members ain't working with more complex code. This is rather annoying cause it kills the debugger session in eclipse. To reproduce the issue: 1) Compile the attached source with g++: g++ -O0 -g3 recursivegdb.cpp 2) Debug the output: gdb a.out 3) Set breakpoint at main and run b main run 4) display variable v p v 5) Try some minutes to reach the end of it... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21963-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 04 16:19:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 47853 invoked by alias); 4 Oct 2017 16:19:34 -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 47524 invoked by uid 48); 4 Oct 2017 16:19:34 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/22251] New: &str type should be built in Date: Wed, 04 Oct 2017 16:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00007.txt.bz2 Content-length: 728 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22251 Bug ID: 22251 Summary: &str type should be built in Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- pokyo. gdb -nx -quiet (gdb) set lang rust (gdb) ptype &str No symbol 'str' in current context &str is a built-in type, gdb should probably know about it. This happens when debugging a rust program as well, where &str is in the debuginfo. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21964-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 04 17:16:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 108587 invoked by alias); 4 Oct 2017 17:16:03 -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 108546 invoked by uid 48); 4 Oct 2017 17:16:02 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/22251] &str type should be built in Date: Wed, 04 Oct 2017 17:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q4/txt/msg00008.txt.bz2 Content-length: 490 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22251 --- Comment #1 from Tom Tromey --- This may also fall into the problem where ptype isn't trying to parse as a type. I notice that "ptype &[u8]" doesn't work either. This probably requires some core change so the parser can know if it should try a type parse (since I don't want to introduce ambiguities into the grammar) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21965-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 04 20:58:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 83586 invoked by alias); 4 Oct 2017 20:58:13 -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 83555 invoked by uid 48); 4 Oct 2017 20:58:13 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/22254] New: rust needs value_print as well Date: Wed, 04 Oct 2017 20:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00009.txt.bz2 Content-length: 1176 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22254 Bug ID: 22254 Summary: rust needs value_print as well Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- Printing a Path ("*a" in this example): use std::path::Path; use std::ffi::OsString; fn main() { let a =3D Path::new("a/b"); let b =3D a.parent().unwrap(); let bs =3D b.as_os_str(); let c =3D b"a/b"; let d =3D &c[..1]; let e =3D OsString::from("a/b"); let f =3D &e[..]; let zzzzz =3D 3; println!("done {}", b.display()); } will show $23 =3D (std::path::Path ?) std::path::Path { inner: std::ffi::os_str::OsStr { inner: std::sys::imp::os_str::Slice { inner: 0x555555599800 } } } The type is printed twice here - once with the "?" from c_value_print. Rust should implement the value_print hook as well to avoid this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21966-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Oct 05 01:39:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 95155 invoked by alias); 5 Oct 2017 01:39:25 -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 94811 invoked by uid 48); 5 Oct 2017 01:39:25 -0000 From: "weimin.pan at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/18144] [aarch64] the skip prologue functionality doesn't work well for same assembly functions Date: Thu, 05 Oct 2017 01:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: weimin.pan at oracle dot com 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: cc 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: 2017-q4/txt/msg00010.txt.bz2 Content-length: 721 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18144 weimin.pan at oracle dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |weimin.pan at oracle dot c= om --- Comment #2 from weimin.pan at oracle dot com --- It works fine now with current git master: (gdb) disass _start Dump of assembler code for function _start: 0x0000000000400244 <+0>: nop 0x0000000000400248 <+4>: nop 0x000000000040024c <+8>: ret End of assembler dump. (gdb) b _start Breakpoint 1 at 0x400244 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21967-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Oct 05 14:24:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88389 invoked by alias); 5 Oct 2017 14:24:45 -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 88305 invoked by uid 48); 5 Oct 2017 14:24:39 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/18144] [aarch64] the skip prologue functionality doesn't work well for same assembly functions Date: Thu, 05 Oct 2017 14:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: palves at redhat dot com 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: cc 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: 2017-q4/txt/msg00011.txt.bz2 Content-length: 703 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18144 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #3 from Pedro Alves --- GDB stopped skipping the prologue of asm sources with: commit 6e22494e5076e4d3c0b2c2785883162f83db499e Author: Jan Kratochvil AuthorDate: Fri Jun 26 15:11:14 2015 +0200 Do not skip prologue for asm (.S) files --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21968-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 06 09:52:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36549 invoked by alias); 6 Oct 2017 09:52:58 -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 36446 invoked by uid 55); 6 Oct 2017 09:52:57 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug compile/22188] gdb/arm-tdep.c:6449: (rn & 0xe) == 0x1 - tautology Date: Fri, 06 Oct 2017 09:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: compile X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00012.txt.bz2 Content-length: 805 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22188 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Jose E. Marchesi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D2f924de654ff= 8f719faf60b84948397809baaac6 commit 2f924de654ff8f719faf60b84948397809baaac6 Author: Jose E. Marchesi Date: Fri Oct 6 11:49:39 2017 +0200 gdb: Fix decoding of ARM neon memory hint insns. gdb/ChangeLog: 2017-10-05 Jose E. Marchesi PR build/22188 * arm-tdep.c (arm_decode_misc_memhint_neon): Fix decoding of CPS and SETEND. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21969-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 06 10:12:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109567 invoked by alias); 6 Oct 2017 10:12:00 -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 108862 invoked by uid 48); 6 Oct 2017 10:12:00 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug build/22188] gdb/arm-tdep.c:6449: (rn & 0xe) == 0x1 - tautology Date: Fri, 06 Oct 2017 10:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: bug_status cf_reconfirmed_on cc component everconfirmed 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: 2017-q4/txt/msg00013.txt.bz2 Content-length: 691 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22188 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-10-06 CC| |qiyao at gcc dot gnu.org Component|compile |build Ever confirmed|0 |1 --- Comment #2 from Yao Qi --- One build error is fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21971-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 06 14:15:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 46084 invoked by alias); 6 Oct 2017 14:15:41 -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 46061 invoked by uid 48); 6 Oct 2017 14:15:41 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20623] tab-completion doesn't work too well with "(anonymous namespace)" Date: Fri, 06 Oct 2017 14:15: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: 2017-q4/txt/msg00015.txt.bz2 Content-length: 401 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20623 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |palves at redhat do= t com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21970-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 06 14:15:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 45483 invoked by alias); 6 Oct 2017 14:15:24 -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 45386 invoked by uid 48); 6 Oct 2017 14:15:18 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20623] tab-completion doesn't work too well with "(anonymous namespace)" Date: Fri, 06 Oct 2017 14:15: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00014.txt.bz2 Content-length: 545 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20623 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #2 from Pedro Alves --- This series should fix it: https://sourceware.org/ml/gdb-patches/2017-06/msg00012.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21972-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 09 12:04:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 93983 invoked by alias); 9 Oct 2017 12:04:44 -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 93563 invoked by uid 48); 9 Oct 2017 12:04:44 -0000 From: "night_ghost at ykoctpa dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/22271] New: GDB fails on "assertion failed" Date: Mon, 09 Oct 2017 12:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: night_ghost at ykoctpa dot ru X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00016.txt.bz2 Content-length: 722 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22271 Bug ID: 22271 Summary: GDB fails on "assertion failed" Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: night_ghost at ykoctpa dot ru Target Milestone: --- /home/build/work/GCC-5-0-build/src/gdb/gdb/inline-frame.c:167: internal-err= or: inline_frame_this_id: Assertion `frame_id_p (*this_id)' failed. gdb version which comes with gcc-arm-none-eabi-5_4-2016q2 ELF can be sent --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21973-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 09 14:04:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 98952 invoked by alias); 9 Oct 2017 14:04: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 98926 invoked by uid 48); 9 Oct 2017 14:04:23 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22271] GDB fails on "assertion failed" Date: Mon, 09 Oct 2017 14:04: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00017.txt.bz2 Content-length: 827 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22271 --- Comment #1 from Pedro Alves --- Hi! Sorry for the error... > gdb version which comes with gcc-arm-none-eabi-5_4-2016q2 I don't think it's reasonable to expect that we know what version that is. > ELF can be sent That'd be better, because from the info you've provided alone it's impossib= le to debug this. Though, I suspect that it still wouldn't be sufficient. To trigger that assertion, it must be that you run some commands in some seque= nce that triggers the bug, and some of those commands must have been execution commands (run, continue, step, etc.), and we have no idea which those were.= =20 Best would be a small self-contained reproducer. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21974-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 09 16:52:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 30996 invoked by alias); 9 Oct 2017 16:52:59 -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 30624 invoked by uid 55); 9 Oct 2017 16:52:59 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug guile/21104] 7.12.1 does not compile with latest guile (2.1.6) Date: Mon, 09 Oct 2017 16:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: guile X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00018.txt.bz2 Content-length: 1029 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21104 --- Comment #7 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Simon Marchi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D6e66f7538112= d2f5fb1af17dbde33ba37a7171be commit 6e66f7538112d2f5fb1af17dbde33ba37a7171be Author: Simon Marchi Date: Mon Oct 9 12:50:58 2017 -0400 Don't try building gdb against guile-2.2 GDB currently doesn't build with Guile 2.2 (see PR 21104). If one has both Guile 2.2 and 2.0 installed, GDB will pick up Guile 2.2 first and fail building. Until somebody does the work of adapting the GDB code to Guile 2.2, we should not try using it. This patch therefore removes it from configure. gdb/ChangeLog: * configure.ac (try_guile_versions): Remove guile-2.2. * configure: Regenerate. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21975-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 10 03:35:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 12433 invoked by alias); 10 Oct 2017 03:35:16 -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 12410 invoked by uid 48); 10 Oct 2017 03:35:16 -0000 From: "sbansal at ciena dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22275] New: Configuration powerpc-wrs-vxworks is obsolete. Date: Tue, 10 Oct 2017 03:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sbansal at ciena dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00019.txt.bz2 Content-length: 1374 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22275 Bug ID: 22275 Summary: Configuration powerpc-wrs-vxworks is obsolete. Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: sbansal at ciena dot com Target Milestone: --- I am trying to build gdb 8.0 version on my host machine x86 having compiler version 4.8.5 and make 3.82 version. Configuration used : =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D ../gdb-8.0/configure --target=3Dpowerpc-vxworks Getting below error while compiling : checking whether NLS is requested... yes checking for catalogs to be installed...=20 checking whether makeinfo --split-size=3D5000000 supports @click... yes checking for default auto-load directory... $debugdir:$datadir/auto-load checking for default auto-load safe-path... $debugdir:$datadir/auto-load *** Configuration powerpc-wrs-vxworks is obsolete. *** Support has been REMOVED. make[1]: *** [configure-gdb] Error 1 make[1]: Leaving directory `/home/sbansal/vik/gdb/build-gdb' make: *** [all] Error 2 Please let me know if other information is required. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21976-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 10 06:02:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 28645 invoked by alias); 10 Oct 2017 06:02:33 -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 28622 invoked by uid 48); 10 Oct 2017 06:02:33 -0000 From: "night_ghost at ykoctpa dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/22271] GDB fails on "assertion failed" Date: Tue, 10 Oct 2017 06:02: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: night_ghost at ykoctpa dot ru X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q4/txt/msg00020.txt.bz2 Content-length: 313 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22271 --- Comment #2 from night_ghost at ykoctpa dot ru --- Created attachment 10520 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10520&action=3Ded= it ELF for testcase --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21977-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 10 06:07:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 19084 invoked by alias); 10 Oct 2017 06:07:25 -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 19059 invoked by uid 48); 10 Oct 2017 06:07:24 -0000 From: "night_ghost at ykoctpa dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/22271] GDB fails on "assertion failed" Date: Tue, 10 Oct 2017 06:07: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: night_ghost at ykoctpa dot ru X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00021.txt.bz2 Content-length: 411 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22271 --- Comment #3 from night_ghost at ykoctpa dot ru --- sources https://github.com/night-ghost/ardupilot #/arm-none-eabi-gdb --version GNU gdb (GNU Tools for ARM Embedded Processors) 7.10.1.20160616-cvs stop at breakpoint in REVOMINIScheduler::do_task() causes this error --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21978-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 10 11:16:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 17337 invoked by alias); 10 Oct 2017 11:16:17 -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 17313 invoked by uid 48); 10 Oct 2017 11:16:16 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22275] Configuration powerpc-wrs-vxworks is obsolete. Date: Tue, 10 Oct 2017 11:16: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00022.txt.bz2 Content-length: 605 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22275 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- > Please let me know if other information is required. Yes. What is the actual bug you're reporting? VxWorks support was removed from GDB in 2004. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21979-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 10 11:20:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20759 invoked by alias); 10 Oct 2017 11:20:11 -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 20731 invoked by uid 48); 10 Oct 2017 11:20:10 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22271] GDB fails on "assertion failed" Date: Tue, 10 Oct 2017 11:20: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00023.txt.bz2 Content-length: 829 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22271 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #4 from Pedro Alves --- (In reply to night_ghost from comment #3) > #/arm-none-eabi-gdb --version > GNU gdb (GNU Tools for ARM Embedded Processors) 7.10.1.20160616-cvs This is not an upstream GDB version, and it's getting a bit old -- did you report the bug to whom you got toolchain from? Could you try with a more up to date pristine/upstream GDB? It's possible that the bug is already fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21980-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 10 17:46:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 57826 invoked by alias); 10 Oct 2017 17:46:14 -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 57625 invoked by uid 48); 10 Oct 2017 17:46:14 -0000 From: "b.r.longbons at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug server/22279] New: gdbserver 100% CPU usage after gdb quit Date: Tue, 10 Oct 2017 17:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b.r.longbons at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00024.txt.bz2 Content-length: 791 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22279 Bug ID: 22279 Summary: gdbserver 100% CPU usage after gdb quit Product: gdb Version: 7.12 Status: UNCONFIRMED Severity: normal Priority: P2 Component: server Assignee: unassigned at sourceware dot org Reporter: b.r.longbons at gmail dot com Target Milestone: --- Currently tested with 7.12, but it has been around for a while and I don't think anyone has done anything since 7.12. #!/usr/bin/gdb -x set sysroot / target extended-remote | gdbserver --multi stdio quit At this point, the spawned gdbserver will have 100% CPU usage indefinitely. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21981-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 10 18:16:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66349 invoked by alias); 10 Oct 2017 18:16:02 -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 66316 invoked by uid 48); 10 Oct 2017 18:16:00 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug server/22279] gdbserver 100% CPU usage after gdb quit Date: Tue, 10 Oct 2017 18:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00025.txt.bz2 Content-length: 1542 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22279 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- gdb seemingly hangs because it just closes the pipe and then waits for the child (gdbserver in this case) to exit gracefully in reaction to stdin closing.=20 However, gdbserver doesn't normally exit when GDB disconnects. Instead it = goes back to waiting for another connection. That doesn't seem to make sense when connected with STDIO though. If gdbserver's stdin pipe is closed, then you won't be able to reconnect anywa= y. The workaround is to start gdbserver with "--once". I.e., (gdb) target extended-remote | gdbserver --once --multi stdio "--once" makes gdbserver exit when gdb disconnects instead of waiting for another connection, which is exactly what we want here. gdbserver already special-cases a few things when connected in STDIO mode. I think it'd make sense to make STDIO imply --once too. That's probably ea= sy.=20 As usual for smaller user-visible changes, documentation changes and especi= ally testcase will probably be more work than the gdbserver patch itself. (GDB doesn't stay around for me indefinitely, there's a timeout after a few seconds.) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21987-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:44:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36156 invoked by alias); 11 Oct 2017 10:44:22 -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 35848 invoked by uid 48); 11 Oct 2017 10:44:21 -0000 From: "mark at klomp dot org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/11608] gcore does not support build-id Date: Wed, 11 Oct 2017 10:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at klomp dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00031.txt.bz2 Content-length: 388 https://sourceware.org/bugzilla/show_bug.cgi?id=3D11608 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mark at klomp dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21989-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:44:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36828 invoked by alias); 11 Oct 2017 10:44:26 -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 36532 invoked by uid 48); 11 Oct 2017 10:44:23 -0000 From: "mark at klomp dot org" To: gdb-prs@sourceware.org Subject: [Bug symtab/13627] multiple .debug_types per objfile are not supported Date: Wed, 11 Oct 2017 10:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at klomp dot org 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: cc 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: 2017-q4/txt/msg00033.txt.bz2 Content-length: 388 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13627 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mark at klomp dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21985-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:44:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 34596 invoked by alias); 11 Oct 2017 10:44:15 -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 34559 invoked by uid 48); 11 Oct 2017 10:44:14 -0000 From: "mark at klomp dot org" To: gdb-prs@sourceware.org Subject: [Bug backtrace/11586] RFE: .eh_frame_hdr support (=speed-up) Date: Wed, 11 Oct 2017 10:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: mark at klomp dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00029.txt.bz2 Content-length: 388 https://sourceware.org/bugzilla/show_bug.cgi?id=3D11586 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mark at klomp dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21984-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:44:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 33997 invoked by alias); 11 Oct 2017 10:44:11 -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 33962 invoked by uid 48); 11 Oct 2017 10:44:11 -0000 From: "mark at klomp dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/13498] save-index makes gdb slow with dwarf4 Date: Wed, 11 Oct 2017 10:44: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: mark at klomp dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: dje at google dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00028.txt.bz2 Content-length: 388 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13498 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mark at klomp dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21982-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:44:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 33491 invoked by alias); 11 Oct 2017 10:44:08 -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 33420 invoked by uid 48); 11 Oct 2017 10:44:08 -0000 From: "mark at klomp dot org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/11579] RFE: backtrace core without any symfile_objfile Date: Wed, 11 Oct 2017 10:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: mark at klomp dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00026.txt.bz2 Content-length: 388 https://sourceware.org/bugzilla/show_bug.cgi?id=3D11579 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mark at klomp dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21986-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:44:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35301 invoked by alias); 11 Oct 2017 10:44:18 -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 35019 invoked by uid 48); 11 Oct 2017 10:44:17 -0000 From: "mark at klomp dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/15250] use PTRACE_SEIZE and PTRACE_INTERRUPT Date: Wed, 11 Oct 2017 10:44: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at klomp dot org 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: cc 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: 2017-q4/txt/msg00030.txt.bz2 Content-length: 388 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15250 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mark at klomp dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21983-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:44:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 33664 invoked by alias); 11 Oct 2017 10:44:09 -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 33586 invoked by uid 48); 11 Oct 2017 10:44:09 -0000 From: "mark at klomp dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20536] fails to handle DW_AT_upper_bound with DW_AT_constant_value in referenced DIE Date: Wed, 11 Oct 2017 10:44: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.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at klomp dot org 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: cc 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: 2017-q4/txt/msg00027.txt.bz2 Content-length: 388 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20536 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mark at klomp dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21988-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:44:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36459 invoked by alias); 11 Oct 2017 10:44: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 36376 invoked by uid 48); 11 Oct 2017 10:44:23 -0000 From: "mark at klomp dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20426] gdb does not interpret DWARF annotating imported units fully Date: Wed, 11 Oct 2017 10:44: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.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at klomp dot org 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: cc 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: 2017-q4/txt/msg00032.txt.bz2 Content-length: 388 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20426 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mark at klomp dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21991-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:48:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66756 invoked by alias); 11 Oct 2017 10:48:32 -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 66617 invoked by uid 48); 11 Oct 2017 10:48:31 -0000 From: "mjw at fedoraproject dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20536] fails to handle DW_AT_upper_bound with DW_AT_constant_value in referenced DIE Date: Wed, 11 Oct 2017 10:48: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.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mjw at fedoraproject dot org 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: cc 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: 2017-q4/txt/msg00037.txt.bz2 Content-length: 381 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20536 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mjw at fedoraproject dot org | --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21990-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:48:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66465 invoked by alias); 11 Oct 2017 10:48:31 -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 66309 invoked by uid 48); 11 Oct 2017 10:48:31 -0000 From: "mjw at fedoraproject dot org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/11579] RFE: backtrace core without any symfile_objfile Date: Wed, 11 Oct 2017 10:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: mjw at fedoraproject dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00034.txt.bz2 Content-length: 381 https://sourceware.org/bugzilla/show_bug.cgi?id=3D11579 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mjw at fedoraproject dot org | --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21993-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:48:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 69319 invoked by alias); 11 Oct 2017 10:48:38 -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 69254 invoked by uid 48); 11 Oct 2017 10:48:38 -0000 From: "mjw at fedoraproject dot org" To: gdb-prs@sourceware.org Subject: [Bug backtrace/11586] RFE: .eh_frame_hdr support (=speed-up) Date: Wed, 11 Oct 2017 10:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: mjw at fedoraproject dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00036.txt.bz2 Content-length: 381 https://sourceware.org/bugzilla/show_bug.cgi?id=3D11586 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mjw at fedoraproject dot org | --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21992-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:48:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 67761 invoked by alias); 11 Oct 2017 10:48:34 -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 67667 invoked by uid 48); 11 Oct 2017 10:48:34 -0000 From: "mjw at fedoraproject dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/13498] save-index makes gdb slow with dwarf4 Date: Wed, 11 Oct 2017 10:48: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: mjw at fedoraproject dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: dje at google dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00035.txt.bz2 Content-length: 381 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13498 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mjw at fedoraproject dot org | --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21994-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:48:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 73515 invoked by alias); 11 Oct 2017 10:48:49 -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 73211 invoked by uid 48); 11 Oct 2017 10:48:49 -0000 From: "mjw at fedoraproject dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/15250] use PTRACE_SEIZE and PTRACE_INTERRUPT Date: Wed, 11 Oct 2017 10:48: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mjw at fedoraproject dot org 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: cc 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: 2017-q4/txt/msg00038.txt.bz2 Content-length: 381 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15250 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mjw at fedoraproject dot org | --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21997-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:49:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79589 invoked by alias); 11 Oct 2017 10:49:06 -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 79481 invoked by uid 48); 11 Oct 2017 10:49:06 -0000 From: "mjw at fedoraproject dot org" To: gdb-prs@sourceware.org Subject: [Bug symtab/13627] multiple .debug_types per objfile are not supported Date: Wed, 11 Oct 2017 10:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mjw at fedoraproject dot org 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: cc 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: 2017-q4/txt/msg00041.txt.bz2 Content-length: 381 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13627 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mjw at fedoraproject dot org | --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21996-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:49:06 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79297 invoked by alias); 11 Oct 2017 10:49:05 -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 79236 invoked by uid 48); 11 Oct 2017 10:49:05 -0000 From: "mjw at fedoraproject dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20426] gdb does not interpret DWARF annotating imported units fully Date: Wed, 11 Oct 2017 10:49: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.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mjw at fedoraproject dot org 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: cc 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: 2017-q4/txt/msg00040.txt.bz2 Content-length: 381 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20426 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mjw at fedoraproject dot org | --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21995-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 10:49:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78580 invoked by alias); 11 Oct 2017 10:49:04 -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 78194 invoked by uid 48); 11 Oct 2017 10:49:03 -0000 From: "mjw at fedoraproject dot org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/11608] gcore does not support build-id Date: Wed, 11 Oct 2017 10:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mjw at fedoraproject dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00039.txt.bz2 Content-length: 381 https://sourceware.org/bugzilla/show_bug.cgi?id=3D11608 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mjw at fedoraproject dot org | --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21999-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 16:40:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66076 invoked by alias); 11 Oct 2017 16:40:43 -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 65626 invoked by uid 48); 11 Oct 2017 16:40:43 -0000 From: "sourceware.org-prf@jf-luce.name" To: gdb-prs@sourceware.org Subject: [Bug gdb/22282] info locals 1 freeze at 100% Date: Wed, 11 Oct 2017 16:40: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.10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: sourceware.org-prf@jf-luce.name X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00043.txt.bz2 Content-length: 442 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22282 sourceware.org-prf@jf-luce.name changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sourceware.org-prf@jf-luce. | |name --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-21998-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 11 16:40:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53498 invoked by alias); 11 Oct 2017 16:40:30 -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 52784 invoked by uid 48); 11 Oct 2017 16:40:29 -0000 From: "sourceware.org-prf@jf-luce.name" To: gdb-prs@sourceware.org Subject: [Bug gdb/22282] New: info locals 1 freeze at 100% Date: Wed, 11 Oct 2017 16:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: sourceware.org-prf@jf-luce.name X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00042.txt.bz2 Content-length: 850 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22282 Bug ID: 22282 Summary: info locals 1 freeze at 100% Product: gdb Version: 7.10.1 Status: UNCONFIRMED Severity: critical Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: sourceware.org-prf@jf-luce.name Target Milestone: --- Hi, I'm using OS X Yosemite. I've compiled with gcc 7.10. When I debug with gdb 7.10.1 or with gdb 8.0, info locals put gdb at 100% and never returns, but = it doesn't crash. I can supply the executable file. Is it known ? Is there something that I can do. I can consider to debug gdb= ,=20 ut can you point me in the right direction ? Regards. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22000-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Oct 12 11:06:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 121236 invoked by alias); 12 Oct 2017 11:06:17 -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 121213 invoked by uid 48); 12 Oct 2017 11:06:16 -0000 From: "paul.hua.gm at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22286] New: [MIPS] internal-error when read dspctl register Date: Thu, 12 Oct 2017 11:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: paul.hua.gm at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00044.txt.bz2 Content-length: 3182 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22286 Bug ID: 22286 Summary: [MIPS] internal-error when read dspctl register Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: paul.hua.gm at gmail dot com Target Milestone: --- I use 'info r' to read registers on mips64 target with dsp. something wrong. internal-error: void inf_ptrace_fetch_register(regcache*, int): Assertion `(size % sizeof (PTRACE_TYPE_RET)) =3D=3D 0' failed. ----------------cut------------------------------- (gdb) b main Breakpoint 1 at 0x1200038b4 (gdb) r Starting program: /usr/bin/ls=20 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Breakpoint 1, 0x00000001200038b4 in main () (gdb) info r zero at v0 v1 R0 0000000000000000 0000000000000001 0000000000000000 000000fff7ffcf80=20 a0 a1 a2 a3 R4 0000000000000001 000000ffffffad98 000000ffffffada8 0000000000000000=20 a4 a5 a6 a7 R8 000000fff7f36820 000000fff7fdba18 000000ffffffad90 0000000000000001=20 t0 t1 t2 t3 R12 000000fff7d75140 000000000000000b 00000000f63d4e2e 000000fff7ffde28=20 s0 s1 s2 s3 R16 000000fff7f34cc8 000000012001d5e0 0000000000000000 0000000000000000=20 s4 s5 s6 s7 R20 000000012016d750 000000012015af48 0000000000000000 0000000000000000=20 t8 t9 k0 k1 R24 0000000000000000 00000001200038a0 0000000000000000 0000000000000000=20 gp sp s8 ra R28 00000001200438a0 000000ffffffa900 0000000000000000 000000fff7d931a0=20 status lo hi badvaddr ffffffff8500c8f3 0000000000000000 000000000000000a 000000fff7daefe8=20 cause pc 0000000010000024 00000001200038b4=20 fcsr fir hi1 lo1 00000000 00770501 0000000000000000 0000000000000000=20 hi2 lo2 hi3 lo3 0000000000000000 0000000000000000 0000000000000000 0000000000000000=20 dspctl restart ../../binutils-gdb_git_trunk/gdb/inf-ptrace.c:735: internal-error: void inf_ptrace_fetch_register(regcache*, int): Assertion `(size % sizeof (PTRACE_TYPE_RET)) =3D=3D 0' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n)=20 -------------------------------------------------------------------------- --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22001-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Oct 12 11:32:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 762 invoked by alias); 12 Oct 2017 11:32:28 -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 739 invoked by uid 48); 12 Oct 2017 11:32:28 -0000 From: "paul.hua.gm at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22286] [MIPS] internal-error when read dspctl register Date: Thu, 12 Oct 2017 11:32: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: paul.hua.gm at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00045.txt.bz2 Content-length: 1591 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22286 --- Comment #1 from Paul Hua --- In mips64-dsp-linux.c:102 102 tdesc_create_reg (feature, "dspctl", 78, 1, NULL, 32, "int"); define the reg size is '32'=E3=80=82 but in inf-ptrace.c=EF=BC=9A 734 size =3D register_size (gdbarch, regnum); 735 gdb_assert ((size % sizeof (PTRACE_TYPE_RET)) =3D=3D 0); the PTRACE_TYPE_RET is long, sizeof (PTRACE_TYPE_RET) is 8, size is 4, so triger the gdb_assert. we should define dspctl size is 64, like status/cause register. Changelog: 2017-10-12 Chenghua Xu * mips64-dsp-linux.c (initialize_tdesc_mips64_dsp_linux): Change dspctl from 32 to 64 bit. ----------------------------------------------------------------------- diff --git a/gdb/features/mips64-dsp-linux.c b/gdb/features/mips64-dsp-linu= x.c index 05317b7..b42a8ce 100644 --- a/gdb/features/mips64-dsp-linux.c +++ b/gdb/features/mips64-dsp-linux.c @@ -99,7 +99,7 @@ initialize_tdesc_mips64_dsp_linux (void) tdesc_create_reg (feature, "lo2", 75, 1, NULL, 64, "int"); tdesc_create_reg (feature, "hi3", 76, 1, NULL, 64, "int"); tdesc_create_reg (feature, "lo3", 77, 1, NULL, 64, "int"); - tdesc_create_reg (feature, "dspctl", 78, 1, NULL, 32, "int"); + tdesc_create_reg (feature, "dspctl", 78, 1, NULL, 64, "int"); feature =3D tdesc_create_feature (result, "org.gnu.gdb.mips.linux"); tdesc_create_reg (feature, "restart", 79, 1, "system", 64, "int"); --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22002-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Oct 12 11:41:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31128 invoked by alias); 12 Oct 2017 11:41:33 -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 31105 invoked by uid 48); 12 Oct 2017 11:41:33 -0000 From: "paul.hua.gm at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22286] [MIPS] internal-error when read dspctl register Date: Thu, 12 Oct 2017 11:41: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: paul.hua.gm at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00046.txt.bz2 Content-length: 504 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22286 Paul Hua changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |macro@linux-mips.org --- Comment #2 from Paul Hua --- CC: macro@linux-mips.org, cause git blame to you. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22003-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Oct 12 14:33:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 121003 invoked by alias); 12 Oct 2017 14:33:56 -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 120972 invoked by uid 48); 12 Oct 2017 14:33:56 -0000 From: "macro@linux-mips.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22286] [MIPS] internal-error when read dspctl register Date: Thu, 12 Oct 2017 14:33: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: macro@linux-mips.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: macro@linux-mips.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed 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: 2017-q4/txt/msg00047.txt.bz2 Content-length: 1355 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22286 Maciej W. Rozycki changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-10-12 Assignee|unassigned at sourceware dot org |macro@linux-mips.org Ever confirmed|0 |1 --- Comment #3 from Maciej W. Rozycki --- Hi Paul, Thank you for your bug report and the proposed fix. However the DSPControl register is architecturally 32-bit even on 64-bit hardware, like CP1 control registers (e.g. FCSR, etc.) and unlike CP0 registers in general. So I'd rather fix the problem the other way round. I'll look into it. NB I agree Status and Cause are inconsistent in that they are exposed as 64-bit while they are not. The reason is historical and boils down to the layout of the `g'/`G' RSP packets matching debug stubs which predate the introduction of XML register descriptions. This could be fixed in a way similar to how I adjusted the handling of FCSR and FIR not so long ago, however as a non-fatal issue this is not urgent. Maciej --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22004-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Oct 12 17:23:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 117331 invoked by alias); 12 Oct 2017 17:23:26 -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 117303 invoked by uid 48); 12 Oct 2017 17:23:26 -0000 From: "jon.turney at dronecode dot org.uk" To: gdb-prs@sourceware.org Subject: [Bug gdb/21078] gdb compiled with mingw32 crashes on Windows7 when entering any invalid command Date: Thu, 12 Oct 2017 17:23: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jon.turney at dronecode dot org.uk X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00048.txt.bz2 Content-length: 663 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21078 Jon Turney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jon.turney at dronecode do= t org.uk --- Comment #6 from Jon Turney --- This problem is also seen on x86 Cygwin, and same workaround applies. It would be nice if we understood what was going wrong in the unwinder to c= ause this problem, though... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22005-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 13 06:31:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 82834 invoked by alias); 13 Oct 2017 06:31:16 -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 82678 invoked by uid 48); 13 Oct 2017 06:31:16 -0000 From: "asmwarrior at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21078] gdb compiled with mingw32 crashes on Windows7 when entering any invalid command Date: Fri, 13 Oct 2017 06:31: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: asmwarrior at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00049.txt.bz2 Content-length: 785 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21078 asmwarrior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asmwarrior at gmail dot com --- Comment #7 from asmwarrior --- I don't see this issue, I build GDB git master under msys + mingw-w64 mingw-build 5.4 gcc 32 bit version, if you would like to test, I have the binary here: http://forums.codeblocks.org/index.php/topic,22185.0.html, you need to install the official python 2.7 distribution, because my gdb was bu= ild against this python. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22006-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 13 09:05:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 32349 invoked by alias); 13 Oct 2017 09:05:44 -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 32087 invoked by uid 48); 13 Oct 2017 09:05:44 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug server/22137] gdbserver crashes on hosts with pkru register Date: Fri, 13 Oct 2017 09:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_status cf_reconfirmed_on everconfirmed 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: 2017-q4/txt/msg00050.txt.bz2 Content-length: 741 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22137 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-10-13 Ever confirmed|0 |1 --- Comment #3 from Pedro Alves --- > Bug is confirmed. Updating status then. Waldfred, if your account doesn't let you do that yourself, please let me know. And, I believe the bug is fixed in both master and 8.0 branch, right? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22007-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 13 09:08:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127121 invoked by alias); 13 Oct 2017 09:08:55 -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 125744 invoked by uid 55); 13 Oct 2017 09:08:54 -0000 From: "walfred.tedeschi at intel dot com" To: gdb-prs@sourceware.org Subject: [Bug server/22137] gdbserver crashes on hosts with pkru register Date: Fri, 13 Oct 2017 09:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: walfred.tedeschi at intel dot com 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: 2017-q4/txt/msg00051.txt.bz2 Content-length: 1678 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22137 --- Comment #4 from Walfred Tedeschi --- > -----Original Message----- > From: palves at redhat dot com [mailto:sourceware- > bugzilla@sourceware.org] > Sent: Friday, October 13, 2017 11:06 AM > To: Tedeschi, Walfred > Subject: [Bug server/22137] gdbserver crashes on hosts with pkru register >=20 > https://sourceware.org/bugzilla/show_bug.cgi?id=3D22137 >=20 > Pedro Alves changed: >=20 > What |Removed |Added > -------------------------------------------------------------------------= --- > Status|UNCONFIRMED |NEW > Last reconfirmed| |2017-10-13 > Ever confirmed|0 |1 >=20 > --- Comment #3 from Pedro Alves --- > > Bug is confirmed. >=20 > Updating status then. Waldfred, if your account doesn't let you do that > yourself, please let me know. >=20 > And, I believe the bug is fixed in both master and 8.0 branch, right? >=20 Patch works for both! I will patch then! Thanks and regards, /Fred > -- > You are receiving this mail because: > You are on the CC list for the bug. Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22008-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 13 12:24:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 103525 invoked by alias); 13 Oct 2017 12:24:49 -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 103496 invoked by uid 48); 13 Oct 2017 12:24:49 -0000 From: "jon.turney at dronecode dot org.uk" To: gdb-prs@sourceware.org Subject: [Bug gdb/21078] gdb compiled with mingw32 crashes on Windows7 when entering any invalid command Date: Fri, 13 Oct 2017 12:24: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jon.turney at dronecode dot org.uk X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00052.txt.bz2 Content-length: 759 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21078 --- Comment #8 from Jon Turney --- (In reply to asmwarrior from comment #7) > I don't see this issue, I build GDB git master under msys + mingw-w64 > mingw-build 5.4 gcc 32 bit version, if you would like to test, I have the > binary here: http://forums.codeblocks.org/index.php/topic,22185.0.html, y= ou > need to install the official python 2.7 distribution, because my gdb was > build against this python. Since it seems to be something to do with unwinding across DLL boundaries, = I'm going to wildly guess that building without --with-system-readline also prevents this problem. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22009-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 13 12:29:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 22947 invoked by alias); 13 Oct 2017 12:29:07 -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 21331 invoked by uid 55); 13 Oct 2017 12:29:06 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug python/12966] python threads incompatible with gdbserver Date: Fri, 13 Oct 2017 12:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q4/txt/msg00053.txt.bz2 Content-length: 903 https://sourceware.org/bugzilla/show_bug.cgi?id=3D12966 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Debe3b4020204= 2fc644df5ea3bd111425ba1aeeee commit ebe3b40202042fc644df5ea3bd111425ba1aeeee Author: Pedro Alves Date: Fri Oct 13 13:25:20 2017 +0100 Remove is_remote kfail from gdb.python/py-evthreads.exp This testcase works fine with gdbserver nowadays. So remove the kfail. gdb/testsuite/ChangeLog: 2017-10-13 Pedro Alves Simon Marchi PR python/12966 * gdb.python/py-evthreads.exp: Remove is_remote target kfail. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22010-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 13 15:45:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 69407 invoked by alias); 13 Oct 2017 15:45:27 -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 69366 invoked by uid 48); 13 Oct 2017 15:45:25 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22293] New: find command's "halting search" warning missing against gdbserver Date: Fri, 13 Oct 2017 15:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00054.txt.bz2 Content-length: 1512 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22293 Bug ID: 22293 Summary: find command's "halting search" warning missing against gdbserver Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- Currently, native-testing gdb.base/find-unmapped.exp we see: find global_var_0, global_var_2, 0xff warning: Unable to access 398 bytes of target memory at 0x7ffff7ff5e83, halting search. Pattern not found. (gdb) PASS: gdb.base/find-unmapped.exp: find global_var_0, global_var_2, 0= xff While with native-extended-gdbserver we get: find global_var_0, global_var_2, 0xff Pattern not found. (gdb) FAIL: gdb.base/find-unmapped.exp: find global_var_0, global_var_2, 0= xff The test fails because the testcase is expecting the "halting search" warni= ng. And the warning is missing because gdbserver supports the search memory pac= ket, and in that case, the warning is output by gdbserver instead of gdb. Printing the warning in gdbserver's terminal doesn't really help users. It= 'd be much better if the search memory packet was extended to allow reporting = back the memory range that couldn't be read, and then have GDB print the warning, instead of gdbserver. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22011-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 13 15:54:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 39398 invoked by alias); 13 Oct 2017 15:54:37 -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 39371 invoked by uid 55); 13 Oct 2017 15:54:37 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22293] find command's "halting search" warning missing against gdbserver Date: Fri, 13 Oct 2017 15:54: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q4/txt/msg00055.txt.bz2 Content-length: 1477 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22293 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D8b0553c18f0d= c63ab0ae930f2e8eed2bce4cd32c commit 8b0553c18f0dc63ab0ae930f2e8eed2bce4cd32c Author: Pedro Alves Date: Fri Oct 13 16:34:50 2017 +0100 Make gdb.base/find-unmapped.exp pass on remote targets Currently, with --target_board=3Dnative-extended-gdbserver, we get: Running .../src/gdb/testsuite/gdb.base/find-unmapped.exp ... FAIL: gdb.base/find-unmapped.exp: find global_var_0, global_var_2, 0x= ff FAIL: gdb.base/find-unmapped.exp: find global_var_1, global_var_2, 0x= ff FAIL: gdb.base/find-unmapped.exp: find global_var_2, (global_var_2 + = 16), 0xff This commit makes the test pass there, and also enables in on --target_board=3Dnative-gdbserver, and other remote targets. I've filed PR gdb/22293 to track the missing-warning problem. gdb/testsuite/ChangeLog: 2017-10-13 Pedro Alves PR gdb/22293 * gdb.base/find-unmapped.exp: Don't skip if is_remote target. (top level): Move some tests to ... (test_not_found): ... this new procedure. (top level): Call it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22012-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Oct 15 12:48:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 110456 invoked by alias); 15 Oct 2017 12:48:02 -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 110377 invoked by uid 48); 15 Oct 2017 12:48:01 -0000 From: "orgusuk at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug uprobes/22297] New: Program terminated with signal SIGTRAP, Trace/breakpoint trap Date: Sun, 15 Oct 2017 12:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: uprobes X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: orgusuk at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: 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: 2017-q4/txt/msg00056.txt.bz2 Content-length: 1932 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22297 Bug ID: 22297 Summary: Program terminated with signal SIGTRAP, Trace/breakpoint trap Product: systemtap Version: unspecified Status: UNCONFIRMED Severity: critical Priority: P1 Component: uprobes Assignee: systemtap at sourceware dot org Reporter: orgusuk at gmail dot com CC: drow at false dot org, gdb-prs at sourceware dot org, mihai.stanescu at gmail dot com, unassigned at sourcewa= re dot org Target Milestone: --- +++ This bug was initially created as a clone of Bug #9463 +++ [Converted from Gnats 2358] I have a simple program dynamically linked agains pthread. When i try to set a breakpoint in a child thread created with pthread_creat= e i get=20 Program terminated with signal SIGTRAP, Trace/breakpoint trap. I am using NPTL Release: > gdb 6.6 Environment: Gentoo distribution, all patches,kernel 2.6.22-gentoo-r8, also happens with newer kernels gcc (GCC) 4.1.2 (Gentoo 4.1.2) --------------- GNU C Library stable release version 2.6.1, by Roland McGrath et al. Compiled by GNU CC version 4.1.2 (Gentoo 4.1.2). Compiled on a Linux >>2.6.22-gentoo-r8<< system on 2007-11-06. Available extensions: C stubs add-on version 2.1.2 crypt add-on version 2.1 by Michael Glad and others Gentoo patchset 1.1 GNU Libidn by Simon Josefsson Native POSIX Threads Library by Ulrich Drepper et al Support for some architectures added on, not maintained in glibc co= re. BIND-8.2.3-T5B How-To-Repeat: Just compile the program with gcc -g -o pthreadtest pthreadtest.c -lpthreads run program with=20 ./pthreadtest & gdb -p `pgrep pthreadtest` In gdb br 12 continue --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22013-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 16 04:26:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 54702 invoked by alias); 16 Oct 2017 04:26:51 -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 54678 invoked by uid 48); 16 Oct 2017 04:26:51 -0000 From: "IsaacOscar at hotmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22301] New: [AARCH64] can't place breakpoint on STP of double registers Date: Mon, 16 Oct 2017 04:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: IsaacOscar at hotmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00057.txt.bz2 Content-length: 2318 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22301 Bug ID: 22301 Summary: [AARCH64] can't place breakpoint on STP of double registers Product: gdb Version: 7.11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: IsaacOscar at hotmail dot com Target Milestone: --- On aarch64 (the armv8-a version), gdb fails to place breakpoints on STP instruction with double registers as operands, e.g: ``` .globl main main: STP D9, D8, [SP,#-16]! RET ``` When compiled with gcc, and run through gdb: ``` GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "aarch64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./a.out...(no debugging symbols found)...done. (gdb) b main /build/gdb-g58BK_/gdb-7.11.1/gdb/aarch64-tdep.c:334: internal-error: aarch64_analyze_prologue: Assertion `inst.operands[0].type =3D=3D AARCH64_O= PND_Rt' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y This is a bug, please report it. For instructions, see: . /build/gdb-g58BK_/gdb-7.11.1/gdb/aarch64-tdep.c:334: internal-error: aarch64_analyze_prologue: Assertion `inst.operands[0].type =3D=3D AARCH64_O= PND_Rt' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) y Aborted (core dumped) ``` --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22014-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 16 04:28:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 55456 invoked by alias); 16 Oct 2017 04:28:16 -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 55431 invoked by uid 48); 16 Oct 2017 04:28:16 -0000 From: "IsaacOscar at hotmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22301] [AARCH64] can't place breakpoint on STP of double registers Date: Mon, 16 Oct 2017 04:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: IsaacOscar at hotmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q4/txt/msg00058.txt.bz2 Content-length: 314 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22301 --- Comment #1 from Isaac --- Created attachment 10531 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10531&action=3Ded= it Core dump --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22015-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 16 04:31:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 56879 invoked by alias); 16 Oct 2017 04:31:12 -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 56859 invoked by uid 48); 16 Oct 2017 04:31:12 -0000 From: "IsaacOscar at hotmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22301] [AARCH64] can't place breakpoint on STP of double registers Date: Mon, 16 Oct 2017 04:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: IsaacOscar at hotmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00059.txt.bz2 Content-length: 1161 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22301 --- Comment #2 from Isaac --- Interestingly, adding a breakpoint to the actual first instruction of main works, but using 'si' after breaking dosn't: ``` (gdb) b *&main Breakpoint 1 at 0x400570 (gdb) r Starting program: /home/isaacg/a.out Breakpoint 1, 0x0000000000400570 in main () (gdb) si /build/gdb-g58BK_/gdb-7.11.1/gdb/aarch64-tdep.c:334: internal-error: aarch64_analyze_prologue: Assertion `inst.operands[0].type =3D=3D AARCH64_O= PND_Rt' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y This is a bug, please report it. For instructions, see: . /build/gdb-g58BK_/gdb-7.11.1/gdb/aarch64-tdep.c:334: internal-error: aarch64_analyze_prologue: Assertion `inst.operands[0].type =3D=3D AARCH64_O= PND_Rt' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) y Aborted (core dumped) ``` --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22016-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 16 05:45:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 86263 invoked by alias); 16 Oct 2017 05:45:25 -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 85968 invoked by uid 48); 16 Oct 2017 05:45:25 -0000 From: "IsaacOscar at hotmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22301] [AARCH64] can't place breakpoint on STP of double registers Date: Mon, 16 Oct 2017 05:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: IsaacOscar at hotmail 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00060.txt.bz2 Content-length: 574 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22301 Isaac changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Isaac --- It seems it is fixed in version '8.0.1', sorry about the pointless bug repo= rt. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22017-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 17 17:50:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 26911 invoked by alias); 17 Oct 2017 17:50:33 -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 26882 invoked by uid 48); 17 Oct 2017 17:50:33 -0000 From: "dsmith at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/22297] Program terminated with signal SIGTRAP, Trace/breakpoint trap Date: Tue, 17 Oct 2017 17:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 6.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: dsmith at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc component version assigned_to product 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: 2017-q4/txt/msg00061.txt.bz2 Content-length: 646 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22297 David Smith changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dsmith at redhat dot com Component|uprobes |threads Version|unspecified |6.6 Assignee|systemtap at sourceware dot org |unassigned at sourc= eware dot org Product|systemtap |gdb --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22018-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 17 19:14:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88434 invoked by alias); 17 Oct 2017 19:14:18 -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 88407 invoked by uid 48); 17 Oct 2017 19:14:18 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/22297] Program terminated with signal SIGTRAP, Trace/breakpoint trap Date: Tue, 17 Oct 2017 19:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 6.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00062.txt.bz2 Content-length: 515 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22297 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- I'm confused by this bug. Why was 10-year-old bug cloned? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22019-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 17 19:15:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89432 invoked by alias); 17 Oct 2017 19:15:44 -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 89406 invoked by uid 48); 17 Oct 2017 19:15:44 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/22297] Program terminated with signal SIGTRAP, Trace/breakpoint trap Date: Tue, 17 Oct 2017 19:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 6.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: P1 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00063.txt.bz2 Content-length: 569 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22297 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Pedro Alves --- Closing. *** This bug has been marked as a duplicate of bug 9463 *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22020-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 17 19:15:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89627 invoked by alias); 17 Oct 2017 19:15:45 -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 89546 invoked by uid 48); 17 Oct 2017 19:15:44 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/9463] Program terminated with signal SIGTRAP, Trace/breakpoint trap Date: Tue, 17 Oct 2017 19:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 6.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00064.txt.bz2 Content-length: 517 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9463 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |orgusuk at gmail dot com --- Comment #2 from Pedro Alves --- *** Bug 22297 has been marked as a duplicate of this bug. *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22021-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 17 19:18:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 119531 invoked by alias); 17 Oct 2017 19:18:15 -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 119384 invoked by uid 48); 17 Oct 2017 19:18:14 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/9463] Program terminated with signal SIGTRAP, Trace/breakpoint trap Date: Tue, 17 Oct 2017 19:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 6.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 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: 2017-q4/txt/msg00065.txt.bz2 Content-length: 373 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9463 --- Comment #3 from Pedro Alves --- > This is the same as PR threads/2321. I think something must be wrong > with Gentoo's latest glibc; it does not happen on any other system. >=20=20 Marking as dup then. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22023-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 17 19:18:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 2506 invoked by alias); 17 Oct 2017 19:18:47 -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 2233 invoked by uid 48); 17 Oct 2017 19:18:46 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/9426] After upgrading glibc to v. 2.6.1, receive error stating "ptrace: No such process." Date: Tue, 17 Oct 2017 19:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 6.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: WAITING 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: cc 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: 2017-q4/txt/msg00067.txt.bz2 Content-length: 525 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9426 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mihai.stanescu at gmail do= t com --- Comment #8 from Pedro Alves --- *** Bug 9463 has been marked as a duplicate of this bug. *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22022-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 17 19:18:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 2011 invoked by alias); 17 Oct 2017 19:18:46 -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 1860 invoked by uid 48); 17 Oct 2017 19:18:45 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/9463] Program terminated with signal SIGTRAP, Trace/breakpoint trap Date: Tue, 17 Oct 2017 19:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 6.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution 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: 2017-q4/txt/msg00066.txt.bz2 Content-length: 656 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9463 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |palves at redhat dot com Resolution|--- |DUPLICATE --- Comment #4 from Pedro Alves --- Really marking as dup. *** This bug has been marked as a duplicate of bug 9426 *** --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22024-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 17 19:20:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 110158 invoked by alias); 17 Oct 2017 19:20:12 -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 110027 invoked by uid 48); 17 Oct 2017 19:20:12 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/9426] After upgrading glibc to v. 2.6.1, receive error stating "ptrace: No such process." Date: Tue, 17 Oct 2017 19:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 6.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: WAITING 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: 2017-q4/txt/msg00068.txt.bz2 Content-length: 337 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9426 --- Comment #9 from Pedro Alves --- There's no point in keeping this open. Too much has changed meanwhile. If there's still a problem, please file a new bug with new info. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22025-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Oct 17 19:21:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 21712 invoked by alias); 17 Oct 2017 19:21:07 -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 21345 invoked by uid 48); 17 Oct 2017 19:21:07 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/9426] After upgrading glibc to v. 2.6.1, receive error stating "ptrace: No such process." Date: Tue, 17 Oct 2017 19:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 6.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: OBSOLETE 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 cc resolution 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: 2017-q4/txt/msg00069.txt.bz2 Content-length: 507 https://sourceware.org/bugzilla/show_bug.cgi?id=3D9426 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED CC| |palves at redhat dot com Resolution|--- |OBSOLETE --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22026-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 18 16:44:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 60235 invoked by alias); 18 Oct 2017 16:44:44 -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 59541 invoked by uid 48); 18 Oct 2017 16:44:44 -0000 From: "weimin.pan at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18072] 180 fails in gdb.base/watchpoint-reuse-slot.exp on aarch64-linux-gnu Date: Wed, 18 Oct 2017 16:44: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: weimin.pan at oracle dot com 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: cc 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: 2017-q4/txt/msg00070.txt.bz2 Content-length: 2332 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18072 weimin.pan at oracle dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |weimin.pan at oracle dot c= om --- Comment #1 from weimin.pan at oracle dot com --- The test is now passing with upstream gdb: % make check TESTS=3D"gdb.base/watchpoint-reuse-slot.exp" make[1]: Entering directory '/home/wepan/binutils-gdb/gdb/testsuite' Nothing to be done for all... make check-single make[2]: Entering directory '/home/wepan/binutils-gdb/gdb/testsuite' rootme=3D`pwd`; export rootme; srcdir=3D. ; export srcdir ; EXPECT=3D`if [ = "${READ1}" !=3D "" ] ; then echo ${rootme}/expect-read1; elif [ -f ${rootme}/../../expect/expect ] ; then echo ${rootme}/../../expect/expect ; else echo expect ; fi` ; export EXPECT ; EXEEXT=3D ; export EXEEXT ; LD_LIBRARY_PATH=3D$rootme/../../expect:$rootme/../../libstdc++:$rootme/../.= ./tk/unix:$rootme/../../tcl/unix:$rootme/../../bfd:$rootme/../../opcodes:$L= D_LIBRARY_PATH; export LD_LIBRARY_PATH; if [ -f ${rootme}/../../expect/expect ] ; then TCL_LIBRARY=3D${srcdir}/../../tcl/library ; export TCL_LIBRARY ; fi ; runte= st --status gdb.base/watchpoint-reuse-slot.exp Test Run By wepan on Wed Oct 18 09:35:30 2017 Native configuration is aarch64-unknown-linux-gnu =3D=3D=3D gdb tests =3D=3D=3D Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for targ= et. Using /home/wepan/binutils-gdb/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file. Running /home/wepan/binutils-gdb/gdb/testsuite/gdb.base/watchpoint-reuse-slot.exp .= .. =3D=3D=3D gdb Summary =3D=3D=3D # of expected passes 1521 /home/wepan/binutils-gdb/gdb/testsuite/../../gdb/gdb version=20 8.0.50.20170915-git -nw -nx -data-directory /home/wepan/binutils-gdb/gdb/testsuite/../data-directory=20 make[2]: Leaving directory '/home/wepan/binutils-gdb/gdb/testsuite' make[1]: Leaving directory '/home/wepan/binutils-gdb/gdb/testsuite' --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22027-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 18 16:51:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 96730 invoked by alias); 18 Oct 2017 16:51:07 -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 96702 invoked by uid 48); 18 Oct 2017 16:51:07 -0000 From: "weimin.pan at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18071] TLS variables can't be resolved on aarch64-linux-gnu Date: Wed, 18 Oct 2017 16:51: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: weimin.pan at oracle dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: weimin.pan at oracle dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: 2017-q4/txt/msg00071.txt.bz2 Content-length: 395 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18071 weimin.pan at oracle dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |weimin.pan at oracl= e dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22028-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 18 20:00:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 47741 invoked by alias); 18 Oct 2017 20:00:44 -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 47708 invoked by uid 48); 18 Oct 2017 20:00:44 -0000 From: "mgulick at mathworks dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/16577] GDB crash on attempted read from deleted shared library Date: Wed, 18 Oct 2017 20:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mgulick at mathworks dot com 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: cc 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: 2017-q4/txt/msg00072.txt.bz2 Content-length: 2750 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16577 Mike Gulick changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mgulick at mathworks dot c= om --- Comment #3 from Mike Gulick --- I bisected this crash and git points to commit https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommit;h=3D4= bf44c1cf1abad13fcda09e20983757f175c6dca Debugging gdb built from this revision gives the following stack trace: Program received signal SIGSEGV, Segmentation fault. 0x0000000000739dd8 in bfd_getl32 (p=3D0x0) at libbfd.c:622 622 v =3D (unsigned long) addr[0]; (gdb) bt #0 0x0000000000739dd8 in bfd_getl32 (p=3D0x0) at libbfd.c:622 #1 0x00000000006694ac in read_initial_length (abfd=3D0x11fe4110, buf=3D0x0= ,=20 bytes_read_ptr=3D0x7ffc4e4dcd84) at dwarf2-frame.c:1526 #2 0x0000000000669eb6 in decode_frame_entry_1 (unit=3D0x145a6410, start=3D= 0x0,=20 eh_frame_p=3D1, cie_table=3D0x7ffc4e4dcef0, fde_table=3D0x7ffc4e4dcee0,= =20 entry_type=3DEH_CIE_OR_FDE_TYPE_ID) at dwarf2-frame.c:1837 #3 0x000000000066aa43 in decode_frame_entry (unit=3D0x145a6410, start=3D0x= 0,=20 eh_frame_p=3D1, cie_table=3D0x7ffc4e4dcef0, fde_table=3D0x7ffc4e4dcee0,= =20 entry_type=3DEH_CIE_OR_FDE_TYPE_ID) at dwarf2-frame.c:2135 #4 0x000000000066af60 in dwarf2_build_frame_info (objfile=3D0x1484e2a0) at dwarf2-frame.c:2292 #5 0x0000000000669b86 in dwarf2_frame_find_fde (pc=3D0x7ffc4e4dd070,=20 out_offset=3D0x0) at dwarf2-frame.c:1749 #6 0x0000000000669245 in dwarf2_frame_sniffer ( self=3D0x8a4da0 , this_frame=3D0x116fd00,=20 this_cache=3D0x116fd18) at dwarf2-frame.c:1382 #7 0x00000000006d735f in frame_unwind_find_by_frame (this_frame=3D0x116fd0= 0,=20 this_cache=3D0x116fd18) at frame-unwind.c:112 #8 0x00000000006d2a1a in get_frame_id (fi=3D0x116fd00) at frame.c:334 #9 0x00000000005b6399 in step_1 (skip_subroutines=3D1, single_inst=3D0,=20 count_string=3D0x0) at infcmd.c:917 #10 0x00000000005b61bf in next_command (count_string=3D0x0, from_tty=3D1) at infcmd.c:855 I believe there are two separate issues to (possibly) fix here: 1. The gdb segfault when stepping the debugger. 2. The errors/warnings about not being able to open the jna file. I have a preliminary patch to fix 1) that I will post to gdb-patches for feedback. It is debatable whether 2) should be fixed, as that likely invol= ves a special-case to detect and bypass jna files that could yield false-positi= ves. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22029-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Oct 19 02:17:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 77915 invoked by alias); 19 Oct 2017 02:17:31 -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 77890 invoked by uid 48); 19 Oct 2017 02:17:31 -0000 From: "weimin.pan at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21870] aarch64: Leftover uncleared debug registers Date: Thu, 19 Oct 2017 02:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: weimin.pan at oracle dot com 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: 2017-q4/txt/msg00073.txt.bz2 Content-length: 281 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21870 --- Comment #2 from weimin.pan at oracle dot com --- A proposed fix was submitted: https://sourceware.org/ml/gdb-patches/2017-10/msg00149.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22030-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Oct 19 07:53:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 93368 invoked by alias); 19 Oct 2017 07:53:04 -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 93331 invoked by uid 48); 19 Oct 2017 07:53:04 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/18072] 180 fails in gdb.base/watchpoint-reuse-slot.exp on aarch64-linux-gnu Date: Thu, 19 Oct 2017 07:53: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00074.txt.bz2 Content-length: 776 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18072 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Yao Qi --- This bug was fixed by commit ca5fd19bfb2a41fae7696d67d1f4dce5d5a9053a (watchpoint-reuse-slot.exp: skip setting HW breakpoints on some address), b= ut I forgot to mention the PR in commit log, so that commit wasn't associated wi= th this PR. Thanks for verifying this. I'll close this bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22031-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Oct 19 08:33:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94610 invoked by alias); 19 Oct 2017 08:33:12 -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 94410 invoked by uid 48); 19 Oct 2017 08:33:12 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21870] aarch64: Leftover uncleared debug registers Date: Thu, 19 Oct 2017 08:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: 2017-q4/txt/msg00075.txt.bz2 Content-length: 892 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21870 --- Comment #3 from Yao Qi --- (In reply to Jan Kratochvil from comment #0) > Created attachment 10295 [details] > .c standalone testcase >=20 > Testcase verifies if the debug registers are cleared after it is run. > Standalone execution is OK but being spawned from GDB reports an error: >=20 > # ./gdb ~/aarch64-watchpoint > GNU gdb (GDB) 8.0.50.20170731-git > (gdb) run > Starting program: /root/aarch64-watchpoint=20 > aarch64-watchpoint: aarch64-watchpoint.c:91: set_watchpoint: Assertion > `(((dreg_state.dbg_regs[0].ctrl) >> 5) & 0xff) =3D=3D 0' failed. I don't see how does GDB touches hw debug registers, in this case. I have = no idea that why DR_CONTROL_LENGTH (dreg_state.dbg_regs[0].ctrl) is changed to non-zero. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22032-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Oct 19 19:14:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 20101 invoked by alias); 19 Oct 2017 19:14:24 -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 19801 invoked by uid 48); 19 Oct 2017 19:14:23 -0000 From: "mgulick at mathworks dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/16577] GDB crash on attempted read from deleted shared library Date: Thu, 19 Oct 2017 19:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mgulick at mathworks dot com 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: attachments.created 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: 2017-q4/txt/msg00076.txt.bz2 Content-length: 511 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16577 --- Comment #4 from Mike Gulick --- Created attachment 10544 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10544&action=3Ded= it Updated reproducer to reproduce crash on current git tip See README.TXT for instructions. Updated reproducer no longer relies on being in /tmp, and reproduces the problem instantly (no more sleep()). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22033-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 20 08:29:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68858 invoked by alias); 20 Oct 2017 08:29:08 -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 68808 invoked by uid 48); 20 Oct 2017 08:29:07 -0000 From: "night_ghost at ykoctpa dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/22271] GDB fails on "assertion failed" Date: Fri, 20 Oct 2017 08:29: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: night_ghost at ykoctpa dot ru X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00077.txt.bz2 Content-length: 452 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22271 --- Comment #5 from night_ghost at ykoctpa dot ru --- >did you report the bug to whom you got toolchain from? toolchain is from arm.com and they sayd to report bugs to GDB developers >Could you try with a more up to date pristine/upstream GDB? where I can get recent toolchain for Linux 32bit with upstream GDB --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22034-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 23 15:36:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 105332 invoked by alias); 23 Oct 2017 15:36:49 -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 105306 invoked by uid 48); 23 Oct 2017 15:36:49 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22271] GDB fails on "assertion failed" Date: Mon, 23 Oct 2017 15:36: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00078.txt.bz2 Content-length: 885 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22271 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org --- Comment #6 from Yao Qi --- (In reply to night_ghost from comment #5) > >did you report the bug to whom you got toolchain from? >=20 > toolchain is from arm.com and they sayd to report bugs to GDB developers >=20 >=20 > >Could you try with a more up to date pristine/upstream GDB? >=20 > where I can get recent toolchain for Linux 32bit with upstream GDB You can get gdb release here https://sourceware.org/gdb/download/, configure it with --target=3Darm-none-eabi. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22035-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 23 20:53:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 55258 invoked by alias); 23 Oct 2017 20:53: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 55085 invoked by uid 48); 23 Oct 2017 20:53:23 -0000 From: "mgulick at mathworks dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22340] New: attach in gdb/mi doesn't display prompt Date: Mon, 23 Oct 2017 20:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mgulick at mathworks dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00079.txt.bz2 Content-length: 3971 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22340 Bug ID: 22340 Summary: attach in gdb/mi doesn't display prompt Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: mgulick at mathworks dot com Target Milestone: --- When using gdb in mi mode (gdb -i=3Dmi), the "(gdb)" prompt is not displayed properly when running the "attach" command. This is reproducible in emacs = gdb mode. I also tested this with the 'gdbgui' tool, which also gets confused = as to whether gdb is ready to accept more input after attaching to a process. The issue seems to be that the gdb output doesn't print the "(gdb)\n" prompt immediately after printing "^done" (output is from GDB 8.0.1): (gdb)=20 attach 31473 &"attach 31473\n" ~"Attaching to process 31473\n" =3Dthread-group-started,id=3D"i1",pid=3D"31473" =3Dthread-created,id=3D"1",group-id=3D"i1" --> ^done ~"Reading symbols from /bin/sleep..." ~"(no debugging symbols found)...done.\n" =20=20=20 =3Dlibrary-loaded,id=3D"/lib/x86_64-linux-gnu/libc.so.6",target-name=3D"/li= b/x86_64-linux-gnu/libc.so.6",host-name=3D"/lib/x86_64-linux-gnu/libc.so.6"= ,symbols-loaded=3D"0",thread-group=3D"i1",ranges=3D[{from=3D"0x00007f3869fd= 34a0",to=3D"0x00007f386a0ff943"}] =20=20=20 =3Dlibrary-loaded,id=3D"/lib64/ld-linux-x86-64.so.2",target-name=3D"/lib64/= ld-linux-x86-64.so.2",host-name=3D"/lib64/ld-linux-x86-64.so.2",symbols-loa= ded=3D"0",thread-group=3D"i1",ranges=3D[{from=3D"0x00007f386a35fae0",to=3D"= 0x00007f386a378140"}] ~"Reading symbols from /lib/x86_64-linux-gnu/libc.so.6..." ~"(no debugging symbols found)...done.\n" ~"Reading symbols from /lib64/ld-linux-x86-64.so.2..." ~"(no debugging symbols fou2nd)...done.\n" ~"0x00007f386a06df10 in nanosleep () from /lib/x86_64-linux-gnu/libc.so.6\n" =20=20=20 *stopped,frame=3D{addr=3D"0x00007f386a06df10",func=3D"nanosleep",args=3D[],= from=3D"/lib/x86_64-linux-gnu/libc.so.6"},thread-id=3D"1",stopped-threads= =3D"all",core=3D"5" --> (gdb)=20 I get the impression from the GDB/MI syntax (https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Output-Syntax.html#GD= B_002fMI-Output-Syntax) that a result record *must* be immediately followed by a "(gdb)\n" prompt. This behavior apparently changed in GDB 7.8 (I only very recently started u= sing GDB/MI mode, so never noticed this change). A git bisect points at this commit: https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommit;h=3D3= 29ea57934a9d4b250a0b417af1ec47bc2d0ceb6 Up until GDB 7.11, I could work around this by running 'maint set target-as= ync off'. This restored the previous prompting behavior, and this make emacs w= ork as expected. However this stopped working in GDB 7.11. It looks like this behavior changed with this commit: https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommit;h=3D0= b333c5e7d6c3fc65d37ffa11bd21ba52c4adb25. Reproduction steps: $ emacs --version GNU Emacs 24.4.1 $ sleep 1000 & [1] 14132 $ emacs -nw ... >> M-x gdb >> Run gdb (like this): gdb -n -i=3Dmi ... GNU gdb (GDB) 8.0.50.20171023-git ... (gdb) attach 14132 Attaching to process 14132 (gdb) Reading symbols from /bin/sleep...(no debugging symbols found)...done. Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...(no debugging symbols found)...done. Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. 0x00007f29a9214f10 in nanosleep () from /lib/x86_64-linux-gnu/libc.so.6 --- Also tested on Emacs 25.1.1 (Debian 9), with no change in behavior. I'm inclined to point the finger at gdb's mi mode rather than emacs, since 'gdbgui' also fails under similar conditions, but an emacs fix would be jus= t as good. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22036-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 25 02:32:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 25575 invoked by alias); 25 Oct 2017 02:32: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 25541 invoked by uid 48); 25 Oct 2017 02:32:23 -0000 From: "evan.torrie at yahoo dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20981] Dynamic library debugging on MacOS X 10.12 (Sierra) and dyld 15 is broken Date: Wed, 25 Oct 2017 02:32: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: evan.torrie at yahoo dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00080.txt.bz2 Content-length: 491 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20981 evan.torrie at yahoo dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |evan.torrie at yahoo dot c= om --- Comment #5 from evan.torrie at yahoo dot com --- This also occurs on Mac OS X 10.13 (High Sierra) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22037-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 25 04:31:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 47969 invoked by alias); 25 Oct 2017 04:31:00 -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 47371 invoked by uid 48); 25 Oct 2017 04:30:59 -0000 From: "shahzeb001 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20981] Dynamic library debugging on MacOS X 10.12 (Sierra) and dyld 15 is broken Date: Wed, 25 Oct 2017 04:31: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: shahzeb001 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00081.txt.bz2 Content-length: 411 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20981 --- Comment #6 from Shahzeb --- This problem still isn't resolved, but I came up with a solution: Simply ru= n a docker container I've built which has GDB within it. Instructions on my git= hub: https://github.com/shahzeb1/cpp-gdb-docker-image --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22038-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 25 17:00:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 26520 invoked by alias); 25 Oct 2017 17:00:30 -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 26496 invoked by uid 48); 25 Oct 2017 17:00:30 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22350] New: Attempt to set a breakpoint results in out of bounds access to std::vector Date: Wed, 25 Oct 2017 17:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q4/txt/msg00082.txt.bz2 Content-length: 1530 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22350 Bug ID: 22350 Summary: Attempt to set a breakpoint results in out of bounds access to std::vector Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: b7.10110111 at gmail dot com Target Milestone: --- Created attachment 10555 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10555&action=3Ded= it Abort backtrace I'm using a modified version of stl_vector.h, where I added some assertions into methods like std::vector::operator[]() which check that the argument f= its actual size of the vector. When compiling GDB 8.0.50.20171025-git with this setup (GCC 5.4.1), I get t= he following assertion failure on any attempt to set a breakpoint: $ gdb -q -ex 'b main' gdb Reading symbols from gdb...done. gdb: /usr/include/c++/5/bits/stl_vector.h:792: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) [with _Tp =3D partial_symbol*; _Alloc =3D std::allocator; std::vector<_Tp, _Alloc>::reference =3D partial_symbol*&; std::vector<_Tp, _Alloc>::size_type =3D long unsigned int= ]: Assertion `__n>From gdb-prs-return-22039-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Oct 25 17:01:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27194 invoked by alias); 25 Oct 2017 17:01:29 -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 27169 invoked by uid 48); 25 Oct 2017 17:01:29 -0000 From: "b7.10110111 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22350] Attempt to set a breakpoint results in out of bounds access to std::vector Date: Wed, 25 Oct 2017 17:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b7.10110111 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00083.txt.bz2 Content-length: 235 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22350 --- Comment #1 from Ruslan --- Test system is Kubuntu 14.04 amd64. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22040-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Oct 26 23:39:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 51325 invoked by alias); 26 Oct 2017 23:39:08 -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 51300 invoked by uid 55); 26 Oct 2017 23:39:07 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/20899] "dwarf2_string_attr" does not check for "DW_FORM_GNU_str_index" Date: Thu, 26 Oct 2017 23:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 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: 2017-q4/txt/msg00084.txt.bz2 Content-length: 1080 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20899 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The gdb-8.0-branch branch has been updated by Simon Marchi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D06848393c68c= 1b370cf2441756ed7413f4442515 commit 06848393c68c1b370cf2441756ed7413f4442515 Author: Leszek Swirski Date: Thu Oct 26 19:19:33 2017 -0400 Fix dwarf2_string_attr for -gsplit-dwarf The dwarf2_string_attr did not allow DW_FORM_GNU_str_index as a form for string types. This manifested as null strings in the namespace_name lookup (replaced with "(anonymous namespace)") when debugging Fission-compiled code. (cherry picked from commits 16eb6b2db49e6cf2fdca56efd37689fcc170cd37 and b33404388e5bbd8a1fddfde73cd4593ae2b557e8) gdb/ChangeLog: PR symtab/20899 * dwarf2read.c (dwarf2_string_attr): Allow DW_FORM_GNU_str_index. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22041-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 27 06:22:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122642 invoked by alias); 27 Oct 2017 06:22:44 -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 122616 invoked by uid 48); 27 Oct 2017 06:22:44 -0000 From: "night_ghost at ykoctpa dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/22271] GDB fails on "assertion failed" Date: Fri, 27 Oct 2017 06:22: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: night_ghost at ykoctpa dot ru X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00085.txt.bz2 Content-length: 236 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22271 --- Comment #7 from night_ghost at ykoctpa dot ru --- tested with upstream, crash seems to be gone --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22042-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 27 08:17:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 59967 invoked by alias); 27 Oct 2017 08:16:02 -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 59895 invoked by uid 48); 27 Oct 2017 08:16:00 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22271] GDB fails on "assertion failed" Date: Fri, 27 Oct 2017 08:16: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00086.txt.bz2 Content-length: 544 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22271 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #8 from Yao Qi --- It is already fixed in the recent GDB releases. Close it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22043-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 27 12:27:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 40785 invoked by alias); 27 Oct 2017 12:27:15 -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 40734 invoked by uid 48); 27 Oct 2017 12:27:15 -0000 From: "question123446 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20981] Dynamic library debugging on MacOS X 10.12 (Sierra) and dyld 15 is broken Date: Fri, 27 Oct 2017 12:27: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: question123446 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00087.txt.bz2 Content-length: 608 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20981 Andy Law changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |question123446 at gmail do= t com --- Comment #7 from Andy Law --- Gdb 8.0.1 doesn't have this problem as I see. However, the dynamic library still can't debug at all. It can't collect debug symbols... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22044-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 27 13:00:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 74374 invoked by alias); 27 Oct 2017 13:00:36 -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 74280 invoked by uid 48); 27 Oct 2017 13:00:30 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/13669] Infinite recursion in cp_print_value_fields Date: Fri, 27 Oct 2017 13:00: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.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson 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 cc resolution 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: 2017-q4/txt/msg00088.txt.bz2 Content-length: 725 https://sourceware.org/bugzilla/show_bug.cgi?id=3D13669 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED CC| |simon.marchi at ericsson d= ot com Resolution|--- |FIXED --- Comment #18 from Simon Marchi --- Fixed by https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommit;h=3Da= 43f3893f6cb66dfca7f628cd159a008009ad06f --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22045-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 27 14:39:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94012 invoked by alias); 27 Oct 2017 14:39:42 -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 93984 invoked by uid 48); 27 Oct 2017 14:39:42 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tdep/22356] New: [AArch64] 128-bit Q registers are not well handled in displaced stepping and fast tracepoint Date: Fri, 27 Oct 2017 14:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00089.txt.bz2 Content-length: 760 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22356 Bug ID: 22356 Summary: [AArch64] 128-bit Q registers are not well handled in displaced stepping and fast tracepoint Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: qiyao at gcc dot gnu.org Target Milestone: --- AArch64 GDB relies on "instruction relocation" (in arch/aarch64-insn.c) to handle both displaced stepping and fast tracepoint. However, it doesn't ha= ndle any instructions using Q registers. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22046-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Oct 27 14:41:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 97474 invoked by alias); 27 Oct 2017 14:41:36 -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 97448 invoked by uid 48); 27 Oct 2017 14:41:36 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tdep/22356] [AArch64] 128-bit Q registers are not well handled in displaced stepping and fast tracepoint Date: Fri, 27 Oct 2017 14:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: attachments.created 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: 2017-q4/txt/msg00090.txt.bz2 Content-length: 411 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22356 --- Comment #1 from Yao Qi --- Created attachment 10558 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10558&action=3Ded= it A patch as a reproducer. With this patch applied, the bug can be reproduced running disp-step-insn-reloc.exp. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22047-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Oct 28 18:22:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 87077 invoked by alias); 28 Oct 2017 18:22:04 -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 87029 invoked by uid 48); 28 Oct 2017 18:22:02 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug python/21213] garbarge collector eats gdb.selected_thread() Date: Sat, 28 Oct 2017 18:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson 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 cc resolution 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: 2017-q4/txt/msg00091.txt.bz2 Content-length: 724 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21213 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |simon.marchi at ericsson d= ot com Resolution|--- |FIXED --- Comment #2 from Simon Marchi --- Fixed by https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommit;h=3D4= 84d8d361de65a8489252d14511b77c142d859a1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22048-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Oct 29 12:47:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127602 invoked by alias); 29 Oct 2017 12:47:04 -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 127577 invoked by uid 48); 29 Oct 2017 12:47:03 -0000 From: "n-gcc at nn dot kiev.ua" To: gdb-prs@sourceware.org Subject: [Bug symtab/22365] New: "info locals" on an unitialized yet vector causes long garbage print Date: Sun, 29 Oct 2017 12:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: n-gcc at nn dot kiev.ua X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00092.txt.bz2 Content-length: 3514 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22365 Bug ID: 22365 Summary: "info locals" on an unitialized yet vector causes long garbage print Product: gdb Version: 7.11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: n-gcc at nn dot kiev.ua Target Milestone: --- With the code of function shown below, "info locals" causes print of local variable (namely, std::vector) of uninitialized value. Due to extreme lengt= h as result of garbage, this spoils output and hangs execution. The function beginning (relevant part) is: int solution(int N, int A, int B, int C, int D) { Point pointF =3D Point(A, B); Point pointS =3D Point(C, D); if (pointS =3D=3D pointF) { return 0; } int basicMazeSize =3D int(pow(2, N + 1)); Maze basicMaze =3D Maze(Point(0, 0), Point(basicMazeSize, basicMazeSize)); vector mazesF; mazesF.push_back(OrientedMaze(basicMaze, O_up)); vector mazesS; mazesS.push_back(OrientedMaze(basicMaze, O_up)); [... skip rest ...] debugger is stopped at breakpoint at the first function line (`Point pointF= =3D Point(A, B);`); and, `info locals` emits: (prefix [debug] is from Code::Blocks debugger win= dow) [debug]> info locals [debug]pointF =3D { [debug] x =3D 2,=20 [debug] y =3D 0 [debug]} [debug]pointS =3D { [debug] x =3D 20974602,=20 [debug] y =3D 0 [debug]} [debug]basicMazeSize =3D 32767 [debug]basicMaze =3D { [debug] lowerLeft =3D { [debug] x =3D -7268,=20 [debug] y =3D 32767 [debug] },=20 [debug] upperRight =3D { [debug] x =3D -7264,=20 [debug] y =3D 32767 [debug] } [debug]} [debug]mazesF =3D std::vector of length 6954038, capacity 6954038 =3D {{ [debug] maze =3D { [debug] lowerLeft =3D { [debug] x =3D 415531848,=20 [debug] y =3D 254699203 [debug] },=20 [debug] upperRight =3D { [debug] x =3D 33823,=20 [debug] y =3D 1207959552 [debug] } [debug] },=20 [debug] orientation =3D 1208544387 [debug] }, { [debug] maze =3D { [debug] lowerLeft =3D { and so on (millions of lines until stopped). here, not only mazesF is wrong (pointF, pointS are also filled with initial garbage), but vector length causes its full printing. Exact gdb version: GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1 (gdb) show configuration This GDB was configured as follows: configure --host=3Dx86_64-linux-gnu --target=3Dx86_64-linux-gnu --with-auto-load-dir=3D$debugdir:$datadir/auto-load --with-auto-load-safe-path=3D$debugdir:$datadir/auto-load --with-expat --with-gdb-datadir=3D/usr/share/gdb (relocatable) --with-jit-reader-dir=3D/usr/lib/gdb (relocatable) --without-libunwind-ia64 --with-lzma --with-python=3D/usr (relocatable) --without-guile --with-separate-debug-dir=3D/usr/lib/debug (relocatable) --with-system-gdbinit=3D/etc/gdb/gdbinit --with-babeltrace For solution: I don't have a patch, but only an idea that pretty printer sh= all take variable initialization status into account, and avoid working on deta= ils in such cases. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22049-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Oct 29 14:28:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 7581 invoked by alias); 29 Oct 2017 14:28:33 -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 7555 invoked by uid 48); 29 Oct 2017 14:28:32 -0000 From: "n-gcc at nn dot kiev.ua" To: gdb-prs@sourceware.org Subject: [Bug symtab/22365] "info locals" on an unitialized yet vector causes long garbage print Date: Sun, 29 Oct 2017 14:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: n-gcc at nn dot kiev.ua X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00093.txt.bz2 Content-length: 606 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22365 --- Comment #1 from Valentin Nechayev --- I have found gdb has limit on this print (`set print elements`) but Code::Blocks directly disables it with `set print elements 0`. So, anyway this isn't a _bug_ in gdb because it behaves exactly as specifie= d. I'll consider filing a bug to Code::Blocks. OTOH, protection against printing unitialized values can be useful, so I consider not closing it. Feel free to deal with this report in any way. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22050-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 30 01:41:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 56697 invoked by alias); 30 Oct 2017 01:41:57 -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 56557 invoked by uid 48); 30 Oct 2017 01:41:57 -0000 From: "astian at elude dot in" To: gdb-prs@sourceware.org Subject: [Bug record/22368] New: Assertion failure during recorded execution Date: Mon, 30 Oct 2017 01:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: astian at elude dot in X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00094.txt.bz2 Content-length: 7579 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22368 Bug ID: 22368 Summary: Assertion failure during recorded execution Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: record Assignee: unassigned at sourceware dot org Reporter: astian at elude dot in Target Milestone: --- I ran into the following 2 assertion failures when trying to record executi= on of a function: 1. /build/gdb-uGdIdO/gdb-7.12/gdb/record-full.c:1066: internal-error: pti= d_t record_full_wait_1(target_ops*, ptid_t, target_waitstatus*, int): Assertion `(options & TARGET_WNOHANG) !=3D 0' failed. 2. /build/gdb-uGdIdO/gdb-7.12/gdb/nat/x86-linux-dregs.c:146: internal-err= or: void x86_linux_update_debug_registers(lwp_info*): Assertion `lwp_is_stopped (lwp)' failed. It happened for the first time while trying to record execution of a keyboa= rd event handler for a GTK+ widget provided by the `spice-gtk` library and used in the SPICE client `remote-viewer`, part of the `virt-viewer` package. Initially I thought it had something to do with the peculiar situation I was trying to debug: with the keyboard partially "stuck" due to (methinks) being in the middle of an X server "grab". However, after some experimentation, I rather think that some threading shenanigans are at play: the same errors occur when attempting to record other, more typical, functions in the same program. I also confirmed that the recording steps I'm trying to carry out do work w= hen applied to other functions and other programs. STR: 1. On a Debian unstable system (with a configured debug-symbols repositor= y): # apt install gdb virt-viewer virt-viewer-dbgsym libspice-client-gtk-3.0-5-dbgsym Which should give you the following packages (among others): Package Version ------------------------------------------------------------- gdb 7.12-6+b1 (7.12.0.20161007-git) virt-viewer 6.0-2 libspice-client-gtk-3.0-5 0.34-1.1 2. Set up some SPICE server. In my case I have a Xen VM for which QEMU serves the desktop via a SPICE server. 3. Run: $ gdb -x rv.gdb Where "rv.gdb" contains (change the address of the spice server as needed): # Avoid problems with GDB's "record" and call trampolines which # usually manifests as: # Process record does not support instruction 0xc5 at address 0x7ffff7be0990. # Process record: failed to record execution log. set environment LD_BIND_NOW 1 # Avoid interruptions. set pagination off set record full stop-at-limit off file /usr/bin/remote-viewer start spice://localhost:12333 # This was the original reproducer for this bug. To trigger this # breakpoint, bring remote-viewer's window into focus and press (or # release) some key. # # Function "key_event" (in library "spice-gtk") is a GTK+ widget # keyboard event handler. #break key_event #commands #echo Recording function...\n #record #finish #end break virt_viewer_app_on_application_startup # Uncomment this "next" and you get a different error, see below. #next continue next Result: GDB stops because of an assertion failure. The failed assertion is one of the two listed above. It varies which one but the 1st is most commo= n. I also reproduced the bug using my own from-source debug builds of GDB (from 8.0.50-20171029 tarball), virt-viewer (from Debian source package) and spice-gtk (from Debian source package). Example transcript showing the first assertion failure: $ gdb -x rv.gdb GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". Temporary breakpoint 1 at 0x129b0: file remote-viewer-main.c, line 35. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Temporary breakpoint 1, main (argc=3D2, argv=3D0x7fffffffe278) at remote-viewer-main.c:35 35 remote-viewer-main.c: No such file or directory. Breakpoint 2 at 0x5555555709a0: file virt-viewer-app.c, line 1811. [New Thread 0x7fffe18cf700 (LWP 15211)] [New Thread 0x7fffe10ce700 (LWP 15212)] Thread 1 "remote-viewer" hit Breakpoint 2, virt_viewer_app_on_application_startup (app=3D0x5555557f2300 [RemoteViewer]= ) at virt-viewer-app.c:1811 1811 virt-viewer-app.c: No such file or directory. /build/gdb-uGdIdO/gdb-7.12/gdb/record-full.c:1066: internal-error: ptid_t record_full_wait_1(target_ops*, ptid_t, target_waitstatus*, int): Assertion `(options & TARGET_WNOHANG) !=3D 0' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from termina= l] This is a bug, please report it. For instructions, see: . /build/gdb-uGdIdO/gdb-7.12/gdb/record-full.c:1066: internal-error: ptid_t record_full_wait_1(target_ops*, ptid_t, target_waitstatus*, int): Assertion `(options & TARGET_WNOHANG) !=3D 0' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] Aborted (core dumped) (I can provide the core dump if required.) In the script, if instead of: break ... continue next ...one does: break ... next continue next ...instead of the assertion failure we get: [...] Temporary breakpoint 1, main (argc=3D2, argv=3D0x7fffffffe278) at remote-viewer-main.c:35 35 remote-viewer-main.c: No such file or directory. Breakpoint 2 at 0x5555555709a0: file virt-viewer-app.c, line 1811. [New Thread 0x7fffe18cf700 (LWP 15504)] [New Thread 0x7fffe10ce700 (LWP 15505)] Thread 1 "remote-viewer" hit Breakpoint 2, virt_viewer_app_on_application_startup (app=3D0x5555557f2300 [RemoteViewer]= ) at virt-viewer-app.c:1811 1811 virt-viewer-app.c: No such file or directory. 1812 in virt-viewer-app.c rv.gdb:16: Error in sourced command file: Couldn't get registers: No such process. (gdb) The inferior seems to be in a very bad state now: (gdb) next Cannot execute this command while the selected thread is running. Also note that the active thread was changed from 1 to 3: (gdb) info thread Id Target Id Frame 1 Thread 0x7ffff7f8c540 (LWP 15500) "remote-viewer" (running) 2 Thread 0x7fffe18cf700 (LWP 15504) "gmain" (running) * 3 Thread 0x7fffe10ce700 (LWP 15505) "gdbus" (running) Changing it back to 1 does not help. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22051-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 30 12:05:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 32307 invoked by alias); 30 Oct 2017 12:05:51 -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 32267 invoked by uid 48); 30 Oct 2017 12:05:51 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/22365] "info locals" on an unitialized yet vector causes long garbage print Date: Mon, 30 Oct 2017 12:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00095.txt.bz2 Content-length: 888 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22365 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #2 from Pedro Alves --- > OTOH, protection against printing unitialized values can be useful, so I= =20 > consider not closing it. Feel free to deal with this report in any way. There's no way for GDB to know whether the value was initialized or not. A= lso, printing an uninitialized value is really no different from printing a value that was initialized but has meanwhile been corrupted. gdb and pretty prin= ters must be robust against either case. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22052-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 30 14:27:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4093 invoked by alias); 30 Oct 2017 14:27:35 -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 4063 invoked by uid 48); 30 Oct 2017 14:27:34 -0000 From: "astian at elude dot in" To: gdb-prs@sourceware.org Subject: [Bug record/22368] Assertion failure during recorded execution Date: Mon, 30 Oct 2017 14:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: astian at elude dot in X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00096.txt.bz2 Content-length: 1101 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22368 --- Comment #1 from astian at elude dot in --- But of course I screw up the STR! This: > break virt_viewer_app_on_application_startup > # Uncomment this "next" and you get a different error, see below. > #next > continue > next Should be: > break virt_viewer_app_on_application_startup continue > # Uncomment this "next" and you get a different error, see below. > #next record > next That is: run until the breakpoint, optionally execute one line, start recording, execute one line (instead of "next", "step" or even "stepi" also work). Similarly, this: > In the script, if instead of: >=20 > break ... > continue > next >=20 > ...one does: >=20 > break ... > next > continue > next Should be: > In the script, if instead of: >=20 > break ... > continue record > next >=20 > ...one does: >=20 > break ... continue > next record > next --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22053-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Oct 30 14:43:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88374 invoked by alias); 30 Oct 2017 14:43:27 -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 88345 invoked by uid 48); 30 Oct 2017 14:43:25 -0000 From: "astian at elude dot in" To: gdb-prs@sourceware.org Subject: [Bug record/22368] Assertion failure during recorded execution Date: Mon, 30 Oct 2017 14:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: astian at elude dot in X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00097.txt.bz2 Content-length: 18008 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22368 --- Comment #2 from astian at elude dot in --- Here's a transcript of a debug build of GDB 8.0.50.20171029-git debugging another instance of itself while the bug is triggered: $ ~/src/gdb/build/gdb/gdb --data-directory ~/src/gdb/build/gdb/data-direc= tory -ex 'add-auto-load-safe-path ~/src/gdb/build/gdb/gdb-gdb.gdb' -ex 'set pagination off' -ex 'file ~/src/gdb/build/gdb/gdb' -ex 'run --data-directory ~/src/gdb/build/gdb/data-directory -q -x /tmp/rv.gdb' GNU gdb (GDB) 8.0.50.20171029-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". Reading symbols from ~/src/gdb/build/gdb/gdb...done. Setting up the environment for debugging gdb. During symbol reading, unsupported tag: 'DW_TAG_unspecified_type'. Breakpoint 1 at 0x23bee7: file /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/common/errors.c, line 51. During symbol reading, const value length mismatch for 'std::ratio<1, 1000000000>::num', got 8, expected 0. During symbol reading, cannot get low and high bounds for subprogram DIE = at 5383969. During symbol reading, Child DIE 0x5379df and its abstract origin 0x53ea06 have different parents. During symbol reading, DIE 0x540b48 and its abstract origin 0x53d20b have different tags. During symbol reading, DW_AT_call_target target DIE has invalid low pc, f= or referencing DIE 0x5448a7 [in module /home/astian/src/gdb/build/gdb/gdb]. Breakpoint 2 at 0x113eb8: file /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/cli/cli-cmds.c, line 214. Starting program: /home/astian/src/gdb/build/gdb/gdb --data-directory ~/src/gdb/build/gdb/data-directory -q -x /tmp/rv.gdb [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Temporary breakpoint 1 at 0x163aa: file remote-viewer-main.c, line 35. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Temporary breakpoint 1, main (argc=3D2, argv=3D0x7fffffffe1e8) at remote-viewer-main.c:35 35 { Breakpoint 2 at 0x555555570ac4: file virt-viewer-app.c, line 1811. [New Thread 0x7fffe18cf700 (LWP 30603)] [New Thread 0x7fffe10ce700 (LWP 30604)] Thread 1 "remote-viewer" hit Breakpoint 2, virt_viewer_app_on_application_startup (app=3D0x5555557f2300) at virt-viewer-app.c:1811 1811 { Breakpoint 1, internal_error (During symbol reading, incomplete CFI data; unspecified registers (e.g., rax) at 0x55555578feee. During symbol reading, unsupported tag: 'DW_TAG_unspecified_type'. During symbol reading, const value length mismatch for 'std::ratio<1, 1000000000>::num', got 8, expected 0. During symbol reading, Child DIE 0x22bc781 and its abstract origin 0x22c6= c36 have different parents. During symbol reading, cannot get low and high bounds for subprogram DIE = at 36440152. file=3Dfile@entry=3D0x555555a67068 "/home/astian/src/gdb/gdb-8.0.50.20171029/gdb/record-full.c", line=3Dline@entry=3D1050, fmt=3D0x5555559a849f "%s: Assertion `%s' failed."= ) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/common/errors.c:51 51 { (top-gdb) bt #0 internal_error (file=3Dfile@entry=3D0x555555a67068 "/home/astian/src/gdb/gdb-8.0.50.20171029/gdb/record-full.c", line=3Dline@entry=3D1050, fmt=3D0x5555559a849f "%s: Assertion `%s' failed."= ) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/common/errors.c:51 #1 0x0000555555828a31 in record_full_wait_1 (During symbol reading, DIE 0x25d29d9 and its abstract origin 0x25cab35 have different tags. ops=3D0x555555ece680 , ptid=3D..., status=3Dstatus@entry=3D0x7fffffffd7b0, options=3D0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/record-full.c:1050 #2 0x00005555558295e5 in record_full_wait (ops=3D, ptid= =3D..., status=3D0x7fffffffd7b0, options=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/record-full.c:1330 #3 0x000055555585e907 in delegate_wait (self=3D, arg1=3D.= .., arg2=3D, arg3=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/target-delegates.c:138 #4 0x000055555586cd9d in target_wait (During symbol reading, Member func= tion "~displaced_step_closure" (offset 30910879) is virtual but the vtable offse= t is not specified. During symbol reading, DW_AT_call_target target DIE has invalid low pc, f= or referencing DIE 0x1d8a856 [in module /home/astian/src/gdb/build/gdb/gdb]. During symbol reading, Child DIE 0x1d94d41 and its abstract origin 0x1d95= 953 have different tags. ptid=3D..., status=3Dstatus@entry=3D0x7fffffffd7b0, options=3Doptions@ent= ry=3D0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/target.c:2179 #5 0x00005555557d0f25 in wait_one (ws=3Dws@entry=3D0x7fffffffd7b0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:4345 #6 0x00005555557d5599 in stop_all_threads () at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:4558 #7 0x00005555557d599e in stop_waiting (ecs=3Decs@entry=3D0x7fffffffdc50)= at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:7658 #8 0x00005555557d59b7 in end_stepping_range (ecs=3Decs@entry=3D0x7ffffff= fdc50) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:7838 #9 0x00005555557d8c6f in process_event_stop_test (ecs=3Decs@entry=3D0x7fffffffdc50) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:6979 #10 0x00005555557d9d67 in handle_signal_stop (ecs=3Decs@entry=3D0x7ffffff= fdc50) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:6189 #11 0x00005555557daf50 in handle_inferior_event_1 (ecs=3Decs@entry=3D0x7fffffffdc50) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:5378 #12 0x00005555557db061 in handle_inferior_event (ecs=3Decs@entry=3D0x7fffffffdc50) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:5413 #13 0x00005555557db663 in fetch_inferior_event (client_data=3Dclient_data@entry=3D0x0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:3927 #14 0x00005555557c554e in inferior_event_handler (event_type=3Devent_type@entry=3DINF_REG_EVENT, client_data=3Dclient_data@e= ntry=3D0x0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/inf-loop.c:43 #15 0x0000555555825e45 in record_full_async_inferior_event_handler (data=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/record-full.c:769 #16 0x0000555555796384 in check_async_event_handlers () at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/event-loop.c:1064 #17 0x0000555555796ef8 in gdb_do_one_event () at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/event-loop.c:326 During symbol reading, Multiple children of DIE 0x26da14a refer to DIE 0x26da13a as their abstract origin. #18 0x000055555587f0b5 in wait_sync_command_done () at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/top.c:505 #19 0x000055555587f104 in maybe_wait_sync_command_done (was_sync=3D, was_sync@entry=3D0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/top.c:522 #20 0x000055555587f2f1 in execute_command (p=3D, p@entry=3D0x55555610f440 "next", from_tty=3D0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/top.c:610 #21 0x0000555555797f6f in command_handler (command=3D0x55555610f440 "next= ") at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/event-top.c:583 #22 0x000055555587fa3f in read_command_file (During symbol reading, No DW_FORM_block* DW_AT_call_value for DW_TAG_call_site child DIE 0x5cd91f [in module /home/astian/src/gdb/build/gdb/gdb]. stream=3Dstream@entry=3D0x5555560c4a80) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/top.c:426 #23 0x0000555555672318 in script_from_file (stream=3D0x5555560c4a80, file=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/cli/cli-script.c:1582 #24 0x0000555555666f10 in source_script_from_stream (stream=3D0x5555560c4= a80, file=3D0x7fffffffe558 "/tmp/rv.gdb", file_to_open=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/cli/cli-cmds.c:596 #25 0x00005555556699d5 in source_script_with_search (file=3D0x7fffffffe558 "/tmp/rv.gdb", from_tty=3D1, search_path=3D0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/cli/cli-cmds.c:632 #26 0x0000555555669ab3 in source_script (file=3Dfile@entry=3D0x7fffffffe5= 58 "/tmp/rv.gdb", from_tty=3Dfrom_tty@entry=3D1) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/cli/cli-cmds.c:642 #27 0x00005555557f0939 in catch_command_errors (command=3D0x555555669aa5 , arg=3D0x7fffffffe558 "/tmp/rv.gdb", from_tty=3D1) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/main.c:405 #28 0x00005555557f1983 in captured_main_1 (context=3Dcontext@entry=3D0x7fffffffe0d0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/main.c:1116 #29 0x00005555557f1abe in captured_main (data=3Ddata@entry=3D0x7fffffffe0= d0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/main.c:1142 #30 0x00005555557f1b63 in gdb_main (args=3D0x7fffffffe0d0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/main.c:1168 #31 0x00005555555fbe85 in main (argc=3D, argv=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/gdb.c:32 (top-gdb) c Continuing. /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/record-full.c:1050: internal-error: ptid_t record_full_wait_1(target_ops*, ptid_t, target_waitstatus*, int): Assertion `(options & TARGET_WNOHANG) !=3D 0' fai= led. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from termina= l] This is a bug, please report it. For instructions, see: . /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/record-full.c:1050: internal-error: ptid_t record_full_wait_1(target_ops*, ptid_t, target_waitstatus*, int): Assertion `(options & TARGET_WNOHANG) !=3D 0' fai= led. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] Program received signal SIGABRT, Aborted. 0x00007ffff6318fff in raise () from /lib/x86_64-linux-gnu/libc.so.6 (top-gdb) bt #0 0x00007ffff6318fff in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff631a42a in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x0000555555883855 in dump_core () at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/utils.c:282 #3 0x0000555555886e20 in internal_vproblem(internal_problem *, const cha= r *, int, const char *, typedef __va_list_tag __va_list_tag *) (problem=3Dproblem@entry=3D0x555555ea8820 , file=3D= , line=3D1050, fmt=3D, ap=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/utils.c:491 #4 0x0000555555886fa5 in internal_verror (file=3D, line=3D, fmt=3D, ap=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/utils.c:516 #5 0x000055555578ff69 in internal_error (file=3Dfile@entry=3D0x555555a67= 068 "/home/astian/src/gdb/gdb-8.0.50.20171029/gdb/record-full.c", line=3Dline@entry=3D1050, fmt=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/common/errors.c:55 #6 0x0000555555828a31 in record_full_wait_1 (ops=3D0x555555ece680 , ptid=3D..., status=3Dstatus@entry=3D0x7fffffffd7b0, opti= ons=3D0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/record-full.c:1050 #7 0x00005555558295e5 in record_full_wait (ops=3D, ptid= =3D..., status=3D0x7fffffffd7b0, options=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/record-full.c:1330 #8 0x000055555585e907 in delegate_wait (self=3D, arg1=3D.= .., arg2=3D, arg3=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/target-delegates.c:138 #9 0x000055555586cd9d in target_wait (ptid=3D..., status=3Dstatus@entry=3D0x7fffffffd7b0, options=3Doptions@entry=3D0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/target.c:2179 #10 0x00005555557d0f25 in wait_one (ws=3Dws@entry=3D0x7fffffffd7b0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:4345 #11 0x00005555557d5599 in stop_all_threads () at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:4558 #12 0x00005555557d599e in stop_waiting (ecs=3Decs@entry=3D0x7fffffffdc50)= at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:7658 #13 0x00005555557d59b7 in end_stepping_range (ecs=3Decs@entry=3D0x7ffffff= fdc50) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:7838 #14 0x00005555557d8c6f in process_event_stop_test (ecs=3Decs@entry=3D0x7fffffffdc50) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:6979 #15 0x00005555557d9d67 in handle_signal_stop (ecs=3Decs@entry=3D0x7ffffff= fdc50) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:6189 #16 0x00005555557daf50 in handle_inferior_event_1 (ecs=3Decs@entry=3D0x7fffffffdc50) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:5378 #17 0x00005555557db061 in handle_inferior_event (ecs=3Decs@entry=3D0x7fffffffdc50) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:5413 #18 0x00005555557db663 in fetch_inferior_event (client_data=3Dclient_data@entry=3D0x0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/infrun.c:3927 #19 0x00005555557c554e in inferior_event_handler (event_type=3Devent_type@entry=3DINF_REG_EVENT, client_data=3Dclient_data@e= ntry=3D0x0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/inf-loop.c:43 #20 0x0000555555825e45 in record_full_async_inferior_event_handler (data=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/record-full.c:769 #21 0x0000555555796384 in check_async_event_handlers () at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/event-loop.c:1064 #22 0x0000555555796ef8 in gdb_do_one_event () at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/event-loop.c:326 #23 0x000055555587f0b5 in wait_sync_command_done () at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/top.c:505 #24 0x000055555587f104 in maybe_wait_sync_command_done (was_sync=3D, was_sync@entry=3D0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/top.c:522 #25 0x000055555587f2f1 in execute_command (p=3D, p@entry=3D0x55555610f440 "next", from_tty=3D0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/top.c:610 #26 0x0000555555797f6f in command_handler (command=3D0x55555610f440 "next= ") at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/event-top.c:583 #27 0x000055555587fa3f in read_command_file (stream=3Dstream@entry=3D0x5555560c4a80) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/top.c:426 #28 0x0000555555672318 in script_from_file (stream=3D0x5555560c4a80, file=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/cli/cli-script.c:1582 #29 0x0000555555666f10 in source_script_from_stream (stream=3D0x5555560c4= a80, file=3D0x7fffffffe558 "/tmp/rv.gdb", file_to_open=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/cli/cli-cmds.c:596 #30 0x00005555556699d5 in source_script_with_search (file=3D0x7fffffffe558 "/tmp/rv.gdb", from_tty=3D1, search_path=3D0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/cli/cli-cmds.c:632 #31 0x0000555555669ab3 in source_script (file=3Dfile@entry=3D0x7fffffffe5= 58 "/tmp/rv.gdb", from_tty=3Dfrom_tty@entry=3D1) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/cli/cli-cmds.c:642 #32 0x00005555557f0939 in catch_command_errors (command=3D0x555555669aa5 , arg=3D0x7fffffffe558 "/tmp/rv.gdb", from_tty=3D1) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/main.c:405 #33 0x00005555557f1983 in captured_main_1 (context=3Dcontext@entry=3D0x7fffffffe0d0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/main.c:1116 #34 0x00005555557f1abe in captured_main (data=3Ddata@entry=3D0x7fffffffe0= d0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/main.c:1142 #35 0x00005555557f1b63 in gdb_main (args=3D0x7fffffffe0d0) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/main.c:1168 #36 0x00005555555fbe85 in main (argc=3D, argv=3D) at /home/astian/src/gdb/gdb-8.0.50.20171029/gdb/gdb.c:32 (top-gdb) With "/tmp/rv.gdb" being: $ cat /tmp/rv.gdb # Avoid problems with GDB's "record" and call trampolines which # usually manifests as: # Process record does not support instruction 0xc5 at address 0x7ffff7be0990. # Process record: failed to record execution log. set environment LD_BIND_NOW 1 # Avoid interruptions. set pagination off set record full stop-at-limit off directory ~/src/virt-viewer/virt-viewer-6.0/src directory ~/src/virt-viewer/spice-gtk-0.34/src #file /usr/bin/remote-viewer file ~/src/virt-viewer/virt-viewer-6.0/src/remote-viewer start spice://localhost:12333 # This was the original reproducer for this bug. To trigger this # breakpoint, bring remote-viewer's window into focus and press (or # release) some key. # # Function "key_event" (in library "spice-gtk") is a GTK+ widget # keyboard event handler. #break key_event #commands #echo Recording function...\n #record #finish #end break virt_viewer_app_on_application_startup continue # Uncomment this "next" and you get a different error. #next record next --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22054-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 01 14:43:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 12823 invoked by alias); 1 Nov 2017 14:43:36 -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 12801 invoked by uid 48); 1 Nov 2017 14:43:36 -0000 From: "djordje.todorovic@rt-rk.com" To: gdb-prs@sourceware.org Subject: [Bug threads/22381] New: GDB can not read TLS from cross-target core files Date: Wed, 01 Nov 2017 14:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: djordje.todorovic@rt-rk.com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00098.txt.bz2 Content-length: 1038 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22381 Bug ID: 22381 Summary: GDB can not read TLS from cross-target core files Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: threads Assignee: unassigned at sourceware dot org Reporter: djordje.todorovic@rt-rk.com Target Milestone: --- GDB loads native libthread_db that is only good for native debugging. When GDB is configured to run on Linux x86_64 with MIPS target like this: # ./configure --target=3Dmips-mti-linux-gnu and when try to read value of TLS variable from MIPS cross-target core file this message would be printed out: (gdb) p tls_variable Cannot find thread-local storage for LWP 21808, executable file ... Cannot find thread-local variables on this target The same problem would occur with all supported cross-target architectures. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22055-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 01 18:08:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 40222 invoked by alias); 1 Nov 2017 18:08:51 -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 40191 invoked by uid 48); 1 Nov 2017 18:08:51 -0000 From: "sourceware_bugzilla at codyps dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/22383] New: fileio pathnames are not NUL terminated after reading from target memory Date: Wed, 01 Nov 2017 18:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sourceware_bugzilla at codyps dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q4/txt/msg00099.txt.bz2 Content-length: 1992 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22383 Bug ID: 22383 Summary: fileio pathnames are not NUL terminated after reading from target memory Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: remote Assignee: unassigned at sourceware dot org Reporter: sourceware_bugzilla at codyps dot com Target Milestone: --- Created attachment 10564 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10564&action=3Ded= it 0001-gdb-remote-fileio-ensure-that-pathname-is-nul-termin.patch This was noted when using firmware using mbed 5.2's LocalFileSystem to trig= ger semihosting calls. openocd (latest) was then used with semihosting and semihosting_fileio enabled. Gdb was connected to the gdb server provided by openocd. The failure is (generally) observed as a failure to open files. This is due to a few junk bytes after the memory allocated in gdb by alloca= () being treated as part of the path: Here is some output from gdb with a patch to show open calls: > FIO: open("ABCDEFG.TXTM=EF=BF=BDU", 0, 1a4) The semihosting code is, in this case, trying to open "ABCDEFG.TXT", but has some extra chaf on the end. Here is the relevent code from gdb: /* Request pathname. */ pathname =3D (char *) alloca (length); if (target_read_memory (ptrval, (gdb_byte *) pathname, length) !=3D 0) { remote_fileio_ioerror (); return; } /* Check if pathname exists and is not a regular file or directory. If s= o, return an appropriate error code. Same for trying to open directories for writing. */ if (!stat (pathname, &st)) Note that it is trusting that `pathname` is null terminated within the leng= th given in the `Fopen` packet. I've attached a diff that appears to fix this issue for me. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22056-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 01 19:57:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31409 invoked by alias); 1 Nov 2017 19:57:48 -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 30932 invoked by uid 48); 1 Nov 2017 19:57:48 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/22383] fileio pathnames are not NUL terminated after reading from target memory Date: Wed, 01 Nov 2017 19:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00100.txt.bz2 Content-length: 741 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22383 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #1 from Sergio Durigan Junior --- Hello, This patch makes sense to me. Can you please submit it to with a proper ChangeLog entry (see ) so that = the maintainers can check and approve it? Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22057-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Nov 02 20:42:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107224 invoked by alias); 2 Nov 2017 20:42:03 -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 107131 invoked by uid 48); 2 Nov 2017 20:42:02 -0000 From: "pcarroll at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22388] New: assertion "xfered_len>0" in target.c for remote connection Date: Thu, 02 Nov 2017 20:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pcarroll at codesourcery dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00101.txt.bz2 Content-length: 3470 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22388 Bug ID: 22388 Summary: assertion "xfered_len>0" in target.c for remote connection Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: pcarroll at codesourcery dot com Target Milestone: --- We have a customer who is using a Corelis gdb server to connect to gdb. Occasionally, the gdb server will send a 0-byte block of memory for a read. When this happens, gdb gives an assertion from target.c: internal-error: target_xfer_partial: Assertion `*xfered_len > 0' failed. This problem is almost identical to that fixed in https://sourceware.org/ml/gdb-patches/2014-02/msg00636.html In this case, remote.c needs to be modified to return TARGET_XFER_EOF inste= ad of TARGET_XFER_OK or TARGET_XFER_UNAVAILABLE when 0 bytes are to be transferred.=20 The proposed fix would be: --- fsf/remote.c 2017-11-02 15:21:31.358857300 -0500 +++ fix/remote.c 2017-11-02 15:24:35.536391700 -0500 @@ -8264,7 +8264,7 @@ remote_write_bytes_aux (const char *head /* Return UNITS_WRITTEN, not TODO_UNITS, in case escape chars caused us = to send fewer units than we'd planned. */ *xfered_len_units =3D (ULONGEST) units_written; - return TARGET_XFER_OK; + return (*xfered_len_units !=3D 0) ? TARGET_XFER_OK : TARGET_XFER_EOF; } /* Write memory data directly to the remote machine. @@ -8358,7 +8358,7 @@ remote_read_bytes_1 (CORE_ADDR memaddr, decoded_bytes =3D hex2bin (p, myaddr, todo_units * unit_size); /* Return what we have. Let higher layers handle partial reads. */ *xfered_len_units =3D (ULONGEST) (decoded_bytes / unit_size); - return TARGET_XFER_OK; + return (*xfered_len_units !=3D 0) ? TARGET_XFER_OK : TARGET_XFER_EOF; } /* Using the set of read-only target sections of remote, read live @@ -8455,13 +8455,14 @@ remote_read_bytes (struct target_ops *op res =3D remote_xfer_live_readonly_partial (ops, myaddr, memad= dr, len, unit_size, xfered_len); if (res =3D=3D TARGET_XFER_OK) - return TARGET_XFER_OK; + return (*xfered_len !=3D 0) ? TARGET_XFER_OK : TARGET_XFER_= EOF; else { /* No use trying further, we know some memory starting at MEMADDR isn't available. */ *xfered_len =3D len; - return TARGET_XFER_UNAVAILABLE; + return (*xfered_len !=3D 0) ? + TARGET_XFER_UNAVAILABLE : TARGET_XFER_EOF; } } @@ -10386,7 +10387,7 @@ remote_write_qxfer (struct target_ops *o unpack_varlen_hex (rs->buf, &n); *xfered_len =3D n; - return TARGET_XFER_OK; + return (*xfered_len !=3D 0) ? TARGET_XFER_OK : TARGET_XFER_EOF; } /* Read OBJECT_NAME/ANNEX from the remote target using a qXfer packet. @@ -10687,7 +10688,7 @@ remote_xfer_partial (struct target_ops * strcpy ((char *) readbuf, rs->buf); *xfered_len =3D strlen ((char *) readbuf); - return TARGET_XFER_OK; + return (*xfered_len !=3D 0) ? TARGET_XFER_OK : TARGET_XFER_EOF; } /* Implementation of to_get_memory_xfer_limit. */ --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22058-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Nov 02 20:54:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 17232 invoked by alias); 2 Nov 2017 20:54:50 -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 17209 invoked by uid 48); 2 Nov 2017 20:54:49 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22388] assertion "xfered_len>0" in target.c for remote connection Date: Thu, 02 Nov 2017 20:54: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00102.txt.bz2 Content-length: 704 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22388 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #1 from Sergio Durigan Junior --- Thanks for the bug report, Paul. At a first glance this patch makes sense to me. Could you please send it to , with a proper ChangeLog entry, so that others= can see and discuss it? Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22059-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Nov 02 21:16:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107537 invoked by alias); 2 Nov 2017 21:16:51 -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 107515 invoked by uid 48); 2 Nov 2017 21:16:51 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/22389] New: aarch64: watchpoints are not merged regression Date: Thu, 02 Nov 2017 21:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00103.txt.bz2 Content-length: 1213 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22389 Bug ID: 22389 Summary: aarch64: watchpoints are not merged regression Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Target Milestone: --- A tracker only. As discussed in: Re: ping#2: [patch] aarch64: PR 19806: watchpoints: false negatives + PR 20207 contiguous ones https://sourceware.org/ml/gdb-patches/2017-10/msg00878.html Formerly GDB did merge all watchpoints happening inside an 1/2/4/8 byte ali= gned region to 8-byte boundary and then reused the same hardware watchpoint regi= ster as they became the same. New GDB does not merge them as it can properly prevent false positives (or formerly false negatives). But then it is now using separate hardware watchpoint register for each different watchpoint - despite GDB could merge adjacent watchpoints into a single register (without any false positives/negatives side effects). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22060-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Nov 02 21:17:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 108113 invoked by alias); 2 Nov 2017 21:17:42 -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 108082 invoked by uid 48); 2 Nov 2017 21:17:42 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/22389] aarch64: watchpoints are not merged regression Date: Thu, 02 Nov 2017 21:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: cf_gcctarget cc cf_gcchost dependson 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: 2017-q4/txt/msg00104.txt.bz2 Content-length: 758 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22389 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |aarch64-linux CC| |jan.kratochvil at redhat d= ot com Host| |aarch64-linux Depends on| |19806 Referenced Bugs: https://sourceware.org/bugzilla/show_bug.cgi?id=3D19806 [Bug 19806] Aarch64: watchpoints set on non-8-byte-aligned addresses are al= ways missed --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22061-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Nov 02 21:17:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 108242 invoked by alias); 2 Nov 2017 21:17:44 -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 108116 invoked by uid 48); 2 Nov 2017 21:17:42 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/19806] Aarch64: watchpoints set on non-8-byte-aligned addresses are always missed Date: Thu, 02 Nov 2017 21:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan.kratochvil at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: blocked 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: 2017-q4/txt/msg00105.txt.bz2 Content-length: 518 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19806 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |22389 Referenced Bugs: https://sourceware.org/bugzilla/show_bug.cgi?id=3D22389 [Bug 22389] aarch64: watchpoints are not merged regression --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22062-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Nov 03 18:32:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 17350 invoked by alias); 3 Nov 2017 18:32:26 -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 17159 invoked by uid 48); 3 Nov 2017 18:32:25 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18653] spawn changes SIGPIPE SIG_DFL to SIG_IGN Date: Fri, 03 Nov 2017 18:32: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.12 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00106.txt.bz2 Content-length: 2424 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18653 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #6 from Jan Kratochvil --- I think the fix is incomplete: - it does fix spawned inferiors - it does not fix "shell" commands: grep SigIgn /proc/self/status;./gdb -data-directory data-directory/ -batch = -ex '! grep SigIgn /proc/self/status' -ex start -ex 'call (int)system("grep Sig= Ign /proc/self/status")' --args echo SigIgn: 0000000000000000 SigIgn: 0000000001001000 Temporary breakpoint 1 at 0x1420: file ../src/echo.c, line 109. Temporary breakpoint 1, main (argc=3D1, argv=3D0x7fffffffd768) at ../src/ec= ho.c:109 109 { SigIgn: 0000000000000000 $1 =3D 0 A second issue: https://bugzilla.redhat.com/show_bug.cgi?id=3D1473411#c2 The all-zeros SigIgn is a bit weak. You really want to make sure that if gdb starts with something ignored, then the child process ALSO gets started with that same signal ignored. With working gdb, here's a slightly stronger tes= t: $ ( trap - BUS; sleep 30& grep SigIgn /proc/$!/status ) SigIgn: 0000000000000006 $ ( trap '' BUS; sleep 30& grep SigIgn /proc/$!/status ) SigIgn: 0000000000000046 Proof that we can control whether 0x40 is ignored during sleep using just t= he shell (the shell also ignores SIGINT and SIGQUIT during background tasks; that's life, hence why I used SIGBUS to show what I'm actually toggling) $ ( trap '' BUS; gdb --args sleep 30 ) GNU gdb (GDB) Fedora 8.0-13.fc26 ... (gdb) ! grep SigIgn /proc/self/status SigIgn: 0000000001001040 # So gdb started with SIGBUS ignored, and additionally ignores SIGPIPE itself... (gdb) b main Breakpoint 1 at 0x1590 (gdb) r Starting program: /usr/bin/sleep 30 Breakpoint 1, 0x0000555555555590 in main () (gdb) info thread Id Target Id Frame=20 * 1 process 27153 "sleep" 0x0000555555555590 in main () (gdb) ! grep SigIgn /proc/27153/status SigIgn: 0000000000000040 # ...but the child process sees JUST SIGBUS ignored (ie. the exact environm= ent that we started gdb with, prior to gdb fudging things around) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22063-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Nov 03 19:22:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 118914 invoked by alias); 3 Nov 2017 19:22:44 -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 118845 invoked by uid 48); 3 Nov 2017 19:22:44 -0000 From: "eochgls at web dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/20948] --write option to GDB causes segmentation fault Date: Fri, 03 Nov 2017 19:22: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: eochgls at web dot de X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00107.txt.bz2 Content-length: 938 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20948 Blauhirn changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eochgls at web dot de --- Comment #5 from Blauhirn --- For the real desperate like me, here is a bash workaround. gdb_write() { local x=3D$(mktemp) echo "set prompt (gdb-wrapper) handle SIGINT noprint pass break bfd_close commands return (int) 1 continue end run -q --write $@ quit" >|$x gdb -q gdb -x $x rm $x } Call like `gdb_write myprogram`. This makes gdb ignore the code inside `bfd_close`. I have no idea what dama= ge this might inflict, but the `--write` option does its job this way. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22064-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Nov 04 00:41:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 106692 invoked by alias); 4 Nov 2017 00:41:12 -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 106670 invoked by uid 48); 4 Nov 2017 00:41:11 -0000 From: "hi-angel at yandex dot ru" To: gdb-prs@sourceware.org Subject: [Bug compile/22395] New: ./configure picks up wrong compiler Date: Sat, 04 Nov 2017 00:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: compile X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hi-angel at yandex dot ru X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00108.txt.bz2 Content-length: 1431 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22395 Bug ID: 22395 Summary: ./configure picks up wrong compiler Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: compile Assignee: unassigned at sourceware dot org Reporter: hi-angel at yandex dot ru Target Milestone: --- Upon building gdb with -flto I'm getting dozens of errors like: nat/linux-btrace.h:85:8: warning: type =E2=80=98struct btrace_targe= t_info=E2=80=99 violates the C++ One Definition Rule [-Wodr] struct btrace_target_info ^ remote.c:13157:8: note: a different type is defined in another translation unit struct btrace_target_info ^ nat/linux-btrace.h:102:5: note: the first difference of correspondi= ng definitions is field =E2=80=98variant=E2=80=99 } variant; ^ remote.c:13157:8: note: a type with different number of fields is defined in another translation unit struct btrace_target_info ^ I didn't dig through all of them, but the primary reason seems to be that build-toolchain picks up "g++" as the compiler, whereas the gdb source code does not have .cpp files. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22065-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Nov 05 14:22:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 59126 invoked by alias); 5 Nov 2017 14:22: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 59104 invoked by uid 48); 5 Nov 2017 14:22:23 -0000 From: "mark at klomp dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22399] New: No support for DW_OP_GNU_variable_value Date: Sun, 05 Nov 2017 14:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at klomp dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00109.txt.bz2 Content-length: 771 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22399 Bug ID: 22399 Summary: No support for DW_OP_GNU_variable_value Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: mark at klomp dot org Target Milestone: --- Take the testcase/reproducer from gcc bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D77589 and compile with GNU F= ortran (GCC) 7.2.1 Breakpoint 1, repro () at dwarf-stridex.f90:14 14 print *, c40pt ! break-here (gdb) p c40pt(2) Unhandled dwarf expression opcode 0xfd --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22066-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 06 03:59:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122959 invoked by alias); 6 Nov 2017 03:59:48 -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 122936 invoked by uid 48); 6 Nov 2017 03:59:48 -0000 From: "jidanni at jidanni dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22400] New: Do not mention mailing list Date: Mon, 06 Nov 2017 03:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jidanni at jidanni dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00110.txt.bz2 Content-length: 755 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22400 Bug ID: 22400 Summary: Do not mention mailing list Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jidanni at jidanni dot org Target Milestone: --- On (info "(gdb) Bug Reporting") do not mention the mailing list. Also on http://www.gnu.org/software/gdb/bugs/ do not mention the mailing li= st. If one sends to the mailing list one will just get bounces. If one looks at the archives, they are all spam anyway. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22067-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 06 04:05:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 114313 invoked by alias); 6 Nov 2017 04:05:13 -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 114290 invoked by uid 48); 6 Nov 2017 04:05:13 -0000 From: "jidanni at jidanni dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22401] New: better pager prompt Date: Mon, 06 Nov 2017 04:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jidanni at jidanni dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00111.txt.bz2 Content-length: 1273 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22401 Bug ID: 22401 Summary: better pager prompt Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jidanni at jidanni dot org Target Milestone: --- The prompt ---Type to continue, or q to quit--- is nice, however the user might also want at some point, after reading several pages, to instead just print out all the remaining pages without having to hit RET after each one. Therefore please make it ---Type to continue, a or q to print all or quit--- Also the user should be shown what page he is on: --- 1/26 Type to continue, a or q to print all or quit--- Sure, on (info "(gdb) Screen Size") one can do set pagination off, but I am just talking about a user who is already on the fifth page, and wants to dump all the rest to STDOUT right now. Also I am not asking you for how to do it. I am asking to change the prompt, and add a "a" command. Or a "?" to show all options. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22068-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 06 10:34:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 83954 invoked by alias); 6 Nov 2017 10:34:59 -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 83886 invoked by uid 48); 6 Nov 2017 10:34:58 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug compile/22395] ODR violations Date: Mon, 06 Nov 2017 10:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: compile X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc short_desc 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: 2017-q4/txt/msg00112.txt.bz2 Content-length: 708 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22395 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com Summary|./configure picks up wrong |ODR violations |compiler | --- Comment #1 from Pedro Alves --- Actually, GDB _is_ a C++ program nowadays [1]. The ODR violations should be fixed. [1] - https://sourceware.org/gdb/wiki/cxx-conversion --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22069-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 06 11:38:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 59603 invoked by alias); 6 Nov 2017 11:38:53 -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 59550 invoked by uid 48); 6 Nov 2017 11:38:50 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug build/22102] 32-bit gdb build fails with undefined reference to amd64_create_target_description Date: Mon, 06 Nov 2017 11:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution assigned_to target_milestone 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: 2017-q4/txt/msg00113.txt.bz2 Content-length: 628 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22102 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Assignee|unassigned at sourceware dot org |qiyao at gcc dot gn= u.org Target Milestone|--- |8.1 --- Comment #3 from Yao Qi --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22070-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 06 17:08:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 65419 invoked by alias); 6 Nov 2017 17:08:28 -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 65396 invoked by uid 48); 6 Nov 2017 17:08:28 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22404] New: read after free in dwarf2read.c Date: Mon, 06 Nov 2017 17:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00114.txt.bz2 Content-length: 19242 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22404 Bug ID: 22404 Summary: read after free in dwarf2read.c Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: qiyao at gcc dot gnu.org Target Milestone: --- $ valgrind ./gdb ./testsuite/outputs/gdb.dwarf2/dw2-bad-parameter-type/dw2-bad-parameter-type (gdb) ptype f =3D=3D5804=3D=3D Invalid read of size 1 =3D=3D5804=3D=3D at 0x57696E: ~process_die_scope (dwarf2read.c:8537) =3D=3D5804=3D=3D by 0x57696E: process_die(die_info*, dwarf2_cu*) (dwarf2= read.c:8559) =3D=3D5804=3D=3D by 0x575F48: read_file_scope (dwarf2read.c:9539) =3D=3D5804=3D=3D by 0x575F48: process_die(die_info*, dwarf2_cu*) (dwarf2= read.c:8567) =3D=3D5804=3D=3D by 0x5784BF: process_full_comp_unit (dwarf2read.c:8337) =3D=3D5804=3D=3D by 0x5784BF: process_queue (dwarf2read.c:7828) =3D=3D5804=3D=3D by 0x5784BF: dw2_do_instantiate_symtab(dwarf2_per_cu_da= ta*) (dwarf2read.c:2931) =3D=3D5804=3D=3D by 0x579665: dwarf2_read_symtab(partial_symtab*, objfil= e*) (dwarf2read.c:7694) =3D=3D5804=3D=3D by 0x60A816: psymtab_to_symtab(objfile*, partial_symtab= *) (psymtab.c:768) =3D=3D5804=3D=3D by 0x60CF20: psym_lookup_symbol(objfile*, int, char con= st*, domain_enum_tag) (psymtab.c:519) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_via_quick_fns (symtab.c:2299) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_in_objfile(objfile*, int, ch= ar const*, domain_enum_tag) (symtab.c:2471) =3D=3D5804=3D=3D by 0x647049: lookup_static_symbol(char const*, domain_e= num_tag) (symtab.c:2508) =3D=3D5804=3D=3D by 0x647423: lookup_symbol_aux (symtab.c:2024) =3D=3D5804=3D=3D by 0x647423: lookup_symbol_in_language(char const*, blo= ck const*, domain_enum_tag, language, field_of_this_result*) (symtab.c:1819) =3D=3D5804=3D=3D by 0x6474B5: lookup_symbol(char const*, block const*, domain_enum_tag, field_of_this_result*) (symtab.c:1831) =3D=3D5804=3D=3D by 0x4B12BC: classify_name(parser_state*, block const*,= int) (c-exp.y:2892) =3D=3D5804=3D=3D by 0x4B3B39: c_yylex (c-exp.y:3092) =3D=3D5804=3D=3D by 0x4B3B39: c_yyparse() (c-exp.c:1903) =3D=3D5804=3D=3D Address 0x62a1233 is 291 bytes inside a block of size 4,0= 64 free'd =3D=3D5804=3D=3D at 0x4C2EDEB: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) =3D=3D5804=3D=3D by 0x777B43: _obstack_free (obstack.c:280) =3D=3D5804=3D=3D by 0x556BCA: free_heap_comp_unit(void*) (dwarf2read.c:2= 2844) =3D=3D5804=3D=3D by 0x556C66: free_one_cached_comp_unit(dwarf2_per_cu_da= ta*) (dwarf2read.c:22929) =3D=3D5804=3D=3D by 0x556CBF: dwarf2_release_queue(void*) (dwarf2read.c:= 7865) =3D=3D5804=3D=3D by 0x523445: do_my_cleanups(cleanup**, cleanup*) (clean= ups.c:154) =3D=3D5804=3D=3D by 0x528A6D: throw_exception_cxx(gdb_exception) (common-exceptions.c:289) =3D=3D5804=3D=3D by 0x528B54: throw_exception (common-exceptions.c:317) =3D=3D5804=3D=3D by 0x528B54: throw_it(return_reason, errors, char const= *, __va_list_tag*) (common-exceptions.c:373) =3D=3D5804=3D=3D by 0x528D95: throw_verror(errors, char const*, __va_lis= t_tag*) (common-exceptions.c:379) =3D=3D5804=3D=3D by 0x673EC3: verror(char const*, __va_list_tag*) (utils= .c:249) =3D=3D5804=3D=3D by 0x57DAA8: error(char const*, ...) (errors.c:43) =3D=3D5804=3D=3D by 0x567365: follow_die_ref(die_info*, attribute const*, dwarf2_cu**) [clone .isra.251] (dwarf2read.c:20728) =3D=3D5804=3D=3D Block was alloc'd at =3D=3D5804=3D=3D at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) =3D=3D5804=3D=3D by 0x528FB7: xmalloc (common-utils.c:44) =3D=3D5804=3D=3D by 0x777907: _obstack_begin_worker (obstack.c:141) =3D=3D5804=3D=3D by 0x5669FF: init_cutu_and_read_dies(dwarf2_per_cu_data= *, abbrev_table*, int, int, void (*)(die_reader_specs const*, unsigned char const*, die_info*, int, void*), void*) (dwarf2read.c:5733) =3D=3D5804=3D=3D by 0x567119: load_full_comp_unit(dwarf2_per_cu_data*, l= anguage) (dwarf2read.c:7991) =3D=3D5804=3D=3D by 0x569761: load_cu(dwarf2_per_cu_data*) (dwarf2read.c= :2889) =3D=3D5804=3D=3D by 0x578383: dw2_do_instantiate_symtab(dwarf2_per_cu_da= ta*) (dwarf2read.c:2916) =3D=3D5804=3D=3D by 0x579665: dwarf2_read_symtab(partial_symtab*, objfil= e*) (dwarf2read.c:7694) =3D=3D5804=3D=3D by 0x60A816: psymtab_to_symtab(objfile*, partial_symtab= *) (psymtab.c:768) =3D=3D5804=3D=3D by 0x60CF20: psym_lookup_symbol(objfile*, int, char con= st*, domain_enum_tag) (psymtab.c:519) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_via_quick_fns (symtab.c:2299) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_in_objfile(objfile*, int, ch= ar const*, domain_enum_tag) (symtab.c:2471) =3D=3D5804=3D=3D by 0x647049: lookup_static_symbol(char const*, domain_e= num_tag) (symtab.c:2508) =3D=3D5804=3D=3D=20 =3D=3D5804=3D=3D Invalid read of size 8 =3D=3D5804=3D=3D at 0x576973: ~process_die_scope (dwarf2read.c:8541) =3D=3D5804=3D=3D by 0x576973: process_die(die_info*, dwarf2_cu*) (dwarf2= read.c:8559) =3D=3D5804=3D=3D by 0x575F48: read_file_scope (dwarf2read.c:9539) =3D=3D5804=3D=3D by 0x575F48: process_die(die_info*, dwarf2_cu*) (dwarf2= read.c:8567) =3D=3D5804=3D=3D by 0x5784BF: process_full_comp_unit (dwarf2read.c:8337) =3D=3D5804=3D=3D by 0x5784BF: process_queue (dwarf2read.c:7828) =3D=3D5804=3D=3D by 0x5784BF: dw2_do_instantiate_symtab(dwarf2_per_cu_da= ta*) (dwarf2read.c:2931) =3D=3D5804=3D=3D by 0x579665: dwarf2_read_symtab(partial_symtab*, objfil= e*) (dwarf2read.c:7694) =3D=3D5804=3D=3D by 0x60A816: psymtab_to_symtab(objfile*, partial_symtab= *) (psymtab.c:768) =3D=3D5804=3D=3D by 0x60CF20: psym_lookup_symbol(objfile*, int, char con= st*, domain_enum_tag) (psymtab.c:519) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_via_quick_fns (symtab.c:2299) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_in_objfile(objfile*, int, ch= ar const*, domain_enum_tag) (symtab.c:2471) =3D=3D5804=3D=3D by 0x647049: lookup_static_symbol(char const*, domain_e= num_tag) (symtab.c:2508) =3D=3D5804=3D=3D by 0x647423: lookup_symbol_aux (symtab.c:2024) =3D=3D5804=3D=3D by 0x647423: lookup_symbol_in_language(char const*, blo= ck const*, domain_enum_tag, language, field_of_this_result*) (symtab.c:1819) =3D=3D5804=3D=3D by 0x6474B5: lookup_symbol(char const*, block const*, domain_enum_tag, field_of_this_result*) (symtab.c:1831) =3D=3D5804=3D=3D by 0x4B12BC: classify_name(parser_state*, block const*,= int) (c-exp.y:2892) =3D=3D5804=3D=3D by 0x4B3B39: c_yylex (c-exp.y:3092) =3D=3D5804=3D=3D by 0x4B3B39: c_yyparse() (c-exp.c:1903) =3D=3D5804=3D=3D Address 0x62a1090 is 256 bytes inside a block of size 312= free'd =3D=3D5804=3D=3D at 0x4C2EDEB: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) =3D=3D5804=3D=3D by 0x556C66: free_one_cached_comp_unit(dwarf2_per_cu_da= ta*) (dwarf2read.c:22929) =3D=3D5804=3D=3D by 0x556CBF: dwarf2_release_queue(void*) (dwarf2read.c:= 7865) =3D=3D5804=3D=3D by 0x523445: do_my_cleanups(cleanup**, cleanup*) (clean= ups.c:154) =3D=3D5804=3D=3D by 0x528A6D: throw_exception_cxx(gdb_exception) (common-exceptions.c:289) =3D=3D5804=3D=3D by 0x528B54: throw_exception (common-exceptions.c:317) =3D=3D5804=3D=3D by 0x528B54: throw_it(return_reason, errors, char const= *, __va_list_tag*) (common-exceptions.c:373) =3D=3D5804=3D=3D by 0x528D95: throw_verror(errors, char const*, __va_lis= t_tag*) (common-exceptions.c:379) =3D=3D5804=3D=3D by 0x673EC3: verror(char const*, __va_list_tag*) (utils= .c:249) =3D=3D5804=3D=3D by 0x57DAA8: error(char const*, ...) (errors.c:43) =3D=3D5804=3D=3D by 0x567365: follow_die_ref(die_info*, attribute const*, dwarf2_cu**) [clone .isra.251] (dwarf2read.c:20728) =3D=3D5804=3D=3D by 0x56D738: lookup_die_type(die_info*, attribute const= *, dwarf2_cu*) (dwarf2read.c:19743) =3D=3D5804=3D=3D by 0x56CF19: read_subroutine_type (dwarf2read.c:15083) =3D=3D5804=3D=3D by 0x56CF19: read_type_die_1 (dwarf2read.c:19802) =3D=3D5804=3D=3D by 0x56CF19: read_type_die(die_info*, dwarf2_cu*) (dwarf2read.c:19777) =3D=3D5804=3D=3D Block was alloc'd at =3D=3D5804=3D=3D at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) =3D=3D5804=3D=3D by 0x528FB7: xmalloc (common-utils.c:44) =3D=3D5804=3D=3D by 0x5669F1: init_cutu_and_read_dies(dwarf2_per_cu_data= *, abbrev_table*, int, int, void (*)(die_reader_specs const*, unsigned char const*, die_info*, int, void*), void*) (dwarf2read.c:5732) =3D=3D5804=3D=3D by 0x567119: load_full_comp_unit(dwarf2_per_cu_data*, l= anguage) (dwarf2read.c:7991) =3D=3D5804=3D=3D by 0x569761: load_cu(dwarf2_per_cu_data*) (dwarf2read.c= :2889) =3D=3D5804=3D=3D by 0x578383: dw2_do_instantiate_symtab(dwarf2_per_cu_da= ta*) (dwarf2read.c:2916) =3D=3D5804=3D=3D by 0x579665: dwarf2_read_symtab(partial_symtab*, objfil= e*) (dwarf2read.c:7694) =3D=3D5804=3D=3D by 0x60A816: psymtab_to_symtab(objfile*, partial_symtab= *) (psymtab.c:768) =3D=3D5804=3D=3D by 0x60CF20: psym_lookup_symbol(objfile*, int, char con= st*, domain_enum_tag) (psymtab.c:519) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_via_quick_fns (symtab.c:2299) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_in_objfile(objfile*, int, ch= ar const*, domain_enum_tag) (symtab.c:2471) =3D=3D5804=3D=3D by 0x647049: lookup_static_symbol(char const*, domain_e= num_tag) (symtab.c:2508) =3D=3D5804=3D=3D by 0x647423: lookup_symbol_aux (symtab.c:2024) =3D=3D5804=3D=3D by 0x647423: lookup_symbol_in_language(char const*, blo= ck const*, domain_enum_tag, language, field_of_this_result*) (symtab.c:1819) =3D=3D5804=3D=3D=20 =3D=3D5804=3D=3D Invalid read of size 1 =3D=3D5804=3D=3D at 0x57696E: ~process_die_scope (dwarf2read.c:8537) =3D=3D5804=3D=3D by 0x57696E: process_die(die_info*, dwarf2_cu*) (dwarf2= read.c:8559) =3D=3D5804=3D=3D by 0x5784BF: process_full_comp_unit (dwarf2read.c:8337) =3D=3D5804=3D=3D by 0x5784BF: process_queue (dwarf2read.c:7828) =3D=3D5804=3D=3D by 0x5784BF: dw2_do_instantiate_symtab(dwarf2_per_cu_da= ta*) (dwarf2read.c:2931) =3D=3D5804=3D=3D by 0x579665: dwarf2_read_symtab(partial_symtab*, objfil= e*) (dwarf2read.c:7694) =3D=3D5804=3D=3D by 0x60A816: psymtab_to_symtab(objfile*, partial_symtab= *) (psymtab.c:768) =3D=3D5804=3D=3D by 0x60CF20: psym_lookup_symbol(objfile*, int, char con= st*, domain_enum_tag) (psymtab.c:519) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_via_quick_fns (symtab.c:2299) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_in_objfile(objfile*, int, ch= ar const*, domain_enum_tag) (symtab.c:2471) =3D=3D5804=3D=3D by 0x647049: lookup_static_symbol(char const*, domain_e= num_tag) (symtab.c:2508) =3D=3D5804=3D=3D by 0x647423: lookup_symbol_aux (symtab.c:2024) =3D=3D5804=3D=3D by 0x647423: lookup_symbol_in_language(char const*, blo= ck const*, domain_enum_tag, language, field_of_this_result*) (symtab.c:1819) =3D=3D5804=3D=3D by 0x6474B5: lookup_symbol(char const*, block const*, domain_enum_tag, field_of_this_result*) (symtab.c:1831) =3D=3D5804=3D=3D by 0x4B12BC: classify_name(parser_state*, block const*,= int) (c-exp.y:2892) =3D=3D5804=3D=3D by 0x4B3B39: c_yylex (c-exp.y:3092) =3D=3D5804=3D=3D by 0x4B3B39: c_yyparse() (c-exp.c:1903) =3D=3D5804=3D=3D by 0x4B6A52: c_parse(parser_state*) (c-exp.y:3264) =3D=3D5804=3D=3D Address 0x62a1123 is 19 bytes inside a block of size 4,06= 4 free'd =3D=3D5804=3D=3D at 0x4C2EDEB: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) =3D=3D5804=3D=3D by 0x777B43: _obstack_free (obstack.c:280) =3D=3D5804=3D=3D by 0x556BCA: free_heap_comp_unit(void*) (dwarf2read.c:2= 2844) =3D=3D5804=3D=3D by 0x556C66: free_one_cached_comp_unit(dwarf2_per_cu_da= ta*) (dwarf2read.c:22929) =3D=3D5804=3D=3D by 0x556CBF: dwarf2_release_queue(void*) (dwarf2read.c:= 7865) =3D=3D5804=3D=3D by 0x523445: do_my_cleanups(cleanup**, cleanup*) (clean= ups.c:154) =3D=3D5804=3D=3D by 0x528A6D: throw_exception_cxx(gdb_exception) (common-exceptions.c:289) =3D=3D5804=3D=3D by 0x528B54: throw_exception (common-exceptions.c:317) =3D=3D5804=3D=3D by 0x528B54: throw_it(return_reason, errors, char const= *, __va_list_tag*) (common-exceptions.c:373) =3D=3D5804=3D=3D by 0x528D95: throw_verror(errors, char const*, __va_lis= t_tag*) (common-exceptions.c:379) =3D=3D5804=3D=3D by 0x673EC3: verror(char const*, __va_list_tag*) (utils= .c:249) =3D=3D5804=3D=3D by 0x57DAA8: error(char const*, ...) (errors.c:43) =3D=3D5804=3D=3D by 0x567365: follow_die_ref(die_info*, attribute const*, dwarf2_cu**) [clone .isra.251] (dwarf2read.c:20728) =3D=3D5804=3D=3D Block was alloc'd at =3D=3D5804=3D=3D at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) =3D=3D5804=3D=3D by 0x528FB7: xmalloc (common-utils.c:44) =3D=3D5804=3D=3D by 0x777907: _obstack_begin_worker (obstack.c:141) =3D=3D5804=3D=3D by 0x5669FF: init_cutu_and_read_dies(dwarf2_per_cu_data= *, abbrev_table*, int, int, void (*)(die_reader_specs const*, unsigned char const*, die_info*, int, void*), void*) (dwarf2read.c:5733) =3D=3D5804=3D=3D by 0x567119: load_full_comp_unit(dwarf2_per_cu_data*, l= anguage) (dwarf2read.c:7991) =3D=3D5804=3D=3D by 0x569761: load_cu(dwarf2_per_cu_data*) (dwarf2read.c= :2889) =3D=3D5804=3D=3D by 0x578383: dw2_do_instantiate_symtab(dwarf2_per_cu_da= ta*) (dwarf2read.c:2916) =3D=3D5804=3D=3D by 0x579665: dwarf2_read_symtab(partial_symtab*, objfil= e*) (dwarf2read.c:7694) =3D=3D5804=3D=3D by 0x60A816: psymtab_to_symtab(objfile*, partial_symtab= *) (psymtab.c:768) =3D=3D5804=3D=3D by 0x60CF20: psym_lookup_symbol(objfile*, int, char con= st*, domain_enum_tag) (psymtab.c:519) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_via_quick_fns (symtab.c:2299) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_in_objfile(objfile*, int, ch= ar const*, domain_enum_tag) (symtab.c:2471) =3D=3D5804=3D=3D by 0x647049: lookup_static_symbol(char const*, domain_e= num_tag) (symtab.c:2508) =3D=3D5804=3D=3D=20 =3D=3D5804=3D=3D Invalid read of size 8 =3D=3D5804=3D=3D at 0x576973: ~process_die_scope (dwarf2read.c:8541) =3D=3D5804=3D=3D by 0x576973: process_die(die_info*, dwarf2_cu*) (dwarf2= read.c:8559) =3D=3D5804=3D=3D by 0x5784BF: process_full_comp_unit (dwarf2read.c:8337) =3D=3D5804=3D=3D by 0x5784BF: process_queue (dwarf2read.c:7828) =3D=3D5804=3D=3D by 0x5784BF: dw2_do_instantiate_symtab(dwarf2_per_cu_da= ta*) (dwarf2read.c:2931) =3D=3D5804=3D=3D by 0x579665: dwarf2_read_symtab(partial_symtab*, objfil= e*) (dwarf2read.c:7694) =3D=3D5804=3D=3D by 0x60A816: psymtab_to_symtab(objfile*, partial_symtab= *) (psymtab.c:768) =3D=3D5804=3D=3D by 0x60CF20: psym_lookup_symbol(objfile*, int, char con= st*, domain_enum_tag) (psymtab.c:519) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_via_quick_fns (symtab.c:2299) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_in_objfile(objfile*, int, ch= ar const*, domain_enum_tag) (symtab.c:2471) =3D=3D5804=3D=3D by 0x647049: lookup_static_symbol(char const*, domain_e= num_tag) (symtab.c:2508) =3D=3D5804=3D=3D by 0x647423: lookup_symbol_aux (symtab.c:2024) =3D=3D5804=3D=3D by 0x647423: lookup_symbol_in_language(char const*, blo= ck const*, domain_enum_tag, language, field_of_this_result*) (symtab.c:1819) =3D=3D5804=3D=3D by 0x6474B5: lookup_symbol(char const*, block const*, domain_enum_tag, field_of_this_result*) (symtab.c:1831) =3D=3D5804=3D=3D by 0x4B12BC: classify_name(parser_state*, block const*,= int) (c-exp.y:2892) =3D=3D5804=3D=3D by 0x4B3B39: c_yylex (c-exp.y:3092) =3D=3D5804=3D=3D by 0x4B3B39: c_yyparse() (c-exp.c:1903) =3D=3D5804=3D=3D by 0x4B6A52: c_parse(parser_state*) (c-exp.y:3264) =3D=3D5804=3D=3D Address 0x62a1090 is 256 bytes inside a block of size 312= free'd =3D=3D5804=3D=3D at 0x4C2EDEB: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) =3D=3D5804=3D=3D by 0x556C66: free_one_cached_comp_unit(dwarf2_per_cu_da= ta*) (dwarf2read.c:22929) =3D=3D5804=3D=3D by 0x556CBF: dwarf2_release_queue(void*) (dwarf2read.c:= 7865) =3D=3D5804=3D=3D by 0x523445: do_my_cleanups(cleanup**, cleanup*) (clean= ups.c:154) =3D=3D5804=3D=3D by 0x528A6D: throw_exception_cxx(gdb_exception) (common-exceptions.c:289) =3D=3D5804=3D=3D by 0x528B54: throw_exception (common-exceptions.c:317) =3D=3D5804=3D=3D by 0x528B54: throw_it(return_reason, errors, char const= *, __va_list_tag*) (common-exceptions.c:373) =3D=3D5804=3D=3D by 0x528D95: throw_verror(errors, char const*, __va_lis= t_tag*) (common-exceptions.c:379) =3D=3D5804=3D=3D by 0x673EC3: verror(char const*, __va_list_tag*) (utils= .c:249) =3D=3D5804=3D=3D by 0x57DAA8: error(char const*, ...) (errors.c:43) =3D=3D5804=3D=3D by 0x567365: follow_die_ref(die_info*, attribute const*, dwarf2_cu**) [clone .isra.251] (dwarf2read.c:20728) =3D=3D5804=3D=3D by 0x56D738: lookup_die_type(die_info*, attribute const= *, dwarf2_cu*) (dwarf2read.c:19743) =3D=3D5804=3D=3D by 0x56CF19: read_subroutine_type (dwarf2read.c:15083) =3D=3D5804=3D=3D by 0x56CF19: read_type_die_1 (dwarf2read.c:19802) =3D=3D5804=3D=3D by 0x56CF19: read_type_die(die_info*, dwarf2_cu*) (dwarf2read.c:19777) =3D=3D5804=3D=3D Block was alloc'd at =3D=3D5804=3D=3D at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) =3D=3D5804=3D=3D by 0x528FB7: xmalloc (common-utils.c:44) =3D=3D5804=3D=3D by 0x5669F1: init_cutu_and_read_dies(dwarf2_per_cu_data= *, abbrev_table*, int, int, void (*)(die_reader_specs const*, unsigned char const*, die_info*, int, void*), void*) (dwarf2read.c:5732) =3D=3D5804=3D=3D by 0x567119: load_full_comp_unit(dwarf2_per_cu_data*, l= anguage) (dwarf2read.c:7991) =3D=3D5804=3D=3D by 0x569761: load_cu(dwarf2_per_cu_data*) (dwarf2read.c= :2889) =3D=3D5804=3D=3D by 0x578383: dw2_do_instantiate_symtab(dwarf2_per_cu_da= ta*) (dwarf2read.c:2916) =3D=3D5804=3D=3D by 0x579665: dwarf2_read_symtab(partial_symtab*, objfil= e*) (dwarf2read.c:7694) =3D=3D5804=3D=3D by 0x60A816: psymtab_to_symtab(objfile*, partial_symtab= *) (psymtab.c:768) =3D=3D5804=3D=3D by 0x60CF20: psym_lookup_symbol(objfile*, int, char con= st*, domain_enum_tag) (psymtab.c:519) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_via_quick_fns (symtab.c:2299) =3D=3D5804=3D=3D by 0x64670B: lookup_symbol_in_objfile(objfile*, int, ch= ar const*, domain_enum_tag) (symtab.c:2471) =3D=3D5804=3D=3D by 0x647049: lookup_static_symbol(char const*, domain_e= num_tag) (symtab.c:2508) =3D=3D5804=3D=3D by 0x647423: lookup_symbol_aux (symtab.c:2024) =3D=3D5804=3D=3D by 0x647423: lookup_symbol_in_language(char const*, blo= ck const*, domain_enum_tag, language, field_of_this_result*) (symtab.c:1819) =3D=3D5804=3D=3D=20 Dwarf Error: Cannot find DIE at 0x0 referenced from DIE at 0x29 [in module /home/yao.qi/SourceCode/gnu/build-without-python-guile/gdb/testsuite/output= s/gdb.dwarf2/dw2-bad-parameter-type/dw2-bad-parameter-type] --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22071-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 06 17:57:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41760 invoked by alias); 6 Nov 2017 17:57:31 -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 41729 invoked by uid 48); 6 Nov 2017 17:57:31 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug python/22223] python event.new_thread does not exist but described in online document Date: Mon, 06 Nov 2017 17:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00115.txt.bz2 Content-length: 944 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22223 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --- Comment #1 from Tom Tromey --- The online document is generated from the gdb tree. You probably have an older gdb, and this functionality was added after the version you have was released. So, I don't think there is a bug here. Normally most linux distros, and "make install", will install the info form of the gdb manual. So for the most consistent results, you should consult the manual that you have. The web page says that the latest release's manual is online, but I see that the links are wrong... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22072-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 06 17:58:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 42494 invoked by alias); 6 Nov 2017 17:58:12 -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 42469 invoked by uid 48); 6 Nov 2017 17:58:12 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug python/22195] Provide a help() method to gdb.Command that overrides the docstring Date: Mon, 06 Nov 2017 17:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: tromey at sourceware dot org 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: bug_status cf_reconfirmed_on cc everconfirmed 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: 2017-q4/txt/msg00116.txt.bz2 Content-length: 656 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22195 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-11-06 CC| |tromey at sourceware dot o= rg Ever confirmed|0 |1 --- Comment #1 from Tom Tromey --- Seems reasonable to me. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22073-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 06 18:31:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88567 invoked by alias); 6 Nov 2017 18:31:59 -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 88437 invoked by uid 48); 6 Nov 2017 18:31:58 -0000 From: "luis.machado at linaro dot org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/18964] [mips] 7.10.1 regression: internal-error: mips-tdep.c:1098: bad register size Date: Mon, 06 Nov 2017 18:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.10 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: luis.machado at linaro dot org X-Bugzilla-Status: ASSIGNED 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: assigned_to 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: 2017-q4/txt/msg00117.txt.bz2 Content-length: 416 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18964 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|luis.machado at linaro dot org |unassigned at sourc= eware dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22074-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 06 18:32:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 99813 invoked by alias); 6 Nov 2017 18:32:15 -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 99665 invoked by uid 48); 6 Nov 2017 18:32:15 -0000 From: "luis.machado at linaro dot org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/18964] [mips] 7.10.1 regression: internal-error: mips-tdep.c:1098: bad register size Date: Mon, 06 Nov 2017 18:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.10 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: luis.machado at linaro dot org X-Bugzilla-Status: ASSIGNED 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: 2017-q4/txt/msg00118.txt.bz2 Content-length: 233 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18964 --- Comment #11 from Luis Machado --- No longer working on it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22076-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 06 18:32:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 104960 invoked by alias); 6 Nov 2017 18:32:32 -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 104909 invoked by uid 48); 6 Nov 2017 18:32:32 -0000 From: "luis.machado at linaro dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/20926] gdb misses breakpoint and stops one line after Date: Mon, 06 Nov 2017 18:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: luis.machado at linaro dot org X-Bugzilla-Status: WAITING 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: 2017-q4/txt/msg00120.txt.bz2 Content-length: 232 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20926 --- Comment #2 from Luis Machado --- No longer working on it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22075-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 06 18:32:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 103242 invoked by alias); 6 Nov 2017 18:32:22 -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 103162 invoked by uid 48); 6 Nov 2017 18:32:22 -0000 From: "luis.machado at linaro dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/20926] gdb misses breakpoint and stops one line after Date: Mon, 06 Nov 2017 18:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: luis.machado at linaro dot org X-Bugzilla-Status: WAITING 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: assigned_to 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: 2017-q4/txt/msg00119.txt.bz2 Content-length: 416 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20926 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|luis.machado at linaro dot org |unassigned at sourc= eware dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22077-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 07 21:48:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 28743 invoked by alias); 7 Nov 2017 21:48:32 -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 28636 invoked by uid 48); 7 Nov 2017 21:48:28 -0000 From: "macro@linux-mips.org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/8210] Linux core files should use linux-thread-db.c Date: Tue, 07 Nov 2017 21:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: macro@linux-mips.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 7.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00121.txt.bz2 Content-length: 505 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8210 Maciej W. Rozycki changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |macro@linux-mips.org --- Comment #8 from Maciej W. Rozycki --- And the cross debug case is now PR threads/22381. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22078-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 07 21:50:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 34476 invoked by alias); 7 Nov 2017 21:50:15 -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 34271 invoked by uid 48); 7 Nov 2017 21:50:15 -0000 From: "macro@linux-mips.org" To: gdb-prs@sourceware.org Subject: [Bug threads/22381] GDB can not read TLS from cross-target core files Date: Tue, 07 Nov 2017 21:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: macro@linux-mips.org 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: bug_status cf_reconfirmed_on cc everconfirmed 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: 2017-q4/txt/msg00122.txt.bz2 Content-length: 825 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22381 Maciej W. Rozycki changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-11-07 CC| |macro@linux-mips.org Ever confirmed|0 |1 --- Comment #1 from Maciej W. Rozycki --- See also: (and PR corefiles/8210). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22079-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 08 08:20:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49953 invoked by alias); 8 Nov 2017 08:20:32 -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 49925 invoked by uid 48); 8 Nov 2017 08:20:31 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22407] New: gdb crash in jit.c Date: Wed, 08 Nov 2017 08:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00123.txt.bz2 Content-length: 1199 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22407 Bug ID: 22407 Summary: gdb crash in jit.c Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- I ran gdb on a process tree using these settings: set detach-on-fork off set non-stop on set pagination off set schedule-multiple on Eventually gdb crashed: ../../gdb/breakpoint.c:13853: internal-error: void delete_breakpoint(breakpoint*): Assertion `bpt !=3D NULL' failed. This call comes from jit.c:free_objfile_data: if (ps_data !=3D NULL && ps_data->objfile =3D=3D objfile) { ps_data->objfile =3D NULL; delete_breakpoint (ps_data->jit_breakpoint); ps_data->cached_code_address =3D 0; } Changing this to check that ps_data->jit_breakpoint !=3D NULL worked for me. However I don't have time to write a test, so I'm sending a bug report inst= ead. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22080-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 08 16:01:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 81449 invoked by alias); 8 Nov 2017 16:01: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 81426 invoked by uid 48); 8 Nov 2017 16:01:23 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/22411] New: cp-name-parser.y doesn't grok templates with function type as template argument Date: Wed, 08 Nov 2017 16:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new 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: palves at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00124.txt.bz2 Content-length: 1634 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22411 Bug ID: 22411 Summary: cp-name-parser.y doesn't grok templates with function type as template argument Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- I noticed that gdb/cp-name-parser.y:cp_demangled_name_to_comp fails to grok this: "A::foo::func(int)" which is a valid symbol name that can result from something like this: ~~~ #include namespace A { template struct foo { void func (int) { printf ("hello"); } }; } A::foo f1; // bad cases instantiated from this one here A::foo f2; int main (int argc, char **argv) { f1.func (argc); f2.func (argc); return 0; } ~~~ $ nm a.out | c++filt | grep func 000000000040062a W A::foo::func(int) 000000000040064c W A::foo::func(int) Running the symbol through test-cp-name-parser, we see: $ ./test-cp-name-parser 'A::foo::func(int)' syntax error, near `int)>::func(int)' While the non-function-type one works OK: $ ./test-cp-name-parser 'A::foo::func(int)' A::foo::func(int) A smaller reproducer: $ ./test-cp-name-parser 'foo' syntax error, near `void)>' Function pointer types work OK: $ ./test-cp-name-parser 'foo' --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22081-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 08 22:17:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88544 invoked by alias); 8 Nov 2017 22:17:03 -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 88133 invoked by uid 48); 8 Nov 2017 22:17:03 -0000 From: "weimin.pan at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18003] Some fails in gdb.base/breakpoint-in-ro-region.exp Date: Wed, 08 Nov 2017 22:17: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: weimin.pan at oracle dot com 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: cc 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: 2017-q4/txt/msg00125.txt.bz2 Content-length: 949 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18003 weimin.pan at oracle dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |weimin.pan at oracle dot c= om --- Comment #1 from weimin.pan at oracle dot com --- The test case is now passing with the upstream gdb: % make check TESTS=3D"gdb.base/breakpoint-in-ro-region.exp" ... ... =3D=3D=3D gdb Summary =3D=3D=3D # of expected passes 40 /home/wepan/binutils-gdb/gdb/testsuite/../../gdb/gdb version=20 8.0.50.20170915-git -nw -nx -data-directory /home/wepan/binutils-gdb/gdb/testsuite/../data-directory make[2]: Leaving directory '/home/wepan/binutils-gdb/gdb/testsuite' make[1]: Leaving directory '/home/wepan/binutils-gdb/gdb/testsuite' --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22082-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 08 22:22:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53834 invoked by alias); 8 Nov 2017 22:22: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 53492 invoked by uid 48); 8 Nov 2017 22:22:22 -0000 From: "weimin.pan at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/16200] Running an inferior with incompatible architecture lead to crash Date: Wed, 08 Nov 2017 22:22: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: weimin.pan at oracle dot com 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: cc 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: 2017-q4/txt/msg00126.txt.bz2 Content-length: 641 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16200 weimin.pan at oracle dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |weimin.pan at oracle dot c= om --- Comment #1 from weimin.pan at oracle dot com --- The crash problem is not reproducible with the upstream gdb: % gdb -batch -ex 'set architecture mips' -ex run /bin/ls Undefined item: "mips". bin tests [Inferior 1 (process 32096) exited normally] --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22083-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Nov 10 14:44:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 77796 invoked by alias); 10 Nov 2017 14:43:59 -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 77564 invoked by uid 48); 10 Nov 2017 14:43:58 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22417] New: Get garbage data when reading .interp section Date: Fri, 10 Nov 2017 14:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00127.txt.bz2 Content-length: 10243 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22417 Bug ID: 22417 Summary: Get garbage data when reading .interp section Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: qiyao at gcc dot gnu.org Target Milestone: --- Build GDB with asan. start GDBserver, $ ./gdbserver/gdbserver :1234 ./testsuite/outputs/gdb.base/catch-syscall/catch-syscall start GDB, $ ./gdb -data-directory=3D$PWD/data-directory -ex "b main" -ex "target rem= ote :1234" -ex "c" -ex "catch syscall execve" -ex "set do_execve =3D 1" -ex "c"= -ex "c" -ex "c" -ex "c" ./testsuite/outputs/gdb.base/catch-syscall/catch-syscall ... ... Breakpoint 1, main (argc=3D1, argv=3D0x7fffffffe3d8) at /home/yao.qi/SourceCode/gnu/build-with-asan/gdb/testsuite/../../../binutils= -gdb/gdb/testsuite/gdb.base/catch-syscall.c:47 47 { Continuing. [Inferior 1 (process 22322) exited normally] start GDBserver again, and type command in GDB again, (gdb) target remote :1234 `target:/home/yao.qi/SourceCode/gnu/build-with-asan/gdb/testsuite/outputs/g= db.base/catch-syscall/catch-syscall' has disappeared; keeping its symbols. Remote debugging using :1234 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D22332=3D=3DERROR: AddressSanitizer: heap-buffer-overflow on address 0x60300004a4ec at pc 0x7f2be286820b bp 0x7fff37d48e40 sp 0x7fff37d485e8 READ of size 29 at 0x60300004a4ec thread T0 #0 0x7f2be286820a in __interceptor_strlen (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x7020a) #1 0xf6745d in xstrdup ../../binutils-gdb/libiberty/xstrdup.c:33 #2 0xb71293 in solib_find_1 ../../binutils-gdb/gdb/solib.c:218 #3 0xb7214f in solib_find(char const*, int*) ../../binutils-gdb/gdb/solib.c:462 #4 0xb72391 in solib_bfd_open(char*) ../../binutils-gdb/gdb/solib.c:503 #5 0x46352c in enable_break ../../binutils-gdb/gdb/solib-svr4.c:2336 #6 0x466a3c in svr4_solib_create_inferior_hook ../../binutils-gdb/gdb/solib-svr4.c:3059 #7 0xb75a71 in solib_create_inferior_hook(int) ../../binutils-gdb/gdb/solib.c:1232 #8 0xa0e8f9 in post_create_inferior(target_ops*, int) ../../binutils-gdb/gdb/infcmd.c:492 #9 0xa28c17 in start_remote(int) ../../binutils-gdb/gdb/infrun.c:3241 #10 0x4ea1b8 in remote_start_remote ../../binutils-gdb/gdb/remote.c:4287 #11 0x4eceef in remote_open_1 ../../binutils-gdb/gdb/remote.c:5144 #12 0x4ea5ff in remote_open ../../binutils-gdb/gdb/remote.c:4382 #13 0xc0ede1 in open_target ../../binutils-gdb/gdb/target.c:358 #14 0x5560e6 in do_sfunc ../../binutils-gdb/gdb/cli/cli-decode.c:138 #15 0x55d6f4 in cmd_func(cmd_list_element*, char*, int) ../../binutils-gdb/gdb/cli/cli-decode.c:1952 #16 0xc42804 in execute_command(char*, int) ../../binutils-gdb/gdb/top.c:608 #17 0x978192 in command_handler(char*) ../../binutils-gdb/gdb/event-top.c:583 #18 0x978a00 in command_line_handler(char*) ../../binutils-gdb/gdb/event-top.c:773 #19 0x97700a in gdb_rl_callback_handler ../../binutils-gdb/gdb/event-top.c:213 #20 0xce9782 in rl_callback_read_char ../../binutils-gdb/readline/callback.c:220 #21 0x976cb7 in gdb_rl_callback_read_char_wrapper_noexcept ../../binutils-gdb/gdb/event-top.c:175 #22 0x976e3b in gdb_rl_callback_read_char_wrapper ../../binutils-gdb/gdb/event-top.c:192 #23 0x977d43 in stdin_event_handler(int, void*) ../../binutils-gdb/gdb/event-top.c:511 #24 0x9741fa in handle_file_event ../../binutils-gdb/gdb/event-loop.c:7= 33 #25 0x974a6c in gdb_wait_for_event ../../binutils-gdb/gdb/event-loop.c:= 859 #26 0x9728ed in gdb_do_one_event() ../../binutils-gdb/gdb/event-loop.c:= 347 #27 0x9729b5 in start_event_loop() ../../binutils-gdb/gdb/event-loop.c:= 371 #28 0xa885b5 in captured_command_loop ../../binutils-gdb/gdb/main.c:329 #29 0xa8af58 in captured_main ../../binutils-gdb/gdb/main.c:1152 #30 0xa8b0d5 in gdb_main(captured_main_args*) ../../binutils-gdb/gdb/main.c:1168 #31 0x40fb88 in main ../../binutils-gdb/gdb/gdb.c:32 #32 0x7f2be0b7882f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #33 0x40f9e8 in _start (/home/yao.qi/SourceCode/gnu/build-with-asan/gdb/gdb+0x40f9e8) 0x60300004a4ec is located 0 bytes to the right of 28-byte region [0x60300004a4d0,0x60300004a4ec) allocated by thread T0 here: #0 0x7f2be2890602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x83a171 in xmalloc ../../binutils-gdb/gdb/common/common-utils.c:44 #2 0x45c948 in find_program_interpreter ../../binutils-gdb/gdb/solib-svr4.c:587 #3 0x4634b9 in enable_break ../../binutils-gdb/gdb/solib-svr4.c:2313 #4 0x466a3c in svr4_solib_create_inferior_hook ../../binutils-gdb/gdb/solib-svr4.c:3059 #5 0xb75a71 in solib_create_inferior_hook(int) ../../binutils-gdb/gdb/solib.c:1232 #6 0xa0e8f9 in post_create_inferior(target_ops*, int) ../../binutils-gdb/gdb/infcmd.c:492 #7 0xa28c17 in start_remote(int) ../../binutils-gdb/gdb/infrun.c:3241 #8 0x4ea1b8 in remote_start_remote ../../binutils-gdb/gdb/remote.c:4287 #9 0x4eceef in remote_open_1 ../../binutils-gdb/gdb/remote.c:5144 #10 0x4ea5ff in remote_open ../../binutils-gdb/gdb/remote.c:4382 #11 0xc0ede1 in open_target ../../binutils-gdb/gdb/target.c:358 #12 0x5560e6 in do_sfunc ../../binutils-gdb/gdb/cli/cli-decode.c:138 #13 0x55d6f4 in cmd_func(cmd_list_element*, char*, int) ../../binutils-gdb/gdb/cli/cli-decode.c:1952 #14 0xc42804 in execute_command(char*, int) ../../binutils-gdb/gdb/top.c:608 #15 0x978192 in command_handler(char*) ../../binutils-gdb/gdb/event-top.c:583 #16 0x978a00 in command_line_handler(char*) ../../binutils-gdb/gdb/event-top.c:773 #17 0x97700a in gdb_rl_callback_handler ../../binutils-gdb/gdb/event-top.c:213 #18 0xce9782 in rl_callback_read_char ../../binutils-gdb/readline/callback.c:220 #19 0x976e3b in gdb_rl_callback_read_char_wrapper ../../binutils-gdb/gdb/event-top.c:192 #20 0x977d43 in stdin_event_handler(int, void*) ../../binutils-gdb/gdb/event-top.c:511 #21 0x9741fa in handle_file_event ../../binutils-gdb/gdb/event-loop.c:7= 33 #22 0x974a6c in gdb_wait_for_event ../../binutils-gdb/gdb/event-loop.c:= 859 #23 0x9728ed in gdb_do_one_event() ../../binutils-gdb/gdb/event-loop.c:= 347 #24 0x9729b5 in start_event_loop() ../../binutils-gdb/gdb/event-loop.c:= 371 #25 0xa885b5 in captured_command_loop ../../binutils-gdb/gdb/main.c:329 #26 0xa8af58 in captured_main ../../binutils-gdb/gdb/main.c:1152 #27 0xa8b0d5 in gdb_main(captured_main_args*) ../../binutils-gdb/gdb/main.c:1168 #28 0x40fb88 in main ../../binutils-gdb/gdb/gdb.c:32 #29 0x7f2be0b7882f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) ------------------------------------- I debug gdb a little bit, set breakpoint on find_program_interpreter, and l= ooks it returns garbage data, because abfd->iovec is not correctly set, 196 nread =3D abfd->iovec->bread (abfd, ptr, size); (gdb) p abfd->iovec $3 =3D (const struct bfd_iovec *) 0x13d9240 (gdb) p abfd $4 =3D (bfd *) 0x612000031e40 (gdb) p *abfd $5 =3D {filename =3D 0x60b00003ca50 "target:/home/yao.qi/SourceCode/gnu/build-with-asan/gdb/testsuite/outputs/g= db.base/catch-syscall/catch-syscall",=20 xvec =3D 0x13e3080 , iostream =3D 0x62100042cd10, iovec= =3D 0x13d9240 , lru_prev =3D 0x0, lru_next =3D 0x0, where =3D 568= ,=20 mtime =3D 1510322635, id =3D 9, format =3D bfd_object, direction =3D read= _direction, flags =3D 33042, cacheable =3D 0, target_defaulted =3D 1, opened_once =3D 0= ,=20 mtime_set =3D 0, no_export =3D 0, output_has_begun =3D 0, has_armap =3D 0, is_thin_archive =3D 0, selective_search =3D 0, is_linker_output =3D 0, is_linker_input =3D 0,=20 plugin_format =3D bfd_plugin_unknown, lto_output =3D 0, plugin_dummy_bfd = =3D 0x0, origin =3D 0, proxy_origin =3D 0, section_htab =3D {table =3D 0x62100044491= 0,=20 newfunc =3D 0xd2a6fd , memory =3D 0x603000038= c50, size =3D 61, count =3D 32, entsize =3D 304, frozen =3D 0}, sections =3D 0x6= 2100042b990,=20 section_last =3D 0x621000445360, section_count =3D 32, archive_pass =3D 0, start_address =3D 4195952, outsymbols =3D 0x0, symcount =3D 0, dynsymcount = =3D 0,=20 arch_info =3D 0x14163c0 , arelt_data =3D 0x0, my_archive= =3D 0x0, archive_next =3D 0x0, archive_head =3D 0x0, nested_archives =3D 0x0, link = =3D { next =3D 0x0, hash =3D 0x0}, tdata =3D {aout_data =3D 0x62100042cd38, a= out_ar_data =3D 0x62100042cd38, oasys_obj_data =3D 0x62100042cd38,=20 oasys_ar_data =3D 0x62100042cd38, coff_obj_data =3D 0x62100042cd38, pe_= obj_data =3D 0x62100042cd38, xcoff_obj_data =3D 0x62100042cd38, ecoff_obj_data =3D=20 0x62100042cd38, ieee_data =3D 0x62100042cd38, ieee_ar_data =3D 0x621000= 42cd38, srec_data =3D 0x62100042cd38, verilog_data =3D 0x62100042cd38,=20 ihex_data =3D 0x62100042cd38, tekhex_data =3D 0x62100042cd38, elf_obj_d= ata =3D 0x62100042cd38, nlm_obj_data =3D 0x62100042cd38, bout_data =3D 0x62100042cd= 38,=20 mmo_data =3D 0x62100042cd38, sun_core_data =3D 0x62100042cd38, sco5_cor= e_data =3D 0x62100042cd38, trad_core_data =3D 0x62100042cd38, som_data =3D 0x62100042c= d38,=20 hpux_core_data =3D 0x62100042cd38, hppabsd_core_data =3D 0x62100042cd38, sgi_core_data =3D 0x62100042cd38, lynx_core_data =3D 0x62100042cd38,=20 osf_core_data =3D 0x62100042cd38, cisco_core_data =3D 0x62100042cd38, versados_data =3D 0x62100042cd38, netbsd_core_data =3D 0x62100042cd38,=20 mach_o_data =3D 0x62100042cd38, mach_o_fat_data =3D 0x62100042cd38, plu= gin_data =3D 0x62100042cd38, pef_data =3D 0x62100042cd38, pef_xlib_data =3D 0x621000= 42cd38,=20 sym_data =3D 0x62100042cd38, any =3D 0x62100042cd38}, usrdata =3D 0x60b= 00003c9a0, memory =3D 0x603000038c80, build_id =3D 0x62100042a8d0} --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22084-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Nov 10 15:15:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 97045 invoked by alias); 10 Nov 2017 15:15:00 -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 96923 invoked by uid 48); 10 Nov 2017 15:15:00 -0000 From: "romeo.berlov at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22418] New: libpthread.so.0 error Date: Fri, 10 Nov 2017 15:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: romeo.berlov at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00128.txt.bz2 Content-length: 6169 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22418 Bug ID: 22418 Summary: libpthread.so.0 error Product: gdb Version: unknown Status: UNCONFIRMED Severity: critical Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: romeo.berlov at gmail dot com Target Milestone: --- Ubuntu 16 Native stacktrace: mono() [0x49ff2f] mono() [0x4f390e] mono() [0x426c19] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390) [0x7f1678e4a390] [0x41348ef0] Debug info from gdb: [New LWP 8023] [New LWP 8024] [New LWP 8029] [New LWP 8030] [New LWP 8031] [New LWP 8032] [New LWP 8033] [New LWP 8038] [New LWP 8041] [New LWP 8042] [New LWP 8055] [New LWP 8058] [New LWP 8059] [New LWP 8069] [New LWP 8074] [New LWP 8088] [New LWP 8092] [New LWP 8139] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x00007f1678e49f7b in __waitpid (pid=3D8140, stat_loc=3D0x7f167997928c, opt= ions=3D0) at ../sysdeps/unix/sysv/linux/waitpid.c:29 29 ../sysdeps/unix/sysv/linux/waitpid.c: =D0=9D=D0=B5=D1=82 =D1=82=D0= =B0=D0=BA=D0=BE=D0=B3=D0=BE =D1=84=D0=B0=D0=B9=D0=BB=D0=B0 =D0=B8=D0=BB=D0= =B8 =D0=BA=D0=B0=D1=82=D0=B0=D0=BB=D0=BE=D0=B3=D0=B0. Id Target Id Frame=20 * 1 Thread 0x7f1679964780 (LWP 8022) "mono" 0x00007f1678e49f7b in __waitpid (pid=3D8140, stat_loc=3D0x7f167997928c, options=3D0) at ../sysdeps/unix/sysv/linux/waitpid.c:29 2 Thread 0x7f1677fff700 (LWP 8023) "mono" pthread_cond_wait@@GLIBC_2.3.2 ()= at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 3 Thread 0x7f1675f15700 (LWP 8024) "Finalizer" 0x00007f1678e48827 in futex_abstimed_wait_cancelable (private=3D0, abstime=3D0x0, expected=3D0, futex_word=3D0x956820) at ../sysdeps/unix/sysv/linux/futex-internal.h:205 4 Thread 0x7f16601f5700 (LWP 8029) "mono" 0x00007f1678b6a70d in poll () at ../sysdeps/unix/syscall-template.S:84 5 Thread 0x7f16601b4700 (LWP 8030) "mono" __clock_nanosleep (clock_id=3D, flags=3D1, req=3D0x7f16601b3db0, rem=3D0x0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48 6 Thread 0x7f165bfff700 (LWP 8031) "Threadpool work" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 7 Thread 0x7f165bdfe700 (LWP 8032) "Threadpool work" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 8 Thread 0x7f165a9cf700 (LWP 8033) "Threadpool work" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 9 Thread 0x7f1647bff700 (LWP 8038) "mono" __clock_nanosleep (clock_id=3D, flags=3D1, req=3D0x7f1647bfe8d0, rem=3D0x0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48 10 Thread 0x7f16473ff700 (LWP 8041) "mono" __clock_nanosleep (clock_id=3D, flags=3D1, req=3D0x7f16473fe880, rem=3D0x0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48 11 Thread 0x7f16471fe700 (LWP 8042) "Timer-Scheduler" pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 12 Thread 0x7f16464fc700 (LWP 8055) "mono" 0x00007f1678b6624d in read () at ../sysdeps/unix/syscall-template.S:84 13 Thread 0x7f16466fd700 (LWP 8058) "mono" __clock_nanosleep (clock_id=3D, flags=3D1, req=3D0x7f16466fc8f0, rem=3D0x0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48 14 Thread 0x7f166896c700 (LWP 8059) "mono" __clock_nanosleep (clock_id=3D, flags=3D1, req=3D0x7f166896b8f0, rem=3D0x0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48 15 Thread 0x7f1645aff700 (LWP 8069) "mono" __clock_nanosleep (clock_id=3D, flags=3D1, req=3D0x7f1645afe6e0, rem=3D0x0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48 16 Thread 0x7f16452fb700 (LWP 8074) "mono" __clock_nanosleep (clock_id=3D, flags=3D1, req=3D0x7f16452fa8f0, rem=3D0x0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48 17 Thread 0x7f16454fc700 (LWP 8088) "mono" __clock_nanosleep (clock_id=3D, flags=3D1, req=3D0x7f16454fb8f0, rem=3D0x0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48 18 Thread 0x7f16468fe700 (LWP 8092) "mono" __clock_nanosleep (clock_id=3D, flags=3D1, req=3D0x7f16468fd7f0, rem=3D0x0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48 19 Thread 0x7f16456fd700 (LWP 8139) "mono" __clock_nanosleep (clock_id=3D, flags=3D1, req=3D0x7f16456fc810, rem=3D0x0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48 Thread 19 (Thread 0x7f16456fd700 (LWP 8139)): #0 __clock_nanosleep (clock_id=3D, flags=3D1, req=3D0x7f16456fc810, rem=3D0= x0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48 #1 0x0000000000617160 in ?? () #2 0x000000000058743a in ?? () #3 0x0000000041e66b92 in ?? () #4 0x00007f1664001900 in ?? () #5 0x00007f167829f018 in ?? () #6 0x00007f167829eeb8 in ?? () #7 0x00007f167829ef80 in ?? () #8 0x00007f167829eeb8 in ?? () #9 0x00007f1664019100 in ?? () #10 0x00007f16456fc870 in ?? () #11 0x00007f16456fc9d0 in ?? () #12 0x00007f16456fc880 in ?? () /build/gdb-cXfXJ3/gdb-7.11.1/gdb/dwarf2-frame.c:690: internal-error: Unknown CFI encountered. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] This is a bug, please report it. For instructions, see: =2E /build/gdb-cXfXJ3/gdb-7.11.1/gdb/dwarf2-frame.c:690: internal-error: Unknown CFI encountered. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries=20 used by your application. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22085-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Nov 11 04:31:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36466 invoked by alias); 11 Nov 2017 04:31:20 -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 36436 invoked by uid 48); 11 Nov 2017 04:31:19 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug testsuite/22420] New: gdb.base/dtrace-probe.exp not working (as in "not able to run") Date: Sat, 11 Nov 2017 04:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone attachments.created Message-ID: 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: 2017-q4/txt/msg00129.txt.bz2 Content-length: 1280 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22420 Bug ID: 22420 Summary: gdb.base/dtrace-probe.exp not working (as in "not able to run") Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: sergiodj at redhat dot com CC: jose.marchesi at oracle dot com Target Milestone: --- Created attachment 10580 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10580&action=3Ded= it gdb.log generated when running the test I've been meaning to file this bug for a while now. Unfortunately gdb.base/dtrace-probe.exp is not working anymore. I cannot really say when= was the last time it worked, but I remember seeing reports of compilation failu= res for quite some time on BuildBot. I am attaching the gdb.log generated when I run "make check-gdb TESTS=3Dgdb.base/dtrace-probe.exp" on my x86_64 Fedora 26 machine. I also = took the liberty to add Jose Marchesi to the Cc list, since he is the original author of the test infrastructure for DTrace probes. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22086-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Nov 12 15:52:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94898 invoked by alias); 12 Nov 2017 15:52:15 -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 94878 invoked by uid 48); 12 Nov 2017 15:52:15 -0000 From: "zed.three at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug fortran/22424] New: gdb.lookup_type fails for Fortran Date: Sun, 12 Nov 2017 15:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: fortran X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: zed.three at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00130.txt.bz2 Content-length: 1429 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22424 Bug ID: 22424 Summary: gdb.lookup_type fails for Fortran Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran Assignee: unassigned at sourceware dot org Reporter: zed.three at gmail dot com Target Milestone: --- `gdb.lookup_type` from the Python API doesn't work for Fortran. In the following Fortran program (compiled with gfortran 7.2.1):=20 program mvce implicit none type :: my_type integer :: my_int end type my_type type(my_type) :: foo foo%my_int =3D 4 print*, foo%my_int end program mvce gives: (gdb) py gdb.lookup_type(str(gdb.parse_and_eval("foo").type)) Traceback (most recent call last): File "", line 1, in gdb.error: No type named Type my_type. Error while executing Python code. Possibly related is that `info types` also doesn't work for Fortran, althou= gh `info types ` does: (gdb) info types All defined types: File ../../../gcc/fortran/libgfortran.h: Language not supported. (gdb) info types my_type All types matching regular expression "my_type": File mvce.f90: Type my_type; --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22087-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 13 13:07:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89798 invoked by alias); 13 Nov 2017 13:07:20 -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 89775 invoked by uid 48); 13 Nov 2017 13:07:20 -0000 From: "rep.dot.nop at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/22430] New: internal-error in block_symbol cp_lookup_bare_symbol Date: Mon, 13 Nov 2017 13:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rep.dot.nop at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00131.txt.bz2 Content-length: 1202 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22430 Bug ID: 22430 Summary: internal-error in block_symbol cp_lookup_bare_symbol Product: gdb Version: 7.12 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: rep.dot.nop at gmail dot com Target Milestone: --- $ echo "int main(void){return 0;}" | gcc -g -xc++ - -o /tmp/o $ gdb -q /tmp/o Reading symbols from /tmp/o...done. (gdb) b foo->bar::baz Function "foo->bar::baz" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (foo->bar::baz) pending. (gdb) run Starting program: /tmp/o=20 /build/gdb-uGdIdO/gdb-7.12/gdb/cp-namespace.c:173: internal-error: block_sy= mbol cp_lookup_bare_symbol(const language_defn*, const char*, const block*, domain_enum, int): Assertion `strstr (name, "::") =3D=3D NULL' failed. GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git Admittedly resembles "Doctor, it hurts when i.." but maybe could be handled more gracefully. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22088-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 13 16:26:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 91424 invoked by alias); 13 Nov 2017 16:26:41 -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 90850 invoked by uid 48); 13 Nov 2017 16:26:41 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/16200] Running an inferior with incompatible architecture lead to crash Date: Mon, 13 Nov 2017 16: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME 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 cc resolution 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: 2017-q4/txt/msg00132.txt.bz2 Content-length: 604 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16200 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |qiyao at gcc dot gnu.org Resolution|--- |WORKSFORME --- Comment #2 from Yao Qi --- I can't reproduce it either. Close it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22089-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 14 09:51:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 72684 invoked by alias); 14 Nov 2017 09:51:28 -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 72652 invoked by uid 48); 14 Nov 2017 09:51:27 -0000 From: "eshaahuja1991 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/7628] re-connect: so target knows that a new session has been started Date: Tue, 14 Nov 2017 09:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: eshaahuja1991 at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00133.txt.bz2 Content-length: 391 https://sourceware.org/bugzilla/show_bug.cgi?id=3D7628 eshaahuja1991 at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eshaahuja1991 at gmail dot= com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22090-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 14 09:52:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 74716 invoked by alias); 14 Nov 2017 09:52:48 -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 74691 invoked by uid 48); 14 Nov 2017 09:52:47 -0000 From: "eshaahuja1991 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/22435] New: During remote debugging, gdbserver is unable to connect to gdb client when the debug session is invoked for the second time Date: Tue, 14 Nov 2017 09:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: eshaahuja1991 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00134.txt.bz2 Content-length: 6767 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22435 Bug ID: 22435 Summary: During remote debugging, gdbserver is unable to connect to gdb client when the debug session is invoked for the second time Product: gdb Version: 7.12.1 Status: UNCONFIRMED Severity: critical Priority: P2 Component: cli Assignee: unassigned at sourceware dot org Reporter: eshaahuja1991 at gmail dot com Target Milestone: --- C:\Users\abc>arm-linux-gnueabihf-gdb GNU gdb (Linaro_GDB-2017.05) 7.12.1.20170417-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=3Di686-w64-mingw32 --target=3Darm-linux-gnueabihf". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) target extended-remote 192.168.2.2:5000 Remote debugging using 192.168.2.2:5000 (gdb) set detach-on-fork off (gdb) set follow-fork-mode child (gdb) attach 12910 Attaching to process 12910 Reading /home/root/myApp from remote target... warning: File transfers from remote targets can be slow. Use "set sysroot" = to access files locally instead. Reading /home/root/myApp from remote target... Reading symbols from target:/home/root/myApp...done. Reading /lib/libdl.so.2 from remote target... Reading /usr/lib/libffi.so.6 from remote target... Reading /lib/libpthread.so.0 from remote target... Reading /usr/lib/libstdc++.so.6 from remote target... Reading /lib/libm.so.6 from remote target... Reading /lib/libgcc_s.so.1 from remote target... Reading /lib/libc.so.6 from remote target... Reading /lib/ld-linux-armhf.so.3 from remote target... Reading symbols from target:/lib/libdl.so.2...Reading /lib/libdl-2.22.so fr= om remote target... Reading /lib/.debug/libdl-2.22.so from remote target... (no debugging symbols found)...done. Reading symbols from target:/usr/lib/libffi.so.6...Reading /usr/lib/libffi.so.6.0.4 from remote target... Reading /usr/lib/.debug/libffi.so.6.0.4 from remote target... (no debugging symbols found)...done. Reading symbols from target:/lib/libpthread.so.0...Reading /lib/libpthread-2.22.so from remote target... Reading /lib/.debug/libpthread-2.22.so from remote target... (no debugging symbols found)...done. Reading symbols from target:/usr/lib/libstdc++.so.6...Reading /usr/lib/libstdc++.so.6.0.21 from remote target... Reading /usr/lib/.debug/libstdc++.so.6.0.21 from remote target... (no debugging symbols found)...done. Reading symbols from target:/lib/libm.so.6...Reading /lib/libm-2.22.so from remote target... Reading /lib/.debug/libm-2.22.so from remote target... (no debugging symbols found)...done. Reading symbols from target:/lib/libgcc_s.so.1...Reading /lib/.debug/libgcc_s.so.1 from remote target... (no debugging symbols found)...done. Reading symbols from target:/lib/libc.so.6...Reading /lib/libc-2.22.so from remote target... Reading /lib/.debug/libc-2.22.so from remote target... (no debugging symbols found)...done. Reading symbols from target:/lib/ld-linux-armhf.so.3...Reading /lib/ld-2.22= .so from remote target... Reading /lib/.debug/ld-2.22.so from remote target... (no debugging symbols found)...done. Reading /lib/ld-linux-armhf.so.3 from remote target... [New Thread 12910.12912] [New Thread 12910.12913] [New Thread 12910.12914] [New Thread 12910.12915] [New Thread 12910.12916] [New Thread 12910.12917] [New Thread 12910.12919] [New Thread 12910.12920] [New Thread 12910.12921] [New Thread 12910.12922] [New Thread 12910.12923] [New Thread 12910.12924] [New Thread 12910.12925] [New Thread 12910.12926] [New Thread 12910.12927] [New Thread 12910.12928] [New Thread 12910.13024] [New Thread 12910.13025] [New Thread 12910.13026] [New Thread 12910.13027] [New Thread 12910.13028] [New Thread 12910.13029] [New Thread 12910.13030] [New Thread 12910.13031] [New Thread 12910.13032] [New Thread 12910.13033] [New Thread 12910.13034] [New Thread 12910.13041] 0x76885924 in nanosleep () from target:/lib/libc.so.6 (gdb) b printWithArgs1 Function "printWithArgs1" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (printWithArgs1) pending. (gdb) c Continuing. Reading /home/root/libdebugTest.so from remote target... [Switching to Thread 12910.13041] Thread 29 "myApp" hit Breakpoint 1, printWithArgs1 (a=3D0x621011b0 " esha",= b=3D12, c=3D45.6699982) at ..\debugTest.c:9 9 printf("\n\n a: %s, b: %d, c: %f\n\n", a, b, c); (gdb) c Continuing. warning: Temporarily disabling breakpoints for unloaded shared library "target:/home/root/libdebugTest.so" The target is not responding to interrupt requests. Stop debugging it? (y or n) deQuit (expect signal SIGINT when the program is resumed) (gdb) detach Cannot execute this command while the target is running. Use the "interrupt" command to stop the target and then try again. (gdb) i inferiors Num Description Executable * 1 process 12910 target:/home/root/myApp (gdb) detach inferior 1 Cannot execute this command while the target is running. Use the "interrupt" command to stop the target and then try again. (gdb) help detach inferior Detach from inferior ID (or list of IDS). (gdb) detach inferior 1 Cannot execute this command while the target is running. Use the "interrupt" command to stop the target and then try again. (gdb) Quit (expect signal SIGINT when the program is resumed) (gdb) detach inferior 1 Cannot execute this command while the target is running. Use the "interrupt" command to stop the target and then try again. (gdb) detach Cannot execute this command while the target is running. Use the "interrupt" command to stop the target and then try again. (gdb) q A debugging session is active. Inferior 1 [process 12910] will be detached. Quit anyway? (y or n) y Cannot execute this command while the target is running. Use the "interrupt" command to stop the target and then try again. At gdbserver side (Remote target), this message is displayed: root@user:~# gdbserver --multi :5000 Listening on port 5000 Remote debugging from host 192.168.2.23 Attached; pid =3D 12910 client connection closed --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22091-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 14 09:55:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78755 invoked by alias); 14 Nov 2017 09:55:05 -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 78731 invoked by uid 48); 14 Nov 2017 09:55:04 -0000 From: "eshaahuja1991 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/22435] During remote debugging, gdbserver is unable to connect to gdb client when the debug session is invoked for the second time Date: Tue, 14 Nov 2017 09:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: 7.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: eshaahuja1991 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00135.txt.bz2 Content-length: 2449 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22435 --- Comment #1 from eshaahuja1991 at gmail dot com --- For debugging an application which is already running on remote target (architecture: arm-linux-gnueabihf), I am using gdb from Linaro toolchain: = GNU gdb (Linaro_GDB-2017.05) 7.12.1.20170417-git and on the target, gdbserver(G= NU gdbserver (GDB) 7.12.1.20170417-git). I have ran the gdbserver on the remote target side in a multi mode as: 'gdbserver --multi :. The commands used for debugging the application (myApp) remotely, which is already runni= ng on remote target are highlighted in the gdb traces below. After the debug is complete, I want to detach my application (myApp) from g= db, because my application (myApp) should be running indefinitely. I tried the commands: detach, detach inferior id, but got the response that "Cannot exe= cute this command while the target is running. Use the "interrupt" command to st= op the target and then try again". I then tried to give interrupt command, keyboard interrupt. After this, I got back the gdb control, then I tried to quit the gdb session using "q" command. I response I got after this is: "A debugging session is active. Inferior 1 [process 12910] will be detached. Q= uit anyway? (y or n)". I entered "y" as my response which gave the response as: "Cannot execute this command while the target is running. Use the "interrup= t" command to stop the target and then try again". This completed my gdb client session. At the remote target side, gdbserver responded to this quit as: "client connection closed".=20 This debug session was successful. But as my gdbserver was in multi mode, w= hen I try to start a new debug session and attach my running application (myApp) again to gdbserver which is already running in multi mode on the same port number, my gdb client at host is unable to connect to gdbserver at target s= ide. This command is not executed: "target extended-remote 192.168.2.2:5000" Earlier with gdb 7.8 and gdbserver 7.8, I was able to successfully detach my running application (myApp). And the above scenario of attaching a process again to the same gdbserver used to work. But gdbserver 7.8 did not support debugging child process, hence i needed to move to gdb client and server 7.= 12, which supports child process debug. Detailed gdb traces are as provided before --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22092-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 14 14:12:21 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 96521 invoked by alias); 14 Nov 2017 14:12:21 -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 96295 invoked by uid 48); 14 Nov 2017 14:12:20 -0000 From: "wsimmons at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20981] Dynamic library debugging on MacOS X 10.12 (Sierra) and dyld 15 is broken Date: Tue, 14 Nov 2017 14:12: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wsimmons at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00136.txt.bz2 Content-length: 395 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20981 Wade Simmons changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wsimmons at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22093-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 14 22:40:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68748 invoked by alias); 14 Nov 2017 22:40:19 -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 68717 invoked by uid 55); 14 Nov 2017 22:40:18 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22388] assertion "xfered_len>0" in target.c for remote connection Date: Tue, 14 Nov 2017 22:40: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00137.txt.bz2 Content-length: 1429 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22388 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Simon Marchi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D92ffd4751920= 30a46a6046177c732372b4dadad5 commit 92ffd475192030a46a6046177c732372b4dadad5 Author: Paul Carroll Date: Tue Nov 14 17:37:37 2017 -0500 Fix 'xfered>0' assertion in target.c for remote connection We have a customer who is using a Corelis gdb server to connect to gdb. Occasionally, the gdb server will send a 0-byte block of memory for a read. When this happens, gdb gives an assertion from target.c: internal-error: target_xfer_partial: Assertion `*xfered_len > 0' failed. This problem is almost identical to that fixed in https://sourceware.org/ml/gdb-patches/2014-02/msg00636.html In this case, remote.c needs to be modified to return TARGET_XFER_EOF instead of TARGET_XFER_OK or TARGET_XFER_UNAVAILABLE when 0 bytes are transferred. gdb/ChangeLog: PR gdb/22388 * remote.c (remote_write_bytes_aux, remote_read_bytes_1, remote_read_bytes, remote_write_qxfer, remote_xfer_partial): Return TARGET_XFER_EOF if size of returned data is 0. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22094-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 14 22:41:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 70324 invoked by alias); 14 Nov 2017 22:41:47 -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 70286 invoked by uid 48); 14 Nov 2017 22:41:46 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22388] assertion "xfered_len>0" in target.c for remote connection Date: Tue, 14 Nov 2017 22:41: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson 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 cc resolution 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: 2017-q4/txt/msg00138.txt.bz2 Content-length: 727 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22388 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |simon.marchi at ericsson d= ot com Resolution|--- |FIXED --- Comment #3 from Simon Marchi --- Fix pushed: https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dcommit;h=3D9= 2ffd475192030a46a6046177c732372b4dadad5 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22095-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 15 23:38:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 130852 invoked by alias); 15 Nov 2017 23:38:09 -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 130822 invoked by uid 48); 15 Nov 2017 23:38:09 -0000 From: "weimin.pan at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20760] Crash when casting variable to char[][] type Date: Wed, 15 Nov 2017 23:38: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: weimin.pan at oracle dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00139.txt.bz2 Content-length: 769 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20760 weimin.pan at oracle dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |weimin.pan at oracle dot c= om --- Comment #1 from weimin.pan at oracle dot com --- Upstream gdb can now handle the "print" command correctly: (gdb) break main Breakpoint 1 at 0x100570: file cast-crash.c, line 3. (gdb) run Starting program: /tmp/20760/a.out=20 Breakpoint 1, main (argc=3D1, argv=3D0x7fefffff508) at cast-crash.c:3 3 return 0; (gdb) print (char[][]) argc $1 =3D {"", "", "", "\001"} --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22096-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Nov 16 15:34:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 39977 invoked by alias); 16 Nov 2017 15:34:46 -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 39521 invoked by uid 48); 16 Nov 2017 15:34:45 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20760] Crash when casting variable to char[][] type Date: Thu, 16 Nov 2017 15:34: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00140.txt.bz2 Content-length: 1987 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20760 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #2 from Pedro Alves --- Casting to "type[]" results in reinterpreting the object as an array of the same size (in bytes) as the original object. (top-gdb) p argc $1 =3D 2 (top-gdb) p /x (char[]) argc $2 =3D {0x2, 0x0, 0x0, 0x0} (top-gdb) p /x (char[4]) argc $3 =3D {0x2, 0x0, 0x0, 0x0} (top-gdb) p sizeof ((char[]) argc) $4 =3D 4 (top-gdb) p /x (char[]) argv $5 =3D {0x98, 0xd9, 0xff, 0xff, 0xff, 0x7f, 0x0, 0x0} (top-gdb) p /z argv $6 =3D 0x00007fffffffd998 (top-gdb) p sizeof ((char[]) argv) $7 =3D 8 (top-gdb) p sizeof ((char[]) argv[0]) $8 =3D 8 (top-gdb) p sizeof ((char[]) argv[0][0]) $9 =3D 1 Not sure exactly how a cast to "type[][]", should behave, though. Should probably be an error -- in C/C++, multidimensional arrays must have bounds for all dimensions except the first. Current master still crashes if you pass 0 as bound size for one of the dimensions: (gdb) p (char[][0])argc /home/pedro/gdb/src/gdb/gdbtypes.c:4819: internal-error: type* copy_type(c= onst type*): Assertion `TYPE_OBJFILE_OWNED (type)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n)=20 Same for "(char[0][])". OOC, while at it, it looks like GDB treats arrays with zero elements as hav= ing sizeof =3D=3D 0, just like GCC, but then when you print the array it prints= "0x0": (top-gdb) p (char[0]) argc $1 =3D 0x0 (top-gdb) ptype $3 type =3D char [0] (top-gdb) p $3 $2 =3D 0x0 That should probably better print an empty array instead: $2 =3D {} --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22097-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Nov 17 15:23:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36216 invoked by alias); 17 Nov 2017 15:23:41 -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 36190 invoked by uid 48); 17 Nov 2017 15:23:41 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22453] New: "maint space" doesn't work with "gdb -ex" Date: Fri, 17 Nov 2017 15:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00141.txt.bz2 Content-length: 659 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22453 Bug ID: 22453 Summary: "maint space" doesn't work with "gdb -ex" Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- I was trying to write a little script to investigate gdb memory use. I tried: gdb -nx -batch -ex 'maint space 1' -ex 'file ./gdb' However, this doesn't work. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22098-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Nov 17 15:33:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 105507 invoked by alias); 17 Nov 2017 15:33:16 -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 105305 invoked by uid 48); 17 Nov 2017 15:33:16 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug cli/22454] New: logging sometimes prints prompt Date: Fri, 17 Nov 2017 15:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00142.txt.bz2 Content-length: 946 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22454 Bug ID: 22454 Summary: logging sometimes prints prompt Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: cli Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- I was trying to script gdb and I noticed that sometimes, the prompt will show up in the logging output. Try this: gdb -nx << END set logging file /tmp/out set logging on print 23 quit END When I do this, /tmp/out contains: (gdb) $1 =3D 23 (gdb) (... and there's no final newline) On irc palves said: probably readline vs no-readline. try "set editing off" in an interactive session. I see prompts in the log with that. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22099-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Nov 17 15:34:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 130544 invoked by alias); 17 Nov 2017 15:34:30 -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 130337 invoked by uid 48); 17 Nov 2017 15:34:29 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug cli/22454] logging sometimes prints prompt Date: Fri, 17 Nov 2017 15:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q4/txt/msg00143.txt.bz2 Content-length: 260 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22454 --- Comment #1 from Tom Tromey --- Sticking 'set editing on' into the script worked for me. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22100-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Nov 17 15:39:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3600 invoked by alias); 17 Nov 2017 15:39:27 -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 3235 invoked by uid 48); 17 Nov 2017 15:39:27 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/8128] setting a breakpoint on C++ member functions Date: Fri, 17 Nov 2017 15: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00144.txt.bz2 Content-length: 632 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8128 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #7 from Sergio Durigan Junior --- Hm, this bug has been closed, but judging by the commit log it was probably= a typo/thinko. I think bug 8218 should have been closed instead, right? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22101-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Nov 17 15:40:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 82382 invoked by alias); 17 Nov 2017 15:40:26 -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 81029 invoked by uid 48); 17 Nov 2017 15:40:24 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/8218] ptype claims destructors have arg Date: Fri, 17 Nov 2017 15:40: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00145.txt.bz2 Content-length: 588 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8218 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #6 from Sergio Durigan Junior --- Bug 8128 has been closed, but commit 5f4d10850850cd95af5e95a16848c8c07a273d= 88 apparently fixes this one. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22102-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Nov 17 16:13:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 84709 invoked by alias); 17 Nov 2017 16:13:24 -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 84674 invoked by uid 48); 17 Nov 2017 16:13:24 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug cli/22455] New: blank line repeats commands even when scripting Date: Fri, 17 Nov 2017 16:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00146.txt.bz2 Content-length: 761 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22455 Bug ID: 22455 Summary: blank line repeats commands even when scripting Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: cli Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- Try this: gdb -nx << END print 23 END I get this in the output: (gdb) $1 =3D 23 (gdb) $2 =3D 23 The reason is that gdb is repeating the command, due to the blank line. I think instead gdb should only repeat when the commands are coming from the tty. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22103-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Nov 17 17:59:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3270 invoked by alias); 17 Nov 2017 17:59:48 -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 3127 invoked by uid 48); 17 Nov 2017 17:59:48 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/22456] New: Can't access minsyms in Rust Date: Fri, 17 Nov 2017 17:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00147.txt.bz2 Content-length: 1072 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22456 Bug ID: 22456 Summary: Can't access minsyms in Rust Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- Currently you can't print minsyms when the current language is rust: $ gdb ./testsuite/outputs/gdb.base/nodebug/nodebug=20 ... (gdb) show language=20 The current source language is "auto; currently c". (gdb) p dataglobal 'dataglobal' has unknown type; cast it to its declared type (gdb) set language rust=20 (gdb) p dataglobal No symbol 'dataglobal' in current context gdb.base/nodebug.exp currently has this to cope: # Rust can't access minsyms? set rust_nosym "No symbol 'top' in current context" which will need to be tweaked if/when the problem is fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22104-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Nov 19 20:24:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 3924 invoked by alias); 19 Nov 2017 20:24:38 -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 3901 invoked by uid 48); 19 Nov 2017 20:24:37 -0000 From: "sebastien15753 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22461] New: breakpoint after mprotect Date: Sun, 19 Nov 2017 20:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sebastien15753 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q4/txt/msg00148.txt.bz2 Content-length: 3620 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22461 Bug ID: 22461 Summary: breakpoint after mprotect Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: sebastien15753 at gmail dot com Target Milestone: --- Created attachment 10622 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10622&action=3Ded= it code that induce the bug I built a shared library (.so) and a binary that use this library. The binary results in the compilation of main.c (in attachment) and is mapp= ed from 0x555555554000 to 0x555555555000. The library results in the compilation of perso.c(in attachment) and is map= ped from 0x7ffff7bd6000 to 7ffff7bd7000. The main() function simply call a function in that library. The function in the library remove the PROT_EXEC flag of the range 0x555555554000 to 0x555555555000 where is mapped the binary, execute another function called `myfunction` in the same library and restore the PROT_EXEC = flag of the range 0x555555554000 to 0x555555555000. Executing it inside gdb with no breakpoints works fine. The bug is, if I set a breakpoint at myfunction() and execute it I have a SIGSEGV signal. One can reproduce the bug by downloading the attached files and compile by using the Makefile.=20 gdb commands for reproduction are : $ gdb binary (gdb) b main (gdb) r (gdb) b myfunction (gdb) c (gdb) si #SIGSEGV An example is done in attachment as a screenshot.=20 Some other useful information : [seb@archlinux code]$ uname -a Linux archlinux 4.13.12-1-ARCH #1 SMP PREEMPT Wed Nov 8 11:54:06 CET 20= 17 x86_64 GNU/Linux [seb@archlinux code]$ gcc -v Utilisation des specs internes. COLLECT_GCC=3Dgcc COLLECT_LTO_WRAPPER=3D/usr/lib/gcc/x86_64-pc-linux-gnu/7.2.0/lto-wrapper Cible : x86_64-pc-linux-gnu Configur=C3=A9 avec: /build/gcc/src/gcc/configure --prefix=3D/usr --libdir= =3D/usr/lib --libexecdir=3D/usr/lib --mandir=3D/usr/share/man --infodir=3D/usr/share/in= fo --with-bugurl=3Dhttps://bugs.archlinux.org/ --enable-languages=3Dc,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=3Dposix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=3Dgnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=3Dgnu --enable-gnu-indirect-function --disable-multilib --disable-werror --enable-checking=3Drelease --enable-default-pie --enable-default-ssp Mod=C3=A8le de thread: posix gcc version 7.2.0 (GCC)=20 [seb@archlinux code]$ gdb -v GNU gdb (GDB) 8.0.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22105-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 20 19:10:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27516 invoked by alias); 20 Nov 2017 19:10:36 -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 27481 invoked by uid 48); 20 Nov 2017 19:10:35 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug build/22206] [8.1 regression] SPARC M7 ADI patches break Solaris build Date: Mon, 20 Nov 2017 19:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com 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: cc target_milestone 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: 2017-q4/txt/msg00149.txt.bz2 Content-length: 788 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22206 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brobecker at gnat dot com Target Milestone|8.1 |--- --- Comment #4 from Joel Brobecker --- Hello. First of all, thank you for working on this and the patch your check= ed in. Since the debugger now has your patch and compiled, I removed the target milestone, as I don't view this as blocking for 8.1 release anymore. If I missed something, please let me know. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22106-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 21 02:00:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 110059 invoked by alias); 21 Nov 2017 02:00:29 -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 110002 invoked by uid 48); 21 Nov 2017 02:00:25 -0000 From: "hi-angel at yandex dot ru" To: gdb-prs@sourceware.org Subject: [Bug macros/22466] New: user-defined function thinks it lacks an argument Date: Tue, 21 Nov 2017 02:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: macros X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hi-angel at yandex dot ru X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00150.txt.bz2 Content-length: 1050 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22466 Bug ID: 22466 Summary: user-defined function thinks it lacks an argument Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: macros Assignee: unassigned at sourceware dot org Reporter: hi-angel at yandex dot ru Target Milestone: --- Steps: 1. Define in gdb_init the following function: define print_arg2 print ($argc =3D=3D 0)? $rsi : *($arg0*)$rsi end 2. Start debugging, and run "print_arg2" Expected results: print of the $rsi register Actual results: error "Missing argument 0 in user function." Additional info: it works with the following, semantically the same, code: define print_arg2 if ($argc =3D=3D 0) print $rsi else print *($arg0*)$rsi end end --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22107-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 21 02:34:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 128483 invoked by alias); 21 Nov 2017 02:34:35 -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 128461 invoked by uid 48); 21 Nov 2017 02:34:35 -0000 From: "hi-angel at yandex dot ru" To: gdb-prs@sourceware.org Subject: [Bug macros/22467] New: No way to undefine defined function Date: Tue, 21 Nov 2017 02:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: macros X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hi-angel at yandex dot ru X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00151.txt.bz2 Content-length: 1233 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22467 Bug ID: 22467 Summary: No way to undefine defined function Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: macros Assignee: unassigned at sourceware dot org Reporter: hi-angel at yandex dot ru Target Milestone: --- gdb has lots of shortcuts, and sometimes user-defined functions overlaps wi= th them. E.g. I was just experimenting with printing within a live debugging session, and without any backthought I defined a function named "p". This effectively made all my commands on breakpoints that using "p" as a shortcu= t to "print" invalid, and worsened experience because I can't use the single let= ter anymore; and there's no way to revert this change other than quitting the session or defining a function "p" with a loop for passing arguments to the actual "print". There should be a way to undefine user-defined functions. There's also a question on SO: https://stackoverflow.com/questions/32378107/delete-user-defined-commands-i= n-gdb --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22108-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 21 03:45:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 24515 invoked by alias); 21 Nov 2017 03:45:38 -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 24477 invoked by uid 48); 21 Nov 2017 03:45:37 -0000 From: "hi-angel at yandex dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/22468] New: gdb don't track the size of the command prompt Date: Tue, 21 Nov 2017 03:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hi-angel at yandex dot ru X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00152.txt.bz2 Content-length: 906 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22468 Bug ID: 22468 Summary: gdb don't track the size of the command prompt Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: hi-angel at yandex dot ru Target Milestone: --- Steps: 1. open gdb 2. type "echo hello", press enter 3. press "Up" to show the command again 4. Press Ctrl+a to set the caret at the beginning of the line Expected results: caret is before the word "echo" Actual results: caret gets set to behind the word "gdb" (i.e. behind the command prompt). Additional info: this might be related to https://sourceware.org/bugzilla/show_bug.cgi?id=3D21689 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22109-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 21 10:49:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 31903 invoked by alias); 21 Nov 2017 10:49:28 -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 31270 invoked by uid 55); 21 Nov 2017 10:49:27 -0000 From: "ro at CeBiTec dot Uni-Bielefeld.DE" To: gdb-prs@sourceware.org Subject: [Bug build/22206] [8.1 regression] SPARC M7 ADI patches break Solaris build Date: Tue, 21 Nov 2017 10:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE 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: 2017-q4/txt/msg00153.txt.bz2 Content-length: 371 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22206 --- Comment #5 from Rainer Orth --- No, that's fine. I do have some notes on how to make this work on Solaris, and even the hardware to test it, but it will probably be some time. Rainer --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22110-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 21 16:13:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 99386 invoked by alias); 21 Nov 2017 16:13:19 -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 99360 invoked by uid 48); 21 Nov 2017 16:13:19 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/16224] add "pahole" functionality to ptype Date: Tue, 21 Nov 2017 16:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc assigned_to 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: 2017-q4/txt/msg00154.txt.bz2 Content-length: 692 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16224 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |sergiodj at redhat dot com Assignee|unassigned at sourceware dot org |sergiodj at redhat = dot com --- Comment #1 from Sergio Durigan Junior --- Patch: https://sourceware.org/ml/gdb-patches/2017-11/msg00435.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22111-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 21 18:47:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35915 invoked by alias); 21 Nov 2017 18:47:11 -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 35888 invoked by uid 48); 21 Nov 2017 18:47:11 -0000 From: "schwab@linux-m68k.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22468] gdb don't track the size of the command prompt Date: Tue, 21 Nov 2017 18:47: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: schwab@linux-m68k.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00155.txt.bz2 Content-length: 248 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22468 --- Comment #1 from Andreas Schwab --- You should add a newline. Type C-l to recover. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22112-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 21 18:49:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64304 invoked by alias); 21 Nov 2017 18:49:50 -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 64281 invoked by uid 48); 21 Nov 2017 18:49:50 -0000 From: "hi-angel at yandex dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/22468] gdb don't track the size of the command prompt Date: Tue, 21 Nov 2017 18:49: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hi-angel at yandex dot ru X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00156.txt.bz2 Content-length: 437 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22468 --- Comment #2 from Hi-Angel --- I understand that, I mostly reported because I think this might be caused by similar problem of not tracking the size as the other bug with colors, wher= e it is more serious, serious enough to not actually use colors in command promp= t. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22113-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 21 21:56:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23269 invoked by alias); 21 Nov 2017 21:56:53 -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 23241 invoked by uid 48); 21 Nov 2017 21:56:52 -0000 From: "schwab@linux-m68k.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22468] gdb don't track the size of the command prompt Date: Tue, 21 Nov 2017 21:56: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: schwab@linux-m68k.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00157.txt.bz2 Content-length: 298 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22468 --- Comment #3 from Andreas Schwab --- If you want to include non-printing characters in the prompt you need to bracket them with \[ \]. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22114-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 22 02:06:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 32436 invoked by alias); 22 Nov 2017 02:06:29 -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 32410 invoked by uid 48); 22 Nov 2017 02:06:29 -0000 From: "hi-angel at yandex dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/22468] gdb don't track the size of the command prompt Date: Wed, 22 Nov 2017 02:06: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hi-angel at yandex dot ru X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00158.txt.bz2 Content-length: 486 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22468 --- Comment #4 from Hi-Angel --- (In reply to Andreas Schwab from comment #3) > If you want to include non-printing characters in the prompt you need to > bracket them with \[ \]. It doesn't help. I just tried reproducing the linked bug #21689 but with surrouding the prompt with \[ and \] =E2=80=94 and it still repro. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22115-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 22 05:31:07 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109317 invoked by alias); 22 Nov 2017 05:30:36 -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 67044 invoked by uid 48); 22 Nov 2017 05:29:46 -0000 From: "hi-angel at yandex dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/22472] New: Arguments evaluation doesn't always work Date: Wed, 22 Nov 2017 05:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hi-angel at yandex dot ru X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00159.txt.bz2 Content-length: 1038 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22472 Bug ID: 22472 Summary: Arguments evaluation doesn't always work Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: hi-angel at yandex dot ru Target Milestone: --- Steps to reproduce: 1. start `gdb -nh` 2. define the following command (gdb) define argnum Type commands for definition of "argnum". End with a line saying just "end". >print $argc >end (gdb)=20 3. type the following: (gdb) argnum (1+1) $1 =3D 1 works as expected. 4. type the following: (gdb) argnum (1 + 1) $2 =3D 3 Expected: same result as at point 3. Actual result: gdb did not evaluate the argument, and passed three instead = of one. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22116-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 22 09:52:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 121068 invoked by alias); 22 Nov 2017 09:52:32 -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 121010 invoked by uid 48); 22 Nov 2017 09:52:32 -0000 From: "michael.platzer at hotmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/22474] New: Python API: stop event: GDB crashes if function called through parse_and_eval() exits Date: Wed, 22 Nov 2017 09:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: michael.platzer at hotmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q4/txt/msg00160.txt.bz2 Content-length: 3397 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22474 Bug ID: 22474 Summary: Python API: stop event: GDB crashes if function called through parse_and_eval() exits Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: michael.platzer at hotmail dot com Target Milestone: --- Created attachment 10626 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10626&action=3Ded= it The *.c and *.py files to reproduce the error. OS: 4.13.11-1-ARCH x86_64 GNU/Linux GDB version: GNU gdb (GDB) 8.0.1.20171108-git (local build) GCC version: gcc (GCC) 7.2.0 (arch linux package) Python version: Python 3.6.3 (arch linux package) Note: GNU gdb (GDB) 8.0.1 (arch linux package) behaves identically I execute GDB in batch mode, running a python script which uses an event handler to catch stop events caused by breakpoints; within the event handle= r, calling a function in the executable (using gdb.parse_and_eval()) which in = turn calls exit(3) produces an assertion violation in thread.c: ../../gdb/thread.c:101: internal-error: thread_info* inferior_thread(): Assertion `tp' failed. STEPS TO REPRODUCE: 1. Create a *.c and a *.py file, with following content: ---------------------------------------------------------------------------= ----- $ cat foo_exit.c #include void foo() { exit(0); } int main(int argc, char *argv[]) { return 0; } $ cat bp_stop.py import gdb def stop_handler(ev): if type(ev) is gdb.BreakpointEvent: try: gdb.parse_and_eval('foo()') except gdb.error as err: print('caught gdb error: ' + str(err)) gdb.events.stop.connect(stop_handler) gdb.execute('break main') gdb.execute('run') ---------------------------------------------------------------------------= ----- 2. Compile the *.c file: ---------------------------------------------------------------------------= ----- $ gcc -g -o foo_exit foo_exit.c ---------------------------------------------------------------------------= ----- 3. Run GDB: ---------------------------------------------------------------------------= ----- $ gdb --batch -x bp_stop.py foo_exit Breakpoint 1 at 0x663: file foo_exit.c, line 8. [Inferior 1 (process 3415) exited normally] caught gdb error: The program being debugged exited while in a function cal= led from GDB. Evaluation of the expression containing the function (foo) will be abandoned. ../../gdb/thread.c:101: internal-error: thread_info* inferior_thread(): Assertion `tp' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] This is a bug, please report it. For instructions, see: . ../../gdb/thread.c:101: internal-error: thread_info* inferior_thread(): Assertion `tp' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] Aborted (core dumped) ---------------------------------------------------------------------------= ----- --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22117-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 22 09:54:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 100266 invoked by alias); 22 Nov 2017 09:54:43 -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 100244 invoked by uid 48); 22 Nov 2017 09:54:42 -0000 From: "michael.platzer at hotmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/22475] New: Python API: breakpoint subclass: GDB crashes if function called through parse_and_eval() exits Date: Wed, 22 Nov 2017 09:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: michael.platzer at hotmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q4/txt/msg00161.txt.bz2 Content-length: 3346 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22475 Bug ID: 22475 Summary: Python API: breakpoint subclass: GDB crashes if function called through parse_and_eval() exits Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: michael.platzer at hotmail dot com Target Milestone: --- Created attachment 10627 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10627&action=3Ded= it The *.c and *.py files to reproduce the error. OS: 4.13.11-1-ARCH x86_64 GNU/Linux GDB version: GNU gdb (GDB) 8.0.1.20171108-git (local build) GCC version: gcc (GCC) 7.2.0 (arch linux package) Python version: Python 3.6.3 (arch linux package) Note: GNU gdb (GDB) 8.0.1 (arch linux package) behaves identically I execute GDB in batch mode, running a python script which uses a subclass = of gdb.Breakpoint; within the stop() method of this subclass, calling a functi= on in the executable (using gdb.parse_and_eval()) which in turn calls exit(3) produces an assertion violation in thread.c: ../../gdb/thread.c:1123: internal-error: void finish_thread_state(ptid_t): Assertion `tp' failed. STEPS TO REPRODUCE: 1. Create a *.c and a *.py file, with following content: ---------------------------------------------------------------------------= ----- $ cat foo_exit.c #include void foo() { exit(0); } int main(int argc, char *argv[]) { return 0; } $ cat bp_stop.py import gdb class MainBreak(gdb.Breakpoint): def stop(self): try: gdb.parse_and_eval('foo()') except gdb.error as err: print('caught gdb error: ' + str(err)) MainBreak('main') gdb.execute('run') ---------------------------------------------------------------------------= ----- 2. Compile the *.c file: ---------------------------------------------------------------------------= ----- $ gcc -g -o foo_exit foo_exit.c ---------------------------------------------------------------------------= ----- 3. Run GDB: ---------------------------------------------------------------------------= ----- $ gdb --batch -x bp_stop.py foo_exit Breakpoint 1 at 0x663: file foo_exit.c, line 8. [Inferior 1 (process 3843) exited normally] caught gdb error: The program being debugged exited while in a function cal= led from GDB. Evaluation of the expression containing the function (foo) will be abandoned. ../../gdb/thread.c:1123: internal-error: void finish_thread_state(ptid_t): Assertion `tp' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] This is a bug, please report it. For instructions, see: . ../../gdb/thread.c:1123: internal-error: void finish_thread_state(ptid_t): Assertion `tp' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] Aborted (core dumped) ---------------------------------------------------------------------------= ----- --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22118-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 22 18:45:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107550 invoked by alias); 22 Nov 2017 18:45:55 -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 107519 invoked by uid 48); 22 Nov 2017 18:45:55 -0000 From: "schwab@linux-m68k.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22472] Arguments evaluation doesn't always work Date: Wed, 22 Nov 2017 18:45: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: schwab@linux-m68k.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00162.txt.bz2 Content-length: 533 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22472 Andreas Schwab changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Andreas Schwab --- Argument parsing is purely textual. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22119-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 22 20:41:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 44777 invoked by alias); 22 Nov 2017 20:41:17 -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 44752 invoked by uid 48); 22 Nov 2017 20:41:17 -0000 From: "hi-angel at yandex dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/22472] Arguments evaluation doesn't always work Date: Wed, 22 Nov 2017 20:41: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hi-angel at yandex dot ru X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: 2017-q4/txt/msg00163.txt.bz2 Content-length: 272 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22472 --- Comment #2 from Hi-Angel --- @Andreas I am sorry about that. But why did you close the bug as invalid? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22120-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Nov 23 01:13:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 105116 invoked by alias); 23 Nov 2017 01:13:39 -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 105083 invoked by uid 48); 23 Nov 2017 01:13:39 -0000 From: "b2.temp at gmx dot com" To: gdb-prs@sourceware.org Subject: [Bug d/22480] New: `ptype` returns `struct` for D classes Date: Thu, 23 Nov 2017 01:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: d X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: b2.temp at gmx dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00164.txt.bz2 Content-length: 775 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22480 Bug ID: 22480 Summary: `ptype` returns `struct` for D classes Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: d Assignee: unassigned at sourceware dot org Reporter: b2.temp at gmx dot com Target Milestone: --- --- module runnable; class A {} void main() { A a; } --- `ptype a` gives --- type =3D struct runnable.A { } * --- which means that there's not the hint required if we must `print a` or=20 `print *a` the later syntax is required for a class. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22121-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Nov 23 11:54:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 115723 invoked by alias); 23 Nov 2017 11:54:47 -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 115697 invoked by uid 48); 23 Nov 2017 11:54:45 -0000 From: "hi-angel at yandex dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/22481] New: Python Exception Trying to read string with inappropriate type `int'.: Date: Thu, 23 Nov 2017 11:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hi-angel at yandex dot ru X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00165.txt.bz2 Content-length: 1574 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22481 Bug ID: 22481 Summary: Python Exception Trying to read string with inappropriate type `int'.: Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: hi-angel at yandex dot ru Target Milestone: --- #Steps to reproduce: 1. Write the following code to ~/gdb.py=20 class my_print: def __init__(self, val): self.val =3D val def to_string(self): return self.val.string() def lookup_type_my_int (val): if str(val.type) =3D=3D 'int': return my_print(val) return None gdb.pretty_printers.append(lookup_type_my_int) 2. Run `gdb -nh` 3. type `source ~/gdb.py` 4. type `print 1` Expected result: the value of "val" is printed Actual results: error "$1 =3D Python Exception Trying t= o read string with inappropriate type `int'.:". #Additional info: python version 3.6.3 Some more results because this issue might be useful for someone coming from google in attempt to use pretty printers: Using "return str(self.val)" results in "$1 =3D Python Exception maximum recursion depth exceeded in comparison: 1" And using simply "return self.val" results in "[1] 29554 segmentation fa= ult (core dumped) gdb -q -nh" --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22122-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Nov 23 22:20:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 119166 invoked by alias); 23 Nov 2017 22:20:49 -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 119130 invoked by uid 48); 23 Nov 2017 22:20:48 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug python/22475] Python API: breakpoint subclass: GDB crashes if function called through parse_and_eval() exits Date: Thu, 23 Nov 2017 22:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: bug_status cf_reconfirmed_on cc everconfirmed 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: 2017-q4/txt/msg00166.txt.bz2 Content-length: 654 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22475 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-11-23 CC| |qiyao at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Yao Qi --- Reproduced with GDB 8.0.1, 8.0, and 7.11.1. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22123-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Nov 23 22:22:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 124647 invoked by alias); 23 Nov 2017 22:22:34 -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 124599 invoked by uid 48); 23 Nov 2017 22:22:34 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug python/22475] Python API: breakpoint subclass: GDB crashes if function called through parse_and_eval() exits Date: Thu, 23 Nov 2017 22:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone 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: 2017-q4/txt/msg00167.txt.bz2 Content-length: 509 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22475 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.1 --- Comment #2 from Yao Qi --- Set the target milestone to 8.1, although it is not a regression from last release. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22124-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Nov 24 03:53:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89601 invoked by alias); 24 Nov 2017 03:53:21 -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 89579 invoked by uid 48); 24 Nov 2017 03:53:21 -0000 From: "17joshuanewcomb at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug exp/22487] New: `51-var-list-children var3` is not returning within 10 seconds Date: Fri, 24 Nov 2017 03:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: 17joshuanewcomb at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00168.txt.bz2 Content-length: 1231 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22487 Bug ID: 22487 Summary: `51-var-list-children var3` is not returning within 10 seconds Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: exp Assignee: unassigned at sourceware dot org Reporter: 17joshuanewcomb at gmail dot com Target Milestone: --- I have a rather severe problem using gdb through eclipse. The command "-var-list-children var3" fails to return during certain stages of debuggin= g. When this happens, it doesn't just lock up, it causes a fairly rapid memory leak, forcing me to terminate gdb and the debugging session with it. On my system, its a very reproducable problem. GDB 8.0.1-1 Arch Linux Kernel version 4.13.12-1 IDE: Eclipse CDT latest P.S. I already filed a bug report to the eclipse devs, they found nothing w= rong with their software, and told me to come to you with this problem, I am hop= ing you can help fix this. I really depend on GDB to get anything done in the w= orld of programming. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22125-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Nov 24 22:27:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 1361 invoked by alias); 24 Nov 2017 22:27:29 -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 1327 invoked by uid 48); 24 Nov 2017 22:27:29 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug macros/22467] No way to undefine defined function Date: Fri, 24 Nov 2017 22:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: macros X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed 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: 2017-q4/txt/msg00169.txt.bz2 Content-length: 761 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22467 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-11-24 CC| |sergiodj at redhat dot com Assignee|unassigned at sourceware dot org |sergiodj at redhat = dot com Ever confirmed|0 |1 --- Comment #1 from Sergio Durigan Junior --- I have a patch for that. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22126-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Nov 25 01:39:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 125754 invoked by alias); 25 Nov 2017 01:39:30 -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 125714 invoked by uid 48); 25 Nov 2017 01:39:30 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22491] New: gdb.arch/amd64-stap-optional-prefix.exp fails after probe C++-ification patch Date: Sat, 25 Nov 2017 01:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00170.txt.bz2 Content-length: 1296 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22491 Bug ID: 22491 Summary: gdb.arch/amd64-stap-optional-prefix.exp fails after probe C++-ification patch Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: sergiodj at redhat dot com Reporter: sergiodj at redhat dot com Target Milestone: 8.1 Pedro has pointed out that a regression has been introduced by my C++-ifica= tion patches touching the probe interfaces (https://sourceware.org/ml/gdb-patches/2017-11/msg00525.html). The problem happens on gdb.arch/amd64-stap-optional-prefix.exp: 77 break -pstap bar 78 Breakpoint 3 at 0x40048d 79 (gdb) PASS: gdb.arch/amd64-stap-optional-prefix.exp: bar: break -pstap = bar 80 continue 81 Continuing. 82=20 83 Program received signal SIGILL, Illegal instruction. 84 main () at amd64-stap-optional-prefix.S:26 85 26 STAP_PROBE1(probe, foo, (%rsp)) It is still not clear why, but I am investigating. I am marking this bug's Target milestone to 8.1, because it is a regression that shouldn't be prese= nt in the next branch. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22127-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Nov 25 01:39:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 126136 invoked by alias); 25 Nov 2017 01:39:41 -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 126115 invoked by uid 48); 25 Nov 2017 01:39:41 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22491] gdb.arch/amd64-stap-optional-prefix.exp fails after probe C++-ification patch Date: Sat, 25 Nov 2017 01:39: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status 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: 2017-q4/txt/msg00171.txt.bz2 Content-length: 388 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22491 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22129-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Nov 25 06:25:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63514 invoked by alias); 25 Nov 2017 06:25:42 -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 63494 invoked by uid 48); 25 Nov 2017 06:25:42 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22491] gdb.arch/amd64-stap-optional-prefix.exp fails after probe C++-ification patch Date: Sat, 25 Nov 2017 06:25: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: 8.1 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00173.txt.bz2 Content-length: 568 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22491 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Sergio Durigan Junior --- Fixed. 685de8c2990a04fba5e2954b7ff089a2c641071f --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22128-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Nov 25 06:25:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 62456 invoked by alias); 25 Nov 2017 06:25:00 -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 62437 invoked by uid 55); 25 Nov 2017 06:25:00 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22491] gdb.arch/amd64-stap-optional-prefix.exp fails after probe C++-ification patch Date: Sat, 25 Nov 2017 06:25: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00172.txt.bz2 Content-length: 2838 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22491 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D685de8c2990a= 04fba5e2954b7ff089a2c641071f commit 685de8c2990a04fba5e2954b7ff089a2c641071f Author: Sergio Durigan Junior Date: Sat Nov 25 01:13:03 2017 -0500 Fix PR gdb/22491: Regression when setting SystemTap probe semaphores Pedro has kindly pointed out that gdb.arch/amd64-stap-optional-prefix.exp was failing after my C++-ification patches touching the probe interface. The failure is kind of cryptic: 77 break -pstap bar 78 Breakpoint 3 at 0x40048d 79 (gdb) PASS: gdb.arch/amd64-stap-optional-prefix.exp: bar: break -ps= tap bar 80 continue 81 Continuing. 82 83 Program received signal SIGILL, Illegal instruction. 84 main () at amd64-stap-optional-prefix.S:26 85 26 STAP_PROBE1(probe, foo, (%rsp)) It took me a while to figure out where this SIGILL is coming from. Initially I thought it was something related to writing registers to the inferior when dealing with probe arguments, but I discarded this since the arguments were not touching any registers. In the end, this was a mistake that was introduced during the review process of the patch. When setting/clearing a SystemTap probe's semaphore, the code was using 'm_address' (which refers the probe's address) instead of 'm_sem_addr' (which refers to the semaphore's address). This caused GDB to write a bogus value in the wrong memory position, which in turn caused the SIGILL. I am pushing this patch to correct the mistake. On a side note: I told Pedro that the BuildBot hadn't caught the failure during my try build, and for a moment there was a suspicion that the BuildBot might be at fault here. However, I investigate this and noticed that I only did one try build, with a patch that was correctly using 'm_sem_addr' where applicable, and therefore no failure should have happened indeed. I probably should have requested another try build after addressing the review's comments, but they were mostly basic and I didn't think it was needed. Oh, well. 2017-11-25 Sergio Durigan Junior PR gdb/22491 * stap-probe.c (relocate_address): New function. (stap_probe::get_relocated_address): Use 'relocate_address'. (stap_probe::set_semaphore): Use 'relocate_address' and pass 'm_sem_addr'. (stap_probe::clear_semaphore): Likewise. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22130-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Nov 25 16:48:43 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 2648 invoked by alias); 25 Nov 2017 16:48:43 -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 2487 invoked by uid 48); 25 Nov 2017 16:48:26 -0000 From: "hi-angel at yandex dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/22472] Arguments evaluation doesn't always work Date: Sat, 25 Nov 2017 16:48: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hi-angel at yandex dot ru X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: 2017-q4/txt/msg00174.txt.bz2 Content-length: 533 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22472 --- Comment #3 from Hi-Angel --- @Andreas let me elaborate: such behavior is irrational for obvious reasons.= I know a lot of languages, but not a single one, where passing an arithmetic operation in braces without whitespace works different from doing the same = with whitespace. So, do you have a link to docs or whatever to confirm that this is a valid behavior? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22131-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Nov 26 09:58:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 105671 invoked by alias); 26 Nov 2017 09:58:42 -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 105617 invoked by uid 48); 26 Nov 2017 09:58:41 -0000 From: "kryukov at frtk dot ru" To: gdb-prs@sourceware.org Subject: [Bug build/22495] New: remote-sim.c should be built with -Wno-format-literal Date: Sun, 26 Nov 2017 09:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kryukov at frtk dot ru X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00175.txt.bz2 Content-length: 1801 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22495 Bug ID: 22495 Summary: remote-sim.c should be built with -Wno-format-literal Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: kryukov at frtk dot ru Target Milestone: --- Hi remote-sim.c contains calls of `vfprintf_filtered` function with non-literal format. Clang is able to track that if '-Wformat-literal' warning is enable= d, leading to compilation failure: clang++-5.0 -x c++ -std=3Dgnu++11 -g -O2 -I. -I. -I./common -I./config -DLOCALEDIR=3D"\"/home/travis/build/pavelkryukov/gnu-binutils-clang/binutil= s-gdb/cross/mips/share/locale\"" -DHAVE_CONFIG_H -I./../include/opcode -I./../opcodes/.. -I./../readline/..= =20 -I../bfd -I./../bfd -I./../include -I../libdecnumber -I./../libdecnumber=20 -I./gnulib/import -Ibuild-gnulib/import -DTUI=3D1 -I/usr/include/python2= .7 -I/usr/include/python2.7 -Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-body -Wno-sign-compare -Wno-narrowing -Wno-mismatched-tags -Wformat-nonliteral -Werror -c -o remote-sim.o -MT remote-sim.o -MMD -MP -MF ./.deps/remote-sim= .Tpo remote-sim.c remote-sim.c:386:34: error: format string is not a string literal [-Werror,-Wformat-nonliteral] vfprintf_filtered (gdb_stdout, format, args); As a workaround, we may add an exception for `remote-sim.c` in the same man= ner=20 as for `target-float.c`. I pushed a patch to master branch of this reposito= ry: https://github.com/pavelkryukov/binutils-gdb.git --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22132-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Nov 26 09:59:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 106498 invoked by alias); 26 Nov 2017 09:59:30 -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 106474 invoked by uid 48); 26 Nov 2017 09:59:29 -0000 From: "kryukov at frtk dot ru" To: gdb-prs@sourceware.org Subject: [Bug build/22495] remote-sim.c should be built with -Wno-format-nonliteral Date: Sun, 26 Nov 2017 09:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kryukov at frtk dot ru X-Bugzilla-Status: UNCONFIRMED 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: short_desc 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: 2017-q4/txt/msg00176.txt.bz2 Content-length: 525 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22495 Pavel I. Kryukov changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|remote-sim.c should be |remote-sim.c should be |built with |built with |-Wno-format-literal |-Wno-format-nonliteral --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22133-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Nov 26 17:34:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 48920 invoked by alias); 26 Nov 2017 17:34:34 -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 48898 invoked by uid 48); 26 Nov 2017 17:34:34 -0000 From: "zed.three at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug fortran/22497] New: Unable to access base type of derived types Date: Sun, 26 Nov 2017 17:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: fortran X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: zed.three at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00177.txt.bz2 Content-length: 1276 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22497 Bug ID: 22497 Summary: Unable to access base type of derived types Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran Assignee: unassigned at sourceware dot org Reporter: zed.three at gmail dot com Target Milestone: --- Given the program below, I get the following error when trying to print the base type of "bar": (gdb) p bar%my_type=20 A syntax error in expression, near `my_type'. (gdb) p bar%my_int=20 There is no member named my_int. (gdb) p bar%my_type%my_int A syntax error in expression, near `my_type%my_int'. (gdb) p bar $1 =3D ( my_type =3D ( my_int =3D 1 ) ) Note that all of the expressions I'm trying to print are valid Fortran expressions, and that `p foo%my_int` works MVCE: program mvce implicit none type :: my_type integer :: my_int end type my_type type, extends(my_type) :: extended_type end type extended_type type(my_type) :: foo type(extended_type) :: bar foo%my_int =3D 0 bar%my_int =3D 1 print*, foo, bar end program mvce --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22134-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Nov 26 17:49:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 25463 invoked by alias); 26 Nov 2017 17:49:18 -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 25441 invoked by uid 48); 26 Nov 2017 17:49:17 -0000 From: "zed.three at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/22498] New: Can't access type component when calling script from command line Date: Sun, 26 Nov 2017 17:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: zed.three at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00178.txt.bz2 Content-length: 1273 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22498 Bug ID: 22498 Summary: Can't access type component when calling script from command line Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: zed.three at gmail dot com Target Milestone: --- Running the "reproducer.py" script below from the command line results in: {my_char =3D 'good'} while calling it from inside gdb produces the correct result: (gdb) py exec(open("reproducer.py").read()) ... ( my_char =3D 'good' ) 'good' Changing `my_char` to type `integer` does seem to work though. --- mvce.f90: program mvce implicit none type :: my_type character(len=3D4) :: my_char end type my_type type(my_type) :: foo foo%my_char =3D "good" print*, foo%my_char end program mvce --- reproducer.py: gdb.execute("file a.out") gdb.execute("b 11") gdb.execute("run") foo =3D gdb.parse_and_eval("foo") print(foo, foo['my_char']) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22135-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Nov 26 17:49:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 25839 invoked by alias); 26 Nov 2017 17:49:29 -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 25816 invoked by uid 48); 26 Nov 2017 17:49:28 -0000 From: "zed.three at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/22498] Can't access type component when calling script from command line Date: Sun, 26 Nov 2017 17:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: zed.three at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00179.txt.bz2 Content-length: 382 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22498 zed.three at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zed.three at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22137-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Nov 26 19:05:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 110361 invoked by alias); 26 Nov 2017 19:05: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 110337 invoked by uid 48); 26 Nov 2017 19:05:51 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22499] 8.0 regression: wrongly read $xmm0 Date: Sun, 26 Nov 2017 19:05: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_gcctarget cc cf_gcchost target_milestone 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: 2017-q4/txt/msg00181.txt.bz2 Content-length: 665 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22499 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |x86_64-linux CC| |jan.kratochvil at redhat d= ot com, | |palves at redhat dot com Host| |x86_64-linux Target Milestone|--- |8.1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22136-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Nov 26 19:05:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109774 invoked by alias); 26 Nov 2017 19:05:09 -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 109747 invoked by uid 48); 26 Nov 2017 19:05:09 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22499] New: 8.0 regression: wrongly read $xmm0 Date: Sun, 26 Nov 2017 19:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00180.txt.bz2 Content-length: 1399 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22499 Bug ID: 22499 Summary: 8.0 regression: wrongly read $xmm0 Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Target Milestone: --- gdb prints wrong result of double variable in -mavx mode https://bugzilla.redhat.com/show_bug.cgi?id=3D1515209 by the courtesy of Peter Steinbach 398e081380a204e3b9fb4eb4da069ccf471f930e is the first bad commit commit 398e081380a204e3b9fb4eb4da069ccf471f930e Author: Pedro Alves Date: Wed Sep 30 19:23:39 2015 +0100 x86/Linux: reenable all-stop on top of non-stop cat test.cpp < int main(int argc, char** argv){ double rvalue =3D 0.3; std::cout << "- " << rvalue << "\n"; double a,b; rvalue =3D 0.3; std::cout << ": " << rvalue << "\n"; return rvalue < 1. ? 0 : 1; } EOH gdb -batch ./test -ex 'b 5' -ex r -ex step -ex 'p rvalue' Actual results: $1 =3D 7.0607433379231282e-184 Expected results: $1 =3D 0.29999999 gdb -batch ./test -ex 'b 5' -ex r -ex stepi -ex 'p/x $xmm0' 2>&1|tee /proc/self/fd/2|grep 0x3fd3333333333333 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22138-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Nov 26 19:10:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 117346 invoked by alias); 26 Nov 2017 19:10:04 -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 117322 invoked by uid 48); 26 Nov 2017 19:10:03 -0000 From: "jonah at kichwacoders dot com" To: gdb-prs@sourceware.org Subject: [Bug exp/22487] `51-var-list-children var3` is not returning within 10 seconds Date: Sun, 26 Nov 2017 19:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jonah at kichwacoders dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00182.txt.bz2 Content-length: 405 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22487 Jonah Graham changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonah at kichwacoders dot = com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22139-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Nov 26 19:10:08 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 117619 invoked by alias); 26 Nov 2017 19:10:08 -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 117589 invoked by uid 48); 26 Nov 2017 19:10:08 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22499] 8.0 regression: wrongly read $xmm0 Date: Sun, 26 Nov 2017 19:10: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00183.txt.bz2 Content-length: 387 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22499 --- Comment #1 from Jan Kratochvil --- Reproducibility requires gcc -avx: g++ -mavx -g test.cpp Verified with GDB GIT: 2b63c337d99fe12220e6ca12a71dac6cdd3224d3 gcc-7.2.1-2.fc27.x86_64 PASS: gdb-7.9 FAIL: gdb-8.0 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22140-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 27 03:47:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 127680 invoked by alias); 27 Nov 2017 03:47:09 -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 127656 invoked by uid 55); 27 Nov 2017 03:47:09 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21945] Improve find command string search Date: Mon, 27 Nov 2017 03:47: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00184.txt.bz2 Content-length: 1086 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21945 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Simon Marchi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dee9a09e959a5= b7c152cc72028d4f6c879bc901c9 commit ee9a09e959a5b7c152cc72028d4f6c879bc901c9 Author: Dominik Czarnota Date: Sun Nov 26 22:42:18 2017 -0500 Update find command help and search memory docs This patch updates the `find` command help and docs description to show how to search for not null terminated strings when current language's strings includes it. gdb/ChangeLog: PR gdb/21945 * findcmd.c (_initialize_mem_search): Update find command help text. gdb/doc/ChangeLog: PR gdb/21945 * gdb.texinfo (Search Memory): Update description and example about how to search a string without NULL terminator. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22141-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 27 11:27:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 45055 invoked by alias); 27 Nov 2017 11:27:14 -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 45033 invoked by uid 48); 27 Nov 2017 11:27:14 -0000 From: "bugzilla at tecnocode dot co.uk" To: gdb-prs@sourceware.org Subject: [Bug gdb/22501] New: Incorrect sizeof(symbol) == 4 on a 64-bit platform Date: Mon, 27 Nov 2017 11:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bugzilla at tecnocode dot co.uk X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00185.txt.bz2 Content-length: 1956 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22501 Bug ID: 22501 Summary: Incorrect sizeof(symbol) =3D=3D 4 on a 64-bit platform Product: gdb Version: 7.12 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: bugzilla at tecnocode dot co.uk Target Milestone: --- If I compile GLib normally on a 64-bit platform, without CFLAGS=3D-g, run a= test program, and `print sizeof(__glib_assert_msg)`, gdb (incorrectly) tells me = it=E2=80=99s 4 bytes: However, it=E2=80=99s a char*, and its size according to objdump is (correctly) 8 bytes: (gdb) print sizeof(__glib_assert_msg) $1 =3D 4 (gdb) print sizeof(char*) $2 =3D 8 objdump -t ./glib/.libs/libglib-2.0.so.0.5400.2 | grep assert_msg 000000000032c3e0 g O .bss 0000000000000008=20=20=20=20=20=20=20=20= =20=20=20=20=20 __glib_assert_msg No debug information is being loaded while running gdb: (gdb) info sharedlibrary >>From To Syms Read Shared Object Library 0x00007ffff7dd9aa0 0x00007ffff7df51b0 Yes /lib64/ld-linux-x86-64.= so.2 0x00007ffff7ac6e90 0x00007ffff7b5ae90 Yes (*)=20=20=20=20 /tmp/build-snapshot.Ry9JWQsWNS/s/glib/.libs/libglib-2.0.so.0 0x00007ffff772c910 0x00007ffff7856423 Yes=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libc.so.6 0x00007ffff749b5d0 0x00007ffff74edab1 Yes (*)=20=20=20=20 /lib/x86_64-linux-gnu/libpcre.so.3 0x00007ffff7282ab0 0x00007ffff728f811 Yes=20=20=20=20=20=20=20=20 /lib/x86_64-linux-gnu/libpthread.so.0 (*): Shared library is missing debugging information. I can provide other information if needed. --- This looks similar to bug #12281. The downstream GLib bug which triggered t= his is https://bugzilla.gnome.org/show_bug.cgi?id=3D782057. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22142-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 27 11:45:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 79537 invoked by alias); 27 Nov 2017 11:45:35 -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 79416 invoked by uid 48); 27 Nov 2017 11:45:30 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22501] Incorrect sizeof(symbol) == 4 on a 64-bit platform Date: Mon, 27 Nov 2017 11:45: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.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00186.txt.bz2 Content-length: 930 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22501 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- The problem is that without debug info (-g), GDB can't know that "__glib_assert_msg" is a "char *". And then, in all released versions,=20 if GDB doesn't know the type of the object, it assumes "int",=20 which has sizeof 4. This assumption was recently removed in GDB master (soon-to-be gdb 8.1), exactly because it's very confusing: https://sourceware.org/ml/gdb-patches/2017-07/msg00137.html specifically: https://sourceware.org/ml/gdb-patches/2017-07/msg00150.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22143-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 27 11:48:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 87569 invoked by alias); 27 Nov 2017 11:48:37 -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 87350 invoked by uid 48); 27 Nov 2017 11:48:25 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug exp/12281] Incorrect interpretation of returned point in 64 bit platform Date: Mon, 27 Nov 2017 11:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat 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: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution target_milestone 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: 2017-q4/txt/msg00187.txt.bz2 Content-length: 1071 https://sourceware.org/bugzilla/show_bug.cgi?id=3D12281 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |palves at redhat dot com Resolution|--- |FIXED Target Milestone|--- |8.1 --- Comment #1 from Pedro Alves --- The problem is that without debug info (-g), GDB can't know the return type of the function, And then, in all released versions, if GDB doesn't know = the type of the function, it assumes "int ()". This assumption was recently removed in GDB master (soon-to-be gdb 8.1), exactly because it's very confusing: https://sourceware.org/ml/gdb-patches/2017-07/msg00137.html specifically: https://sourceware.org/ml/gdb-patches/2017-07/msg00150.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22144-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 27 11:49:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88092 invoked by alias); 27 Nov 2017 11:49:09 -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 88069 invoked by uid 48); 27 Nov 2017 11:49:08 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug exp/12281] Incorrect interpretation of returned point in 64 bit platform Date: Mon, 27 Nov 2017 11:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat 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: 8.1 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: 2017-q4/txt/msg00188.txt.bz2 Content-length: 402 https://sourceware.org/bugzilla/show_bug.cgi?id=3D12281 --- Comment #2 from Pedro Alves --- (In reply to Pedro Alves from comment #1) > specifically: > https://sourceware.org/ml/gdb-patches/2017-07/msg00150.html I actually meant: https://sourceware.org/ml/gdb-patches/2017-07/msg00139.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22145-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 27 12:00:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107463 invoked by alias); 27 Nov 2017 12:00:44 -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 106703 invoked by uid 48); 27 Nov 2017 12:00:42 -0000 From: "bugzilla at tecnocode dot co.uk" To: gdb-prs@sourceware.org Subject: [Bug gdb/22501] Incorrect sizeof(symbol) == 4 on a 64-bit platform Date: Mon, 27 Nov 2017 12:00: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.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bugzilla at tecnocode dot co.uk X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00189.txt.bz2 Content-length: 874 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22501 --- Comment #2 from Philip Withnall --- (In reply to Pedro Alves from comment #1) > The problem is that without debug info (-g), GDB can't know that > "__glib_assert_msg" is a "char *". And then, in all released versions,=20 > if GDB doesn't know the type of the object, it assumes "int",=20 > which has sizeof 4. >=20 > This assumption was recently removed in GDB master (soon-to-be gdb 8.1), > exactly because it's very confusing: > https://sourceware.org/ml/gdb-patches/2017-07/msg00137.html > specifically: > https://sourceware.org/ml/gdb-patches/2017-07/msg00150.html I see, that explains things. I look forward to your patch series landing. Is there a bug which this one should be duped to? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22146-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 27 12:06:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41767 invoked by alias); 27 Nov 2017 12:06:14 -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 41740 invoked by uid 48); 27 Nov 2017 12:06:13 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22501] Incorrect sizeof(symbol) == 4 on a 64-bit platform Date: Mon, 27 Nov 2017 12:06: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.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00190.txt.bz2 Content-length: 916 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22501 --- Comment #3 from Pedro Alves --- (In reply to Philip Withnall from comment #2) > I see, that explains things. I look forward to your patch series landing.= =20 It already landed a while ago. If you try out current master, you'll get a= n=20 error instead of "=3D 4". > Is there a bug which this one should be duped to? There probably is, though I haven't looked. This is a very frequent source= of confusion. For sizeof in particular, I'm wondering whether it makes sense (or rather i= f it could ever be a problem) for GDB to use/print the size as recorded in the E= LF symbol table, when it is available. That might be doable. (though I proba= bly won't be able to try it myself soon enough). Not sure it's worth the troub= le, though. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22147-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 27 18:37:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 106794 invoked by alias); 27 Nov 2017 18:37:58 -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 106770 invoked by uid 48); 27 Nov 2017 18:37:58 -0000 From: "pflarr at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug python/22503] New: GDB uses PYTHONHOME environment variable, but can't find the correct python environment. Date: Mon, 27 Nov 2017 18:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 7.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pflarr at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00191.txt.bz2 Content-length: 1444 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22503 Bug ID: 22503 Summary: GDB uses PYTHONHOME environment variable, but can't find the correct python environment. Product: gdb Version: 7.6 Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: pflarr at gmail dot com Target Milestone: --- When running gdb with PYTHONHOME set to a custom python environment, gdb se= ems to use that python but can't find the correct environment. The result, as typical when python can't find its environment, is for python to fail on tr= ying to import the site module, giving the following error: ImportError: No module named site This appears to apply to all versions of gdb with python support. The workaround is to run gdb with PYTHONHOME forced to the system python, s= uch as `$ PYTHONHOME=3D/usr gdb`. This isn't really good enough for us though, = as having non-system PYTHONHOME set is standard in our user build environments. My guess at the fix is for gdb to ignore PYTHONHOME (and probably PYTHONPAT= H), and always use the python it was built against. The python command line provides a -E option to do exactly that, or you can unsetenv on PYTHONHOME within gdb. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22148-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Nov 27 22:22:31 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35546 invoked by alias); 27 Nov 2017 22:22:31 -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 35522 invoked by uid 48); 27 Nov 2017 22:22:31 -0000 From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/16224] add "pahole" functionality to ptype Date: Mon, 27 Nov 2017 22:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: brobecker at gnat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc target_milestone 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: 2017-q4/txt/msg00192.txt.bz2 Content-length: 543 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16224 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brobecker at gnat dot com Target Milestone|--- |8.1 --- Comment #2 from Joel Brobecker --- Trying to aim for 8.1... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22150-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 28 14:56:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 76787 invoked by alias); 28 Nov 2017 14:56:41 -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 76765 invoked by uid 48); 28 Nov 2017 14:56:41 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22511] Regression in "commands" Date: Tue, 28 Nov 2017 14:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone 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: 2017-q4/txt/msg00194.txt.bz2 Content-length: 371 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22511 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22149-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 28 14:56:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 76365 invoked by alias); 28 Nov 2017 14:56:35 -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 76311 invoked by uid 48); 28 Nov 2017 14:56:34 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22511] New: Regression in "commands" Date: Tue, 28 Nov 2017 14:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00193.txt.bz2 Content-length: 1137 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22511 Bug ID: 22511 Summary: Regression in "commands" Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- Filing this so we don't forget before the 8.1 release.=20=20 >>From https://sourceware.org/ml/gdb-patches/2017-11/msg00088.html : ~~~ Pedro pointed out a regression in "commands", where trying to clear a breakpoint's command list would fail: (top-gdb) commands Type commands for breakpoint(s) 3, one per line. End with a line saying just "end". >end No breakpoints specified. (top-gdb) I believe the bug was introduced by my patch that changes counted_command_line to be a shared_ptr. This causes the problem because now the counted_command_line in commands_command_1 can be NULL, whereas previously it never could be. ~~~ --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22151-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 28 17:08:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107721 invoked by alias); 28 Nov 2017 17:08:58 -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 107449 invoked by uid 48); 28 Nov 2017 17:08:57 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22499] 8.0 regression: wrongly read $xmm0 Date: Tue, 28 Nov 2017 17:08: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00195.txt.bz2 Content-length: 367 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22499 --- Comment #2 from Pedro Alves --- Confirmed, I can reproduce this. With current master, "maint set target-non-stop off", which has the same ef= fect as reverting the offending patch, works around it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22152-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 28 17:30:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68783 invoked by alias); 28 Nov 2017 17:30:40 -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 68754 invoked by uid 48); 28 Nov 2017 17:30:40 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22499] 8.0 regression: wrongly read $xmm0 Date: Tue, 28 Nov 2017 17:30: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00196.txt.bz2 Content-length: 495 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22499 --- Comment #3 from Pedro Alves --- For some odd reason, "maint set target-non-stop on/off" makes a difference = in the value of $ymm0: (gdb) info all-registers $ymm0 - ymm0 {v8_float =3D {0x0, 0x1, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, ... + ymm0 {v8_float =3D {0x0, 0xfffffffb, 0x0, 0x0, 0x0, 0x0, 0x0, 0= x0}, ... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22153-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 28 17:35:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 73789 invoked by alias); 28 Nov 2017 17:35:02 -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 73744 invoked by uid 48); 28 Nov 2017 17:35:02 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22499] 8.0 regression: wrongly read $xmm0 Date: Tue, 28 Nov 2017 17:35: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00197.txt.bz2 Content-length: 430 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22499 --- Comment #4 from Pedro Alves --- hmm, I suspect that this is related to something odd with displaced steppin= g, which is enabled by non-stop, because "set displaced off" alone also works around it. Probably the inferior ends up executing the wrong instruction, --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22154-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 28 18:07:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 121577 invoked by alias); 28 Nov 2017 18:07:14 -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 121553 invoked by uid 48); 28 Nov 2017 18:07:13 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22499] 8.0 regression: wrongly read $xmm0 Date: Tue, 28 Nov 2017 18:07: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00198.txt.bz2 Content-length: 501 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22499 --- Comment #5 from Pedro Alves --- Confirmed, the problem is that we displaced-step a RIP-relative instruction that needs adjustment when relocated to the scratch pad: 0x00000000004007f5 <+15>: c5 fb 10 05 8b 01 00 00 vmovsd 0x18b(%rip),%x= mm0=20 # 0x400988 ... but GDB just copies it over to the scratch pad unmodified... --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22155-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Nov 28 21:50:01 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 11330 invoked by alias); 28 Nov 2017 21:50:00 -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 11294 invoked by uid 48); 28 Nov 2017 21:50:00 -0000 From: "17joshuanewcomb at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug exp/22487] `51-var-list-children var3` is not returning within 10 seconds Date: Tue, 28 Nov 2017 21:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: 17joshuanewcomb at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00199.txt.bz2 Content-length: 304 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22487 --- Comment #1 from Joshua Newcomb <17joshuanewcomb at gmail dot com> --- And this is the GDB Traces output: https://bugs.eclipse.org/bugs/attachment.cgi?id=3D271541 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22156-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 29 00:49:09 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 57477 invoked by alias); 29 Nov 2017 00:49:09 -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 57448 invoked by uid 48); 29 Nov 2017 00:49:09 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22499] 8.0 regression: wrongly read $xmm0 Date: Wed, 29 Nov 2017 00:49: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to 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: 2017-q4/txt/msg00200.txt.bz2 Content-length: 598 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22499 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at sourceware dot org |palves at redhat do= t com --- Comment #6 from Pedro Alves --- Patch posted: https://sourceware.org/ml/gdb-patches/2017-11/msg00748.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22157-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 29 09:44:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 74241 invoked by alias); 29 Nov 2017 09:44:54 -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 74212 invoked by uid 48); 29 Nov 2017 09:44:54 -0000 From: "klausman-glibc at schwarzvogel dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/19061] gdb-7.10 hangs/spins-on-cpu when debugging any program on Alpha Date: Wed, 29 Nov 2017 09:44: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.10 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: klausman-glibc at schwarzvogel dot de 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: 2017-q4/txt/msg00201.txt.bz2 Content-length: 428 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19061 --- Comment #7 from Tobias Klausmann --- I *think* this may be fixed in gdb-8. I just checked out gdb-8.0.1-release = from git and I have been unable to reproduce the hang. I will keep using it for everyday stuff and report back if anything breaks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22158-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 29 18:13:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 11054 invoked by alias); 29 Nov 2017 18:13:55 -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 11032 invoked by uid 48); 29 Nov 2017 18:13:55 -0000 From: "thopre01 at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22531] New: FAIL: gdb.base/async.exp & gdb.base/skip.exp Date: Wed, 29 Nov 2017 18:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thopre01 at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q4/txt/msg00202.txt.bz2 Content-length: 1791 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22531 Bug ID: 22531 Summary: FAIL: gdb.base/async.exp & gdb.base/skip.exp Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: thopre01 at gcc dot gnu.org Target Milestone: --- Created attachment 10648 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10648&action=3Ded= it Executable async and skip produced by GCC trunk Hi, The following tests fail on arm-none-eabi targets with debug info generated= by GCC post commit r254010: PASS->FAIL: gdb.base/async.exp: nexti& PASS->FAIL: gdb.base/async.exp: finish& PASS->FAIL: gdb.base/skip.exp: step after disabling 3: step 3 PASS->FAIL: gdb.base/skip.exp: step after disabling 3: step 5 PASS->FAIL: gdb.base/skip.exp: step using -fu for baz: step 3 PASS->FAIL: gdb.base/skip.exp: step using -fu for baz: step 5 PASS->FAIL: gdb.base/skip.exp: step using -rfu for baz: step 3 PASS->FAIL: gdb.base/skip.exp: step using -rfu for baz: step 5 GCC was configured as: --target=3Darm-none-eabi --with-newlib --with-mode= =3Dthumb --with-cpu=3Dcortex-m3 The 2 async tests fail because the addresses are missing: -(gdb) 0x00008172 9 x =3D 5; x =3D 5; x =3D 5; +(gdb) 9 x =3D 5; x =3D 5; x =3D 5; -Run till exit from #0 0x00008172 in foo () +Run till exit from #0 foo () The skip tests fail because the wrong line is shown by gdb after doing step. This bug was already reported against GCC (PR83199) and was triaged as bein= g a GDB issue. Attached are the async and skip binary produced by GCC. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22159-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 29 19:31:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 46626 invoked by alias); 29 Nov 2017 19:31:26 -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 46593 invoked by uid 48); 29 Nov 2017 19:31:26 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug server/22137] gdbserver crashes on hosts with pkru register Date: Wed, 29 Nov 2017 19:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: cc 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: 2017-q4/txt/msg00203.txt.bz2 Content-length: 413 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22137 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jan.kratochvil at redhat d= ot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22160-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 29 19:49:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 39210 invoked by alias); 29 Nov 2017 19:49:25 -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 39185 invoked by uid 55); 29 Nov 2017 19:49:25 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug c++/19436] C++11 ABI tag does not work Date: Wed, 29 Nov 2017 19:49: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: cvs-commit at gcc dot gnu.org 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: 2017-q4/txt/msg00204.txt.bz2 Content-length: 3732 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19436 --- Comment #5 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dbd69330db86b= 2367aac8aac5915f1686451c9d5d commit bd69330db86b2367aac8aac5915f1686451c9d5d Author: Pedro Alves Date: Wed Nov 29 19:33:24 2017 +0000 Breakpoints in symbols with ABI tags (PR c++/19436) Trying to set a breakpoint in a function with an ABI tag does not work currently. E.g., debugging gdb itself, we see this with the "string_printf" function: (top-gdb) b string_print [TAB] (top-gdb) b string_printf[abi:cxx11](char const*, ...) [RET] No source file named string_printf[abi. Make breakpoint pending on future shared library load? (y or [n]) Quoting doesn't help: (top-gdb) b 'string_printf[abi:cxx11]'(char const*, ...) malformed linespec error: unexpected string, "(char const*, ...)" (top-gdb) b 'string_printf[abi:cxx11](char const*, ...)' No source file named string_printf[abi. Make breakpoint pending on future shared library load? (y or [n]) n This patch fixes this, and takes it a bit further. The actual symbol name as demangled by libiberty's demangler is really string_printf[abi:cxx11](char const*, ...) however, this patch makes it possible to set the breakpoint with string_printf(char const*, ...) too. I.e., ignoring the ABI tag. And to match, it teaches the completer to complete the symbol name without the ABI tag, i.e., "string_pri" -> "string_printf(char const*, ...)" If however, you really want to break on a symbol with the tag, then you simply start writing the tag, and GDB will preserve it, like: "string_printf[a" -> "string_printf[abi:cxx11](char const*, ...= )" Grows the gdb.linespec/ tests like this: -# of expected passes 8977 +# of expected passes 9176 gdb/ChangeLog: 2017-11-29 Pedro Alves PR c++/19436 * NEWS: Mention setting breakpoints on functions with C++ ABI tags. * completer.h (completion_match_for_lcd) : New methods. : Consider ignored ranges. : Clear ignored ranges. : New fields. * cp-support.c (cp_search_name_hash): Ignore ABI tags. (cp_symbol_name_matches_1, cp_fq_symbol_name_matches): Pass the completion_match_for_lcd pointer to strncmp_iw_with_mode. (test_cp_symbol_name_cmp): Add [abi:...] tags unit tests. * language.c (default_symbol_name_matcher): Pass the completion_match_for_lcd pointer to strncmp_iw_with_mode. * linespec.c (linespec_lexer_lex_string): Don't tokenize ABI tags. * utils.c (skip_abi_tag): New function. (strncmp_iw_with_mode): Add completion_match_for_lcd parameter. Handle ABI tags. * utils.h (strncmp_iw_with_mode): Add completion_match_for_lcd parameter. gdb/testsuite/ChangeLog: 2017-11-29 Pedro Alves PR c++/19436 * gdb.linespec/cpls-abi-tag.cc: New file. * gdb.linespec/cpls-abi-tag.exp: New file. gdb/doc/ChangeLog: 2017-11-29 Pedro Alves PR c++/19436 * gdb.texinfo (Debugging C Plus Plus): Document setting breakpoints in functions with ABI tags. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22161-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 29 20:04:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35575 invoked by alias); 29 Nov 2017 20:04:44 -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 35552 invoked by uid 48); 29 Nov 2017 20:04:42 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/16874] Setting a breakpoint on function in anonymous namespace is unnecessarily awkward Date: Wed, 29 Nov 2017 20:04: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: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: patrick at parcs dot ath.cx 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: 2017-q4/txt/msg00205.txt.bz2 Content-length: 2694 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16874 --- Comment #15 from Pedro Alves --- The series above is finally all merged to master. These are the related improvements that you'll find there: * Completion improvements ** GDB can now complete function parameters in linespecs and explicit locations without quoting. When setting breakpoints, quoting around functions names to help with TAB-completion is generally no longer necessary. For example, this now completes correctly: (gdb) b function(in[TAB] (gdb) b function(int) Related, GDB is no longer confused with completing functions in C++ anonymous namespaces: (gdb) b (anon[TAB] (gdb) b (anonymous namespace)::[TAB][TAB] (anonymous namespace)::a_function() (anonymous namespace)::b_function() ** GDB now has much improved linespec and explicit locations TAB completion support, that better understands what you're completing and offers better suggestions. For example, GDB no longer offers data symbols as possible completions when you're setting a breakpoint. ** GDB now TAB-completes label symbol names. ** The "complete" command now mimics TAB completion accurately. * Breakpoints on C++ functions are now set on all scopes by default By default, breakpoints on functions/methods are now interpreted as specifying all functions with the given name ignoring missing leading scopes (namespaces and classes). For example, assuming a C++ program with symbols named: A::B::func() B::func() both commands "break func()" and "break B::func()" set a breakpoint on both symbols. You can use the new flag "-qualified" to override this. This makes GDB interpret the specified function name as a complete fully-qualified name instead. For example, using the same C++ program, the "break -q B::func" command sets a breakpoint on "B::func", only. * Breakpoints on functions marked with C++ ABI tags GDB can now set breakpoints on functions marked with C++ ABI tags (e.g., [abi:cxx11]). See here for a description of ABI tags: https://developers.redhat.com/blog/2015/02/05/gcc5-and-the-c11-abi/ Functions with a C++11 abi tag are demangled/displayed like this: function[abi:cxx11](int) ^^^^^^^^^^^ You can now set a breakpoint on such functions simply as if they had no tag, like: (gdb) b function(int) Or if you need to disambiguate between tags, like: (gdb) b function[abi:other_tag](int) Tab completion was adjusted accordingly as well. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22162-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 29 20:18:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78675 invoked by alias); 29 Nov 2017 20:18:34 -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 78644 invoked by uid 48); 29 Nov 2017 20:18:33 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/19436] C++11 ABI tag does not work Date: Wed, 29 Nov 2017 20:18: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: palves at redhat dot com 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: cc 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: 2017-q4/txt/msg00206.txt.bz2 Content-length: 1149 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19436 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #6 from Pedro Alves --- "print" (In reply to Jan Kratochvil from comment #0) > It affects default configuration of latest stable release of GCC. >=20 >=20 >=20 > echo -e '#include \nstd::string foovar;'|g++ -c -o 20.o -Wall -g = -x > c++ -;nm -C 20.o|grep -w foovar > 0000000000000000 B foovar[abi:cxx11] > gdb -batch ./20.o -ex "p foovar" -ex "p 'foovar[abi:cxx11]'" This now works in master: gdb -batch ./20.o -ex "p foovar" -ex "p 'foovar[abi:cxx11]'" $1 =3D "" $2 =3D "" which turns out to be a happy consequence of the commit listed above. I'm leaving the bug open because while bd69330db86b added comprehensive tes= ts for breakpoints-on-symbols-with-abi-tags, it added none for print/expressio= ns. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22163-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 29 20:19:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 80694 invoked by alias); 29 Nov 2017 20:19:51 -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 80411 invoked by uid 48); 29 Nov 2017 20:19:50 -0000 From: "dmalcolm at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/16874] Setting a breakpoint on function in anonymous namespace is unnecessarily awkward Date: Wed, 29 Nov 2017 20:19: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: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: dmalcolm at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: patrick at parcs dot ath.cx 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: 2017-q4/txt/msg00207.txt.bz2 Content-length: 1061 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16874 --- Comment #16 from Dave Malcolm --- (In reply to Pedro Alves from comment #15) > The series above is finally all merged to master. These are the related > improvements that you'll find there: [...] Thanks for the improvements! > * Breakpoints on C++ functions are now set on all scopes by default >=20 > By default, breakpoints on functions/methods are now interpreted as > specifying all functions with the given name ignoring missing > leading scopes (namespaces and classes). >=20 > For example, assuming a C++ program with symbols named: >=20 > A::B::func() > B::func() >=20 > both commands "break func()" and "break B::func()" set a breakpoint > on both symbols. To clarify, if there is a symbol: (anonymous namespace)::func() will "break func" set a breakpoint on it? (without me having to type or tab-complete the "(anonymous namespace)" part?) [...] --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22164-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Nov 29 20:29:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 113802 invoked by alias); 29 Nov 2017 20:29:45 -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 113757 invoked by uid 48); 29 Nov 2017 20:29:44 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/16874] Setting a breakpoint on function in anonymous namespace is unnecessarily awkward Date: Wed, 29 Nov 2017 20:29: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: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: patrick at parcs dot ath.cx 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: 2017-q4/txt/msg00208.txt.bz2 Content-length: 778 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16874 --- Comment #17 from Pedro Alves --- (In reply to Dave Malcolm from comment #16) > (In reply to Pedro Alves from comment #15) > > The series above is finally all merged to master. These are the related > > improvements that you'll find there: >=20 > [...] >=20 > Thanks for the improvements! My pleasure! Making things better for GCC folks was one of my sekrit driving forces. :-) > To clarify, if there is a symbol: >=20 > (anonymous namespace)::func() >=20 > will "break func" set a breakpoint on it? (without me having to type or > tab-complete the "(anonymous namespace)" part?) >=20 > [...] Yes. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22165-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Nov 30 10:51:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 24264 invoked by alias); 30 Nov 2017 10:51: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 24231 invoked by uid 48); 30 Nov 2017 10:51:22 -0000 From: "thopre01 at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/22091] PASS->FAIL: gdb.arch/thumb2-it.exp Date: Thu, 30 Nov 2017 10:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thopre01 at gcc dot gnu.org 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00209.txt.bz2 Content-length: 577 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22091 Thomas Preud'homme changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Thomas Preud'homme --- Fixed on trunk as of 8f8f815255bf36800cdfff93fd88a62aaa39ce16 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22166-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Nov 30 10:55:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 26668 invoked by alias); 30 Nov 2017 10:55:34 -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 26644 invoked by uid 48); 30 Nov 2017 10:55:34 -0000 From: "thopre01 at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/20818] PASS->FAIL: gdb.base/ptype.exp: ptype old_fptr Date: Thu, 30 Nov 2017 10:55: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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thopre01 at gcc dot gnu.org 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00210.txt.bz2 Content-length: 537 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20818 Thomas Preud'homme changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Thomas Preud'homme --- Now passing on trunk. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22167-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 01 15:35:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 60581 invoked by alias); 1 Dec 2017 15:35:00 -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 60539 invoked by uid 48); 1 Dec 2017 15:34:59 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22511] Regression in "commands" Date: Fri, 01 Dec 2017 15:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to 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: 2017-q4/txt/msg00211.txt.bz2 Content-length: 488 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22511 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg Assignee|unassigned at sourceware dot org |tromey at sourcewar= e dot org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22168-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 01 20:34:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 46373 invoked by alias); 1 Dec 2017 20:34:24 -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 46347 invoked by uid 48); 1 Dec 2017 20:34:24 -0000 From: "17joshuanewcomb at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug exp/22487] `51-var-list-children var3` is not returning within 10 seconds Date: Fri, 01 Dec 2017 20:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: 17joshuanewcomb at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q4/txt/msg00212.txt.bz2 Content-length: 420 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22487 --- Comment #2 from Joshua Newcomb <17joshuanewcomb at gmail dot com> --- Created attachment 10656 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10656&action=3Ded= it Test Case program Here's a test case that causes GDB MI to have a problem, at least in Eclipse Latest. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22169-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Dec 03 18:28:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109343 invoked by alias); 3 Dec 2017 18:28:28 -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 109322 invoked by uid 48); 3 Dec 2017 18:28:28 -0000 From: "francois.court at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/22541] New: Gdb crashes on variadic templates Date: Sun, 03 Dec 2017 18:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: francois.court at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q4/txt/msg00213.txt.bz2 Content-length: 2306 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22541 Bug ID: 22541 Summary: Gdb crashes on variadic templates Product: gdb Version: 7.6 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: francois.court at gmail dot com Target Milestone: --- Created attachment 10660 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10660&action=3Ded= it crashing and non crashing version of test exec **Windows 10 Pro x64 version 1703 build 15063.608 **gcc Using built-in specs. COLLECT_GCC=3Dgcc COLLECT_LTO_WRAPPER=3DD:/Dev/Codeblocks/MinGW/bin/../libexec/gcc/mingw32/4.= 9.2/lto-wrapper.exe Target: mingw32 Configured with: ../../../src/gcc-4.9.2/configure --build=3Dmingw32 --enable-languages=3Dada,c,c++,fortran,lto,objc,obj-c++ --enable-libgomp --enable-lto --enable-graphite --enable-libstdcxx-debug --enable-threads=3D= posix --enable-version-specific-runtime-libs --enable-fully-dynamic-string --enable-libstdcxx-threads --enable-libstdcxx-time --with-gnu-ld --disable-werror --disable-nls --disable-win32-registry --disable-symvers --enable-cxx-flags=3D'-fno-function-sections -fno-data-sections -DWINPTHREAD_STATIC' --prefix=3D/mingw32tdm --with-local-prefix=3D/mingw32t= dm --with-pkgversion=3Dtdm-1 --enable-sjlj-exceptions --with-bugurl=3Dhttp://tdm-gcc.tdragon.net/bugs Thread model: posix gcc version 4.9.2 (tdm-1) **ld -v GNU ld (GNU Binutils) 2.24 **IDE Codeblocks 16.01 Build Jan 25 2016 - wx2.8.12- 32bit **gdb GNU gdb (GDB) 7.6.1 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "mingw32". **Description gdb crashes loading symbols; the same executable loads and debugs well when= the inclusion of a variadic template call is replaced by its non-variadic equivalent. Attached are the two versions of the exec, the one crashing and the other f= ine --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22170-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 04 16:19:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 48881 invoked by alias); 4 Dec 2017 16:19:42 -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 48823 invoked by uid 55); 4 Dec 2017 16:19:42 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22499] 8.0 regression: wrongly read $xmm0 Date: Mon, 04 Dec 2017 16:19: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00214.txt.bz2 Content-length: 2436 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22499 --- Comment #7 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D50a1fdd59c17= 77672a9be0e81fe2301c2a115fce commit 50a1fdd59c1777672a9be0e81fe2301c2a115fce Author: Pedro Alves Date: Mon Dec 4 15:59:20 2017 +0000 Fix displaced-stepping RIP-relative VEX-encoded instructions (AVX) (PR gdb/22499) PR gdb/22499 is about a latent bug exposed by the switch to "maint set target-non-stop on" by default on x86-64 GNU/Linux, a while ago. With that on, GDB is also preferring to use displaced-stepping by default. The testcase in the bug is failing because GDB ends up incorrectly displaced-stepping over a RIP-relative VEX-encoded instruction, like this: 0x00000000004007f5 <+15>: c5 fb 10 05 8b 01 00 00 vmovsd 0x18b(%rip),%xmm0 # 0x400988 While RIP-relative instructions need adjustment when relocated to the scratch pad, GDB ends up just copying VEX-encoded instructions to the scratch pad unmodified, with the end result that the inferior ends up executing an instruction that fetches/writes memory from the wrong address... This patch teaches GDB about the VEX-encoding prefixes, fixing the problem, and adds a testcase that fails without the GDB fix. I think we may need a similar treatment for EVEX-encoded instructions, but I didn't address that simply because I couldn't find any EVEX-encoded RIP-relative instruction in the gas testsuite. In any case, this commit is forward progress as-is already. gdb/ChangeLog: 2017-12-04 Pedro Alves PR gdb/22499 * amd64-tdep.c (amd64_insn::rex_offset): Rename to... (amd64_insn::enc_prefix_offset): ... this, and tweak comment. (vex2_prefix_p, vex3_prefix_p): New functions. (amd64_get_insn_details): Adjust to rename. Also skip VEX2 and VEX3 prefixes. (fixup_riprel): Set VEX3.!B. gdb/testsuite/ChangeLog: 2017-12-04 Pedro Alves PR gdb/22499 * gdb.arch/amd64-disp-step-avx.S: New file. * gdb.arch/amd64-disp-step-avx.exp: New file. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22171-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 04 16:21:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 50481 invoked by alias); 4 Dec 2017 16:21:50 -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 50461 invoked by uid 48); 4 Dec 2017 16:21:50 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22499] 8.0 regression: wrongly read $xmm0 Date: Mon, 04 Dec 2017 16:21: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.1 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00215.txt.bz2 Content-length: 502 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22499 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #8 from Pedro Alves --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22172-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 04 16:54:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36140 invoked by alias); 4 Dec 2017 16:54:48 -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 36112 invoked by uid 48); 4 Dec 2017 16:54:48 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug python/22475] Python API: breakpoint subclass: GDB crashes if function called through parse_and_eval() exits Date: Mon, 04 Dec 2017 16:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: target_milestone 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: 2017-q4/txt/msg00216.txt.bz2 Content-length: 453 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22475 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|8.1 |--- --- Comment #3 from Yao Qi --- Clear the target milestone. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22173-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 04 17:18:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 119697 invoked by alias); 4 Dec 2017 17:18:20 -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 119663 invoked by uid 48); 4 Dec 2017 17:18:20 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/22545] New: add inclusive range syntax to rust Date: Mon, 04 Dec 2017 17:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00217.txt.bz2 Content-length: 750 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22545 Bug ID: 22545 Summary: add inclusive range syntax to rust Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- Rust is getting syntax for an inclusive range, see https://github.com/rust-lang/rust/issues/28237 At some point (I'm generally not sure if this sort of thing should be done when the feature stabilizes, or earlier), this should be added to rust-exp.y. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22174-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 05 00:47:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 56001 invoked by alias); 5 Dec 2017 00:47:12 -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 55965 invoked by uid 48); 5 Dec 2017 00:47:11 -0000 From: "chrisfriedt at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20981] Dynamic library debugging on MacOS X 10.12 (Sierra) and dyld 15 is broken Date: Tue, 05 Dec 2017 00:47: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: chrisfriedt at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00218.txt.bz2 Content-length: 217 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20981 --- Comment #8 from Chris Friedt --- #sadface :( --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22175-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 05 11:55:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 111592 invoked by alias); 5 Dec 2017 11:55:46 -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 111562 invoked by uid 48); 5 Dec 2017 11:55:46 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/20981] Dynamic library debugging on MacOS X 10.12 (Sierra) and dyld 15 is broken Date: Tue, 05 Dec 2017 11:55: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00219.txt.bz2 Content-length: 796 https://sourceware.org/bugzilla/show_bug.cgi?id=3D20981 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #9 from Pedro Alves --- The simple hard fact is that unfortunately the macOS/Darwin port isn't real= ly getting much attention. Most gdb devs tend to run/focus on GNU/Linux. We need someone motivated to actually dig in to the sources, study the issu= e in detail, and fix the issue. Who knows, maybe end up becoming port maintaine= r.=20 :-) This could be you! --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22176-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 06 13:20:58 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 109254 invoked by alias); 6 Dec 2017 13:20:57 -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 109230 invoked by uid 48); 6 Dec 2017 13:20:56 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22556] New: Regression: gdb.threads/names.exp with --target_board=native-gdbserver Date: Wed, 06 Dec 2017 13:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00220.txt.bz2 Content-length: 2289 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22556 Bug ID: 22556 Summary: Regression: gdb.threads/names.exp with --target_board=3Dnative-gdbserver Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- I've seeing an odd regression in gdb.threads/names.exp (at least) when test= ing against --target_board=3Dnative-gdbserver ~~~ Thread 1 "main" hit Breakpoint 1, all_threads_ready () at src/gdb/testsuite/gdb.threads/names.c:51 51 } (gdb) info threads Id Target Id Frame=20 * 1 Thread 4090.4090 "main" () all_threads_ready () at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/testsuite/gdb.threads/names.c:= 51 2 Thread 4090.4093 "carrot" () pthread_barrier_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_barrier_wait.S:71 3 Thread 4090.4094 "potato" () pthread_barrier_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_barrier_wait.S:71 4 Thread 4090.4095 "celery" () pthread_barrier_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_barrier_wait.S:71 (gdb) FAIL: gdb.threads/names.exp: list threads ~~~ Notice the spurious "()" in=20 "main" () all_threads_ready () ^^ Testing against the native target doesn't show that: (gdb) info threads Id Target Id Frame=20 * 1 Thread 0x7ffff7fc1700 (LWP 4439) "main" all_threads_ready () at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/testsuite/gdb.threads/names.c:= 51 2 Thread 0x7ffff74fa700 (LWP 4443) "carrot" pthread_barrier_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_barrier_wait.S:71 3 Thread 0x7ffff6cf9700 (LWP 4444) "potato" pthread_barrier_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_barrier_wait.S:71 4 Thread 0x7ffff64f8700 (LWP 4445) "celery" pthread_barrier_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_barrier_wait.S:71 (gdb) PASS: gdb.threads/names.exp: list threads Seems recent-ish -- I don't see the failure in the logs of a testrun from O= ct 19. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22177-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 06 13:22:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 110455 invoked by alias); 6 Dec 2017 13:22:45 -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 110433 invoked by uid 48); 6 Dec 2017 13:22:44 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22556] Regression: gdb.threads/names.exp with --target_board=native-gdbserver Date: Wed, 06 Dec 2017 13:22: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone 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: 2017-q4/txt/msg00221.txt.bz2 Content-length: 511 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22556 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.1 --- Comment #1 from Pedro Alves --- Setting milestone so we don't forget. (I'm not looking at this right now.) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22178-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 06 13:28:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 128234 invoked by alias); 6 Dec 2017 13:28:26 -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 128207 invoked by uid 48); 6 Dec 2017 13:28:26 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22557] New: Regression: gdb.base/dtrace-probe.exp with --target_board=native-gdbserver Date: Wed, 06 Dec 2017 13:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00222.txt.bz2 Content-length: 1167 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22557 Bug ID: 22557 Summary: Regression: gdb.base/dtrace-probe.exp with --target_board=3Dnative-gdbserver Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- With --target_board=3Dnative-gdbserver, I'm seeing this regression compared= to a run on 20171018: Breakpoint 5, 0x00000000004005d2 in main () (gdb) PASS: gdb.base/dtrace-probe.exp: continue to breakpoint: test:progress-counter print $_probe_argc $1 =3D 2 (gdb) PASS: gdb.base/dtrace-probe.exp: print $_probe_argc for probe progress-counter print $_probe_arg0 $2 =3D 4195968 (gdb) FAIL: gdb.base/dtrace-probe.exp: print $_probe_arg0 for probe progress-counter This is with 846fefbdb228, meaning I still see this after commit 685de8c299= 0a ("Fix PR gdb/22491: Regression when setting SystemTap probe semaphores"). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22179-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 06 13:28:42 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 6233 invoked by alias); 6 Dec 2017 13:28:42 -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 5558 invoked by uid 48); 6 Dec 2017 13:28:42 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22557] Regression: gdb.base/dtrace-probe.exp with --target_board=native-gdbserver Date: Wed, 06 Dec 2017 13:28: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone 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: 2017-q4/txt/msg00223.txt.bz2 Content-length: 371 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22557 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22180-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 06 13:31:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 45051 invoked by alias); 6 Dec 2017 13:31:05 -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 45028 invoked by uid 48); 6 Dec 2017 13:31:05 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22557] Regression: gdb.base/dtrace-probe.exp Date: Wed, 06 Dec 2017 13:31: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc 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: 2017-q4/txt/msg00224.txt.bz2 Content-length: 825 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22557 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Regression: |Regression: |gdb.base/dtrace-probe.exp |gdb.base/dtrace-probe.exp |with | |--target_board=3Dnative-gdbse | |rver | --- Comment #1 from Pedro Alves --- Actually I see it too with the native target. I suspect this is more fall out from the probe C++ification. (Just a guess, I'm not really looking at it.) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22181-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 06 13:43:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 110492 invoked by alias); 6 Dec 2017 13:43:29 -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 110462 invoked by uid 48); 6 Dec 2017 13:43:29 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug shlibs/22558] New: Should make "nosharedlibrary" accept a regexp too Date: Wed, 06 Dec 2017 13:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: shlibs X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00225.txt.bz2 Content-length: 738 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22558 Bug ID: 22558 Summary: Should make "nosharedlibrary" accept a regexp too Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: shlibs Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- - "sharedlibrary" accepts a regexp to load the symbols of specific librarie= s. - "nosharedlibrary" ignore any argument and always unloads symbols of all libraries. It'd be handy/nice if "nosharedlibrary" also accepted a pattern. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22182-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 06 16:29:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35197 invoked by alias); 6 Dec 2017 16:29:46 -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 35171 invoked by uid 48); 6 Dec 2017 16:29:45 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22560] New: Avoid IPA interfering with regular breakpoints/debugging Date: Wed, 06 Dec 2017 16:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00226.txt.bz2 Content-length: 3444 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22560 Bug ID: 22560 Summary: Avoid IPA interfering with regular breakpoints/debugging Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- As shown in , = the IPA is nowadays using standard C++ types like std::vector/std::string and m= aybe others, which can conflict with regular debugging. See example at the bottom. Having regular debugging interfere with the IPAs internal operations is not ideal, of course. Pondering about this at least a few ideas came up: #1 - maybe we could somehow make GDB just not set user breakpoints in the I= PA (at least by default). Maybe add a new "do not debug me" attribute to shar= ed libraries, and then have gdbserver report it for the IPA dso. (To avoid hardcoding the name of the IPA library in GDB). This would make GDB not set breakpoints on inlined standard C++ functions/methods, but it wouldn't prev= ent running into breakpoints for calls to non-inlined standard functions/method= s. (i.e., it'd prevent running into std::vector::end if that's inlined, but no= t to std::string::whatever if it's not inlined.) #2 - just try harder to avoid calling into the C/C++ runtime in all the code transitively called by gdb_collect. #3 - Make sure the IPA is fully stripped, except for the symbols that it mu= st export for fast tracepoint functionality (the symbols that gdbserver must locate in the agent. Avoid calling into potentially non-inlined C/C++ runt= ime functions. Maybe solution #3 is the easiest. Thread 1 "ftrace" hit Breakpoint 1, main () at gdb/testsuite/gdb.trace/ftrace.c:50 50 begin (); (gdb) b end Breakpoint 2 at 0x40069b: end. (12 locations) (gdb) ftrace set_point Fast tracepoint 3 at 0x40068b: file src/gdb/testsuite/gdb.trace/ftrace.c, line 29. (gdb) tstart (gdb) c Continuing. Thread 1 "ftrace" hit Breakpoint 2, std::vector >::end (this=3D0x613e00) at /usr/include/c++/5.3.1/bits/stl_vector.h:566 566 { return iterator(this->_M_impl._M_finish); } (gdb) bt #0 0x00007ffff7b10bc0 in std::vector >::end() (this=3D0x613e00) at /usr/include/c++/5.3.1/bits/stl_vector.h:566 #1 0x00007ffff7b1082c in init_target_desc(target_desc*) (tdesc=3D0x613e0= 0) at src/gdb/gdbserver/tdesc.c:27 #2 0x00007ffff7b14048 in amd64_linux_read_description(unsigned long, boo= l) (xcr0=3D7, is_x32=3Dfalse) at src/gdb/gdbserver/linux-x86-tdesc.c:127 #3 0x00007ffff7b13e0b in get_ipa_tdesc(int) (idx=3D2) at src/gdb/gdbserver/linux-amd64-ipa.c:208 #4 0x00007ffff7b12d87 in gdb_collect(tracepoint*, unsigned char*) (tpoint=3D0x7ffff65c6010, regs=3D0x7fffffffd830 "\213\006@") at src/gdb/gdbserver/tracepoint.c:5800 #5 0x000000004000007a in () #6 0x00007ffff65c6010 in () #7 0x00007ffff7fbf740 in () #8 0x0000003100000007 in () #9 0x000000000040068b in marker (anarg=3D32767) at src/gdb/testsuite/gdb.trace/ftrace.c:28 #10 0x00000000004006c3 in main () at src/gdb/testsuite/gdb.trace/ftrace.c= :54 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22183-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 06 16:41:03 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 94789 invoked by alias); 6 Dec 2017 16:41:03 -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 94747 invoked by uid 48); 6 Dec 2017 16:41:01 -0000 From: "alexanderhochbaum at web dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/21100] clang follow-fork-mode child internal-error Date: Wed, 06 Dec 2017 16:41: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.12 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: alexanderhochbaum at web dot de X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00227.txt.bz2 Content-length: 876 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21100 alexanderhochbaum at web dot de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexanderhochbaum at web d= ot de --- Comment #2 from alexanderhochbaum at web dot de --- I have the same internal error but don't know how to easily backtrace gdb itself. So I can not see where it came from. In many locations the argument= to delete_breakpoint is checked before the call. Perhaps someone who knows the code can confirm this is not necessary for=20 delete_breakpoint (ps_data->jit_breakpoint); in #7 0x00000000006c2115 in free_objfile_data (objfile=3D0x39895b0, data=3D0x324b340) at jit.c:1491 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22184-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 06 19:35:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78049 invoked by alias); 6 Dec 2017 19:34:59 -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 78024 invoked by uid 48); 6 Dec 2017 19:34:59 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/22562] New: investigate linespec issues with rust Date: Wed, 06 Dec 2017 19:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00228.txt.bz2 Content-length: 1492 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22562 Bug ID: 22562 Summary: investigate linespec issues with rust Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- Ted reported this behavior from gdb 8.0: (gdb) info line webrender::resource_cache::ResourceCache::update_resources Line 274 of "/builds/worker/workspace/build/src/gfx/webrender/src/resource_cache.rs" starts at address 0x7fffe8c413e0 and ends at 0x7fffe8c41413 . (gdb) disassemble /m webrender::resource_cache::ResourceCache::update_resou= rces No type "resource_cache" within class or namespace "webrender". Quoting the symbol name made it work ok: (gdb) disassemble /m *'webrender::resource_cache::ResourceCache::update_resources' Dump of assembler code for function webrender::resource_cache::ResourceCache::update_resources: 99 fn remove(&mut self, key: ImageKey) -> Option { 0x00007fffe8c41da9 <+2505>: mov %r10,%r8 0x00007fffe8c41dac <+2508>: shr $0x20,%r8 So perhaps some kind of linespec work is needed for Rust. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22185-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 01:13:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 6777 invoked by alias); 7 Dec 2017 01:12:59 -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 6752 invoked by uid 48); 7 Dec 2017 01:12:59 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Thu, 07 Dec 2017 01:12: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: version 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: 2017-q4/txt/msg00229.txt.bz2 Content-length: 487 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 Adam Stylinski changed: What |Removed |Added ---------------------------------------------------------------------------- Version|8.0 |8.0.1 --- Comment #13 from Adam Stylinski --- Still seeing this bug on 8.0.1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22186-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 11:50:23 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 6530 invoked by alias); 7 Dec 2017 11:50: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 Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 6503 invoked by uid 48); 7 Dec 2017 11:50:22 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Thu, 07 Dec 2017 11:50: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00230.txt.bz2 Content-length: 725 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #14 from Pedro Alves --- Sounds like this is the same as Bug 22499 which I just fixed (in master) la= st week [1]. Any chance you could try out the master branch? [1] https://sourceware.org/ml/gdb-patches/2017-11/msg00748.html The workaround for current GB is "set displaced-stepping off". --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22187-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 15:05:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 30149 invoked by alias); 7 Dec 2017 15:05:55 -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 30123 invoked by uid 48); 7 Dec 2017 15:05:54 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22567] New: pending breakpoint location's gdbarch is incorrect after it is resolved Date: Thu, 07 Dec 2017 15:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00231.txt.bz2 Content-length: 2561 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22567 Bug ID: 22567 Summary: pending breakpoint location's gdbarch is incorrect after it is resolved Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: qiyao at gcc dot gnu.org Target Milestone: --- In gdb mainline (8.0.50.20171207), start gdb without executable, set a pend= ing breakpoint, load the executable, and run, (gdb) b set_point1 No symbol table is loaded. Use the "file" command. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (set_point1) pending. (gdb) file ./testsuite/outputs/gdb.trace/pending/pending=20 Reading symbols from ./testsuite/outputs/gdb.trace/pending/pending...done. (gdb) b main Breakpoint 2 at 0x4007c5: file /home/yao.qi/SourceCode/gnu/build/gdb/testsuite/../../../binutils-gdb/gdb/t= estsuite/gdb.trace/pending.c, line 28. (gdb) r Starting program: /home/yao.qi/SourceCode/gnu/build/gdb/testsuite/outputs/gdb.trace/pending/p= ending=20 Python Exception Installation error: gdb.execute_unwinders function is missing:=20 Python Exception Installation error: gdb.execute_unwinders function is missing:=20 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff63b5700 (LWP 24579)] Thread 1 "pending" hit Breakpoint 2, Python Exception Installation error: gdb.execute_unwinders function = is missing:=20 main () at /home/yao.qi/SourceCode/gnu/build/gdb/testsuite/../../../binutils-gdb/gdb/t= estsuite/gdb.trace/pending.c:28 28 const char *libname =3D "pendshr2.sl"; (gdb) info breakpoints=20 Num Type Disp Enb Address What 1 breakpoint keep y 0xf7bd569e ^^^^^^^^^^ 2 breakpoint keep y 0x00000000004007c5 in main=20 at /home/yao.qi/SourceCode/gnu/build/gdb/testsuite/../../../binutils-gdb/gdb/t= estsuite/gdb.trace/pending.c:28 breakpoint already hit 1 time (gdb) p set_point1 $1 =3D {} 0x7ffff7bd569e As we can see, the address of breakpoint 1 is wrong. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22188-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 15:08:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 21066 invoked by alias); 7 Dec 2017 15:08:46 -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 21043 invoked by uid 48); 7 Dec 2017 15:08:46 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22567] pending breakpoint location's gdbarch is incorrect after it is resolved Date: Thu, 07 Dec 2017 15:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_gcctarget bug_status cf_gcchost assigned_to target_milestone 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: 2017-q4/txt/msg00232.txt.bz2 Content-length: 2617 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22567 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |x86_64-pc-linux-gnu Status|NEW |ASSIGNED Host| |x86_64-pc-linux-gnu Assignee|unassigned at sourceware dot org |qiyao at gcc dot gn= u.org Target Milestone|--- |8.1 --- Comment #1 from Yao Qi --- GDB 8.0 is correct, so it is a regression. (gdb) b set_point1 No symbol table is loaded. Use the "file" command. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (set_point1) pending. (gdb) file ./testsuite/outputs/gdb.trace/pending/pending=20 Reading symbols from ./testsuite/outputs/gdb.trace/pending/pending...done. (gdb) b main Breakpoint 2 at 0x4007c5: file /home/yao.qi/SourceCode/gnu/gdb-8/build-8.0/gdb/testsuite/../../../gdb-8.0/= gdb/testsuite/gdb.trace/pending.c, line 28. (gdb) run Starting program: /home/yao.qi/SourceCode/gnu/gdb-8/build-8.0/gdb/testsuite/outputs/gdb.trace= /pending/pending=20 Python Exception Installation error: gdb.execute_unwinders function is missing:=20 Python Exception Installation error: gdb.execute_unwinders function is missing:=20 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff63b2700 (LWP 24608)] Thread 1 "pending" hit Breakpoint 2, Python Exception Installation error: gdb.execute_unwinders function = is missing:=20 main () at /home/yao.qi/SourceCode/gnu/gdb-8/build-8.0/gdb/testsuite/../../../gdb-8.0/= gdb/testsuite/gdb.trace/pending.c:28 28 const char *libname =3D "pendshr2.sl"; (gdb) info breakpoints=20 Num Type Disp Enb Address What 1 breakpoint keep y 0x00007ffff7bd569e ^^^^^^^^^^^^^^^^^^ 2 breakpoint keep y 0x00000000004007c5 in main=20 at /home/yao.qi/SourceCode/gnu/gdb-8/build-8.0/gdb/testsuite/../../../gdb-8.0/= gdb/testsuite/gdb.trace/pending.c:28 breakpoint already hit 1 time (gdb) p set_point1 $1 =3D {} 0x7ffff7bd569e --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22189-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 15:14:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 78749 invoked by alias); 7 Dec 2017 15:14:11 -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 78720 invoked by uid 48); 7 Dec 2017 15:14:11 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Thu, 07 Dec 2017 15:14: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00233.txt.bz2 Content-length: 1149 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #15 from Adam Stylinski --- (In reply to Pedro Alves from comment #14) > Sounds like this is the same as Bug 22499 which I just fixed (in master) > last week [1]. Any chance you could try out the master branch? >=20 > [1] https://sourceware.org/ml/gdb-patches/2017-11/msg00748.html >=20 > The workaround for current GB is "set displaced-stepping off". Sure, can you send me a link to the repo? Your workaround seems to be correct, so there's a good chance your fix will work: (gdb) set displaced-stepping off (gdb) r Starting program: /home/adam/test.out=20 Breakpoint 1, testFunc (a=3D0x0, n=3D0, sx=3D0x0, sy=3D0x0, rc=3D0x0, nr=3D= 0, b=3D4,=20 f=3D9.50000026e+09, c=3D0x0, d=3D0x0, e=3D0x0, gx=3D0x0, gy=3D0x0, gz= =3D0x0) at test.cpp:12 12 float lambda =3D C_LIGHT / f; (gdb) n 13 printf("lambda =3D %f\n", lambda); (gdb) n lambda =3D 0.031557 14 } (gdb) n main () at test.cpp:21 21 return 0; (gdb) n 22 } (gdb) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22190-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 15:56:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 111747 invoked by alias); 7 Dec 2017 15:56:19 -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 111719 invoked by uid 48); 7 Dec 2017 15:56:19 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Thu, 07 Dec 2017 15:56: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00234.txt.bz2 Content-length: 466 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #16 from Pedro Alves --- (In reply to Adam Stylinski from comment #15) > Sure, can you send me a link to the repo? https://sourceware.org/gdb/current/ > Your workaround seems to be correct, so there's a good chance your fix wi= ll > work: Awesome, that's a very good indication indeed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22191-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 16:13:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 63191 invoked by alias); 7 Dec 2017 16:13:32 -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 63167 invoked by uid 48); 7 Dec 2017 16:13:32 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22567] pending breakpoint location's gdbarch is incorrect after it is resolved Date: Thu, 07 Dec 2017 16:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00235.txt.bz2 Content-length: 424 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22567 --- Comment #2 from Yao Qi --- git bisect find this commit, commit 4024cf2b8d864279ff87af1a2ade77ab6d710d50 Author: Pedro Alves Date: Wed Nov 29 19:25:58 2017 +0000 Fix setting-breakpoints regression on PPC64 (function descriptors) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22192-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 16:14:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64066 invoked by alias); 7 Dec 2017 16:14:41 -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 64037 invoked by uid 48); 7 Dec 2017 16:14:41 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Thu, 07 Dec 2017 16:14: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00236.txt.bz2 Content-length: 884 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #17 from Adam Stylinski --- (In reply to Pedro Alves from comment #16) > (In reply to Adam Stylinski from comment #15) >=20 > > Sure, can you send me a link to the repo? >=20 > https://sourceware.org/gdb/current/ >=20 > > Your workaround seems to be correct, so there's a good chance your fix = will > > work: >=20 > Awesome, that's a very good indication indeed. Hmm, getting a build error: target-descriptions.c: In member function =E2=80=98virtual void print_c_tdesc::visit_pre(const target_desc*)=E2=80=99: target-descriptions.c:1836:16: error: types may not be defined in a for-range-declaration [-Werror] for (const struct bfd_arch_info *compatible : e->compatible) ^~~~~~ --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22193-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 16:40:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 131011 invoked by alias); 7 Dec 2017 16:40:05 -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 130979 invoked by uid 48); 7 Dec 2017 16:40:03 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Thu, 07 Dec 2017 16:40: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00237.txt.bz2 Content-length: 1260 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #18 from Adam Stylinski --- (In reply to Adam Stylinski from comment #17) > (In reply to Pedro Alves from comment #16) > > (In reply to Adam Stylinski from comment #15) > >=20 > > > Sure, can you send me a link to the repo? > >=20 > > https://sourceware.org/gdb/current/ > >=20 > > > Your workaround seems to be correct, so there's a good chance your fi= x will > > > work: > >=20 > > Awesome, that's a very good indication indeed. >=20 > Hmm, getting a build error: >=20 > target-descriptions.c: In member function =E2=80=98virtual void > print_c_tdesc::visit_pre(const target_desc*)=E2=80=99: > target-descriptions.c:1836:16: error: types may not be defined in a > for-range-declaration [-Werror] > for (const struct bfd_arch_info *compatible : e->compatible) > ^~~~~~ I think I may have fixed this build error, modified the type to be something that was already declared as a type (const bfd_arch_info_type*). My guess = is at some point this struct was typedef'd to this and meant to be used this w= ay.=20 I'll let you know if this version fixes it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22194-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 16:50:46 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 34546 invoked by alias); 7 Dec 2017 16:50:46 -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 34519 invoked by uid 48); 7 Dec 2017 16:50:45 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Thu, 07 Dec 2017 16:50: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00238.txt.bz2 Content-length: 4277 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #19 from Adam Stylinski --- (In reply to Adam Stylinski from comment #18) > (In reply to Adam Stylinski from comment #17) > > (In reply to Pedro Alves from comment #16) > > > (In reply to Adam Stylinski from comment #15) > > >=20 > > > > Sure, can you send me a link to the repo? > > >=20 > > > https://sourceware.org/gdb/current/ > > >=20 > > > > Your workaround seems to be correct, so there's a good chance your = fix will > > > > work: > > >=20 > > > Awesome, that's a very good indication indeed. > >=20 > > Hmm, getting a build error: > >=20 > > target-descriptions.c: In member function =E2=80=98virtual void > > print_c_tdesc::visit_pre(const target_desc*)=E2=80=99: > > target-descriptions.c:1836:16: error: types may not be defined in a > > for-range-declaration [-Werror] > > for (const struct bfd_arch_info *compatible : e->compatible) > > ^~~~~~ >=20 > I think I may have fixed this build error, modified the type to be someth= ing > that was already declared as a type (const bfd_arch_info_type*). My guess > is at some point this struct was typedef'd to this and meant to be used t= his > way. I'll let you know if this version fixes it. adam@eggsbenedict ~/scratch/binutils-gdb/gdb $ ./gdb ~/test.out=20 Exception caught while booting Guile. Error in function "open-file": No such file or directory: "/usr/share/gdb/guile/gdb/boot.scm" ./gdb: warning: Could not complete Guile gdb module initialization from: /usr/share/gdb/guile/gdb/boot.scm. Limited Guile support is available. Suggest passing --data-directory=3D/path/to/gdb/data-directory. GNU gdb (GDB) 8.0.50.20171207-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /home/adam/test.out...done. (gdb) break testFunc Breakpoint 1 at 0x400530: file test.cpp, line 12. (gdb) r Starting program: /home/adam/test.out=20 Breakpoint 1, testFunc (a=3D0x0, n=3D0, sx=3D0x0, sy=3D0x0, rc=3D0x0, nr=3D= 0, b=3D4, f=3D9.50000026e+09, c=3D0x0, d=3D0x0, e=3D0x0, gx=3D0x0, gy=3D0x0, gz=3D0x0= ) at test.cpp:12 12 float lambda =3D C_LIGHT / f; (gdb) n 13 printf("lambda =3D %f\n", lambda); (gdb)=20 lambda =3D 0.031557 14 } (gdb) n main () at test.cpp:21 21 return 0; (gdb) c Continuing. [Inferior 1 (process 1119) exited normally] (gdb) set displaced-stepping on (gdb) r Starting program: /home/adam/test.out=20 Breakpoint 1, testFunc (a=3D0x0, n=3D0, sx=3D0x0, sy=3D0x0, rc=3D0x0, nr=3D= 0, b=3D4, f=3D9.50000026e+09, c=3D0x0, d=3D0x0, e=3D0x0, gx=3D0x0, gy=3D0x0, gz=3D0x0= ) at test.cpp:12 12 float lambda =3D C_LIGHT / f; (gdb) n 13 printf("lambda =3D %f\n", lambda); (gdb)=20 lambda =3D 0.031557 14 } (gdb)=20 main () at test.cpp:21 21 return 0; (gdb) c Continuing. [Inferior 1 (process 1186) exited normally] Looks good. Here's a patch for that build error, though I assume someone will eventually catch this: diff --git a/gdb/target-descriptions.c b/gdb/target-descriptions.c index 5a6f61945d..363ddf5ac6 100644 --- a/gdb/target-descriptions.c +++ b/gdb/target-descriptions.c @@ -1832,8 +1832,7 @@ public: gdbarch_osabi_name (tdesc_osabi (e))); printf_unfiltered ("\n"); } - - for (const struct bfd_arch_info *compatible : e->compatible) + for (const bfd_arch_info_type *compatible : e->compatible) printf_unfiltered (" tdesc_add_compatible (result, bfd_scan_arch (\"%s\"));\n", compatible->printable_name); --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22195-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 16:57:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 27480 invoked by alias); 7 Dec 2017 16:57:25 -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 27445 invoked by uid 48); 7 Dec 2017 16:57:25 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Thu, 07 Dec 2017 16:57: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00239.txt.bz2 Content-length: 534 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #20 from Adam Stylinski --- Oh also - do you know if your fix could be backported to other releases and pushed to the distributions? It's awesome my debugger doesn't corrupt memo= ry anymore when debugging functions. I guess I can remember to use the workar= ound in the interim - though this makes stepping over a breakpoint impossible, doesn't it? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22196-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 17:16:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122277 invoked by alias); 7 Dec 2017 17:16:45 -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 122256 invoked by uid 48); 7 Dec 2017 17:16:45 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22569] New: Internal error when using "break -source test.c main" Date: Thu, 07 Dec 2017 17:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00240.txt.bz2 Content-length: 1428 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22569 Bug ID: 22569 Summary: Internal error when using "break -source test.c main" Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: simon.marchi at ericsson dot com Target Milestone: --- With this test file: #include #define IS_EVEN(n) (n % 2 =3D=3D 0) namespace foo { bool main () { return true; } } int prout () { return 2; } int main (int argc, char **argv) { if (IS_EVEN (argc) && foo::main () && prout () =3D=3D 3) return 1; else return 0; } Compiled with: g++ test.cpp -o test -g3 -O0 Gives an internal error when running: ./gdb --data-directory=3Ddata-directory -nx test -ex "break -source test.= cpp main" /home/emaisin/src/binutils-gdb/gdb/linespec.c:3302: internal-error: void decode_line_full(const event_location*, int, program_space*, symtab*, int, linespec_result*, const char*, const char*): Assertion `result.size () =3D= =3D 1 || canonical->pre_expanded' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22197-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 17:18:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 123899 invoked by alias); 7 Dec 2017 17:18:37 -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 123872 invoked by uid 48); 7 Dec 2017 17:18:37 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22569] Internal error when using "break -source test.c main" Date: Thu, 07 Dec 2017 17:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: cc 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: 2017-q4/txt/msg00241.txt.bz2 Content-length: 411 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22569 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.marchi at ericsson d= ot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22198-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 17:54:47 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107366 invoked by alias); 7 Dec 2017 17:54:47 -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 107322 invoked by uid 48); 7 Dec 2017 17:54:46 -0000 From: "kungfujesus06 at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Thu, 07 Dec 2017 17:54: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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: 2017-q4/txt/msg00242.txt.bz2 Content-length: 395 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #21 from Adam Stylinski --- Created attachment 10669 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10669&action=3Ded= it fix for building gdb In case you wanted a formal patch (attribution and such). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22199-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 18:19:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 59864 invoked by alias); 7 Dec 2017 18:19:53 -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 59820 invoked by uid 48); 7 Dec 2017 18:19:53 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Thu, 07 Dec 2017 18:19: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00243.txt.bz2 Content-length: 1320 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #22 from Pedro Alves --- (In reply to Adam Stylinski from comment #20) > Oh also - do you know if your fix could be backported to other releases a= nd > pushed to the distributions? It's awesome my debugger doesn't corrupt > memory anymore when debugging functions.=20=20 I think it should be backportable. It's a nasty bug, and I think the fix c= an't make things worse. I'll look into merging into the 8.0 branch when I have a chance, but I don't know whether/when your distro will pick it up. I think Fedora gdb will backport it, or already has, not sure. > I guess I can remember to use the > workaround in the interim - though this makes stepping over a breakpoint > impossible, doesn't it? No, GDB should still be able to move past breakpoints. Did that fail for y= ou? With "set displaced-stepping off" GDB has to stop all threads, remove breakpoint, single-step the thread, reinsert breakpoint, and re-resume all other threads. With displaced stepping, gdb steps the breakpoint out-of-li= ne without disturbing the other threads. So the workaround disables an optimization. (Though things were different in older releases.) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22200-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 18:20:18 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 61169 invoked by alias); 7 Dec 2017 18:20:18 -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 61142 invoked by uid 48); 7 Dec 2017 18:20:17 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Thu, 07 Dec 2017 18:20: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00244.txt.bz2 Content-length: 399 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #23 from Pedro Alves --- (In reply to Adam Stylinski from comment #21) > Created attachment 10669 [details] > fix for building gdb >=20 > In case you wanted a formal patch (attribution and such). Thanks! I'll push it in. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22201-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 18:39:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 36336 invoked by alias); 7 Dec 2017 18:39:15 -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 36307 invoked by uid 55); 7 Dec 2017 18:39:15 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug c++/21222] A function with VEX encoded SSE instructions and a particular number of arguments corrupts a value calculated on the stack when stepping through the function Date: Thu, 07 Dec 2017 18: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00245.txt.bz2 Content-length: 1271 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21222 --- Comment #24 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D23a8d1862b7e= 5b95f0fe9d724c6be326e545e6d1 commit 23a8d1862b7e5b95f0fe9d724c6be326e545e6d1 Author: Adam Stylinski Date: Thu Dec 7 12:51:03 2017 -0500 Fix build with g++ 6.3.1 With g++ 6.3.1: target-descriptions.c: In member function =E2=80=98virtual void print_c_tdesc::visit_pre(const target_desc*)=E2=80=99: target-descriptions.c:1836:16: error: types may not be defined in a for-range-declaration [-Werror] for (const struct bfd_arch_info *compatible : e->compatible) ^~~~~~ I think at some point the forward declaration of this struct had been removed and declared as a typedef. This fixes that. gdb/ChangeLog: 2017-12-07 Adam Stylinski PR c++/21222 * target-descriptions.c (print_c_tdesc::visit_pre): Change type of range-for variable. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22202-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 19:25:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 112027 invoked by alias); 7 Dec 2017 19:25:54 -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 111967 invoked by uid 48); 7 Dec 2017 19:25:53 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22569] Internal error when using "break -source test.c main" Date: Thu, 07 Dec 2017 19:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to 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: 2017-q4/txt/msg00246.txt.bz2 Content-length: 1369 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22569 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com Assignee|unassigned at sourceware dot org |keiths at redhat do= t com --- Comment #1 from Keith Seitz --- This is happening because convert_explicit_location_to_linespec (or some caller?) doesn't check whether the resultant explicit location is valid/fully-specified. The original input string parses as "-source", "test.cpp", and "main". The first two tokens are converted to the explicit (under-specified) source filename. "main" is passed to create_breakpoint as the EXTRA_STRING argument (used for dprtinf conditions or thread/condition/task parsing). However once this explicit location is converted into SaLs, nothing apparen= tly validates the explicit location (or at least this particular (mis)usage). convert_explicit_location_to_linespec does some checking for valid input, e= .g., if a -label is specified but doesn't exit, it will error. I think that it should also check this case, where the input is underspecif= ied. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22203-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 19:42:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 13617 invoked by alias); 7 Dec 2017 19:42:33 -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 13586 invoked by uid 48); 7 Dec 2017 19:42:33 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22569] Internal error when using "break -source test.c main" Date: Thu, 07 Dec 2017 19:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com 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: 2017-q4/txt/msg00247.txt.bz2 Content-length: 432 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22569 --- Comment #2 from Keith Seitz --- (In reply to Keith Seitz from comment #1) > ... (or some caller?) ... Actually, this check is normally performed in string_to_event_location, but there is an early return which does /not/ perform the check. Working on patch/test. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22204-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 21:21:26 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 62373 invoked by alias); 7 Dec 2017 21:21:26 -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 62347 invoked by uid 48); 7 Dec 2017 21:21:26 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22569] Internal error when using "break -source test.c main" Date: Thu, 07 Dec 2017 21:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status 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: 2017-q4/txt/msg00248.txt.bz2 Content-length: 518 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22569 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #3 from Keith Seitz --- Patch submitted: https://sourceware.org/ml/gdb-patches/2017-12/msg00147.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22205-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 21:53:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 7587 invoked by alias); 7 Dec 2017 21:53:35 -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 7548 invoked by uid 55); 7 Dec 2017 21:53:34 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22511] Regression in "commands" Date: Thu, 07 Dec 2017 21:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00249.txt.bz2 Content-length: 1519 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22511 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D99598d713f45= d1b26015ec3562d160dc2b3792e4 commit 99598d713f45d1b26015ec3562d160dc2b3792e4 Author: Tom Tromey Date: Fri Nov 3 10:26:11 2017 -0600 Fix regression in "commands" Pedro pointed out a regression in "commands", where trying to clear a breakpoint's command list would fail: (top-gdb) commands Type commands for breakpoint(s) 3, one per line. End with a line saying just "end". >end No breakpoints specified. (top-gdb) I believe the bug was introduced by my patch that changes counted_command_line to be a shared_ptr. This causes the problem because now the counted_command_line in commands_command_1 can be NULL, whereas previously it never could be. After some discussion, we agreed to simply remove the error case from commands_command_1. 2017-12-07 Tom Tromey PR breakpoints/22511: * breakpoint.c (commands_command_1): Don't throw an exception when no commands have been read. 2017-12-07 Tom Tromey * gdb.base/break.exp: Add test for empty "commands". --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22206-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 21:54:39 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 13479 invoked by alias); 7 Dec 2017 21:54:39 -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 13450 invoked by uid 48); 7 Dec 2017 21:54:38 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22511] Regression in "commands" Date: Thu, 07 Dec 2017 21:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00250.txt.bz2 Content-length: 508 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22511 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Tom Tromey --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22207-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 23:40:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 112192 invoked by alias); 7 Dec 2017 23:40:04 -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 112157 invoked by uid 55); 7 Dec 2017 23:40:03 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22569] Internal error when using "break -source test.c main" Date: Thu, 07 Dec 2017 23:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com 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: 2017-q4/txt/msg00251.txt.bz2 Content-length: 2927 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22569 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Keith Seitz : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dfa6eb693cf43= b427474b1d96ce093f6ea9e5da6a commit fa6eb693cf43b427474b1d96ce093f6ea9e5da6a Author: Keith Seitz Date: Thu Dec 7 12:59:07 2017 -0800 Validate explicit locations with early termination breakpoints/22569 involves an internal error generated by the rather innocent looking command: (gdb) break -source test.cpp main .../linespec.c:3302: internal-error: void decode_line_full(...): Assertion `result.size () =3D=3D 1 || canonical->pre_expanded' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) The input string is tokenized into "-source", "test.cpp", and "main" (input parsing breaks on whitespace). create_breakpoint is then called = with the explicit location (containing only the source file name) and "main"= as the extra_string argument. No SaLs are created for this underspecified explicit location, and the "result.size () =3D=3D 1" evaluates false (as does the pre_expanded con= dition). This triggers the assertion. Normally string_to_explicit_location validates the input string. Howev= er, the presence of the string "main" causes the parser to exit early: 802 else 803 { 804 /* End of the explicit location specification. 805 Stop parsing and return whatever explicit location= was 806 parsed. */ 807 *argp =3D start; 808 return location; 809 } This bypasses the validation that is done a few lines down in this func= tion which would have emitted the expected error. This patch fixes that. Additionally, this patch also fixes an inconsistency with error reporti= ng in this use case: (gdb) b -source foo Source filename requires function, label, or line offset. (gdb) b -source foo main No source file named foo. These two commands should have elicited the same error message. gdb/ChangeLog: PR breakpoints/22569 * location.c (string_to_explicit_location): When terminating parsing early, break out of enclosing loop instead of returning. gdb/testsuite/ChangeLog: PR breakpoints/22569 * gdb.linespec/ls-errs.exp: Change expected result of "break -source this file has spaces.c -line 3". Check that an explicit source file followed by whitespace is identified as an invalid explicit location. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22208-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 07 23:41:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 113853 invoked by alias); 7 Dec 2017 23:41:55 -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 113826 invoked by uid 48); 7 Dec 2017 23:41:54 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22569] Internal error when using "break -source test.c main" Date: Thu, 07 Dec 2017 23:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00252.txt.bz2 Content-length: 525 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22569 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Keith Seitz --- Patch confirmed, closing bug. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22209-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 08 15:47:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 678 invoked by alias); 8 Dec 2017 15:47:58 -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 652 invoked by uid 55); 8 Dec 2017 15:47:58 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22567] pending breakpoint location's gdbarch is incorrect after it is resolved Date: Fri, 08 Dec 2017 15:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00253.txt.bz2 Content-length: 1365 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22567 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Yao Qi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D6b05c8bd4371= 52d7a3ecfc19074ab243ee6c92f2 commit 6b05c8bd437152d7a3ecfc19074ab243ee6c92f2 Author: Yao Qi Date: Fri Dec 8 15:43:49 2017 +0000 Fix PR 22567: set SAL .section in minsym_found PR 22567 is that breakpoint location can't correct gdbarch from SAL, because its fields .section and .symtab is NULL. We use to have code setting .section, but was removed by 4024cf2 - if (msymbol_is_text (msymbol)) + CORE_ADDR func_addr; + if (msymbol_is_function (objfile, msymbol, &func_addr)) { - sal =3D find_pc_sect_line (MSYMBOL_VALUE_ADDRESS (objfile, msymb= ol), - (struct obj_section *) 0, 0); - sal.section =3D MSYMBOL_OBJ_SECTION (objfile, msymbol); this patch adds this back by moving it to the common place at the bottom of the function. gdb: 2017-12-08 Yao Qi PR breakpionts/22567 * linespec.c (minsym_found): Set sal.section. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22210-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 08 16:18:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 48869 invoked by alias); 8 Dec 2017 16:18:29 -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 48837 invoked by uid 48); 8 Dec 2017 16:18:29 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/22562] investigate linespec issues with rust Date: Fri, 08 Dec 2017 16:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q4/txt/msg00254.txt.bz2 Content-length: 340 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22562 --- Comment #1 from Tom Tromey --- It would also be good to look at replicating the new C++ linespec behavior, where "break method" will break on methods in any namespace. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22211-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 08 16:25:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 91672 invoked by alias); 8 Dec 2017 16:25:15 -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 91646 invoked by uid 48); 8 Dec 2017 16:25:15 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug cli/22573] New: "finish" doesn't respect "set print pretty" Date: Fri, 08 Dec 2017 16:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00255.txt.bz2 Content-length: 1680 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22573 Bug ID: 22573 Summary: "finish" doesn't respect "set print pretty" Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: cli Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- I "finished" from a function that returned a structure and got: Value returned is $10 =3D (0x7fffe45a98c8, rustc_trans::debuginfo::metadata::MemberDescriptionFactory::VariantMDF(rust= c_trans::debuginfo::metadata::VariantMemberDescriptionFactory {offsets: alloc::vec::Vec {buf: alloc::raw_vec::RawVec {ptr: core::ptr::Unique {pointer: core::nonzero::NonZero<*const rustc::ty::layout::Size> (0x7fffe43b2b10), _marker: core::marker::PhantomData}, cap: 2, a: alloc::heap::Heap}, len: 2}, args: alloc::vec::Vec<(alloc::string::String, &rustc::ty::TyS)> {buf: alloc::raw_vec::RawVec<(alloc::string::String, &rustc::ty::TyS), alloc::heap::Heap> {ptr: core::ptr::Unique<(alloc::string::String, &rustc::ty::TyS)> {pointer: core::nonzero::NonZero<*const (alloc::string::String, &rustc::ty::TyS)> (0x7fffe4bbaa90), _marker: core::marker::PhantomData<(alloc::string::String, &rustc::ty::TyS)>}, cap: 2, a: alloc::heap::Heap}, len: 2}, span: syntax_pos::span_encoding::Span (71170)})) That's all on one line. I expected it to respect "set print pretty", but it did not. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22212-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 08 16:38:05 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 124880 invoked by alias); 8 Dec 2017 16:38:05 -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 124853 invoked by uid 48); 8 Dec 2017 16:38:04 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/22574] New: support ptype/o in rust Date: Fri, 08 Dec 2017 16:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00256.txt.bz2 Content-length: 671 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22574 Bug ID: 22574 Summary: support ptype/o in rust Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- Bug 16224 is adding pahole-like functionality via "ptype/o". The rust type printer should support this as well. I have started a patch for this, so contact me if you plan to pick this up. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22213-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 08 16:38:12 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 125212 invoked by alias); 8 Dec 2017 16:38:12 -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 125182 invoked by uid 48); 8 Dec 2017 16:38:12 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/22574] support ptype/o in rust Date: Fri, 08 Dec 2017 16:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: dependson 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: 2017-q4/txt/msg00257.txt.bz2 Content-length: 499 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22574 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |16224 Referenced Bugs: https://sourceware.org/bugzilla/show_bug.cgi?id=3D16224 [Bug 16224] add "pahole" functionality to ptype --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22214-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 08 16:38:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 125360 invoked by alias); 8 Dec 2017 16:38:13 -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 125316 invoked by uid 48); 8 Dec 2017 16:38:13 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug cli/16224] add "pahole" functionality to ptype Date: Fri, 08 Dec 2017 16:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: blocked 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: 2017-q4/txt/msg00258.txt.bz2 Content-length: 487 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16224 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |22574 Referenced Bugs: https://sourceware.org/bugzilla/show_bug.cgi?id=3D22574 [Bug 22574] support ptype/o in rust --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22215-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 08 16:42:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 129364 invoked by alias); 8 Dec 2017 16:42:17 -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 129333 invoked by uid 48); 8 Dec 2017 16:42:17 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22557] Regression: gdb.base/dtrace-probe.exp Date: Fri, 08 Dec 2017 16:42: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00259.txt.bz2 Content-length: 505 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22557 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #2 from Sergio Durigan Junior --- I'm looking into this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22216-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 08 17:32:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 125472 invoked by alias); 8 Dec 2017 17:32:22 -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 125448 invoked by uid 48); 8 Dec 2017 17:32:21 -0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22567] pending breakpoint location's gdbarch is incorrect after it is resolved Date: Fri, 08 Dec 2017 17:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.1 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00260.txt.bz2 Content-length: 492 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22567 Yao Qi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Yao Qi --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22217-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 08 19:36:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 46104 invoked by alias); 8 Dec 2017 19:36:16 -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 46076 invoked by uid 48); 8 Dec 2017 19:36:16 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug testsuite/22420] gdb.base/dtrace-probe.exp not working (as in "not able to run") Date: Fri, 08 Dec 2017 19:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com 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: 2017-q4/txt/msg00261.txt.bz2 Content-length: 237 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22420 --- Comment #1 from Sergio Durigan Junior --- I have a patch for this. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22218-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 08 19:53:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 32670 invoked by alias); 8 Dec 2017 19:53:10 -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 32637 invoked by uid 48); 8 Dec 2017 19:53:10 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22557] Regression: gdb.base/dtrace-probe.exp Date: Fri, 08 Dec 2017 19:53: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00262.txt.bz2 Content-length: 497 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22557 --- Comment #3 from Sergio Durigan Junior --- The test is failing for me even before the C++-ification patch, which exclu= des the possibility of a regression introduced by the series. Unfortunately I cannot test things with the regular dtrace program, because= it is proprietary. So it may very well be a problem with pdtrace. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22219-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 08 20:40:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 65591 invoked by alias); 8 Dec 2017 20:40:10 -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 65569 invoked by uid 55); 8 Dec 2017 20:40:10 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22557] Regression: gdb.base/dtrace-probe.exp Date: Fri, 08 Dec 2017 20:40: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00263.txt.bz2 Content-length: 1428 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22557 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D92469284a650= 232768523564f2c715c4ebb57906 commit 92469284a650232768523564f2c715c4ebb57906 Author: Sergio Durigan Junior Date: Fri Dec 8 15:33:55 2017 -0500 Fix thinko on dtrace-probe.c:dtrace_process_dof_probe While investigating PR gdb/22557 ("Regression: gdb.base/dtrace-probe.exp"), I noticed that the code is wrongly declaring a new "expression_up" variable inside the TRY block in "dtrace_process_dof_probe". This causes the outter "expr" variable to be empty, which may have an impact later when evaluating the expression. This commit fixes that. Unfortunately the script used to test DTrace probes (gdb/testsuite/lib/pdtrace.in) is not very reliable so I cannot say whether this commit fixes the PR mentioned above. Nonetheless, it's an obvious fix and should go in. gdb/ChangeLog: 2017-12-08 Sergio Durigan Junior * dtrace-probe.c (dtrace_process_dof_probe): Do not declare a new "expression_up" inside the TRY block. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22220-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Dec 09 11:03:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66939 invoked by alias); 9 Dec 2017 11:03:22 -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 66914 invoked by uid 48); 9 Dec 2017 11:03:21 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/22576] New: ppc64: gdbarch_skip_trampoline_code fails for relro Date: Sat, 09 Dec 2017 11:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00264.txt.bz2 Content-length: 2735 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22576 Bug ID: 22576 Summary: ppc64: gdbarch_skip_trampoline_code fails for relro Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Target Milestone: --- ppc64 ld switched default norelro->relro by: 647e4d46495f2bfb0950fd1066c8a660173cca40 is the first bad commit commit 647e4d46495f2bfb0950fd1066c8a660173cca40 Author: H.J. Lu Date: Wed Jun 22 05:37:24 2016 -0700 ld: Add a linker configure option --enable-relro Tested gdb: c5ba17787d077249ab7071192566a2c0205fc97f 2017-12-09 runtest gdb.reverse/solib-pr ecsave.exp FAIL: gdb.reverse/solib-precsave.exp: reverse-step back to main one FAIL: gdb.reverse/solib-precsave.exp: reverse-step into solib function two FAIL: gdb.reverse/solib-precsave.exp: reverse-step within solib function two FAIL: gdb.reverse/solib-precsave.exp: reverse-step back to main two FAIL: gdb.reverse/solib-precsave.exp: run until end part two FAIL: gdb.reverse/solib-precsave.exp: reverse-next over solib function one (gdb) PASS: gdb.reverse/solib-precsave.exp: reverse-step within solib funct= ion one reverse-step^M 0x00000000100005d8 in 00000017.plt_call.shr2 ()^M (gdb) FAIL: gdb.reverse/solib-precsave.exp: reverse-step back to main one Also reproducible as: PASS: gcc outputs/gdb.reverse/solib-precsave/shr2.c.o -shared -Wl,-soname,shr2.sl= -g -lm -o outputs/gdb.reverse/solib-precsave/shr2.sl -Wl,-z,norelro ../gdb -batch -data-directory ../data-directory/ outputs/gdb.reverse/solib-precsave/solib-precsave -q -ex 'b 38' -ex r -ex record -ex n -ex reverse-step -ex reverse-step -ex 'set debug infrun 0' -ex reverse-step=20 No more reverse-execution history. main () at /home/fedora/jankratochvil/redhat/gdb-git/gdb/testsuite/gdb.reverse/solib-r= everse.c:38 38 b[1] =3D shr2(17); /* middle part two */ FAIL: gcc outputs/gdb.reverse/solib-precsave/shr2.c.o -shared -Wl,-soname,shr2.sl= -g -lm -o outputs/gdb.reverse/solib-precsave/shr2.sl -Wl,-z,relro ../gdb -batch -data-directory ../data-directory/ outputs/gdb.reverse/solib-precsave/solib-precsave -q -ex 'b 38' -ex r -ex record -ex n -ex reverse-step -ex reverse-step -ex 'set debug infrun 0' -ex reverse-step=20 22 return 2*x; 0x00000000100005d8 in 00000017.plt_call.shr2 () It is due to ppc64_skip_trampoline_code_1 does not recognizing PLT from ld = -z relro. This makes gdbarch_skip_trampoline_code to fail (return zero). --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22221-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Dec 10 07:36:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 14901 invoked by alias); 10 Dec 2017 07:36:13 -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 14870 invoked by uid 48); 10 Dec 2017 07:36:12 -0000 From: "hi-angel at yandex dot ru" To: gdb-prs@sourceware.org Subject: [Bug gdb/22472] Arguments evaluation doesn't always work Date: Sun, 10 Dec 2017 07:36: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hi-angel at yandex dot ru X-Bugzilla-Status: UNCONFIRMED 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: bug_status resolution 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: 2017-q4/txt/msg00265.txt.bz2 Content-length: 549 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22472 Hi-Angel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |--- --- Comment #4 from Hi-Angel --- Reopening per lack of elaboration on reasons of closing. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22222-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Dec 10 12:00:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 9133 invoked by alias); 10 Dec 2017 12:00:40 -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 9102 invoked by uid 48); 10 Dec 2017 12:00:39 -0000 From: "schwab@linux-m68k.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22472] Arguments evaluation doesn't always work Date: Sun, 10 Dec 2017 12:00: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: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: schwab@linux-m68k.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00266.txt.bz2 Content-length: 617 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22472 Andreas Schwab changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #5 from Andreas Schwab --- Arguments to user-defined commands aren't evaluated, they are textually spl= it on spaces, as documented in the manual. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22223-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Dec 10 16:13:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53125 invoked by alias); 10 Dec 2017 16:13:17 -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 53094 invoked by uid 48); 10 Dec 2017 16:13:17 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/22576] ppc64: gdbarch_skip_trampoline_code fails for relro Date: Sun, 10 Dec 2017 16:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com 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: cc 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: 2017-q4/txt/msg00267.txt.bz2 Content-length: 572 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22576 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amodra at gmail dot com, | |jan.kratochvil at redhat d= ot com, | |ulrich.weigand at de dot i= bm.com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22224-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Dec 10 22:22:15 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 4643 invoked by alias); 10 Dec 2017 22:22:14 -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 4616 invoked by uid 48); 10 Dec 2017 22:22:14 -0000 From: "amodra at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/22576] ppc64: gdbarch_skip_trampoline_code fails for relro Date: Sun, 10 Dec 2017 22:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: amodra at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: amodra at gmail dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to 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: 2017-q4/txt/msg00268.txt.bz2 Content-length: 456 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22576 Alan Modra changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at sourceware dot org |amodra at gmail dot= com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22225-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 06:12:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 22342 invoked by alias); 11 Dec 2017 06:12:41 -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 22316 invoked by uid 48); 11 Dec 2017 06:12:41 -0000 From: "amodra at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/22576] ppc64: gdbarch_skip_trampoline_code fails for relro Date: Mon, 11 Dec 2017 06:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: amodra at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: amodra at gmail dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00269.txt.bz2 Content-length: 977 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22576 Alan Modra changed: What |Removed |Added ---------------------------------------------------------------------------- CC|amodra at gmail dot com | --- Comment #1 from Alan Modra --- This isn't a simple matter of some plt call sequence not being recognized. = The reason ppc64_skip_trampoline_code is returning zero is that when trying to match the plt_call.shr2 stub in the executable, gdb matches ppc64_standard_linkage5 as it should, but then ppc64_standard_linkage3_targ= et calls get_frame_register_unsigned to retrieve r2 and it returns the value u= sed by the shared library, *not* the executable. So instead of reading the executable plt gdb reads some other random location that happens to be zero= in this case. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22226-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 06:13:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 22954 invoked by alias); 11 Dec 2017 06:13:29 -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 22927 invoked by uid 48); 11 Dec 2017 06:13:29 -0000 From: "amodra at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/22576] ppc64: gdbarch_skip_trampoline_code fails for relro Date: Mon, 11 Dec 2017 06:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: amodra at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: amodra at gmail dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_gcctarget 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: 2017-q4/txt/msg00270.txt.bz2 Content-length: 381 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22576 Alan Modra changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |powerpc64-linux --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22227-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 06:28:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 67059 invoked by alias); 11 Dec 2017 06:28:19 -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 67036 invoked by uid 48); 11 Dec 2017 06:28:19 -0000 From: "amodra at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/22576] ppc64: gdbarch_skip_trampoline_code uses wrong r2 Date: Mon, 11 Dec 2017 06:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: amodra at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: amodra at gmail dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc 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: 2017-q4/txt/msg00271.txt.bz2 Content-length: 762 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22576 Alan Modra changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|ppc64: |ppc64: |gdbarch_skip_trampoline_cod |gdbarch_skip_trampoline_cod |e fails for relro |e uses wrong r2 --- Comment #2 from Alan Modra --- I should add, a bogus r2 value is returned when using a -z norelro library = too, but the resulting wild read happens to hit a non-zero value. So this isn't anything specific to relro. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22228-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 06:49:20 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107335 invoked by alias); 11 Dec 2017 06:49:19 -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 107270 invoked by uid 48); 11 Dec 2017 06:49:09 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/22576] ppc64: gdbarch_skip_trampoline_code uses wrong r2 Date: Mon, 11 Dec 2017 06:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: amodra at gmail dot com 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: 2017-q4/txt/msg00272.txt.bz2 Content-length: 298 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22576 --- Comment #3 from Jan Kratochvil --- You are right I did not understand the ppc64 plt decoding, thanks for handl= ing that. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22229-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 11:09:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53540 invoked by alias); 11 Dec 2017 11:09:10 -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 53511 invoked by uid 48); 11 Dec 2017 11:09:08 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22583] New: gdb.base/breakpoint-in-ro-region.exp regressions on software single-step targets Date: Mon, 11 Dec 2017 11:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00273.txt.bz2 Content-length: 2605 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22583 Bug ID: 22583 Summary: gdb.base/breakpoint-in-ro-region.exp regressions on software single-step targets Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- At , Maciej writes: On 12/09/2017 01:16 AM, Maciej W. Rozycki wrote: > This change, i.e.: >=20 > commit d930703d68ae160ddfe8ebe5fdcf416fb6090e1e > Author: Pedro Alves > Date: Thu Nov 16 18:44:43 2017 +0000 >=20 > caused regressions to appear in remote `mips-mti-linux-gnu' target testin= g=20 > (`x86_64-linux-gnu' host), specifically: >=20 > FAIL: gdb.base/breakpoint-in-ro-region.exp: always-inserted off: auto-hw = off: single-step breakpoint is not left behind > FAIL: gdb.base/breakpoint-in-ro-region.exp: always-inserted off: auto-hw = on: single-step breakpoint is not left behind > FAIL: gdb.base/breakpoint-in-ro-region.exp: always-inserted on: auto-hw o= ff: step in ro region (cannot insert hw break) > FAIL: gdb.base/breakpoint-in-ro-region.exp: always-inserted on: auto-hw o= ff: single-step breakpoint is not left behind > FAIL: gdb.base/breakpoint-in-ro-region.exp: always-inserted on: auto-hw o= n: single-step breakpoint is not left behind >=20 > and indeed detailed logs indicate a breakpoint is left lingering, e.g.: >=20 > (gdb) PASS: gdb.base/breakpoint-in-ro-region.exp: always-inserted off: au= to-hw off: step in ro region (cannot insert sw break) > maint info breakpoints 0 > Num Type Disp Enb Address What > 0 sw single-step keep y 0x00400774 in main at [...]/gdb/testsuite= /gdb.base/breakpoint-in-ro-region.c:24 inf 1 thread 1 > stop only in thread 1 > (gdb) FAIL: gdb.base/breakpoint-in-ro-region.exp: always-inserted off: au= to-hw off: single-step breakpoint is not left behind >=20 > vs: >=20 > (gdb) PASS: gdb.base/breakpoint-in-ro-region.exp: always-inserted off: au= to-hw off: step in ro region (cannot insert sw break) > maint info breakpoints 0 > No breakpoint or watchpoint matching '0'. > (gdb) PASS: gdb.base/breakpoint-in-ro-region.exp: always-inserted off: au= to-hw off: single-step breakpoint is not left behind >=20 > as at commit d930703d68ae^. Filling so we don't forget before 8.1 is out. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22230-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 11:46:48 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 86011 invoked by alias); 11 Dec 2017 11:46:48 -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 85989 invoked by uid 48); 11 Dec 2017 11:46:48 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22584] New: Regression: expression completer and scope operator ("p std::[TAB]" => "p std::std::") Date: Mon, 11 Dec 2017 11:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00274.txt.bz2 Content-length: 1001 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22584 Bug ID: 22584 Summary: Regression: expression completer and scope operator ("p std::[TAB]" =3D> "p std::std::") Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- I noticed this regression in the expression completer: "(gdb) p std::[TAB]" =3D> "(gdb) p std::std::" obviously we should have not completed to "std::std::". Looks like I forgot to take into account the fact that with expressions, the completion word point is not always at the start of the symbol name (it is = with linespecs). I know how to fix it, just need to find time to get to it. Filing so we don't forget before 8.1 is out. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22231-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 11:46:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 87180 invoked by alias); 11 Dec 2017 11:46:54 -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 87158 invoked by uid 48); 11 Dec 2017 11:46:54 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22584] Regression: expression completer and scope operator ("p std::[TAB]" => "p std::std::") Date: Mon, 11 Dec 2017 11:46: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone 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: 2017-q4/txt/msg00275.txt.bz2 Content-length: 371 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22584 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22232-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 11:47:25 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 87607 invoked by alias); 11 Dec 2017 11:47:25 -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 87585 invoked by uid 48); 11 Dec 2017 11:47:25 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22583] gdb.base/breakpoint-in-ro-region.exp regressions on software single-step targets Date: Mon, 11 Dec 2017 11:47: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone 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: 2017-q4/txt/msg00276.txt.bz2 Content-length: 371 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22583 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22233-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 11:52:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 42782 invoked by alias); 11 Dec 2017 11:52:55 -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 42759 invoked by uid 48); 11 Dec 2017 11:52:54 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/22576] ppc64: gdbarch_skip_trampoline_code uses wrong r2 Date: Mon, 11 Dec 2017 11:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: amodra at gmail dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00277.txt.bz2 Content-length: 562 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22576 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #4 from Pedro Alves --- Guess users will see this as a regression? Should we try to fix this for (branching real soon) gdb 8.1 ? --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22234-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 12:21:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 16046 invoked by alias); 11 Dec 2017 12:21:19 -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 16024 invoked by uid 48); 11 Dec 2017 12:21:19 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22557] Regression: gdb.base/dtrace-probe.exp Date: Mon, 11 Dec 2017 12:21: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat 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: 8.1 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00278.txt.bz2 Content-length: 2158 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22557 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Pedro Alves --- (In reply to Sergio Durigan Junior from comment #3) > The test is failing for me even before the C++-ification patch, which > excludes the possibility of a regression introduced by the series. That's not a good assumption to make because it was failing for you for oth= er reasons. It was clearly passing for me, as shown in the log in the OP. I've now confirmed it: the test was passing at 935676c92feb5f35e4634ef58c20ffdfd0979b07^ (before "Convert generic probe interface to C++ (and perform some cleanups)"), and started failing at 9c23b42ffa67b866cd7562c1d8caed70db5d6840 ("Convert DTrace probe interface to C++ (and perform some cleanups)"). > Unfortunately I cannot test things with the regular dtrace program, becau= se > it is proprietary. So it may very well be a problem with pdtrace. TBC, I'm not using regular dtrace either. The difference is that I observed the regression on F23, and pdtrace only gets broken with binutils newer than F23's. If I test on F23 with current master binutils in the PATH, I also s= ee the undefined references to `main'. (In reply to cvs-commit@gcc.gnu.org from comment #4) > commit 92469284a650232768523564f2c715c4ebb57906 > Author: Sergio Durigan Junior > Date: Fri Dec 8 15:33:55 2017 -0500 >=20 > Fix thinko on dtrace-probe.c:dtrace_process_dof_probe >=20=20=20=20=20 ... > This commit fixes that. Unfortunately the script used to test DTrace > probes (gdb/testsuite/lib/pdtrace.in) is not very reliable so I cannot > say whether this commit fixes the PR mentioned above. Nonetheless, > it's an obvious fix and should go in. Yes, this fixed it for me. Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22235-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 20:35:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 126565 invoked by alias); 11 Dec 2017 20:35:35 -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 126534 invoked by uid 48); 11 Dec 2017 20:35:35 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22557] Regression: gdb.base/dtrace-probe.exp Date: Mon, 11 Dec 2017 20:35: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat 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: 8.1 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: 2017-q4/txt/msg00279.txt.bz2 Content-length: 2484 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22557 --- Comment #6 from Sergio Durigan Junior --- (In reply to Pedro Alves from comment #5) > (In reply to Sergio Durigan Junior from comment #3) > > The test is failing for me even before the C++-ification patch, which > > excludes the possibility of a regression introduced by the series. >=20 > That's not a good assumption to make because it was failing for you for > other reasons. It was clearly passing for me, as shown in the log in the= OP. > I've now confirmed it: the test was passing at > 935676c92feb5f35e4634ef58c20ffdfd0979b07^ (before "Convert generic probe > interface to C++ (and perform some cleanups)"), and started failing at > 9c23b42ffa67b866cd7562c1d8caed70db5d6840 ("Convert DTrace probe interface= to > C++ (and perform some cleanups)"). I did not see the log you mentioned. I agree that my conclusion was precipitated, but comment 1 says I suspect this is more fall out from the probe C++ification. (Just a gue= ss, I'm not really looking at it.) So it wasn't clear to me whether the test was passing before or not. Anyway, just explaining why I thought this regression had been introduced b= y an older commit. > > Unfortunately I cannot test things with the regular dtrace program, bec= ause > > it is proprietary. So it may very well be a problem with pdtrace. >=20 > TBC, I'm not using regular dtrace either. The difference is that I obser= ved > the regression on F23, and pdtrace only gets broken with binutils newer t= han > F23's. If I test on F23 with current master binutils in the PATH, I also > see the undefined references to `main'. Right, and putting "-R .eh_frame -K main" in the ${STRIP} line doesn't work. > (In reply to cvs-commit@gcc.gnu.org from comment #4) >=20 > > commit 92469284a650232768523564f2c715c4ebb57906 > > Author: Sergio Durigan Junior > > Date: Fri Dec 8 15:33:55 2017 -0500 > >=20 > > Fix thinko on dtrace-probe.c:dtrace_process_dof_probe > >=20=20=20=20=20 > ... > > This commit fixes that. Unfortunately the script used to test DTra= ce > > probes (gdb/testsuite/lib/pdtrace.in) is not very reliable so I can= not > > say whether this commit fixes the PR mentioned above. Nonetheless, > > it's an obvious fix and should go in. >=20 > Yes, this fixed it for me. Thanks. Thanks for testing it. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22236-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 21:00:00 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 71772 invoked by alias); 11 Dec 2017 21:00:00 -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 71721 invoked by uid 48); 11 Dec 2017 21:00:00 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug testsuite/22420] gdb.base/dtrace-probe.exp not working (as in "not able to run") Date: Mon, 11 Dec 2017 21:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com 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: 2017-q4/txt/msg00280.txt.bz2 Content-length: 895 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22420 --- Comment #2 from Sergio Durigan Junior --- (In reply to Sergio Durigan Junior from comment #1) > I have a patch for this. Well, it turns out the patch doesn't work... I was passing extra options to the 'strip' program in order to prevent the removal of 'main' and '.eh_frame' symbols. ${STRIP} -R .eh_frame -K main ... This "works" in the sense that the compilation succeeds, but there is clear= ly something else that needs to be done because I now see a regression that constantly happens: 133 print $_probe_arg0 134 $2 =3D 0x0 135 (gdb) FAIL: gdb.base/dtrace-probe.exp: print $_probe_arg0 for probe progress-counter As was discussed in PR 22557, this impacts the testing ability of the DTrace probe support on GDB. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22237-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 21:03:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 98922 invoked by alias); 11 Dec 2017 21:03:24 -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 98892 invoked by uid 48); 11 Dec 2017 21:03:23 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22557] Regression: gdb.base/dtrace-probe.exp Date: Mon, 11 Dec 2017 21:03: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat 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: 8.1 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: 2017-q4/txt/msg00281.txt.bz2 Content-length: 654 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22557 --- Comment #7 from Pedro Alves --- (In reply to Sergio Durigan Junior from comment #6) > I did not see the log you mentioned. (...) It's the "I'm seeing this regression" + the gdb.log snippet combined. > So it wasn't clear to me whether the test was passing before or not. OK, so sounds like some terminology mismatch then. A regression is somethi= ng that worked before and now fails. Some new test exposing preexisting probl= ems would be a "new failure" rather than a regression. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22238-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 23:00:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122474 invoked by alias); 11 Dec 2017 23:00:56 -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 122447 invoked by uid 48); 11 Dec 2017 23:00:55 -0000 From: "weimin.pan at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/8748] gdb Date: Mon, 11 Dec 2017 23:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: weimin.pan at oracle dot com X-Bugzilla-Status: SUSPENDED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jimb at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00282.txt.bz2 Content-length: 812 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8748 weimin.pan at oracle dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |weimin.pan at oracle dot c= om --- Comment #4 from weimin.pan at oracle dot com --- Problem is no longer reproducible with upstream gdb(on amd64/aarch6/sparc64= ):=20 % gdb a.out (gdb) b 23 Breakpoint 1 at 0x100800: file t.c, line 23. (gdb) r Starting program: /tmp/8748/t.x Breakpoint 1, norm_inf (A=3D0x3fffffff370, nf=3D4, nc=3D4) at t.c:23 23 return findmax(suma, nc); (gdb) p suma $1 =3D {16, 9, 5, 9} (gdb) whatis suma type =3D double [4] --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22239-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 11 23:43:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89242 invoked by alias); 11 Dec 2017 23:43:27 -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 89219 invoked by uid 48); 11 Dec 2017 23:43:27 -0000 From: "amodra at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/22576] ppc64: gdbarch_skip_trampoline_code uses wrong r2 Date: Mon, 11 Dec 2017 23:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: amodra at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: amodra at gmail dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_file_loc 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: 2017-q4/txt/msg00283.txt.bz2 Content-length: 525 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22576 Alan Modra changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://sourceware.org/ml/g | |db-patches/2017-12/msg00254 | |.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22240-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 12 00:07:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 72279 invoked by alias); 12 Dec 2017 00:07:40 -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 72246 invoked by uid 48); 12 Dec 2017 00:07:40 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/22576] ppc64: gdbarch_skip_trampoline_code uses wrong r2 Date: Tue, 12 Dec 2017 00:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: amodra at gmail dot com X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone 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: 2017-q4/txt/msg00284.txt.bz2 Content-length: 554 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22576 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.1 --- Comment #5 from Pedro Alves --- Wow thanks, that was fast! Setting the milestone, since there's a patch already. (I'll leave it to Ulrich to review.) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22241-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 12 02:06:57 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 51528 invoked by alias); 12 Dec 2017 02:06:57 -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 51467 invoked by uid 55); 12 Dec 2017 02:06:57 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22556] Regression: gdb.threads/names.exp with --target_board=native-gdbserver Date: Tue, 12 Dec 2017 02:06: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00285.txt.bz2 Content-length: 2007 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22556 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Simon Marchi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Da93340589416= 1c8b15f675c48d077b7f7d6aabf2 commit a933405894161c8b15f675c48d077b7f7d6aabf2 Author: Simon Marchi Date: Mon Dec 11 21:05:30 2017 -0500 remote: Return NULL extra_info/name if they are empty Commit remote: C++ify thread_item and threads_listing_context 21fe1c752e254167d953fa8c846280f63a3a5290 broke the test gdb.threads/names.exp. The problem is that since we now use an std::string to hold the extra_info, an empty string is returned by target_extra_thread_info to print_thread_info_1 when the remote stub didn't send any extra info, instead of NULL before. Because of that, print_thread_info_1 prints the extra info between parentheses, which results in some spurious empty parentheses. Expected: * 1 Thread 22752.22752 "main" all_threads_ready () at ... Actual : * 1 Thread 22752.22752 "main" () all_threads_ready () a = ... Since the bug was introduced by a behavior change in the remote target, I chose to fix it on the remote target side by making it return NULL when the extra string is empty. This will avoid possibly changing the behavior of the common code and affecting other targets. The name field has the same problem. If a remote stub returns no thread names, remote_thread_name will return an empty string instead of NULL, so print_thread_info_1 will show empty quotes ("") instead of nothing. gdb/ChangeLog: PR gdb/22556 * remote.c (remote_thread_name): Return NULL if name is empty. (remote_threads_extra_info): Return NULL if extra info is empty. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22242-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 12 12:55:54 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 116472 invoked by alias); 12 Dec 2017 12:55:54 -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 116447 invoked by uid 55); 12 Dec 2017 12:55:53 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tdep/22576] ppc64: gdbarch_skip_trampoline_code uses wrong r2 Date: Tue, 12 Dec 2017 12:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: amodra at gmail dot com X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00286.txt.bz2 Content-length: 2323 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22576 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Ddb9077b7275e= 86637218a7a7d165cb85a4de116f commit db9077b7275e86637218a7a7d165cb85a4de116f Author: Alan Modra Date: Mon Dec 11 17:31:11 2017 +1030 PR22576, ppc64_skip_trampoline_code uses wrong r2 for EXEC_REVERSE The TOC pointer register, r2, on powerpc64 is generally not mentioned in debug info. It is saved and restored by call linkage code, and set to the callee value either by call stub code (ELFv1) or in the callee global entry point code (ELFv2). A call stub uses the caller TOC pointer to access the PLT. So for gdb to read the correct PLT entry in order to determine the destination of the trampoline, gdb needs to know the caller r2. When skipping over trampolines in the normal forward direction, the caller r2 is simply the current value of r2 (at the start of the trampoline). However, when reversing over trampolines the current value of r2 is that for the callee. Using that value results in wild reads of memory rather than the correct PLT entry. This patch corrects the value of r2 by using the value saved on the stack for reverse execution. Note that in reverse execution mode it isn't really necessary for skip_trampoline_code to return the actual destination, so we're doing a little more work than needed here. Any non-zero return value would do (and it would be nicer if the interface was changed to return the start of the stub). PR tdep/22576 * ppc64-tdep.c (ppc64_plt_entry_point): Rewrite to take TOC-relative PLT offset, and retrieve r2 from stack when executing in reverse. (ppc64_standard_linkage1_target): Drop pc param. Calculate offset rather than PLT address. (ppc64_standard_linkage2_target): Likewise. (ppc64_standard_linkage3_target): Likewise. (ppc64_standard_linkage4_target): Likewise. (ppc64_skip_trampoline_code_1): Adjust to suit. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22243-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 12 13:01:45 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 762 invoked by alias); 12 Dec 2017 13:01:45 -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 735 invoked by uid 48); 12 Dec 2017 13:01:45 -0000 From: "amodra at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/22576] ppc64_skip_trampoline_code uses wrong r2 for EXEC_REVERSE Date: Tue, 12 Dec 2017 13:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: amodra at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: amodra at gmail dot com X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution short_desc 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: 2017-q4/txt/msg00287.txt.bz2 Content-length: 702 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22576 Alan Modra changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED Summary|ppc64: |ppc64_skip_trampoline_code |gdbarch_skip_trampoline_cod |uses wrong r2 for |e uses wrong r2 |EXEC_REVERSE --- Comment #7 from Alan Modra --- Fixed --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22244-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 12 14:41:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41417 invoked by alias); 12 Dec 2017 14:41:50 -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 41347 invoked by uid 48); 12 Dec 2017 14:41:50 -0000 From: "petrum at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22594] New: Possible access to unintended variable in "gdb/stabsread.c" line 1364 Date: Tue, 12 Dec 2017 14:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: petrum at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00288.txt.bz2 Content-length: 1410 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22594 Bug ID: 22594 Summary: Possible access to unintended variable in "gdb/stabsread.c" line 1364 Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: petrum at gmail dot com Target Milestone: --- While experimenting with a CodeSonar plugin we develop, we noticed a potential bug in file "gdb/stabsread.c" line 1364, function define_symbol=20 1359 *typedef_sym =3D *sym; 1360 SYMBOL_ACLASS_INDEX (typedef_sym) =3D LOC_TYPEDEF; 1361 SYMBOL_VALUE (typedef_sym) =3D valu; 1362 SYMBOL_DOMAIN (typedef_sym) =3D VAR_DOMAIN; 1363 if (TYPE_NAME (SYMBOL_TYPE (sym)) =3D=3D 0) 1364 TYPE_NAME (SYMBOL_TYPE (sym)) //HERE 1365 =3D obconcat (&objfile->objfile_obstack, 1366 SYMBOL_LINKAGE_NAME (sym), 1367 (char *) NULL); 1368 add_symbol_to_list (typedef_sym, &file_symbols); Shouldn't typedef_sym be used instead of sym (and maybe also in the previous line)? A similar issue might be in line 1320. Regards, Petru Florin Mihancea --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22245-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 12 14:42:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 43835 invoked by alias); 12 Dec 2017 14:42:11 -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 43791 invoked by uid 48); 12 Dec 2017 14:42:11 -0000 From: "petrum at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22594] Possible access to unintended variable in "gdb/stabsread.c" line 1364 Date: Tue, 12 Dec 2017 14:42: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: petrum at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00289.txt.bz2 Content-length: 400 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22594 Petru-Florin Mihancea changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |petrum at gmail dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22246-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 12 17:45:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 124330 invoked by alias); 12 Dec 2017 17:45:33 -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 124270 invoked by uid 48); 12 Dec 2017 17:45:31 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/8748] gdb Date: Tue, 12 Dec 2017 17:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: SUSPENDED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jimb at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00290.txt.bz2 Content-length: 507 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8748 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --- Comment #5 from Sergio Durigan Junior --- This can be closed, then. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22247-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 12 21:35:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 55078 invoked by alias); 12 Dec 2017 21:35: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 55058 invoked by uid 48); 12 Dec 2017 21:35:51 -0000 From: "macro@linux-mips.org" To: gdb-prs@sourceware.org Subject: [Bug remote/22597] New: Empty `qsThreadInfo' reply handling regression causing inability to execute Date: Tue, 12 Dec 2017 21:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: macro@linux-mips.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: 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: 2017-q4/txt/msg00291.txt.bz2 Content-length: 3752 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22597 Bug ID: 22597 Summary: Empty `qsThreadInfo' reply handling regression causing inability to execute Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: remote Assignee: unassigned at sourceware dot org Reporter: macro@linux-mips.org CC: palves at redhat dot com Target Milestone: 8.1 At , I wrote: On Tue, 12 Dec 2017, Maciej W. Rozycki wrote: > Another regression. This makes `mips-mti-linux-gnu' GDB stop working=20 > with older stubs. I have discovered it in an attempt to regression-test= =20 > said GDB with a remote n64 target and `x86_64-pc-linux-gnu' host, and an= =20 > outstanding change which affects non-XML stubs. Any attempt to continue= =20 > execution after the initial connection fails with: >=20 > [...] > Process .../gdb/testsuite/outputs/gdb.base/advance/advance created; pid = =3D 2670 > Listening on port 2346 > target remote [...]:2346 > Remote debugging using [...]:2346 > Reading symbols from .../lib64/ld.so.1...done. > [Switching to Thread
] > (gdb) continue > Cannot execute this command without a live selected thread. > (gdb)=20 >=20 > This is as from commit 5cd63fda035d. Up to 5cd63fda035d^ instead I get: >=20 > [...] > Process .../gdb/testsuite/outputs/gdb.base/advance/advance created; pid = =3D 30044 > Listening on port 2346 > target remote [...]:2346 > Remote debugging using [...]:2346 > Reading symbols from .../lib64/ld.so.1...done. > 0x000000fff79534f0 in __start () from .../lib64/ld.so.1 > (gdb) continue > Continuing. > warning: Could not load shared library symbols for linux-vdso.so.1. > Do you need "set solib-search-path" or "set sysroot"? >=20 > Breakpoint 1, main () at .../gdb/testsuite/gdb.base/advance.c:41 > 41 c =3D 5; > (gdb)=20 >=20 > At the protocol level the difference starts here (bad): >=20 > Sending packet: $qfThreadInfo#bb...Ack > Packet received: m1814 > Sending packet: $qsThreadInfo#c8...Ack > Packet received: l > [Switching to Thread
] > Sending packet: $qSymbol::#5b...Ack > Packet received: qSymbol:6e70746c5f76657273696f6e > Sending packet: $qSymbol::6e70746c5f76657273696f6e#4d...Ack > Packet received: OK > Sending packet: $Hg1814#7d...Ack > Packet received: OK > Sending packet: $Hg0#df...Ack > Packet received: E01 > (gdb) continue > Cannot execute this command without a live selected thread. > (gdb) >=20 > vs (good): >=20 > Sending packet: $qfThreadInfo#bb...Ack > Packet received: m154d > Sending packet: $qsThreadInfo#c8...Ack > Packet received: l > Sending packet: $mfff726c4f0,4#cb...Ack > Packet received: 03e0c825 > Sending packet: $mfff726c4ec,4#fd...Ack > Packet received: 00000000 > Sending packet: $mfff726c4f0,4#cb...Ack > Packet received: 03e0c825 > 0x000000fff726c4f0 in __start () from .../lib64/ld.so.1 > Sending packet: $qSymbol::#5b...Ack > Packet received: qSymbol:6e70746c5f76657273696f6e > Sending packet: $qSymbol::6e70746c5f76657273696f6e#4d...Ack > Packet received: OK > (gdb) continue > Continuing. > Sending packet: $mfff726c4f0,4#cb...Ack > Packet received: 03e0c825 > Sending packet: $Z0,120000d6c,4#36...Ack > Packet received: > Packet Z0 (software-breakpoint) is NOT supported > [...] >=20 > The version of `gdbserver' causing this regression is as at commit=20 > f8b73d13b7ca^, the last MIPS backend version with no XML support. It's=20 > likely that later versions hit this regression too, as the mode of failur= e=20 > is clearly not XML-related. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22248-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 12 21:36:14 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 62723 invoked by alias); 12 Dec 2017 21:36:14 -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 62494 invoked by uid 48); 12 Dec 2017 21:36:14 -0000 From: "macro@linux-mips.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22583] gdb.base/breakpoint-in-ro-region.exp regressions on software single-step targets Date: Tue, 12 Dec 2017 21:36: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: macro@linux-mips.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00292.txt.bz2 Content-length: 390 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22583 Maciej W. Rozycki changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |macro@linux-mips.org --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22249-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 13 14:24:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 116440 invoked by alias); 13 Dec 2017 14:24:34 -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 116380 invoked by uid 48); 13 Dec 2017 14:24:32 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22584] Regression: expression completer and scope operator ("p std::[TAB]" => "p std::std::") Date: Wed, 13 Dec 2017 14:24: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to 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: 2017-q4/txt/msg00293.txt.bz2 Content-length: 602 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22584 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at sourceware dot org |palves at redhat do= t com --- Comment #1 from Pedro Alves --- Fix posted here: https://sourceware.org/ml/gdb-patches/2017-12/msg00301.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22250-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 13 15:40:30 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 59556 invoked by alias); 13 Dec 2017 15:40:30 -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 59529 invoked by uid 48); 13 Dec 2017 15:40:29 -0000 From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21356] value.c:828: internal-error: int value_contents_bits_eq(const value*, int, const value*, int, int): Assertion `offset1 + length <= TYPE_LENGTH (val1->enclosing_type) * TARGET_CHAR_BIT' failed Date: Wed, 13 Dec 2017 15:40: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.12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed 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: 2017-q4/txt/msg00294.txt.bz2 Content-length: 968 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21356 Jan Kratochvil changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-12-13 CC| |jan.kratochvil at redhat d= ot com Assignee|unassigned at sourceware dot org |keiths at redhat do= t com Ever confirmed|0 |1 --- Comment #2 from Jan Kratochvil --- From: Keith Seitz [PATCH] Compute proper length for dynamic types of TYPE_CODE_TYPEDEF https://sourceware.org/ml/gdb-patches/2017-06/msg00679.html Message-Id: <1498265971-27536-1-git-send-email-keiths@redhat.com> --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22251-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 13 16:41:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 93926 invoked by alias); 13 Dec 2017 16:41:27 -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 92542 invoked by uid 55); 13 Dec 2017 16:41:27 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22584] Regression: expression completer and scope operator ("p std::[TAB]" => "p std::std::") Date: Wed, 13 Dec 2017 16:41: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00295.txt.bz2 Content-length: 2604 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22584 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Da22ecf70263e= ff75ca2c5878fe7e8d0311d6737f commit a22ecf70263eff75ca2c5878fe7e8d0311d6737f Author: Pedro Alves Date: Wed Dec 13 16:38:50 2017 +0000 Fix regression: expression completer and scope operator (PR gdb/22584) I noticed this regression in the expression completer: "(gdb) p std::[TAB]" =3D> "(gdb) p std::std::" obviously we should have not completed to "std::std::". The problem is that in the earlier big completer rework, I missed taking into account the fact that with expressions, the completion word point is not always at the start of the symbol name (it is with linespecs). The fix is to run the common prefix / LCD string (what readline uses to expand the input line) through make_completion_match_str too. New testcase included, exercising both TAB completion and the complete command. gdb/ChangeLog: 2017-12-13 Pedro Alves * completer.c (completion_tracker::maybe_add_completion): New 'text' and 'word' parameters. Use make_completion_match_str. (completion_tracker::add_completion): New 'text' and 'word' parameters. Pass down. (completion_tracker::recompute_lowest_common_denominator): Change parameter type to gdb::unique_xmalloc_ptr rval ref. Adjust. * completer.h (completion_tracker::add_completion): New 'text' and 'word' parameters. (completion_tracker::recompute_lowest_common_denominator): Change parameter type to gdb::unique_xmalloc_ptr rval ref. (completion_tracker::recompute_lowest_common_denominator): Change parameter type to gdb::unique_xmalloc_ptr rval ref. * symtab.c (completion_list_add_name): Pass down 'text' and 'word' as well. gdb/testsuite/ChangeLog: 2017-12-13 Pedro Alves * gdb.cp/cpcompletion.exp: Load completion-support.exp. ("expression with namespace"): New set of tests. * gdb.cp/pr9594.cc (Test_NS::foo, Test_NS::bar) (Nested::Test_NS::qux): New. * lib/completion-support.exp (test_gdb_complete_cmd_multiple): Add defaults to 'start_quote_char' and 'end_quote_char' parameters. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22252-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 13 16:42:28 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 67450 invoked by alias); 13 Dec 2017 16:42:28 -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 67111 invoked by uid 48); 13 Dec 2017 16:42:27 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22584] Regression: expression completer and scope operator ("p std::[TAB]" => "p std::std::") Date: Wed, 13 Dec 2017 16:42: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: palves at redhat dot com X-Bugzilla-Target-Milestone: 8.1 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00296.txt.bz2 Content-length: 502 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22584 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Pedro Alves --- Fixed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22253-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 13 19:46:32 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 24768 invoked by alias); 13 Dec 2017 19:46:31 -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 24743 invoked by uid 48); 13 Dec 2017 19:46:31 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22583] gdb.base/breakpoint-in-ro-region.exp regressions on software single-step targets Date: Wed, 13 Dec 2017 19:46: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00297.txt.bz2 Content-length: 401 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22583 --- Comment #1 from Pedro Alves --- I've managed to rebase my old "software single-step on x86-64" branch on current master: https://github.com/palves/gdb/commits/palves/x86_software_single_step and I can reproduce this locally now. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22254-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 13 21:05:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 122484 invoked by alias); 13 Dec 2017 21:05:55 -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 122462 invoked by uid 48); 13 Dec 2017 21:05:55 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22600] New: GDB doesn't handle bitfield offsets on big-endian architectures Date: Wed, 13 Dec 2017 21:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00298.txt.bz2 Content-length: 1584 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22600 Bug ID: 22600 Summary: GDB doesn't handle bitfield offsets on big-endian architectures Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: sergiodj at redhat dot com Target Milestone: --- This bug was discovered while doing the "ptype /o" work, because it uses the same algorithm for calculating offsets on bitfields. The code in question = can be found at value.c:value_primitive_field. It seems like the algorithm for calculating bitfield offsets is not working correctly on BE machines. This is not only for "ptype /o", but also for regular print commands. For example, consider this test: struct tyu { int a1 : 1; int a2 : 3; int a3 : 23; char a4 : 2; int64_t a5; int a6 : 5; int64_t a7 : 3; }; int main (int argc, char *argv[]) { struct tyu e; e.a1 =3D e.a2 =3D e.a3 =3D e.a4 =3D e.a6 =3D e.a7 =3D -1; return 0; } After stopping GDB at the "return 0;" line, here's what we see when we print "e" on x86_64: (gdb) p e $1 =3D {a1 =3D -1, a2 =3D -1, a3 =3D -1, a4 =3D -1 '\377', a5 =3D 1407374= 88344880, a6 =3D -1, a7 =3D -1} While on PPC64BE: (gdb) p e $1 =3D {a1 =3D -1, a2 =3D 3, a3 =3D 3, a4 =3D 3 '\003', a5 =3D 7036753615= 3528, a6 =3D -1, a7 =3D -1} --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22255-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 13 21:17:41 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 49985 invoked by alias); 13 Dec 2017 21:17:41 -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 49956 invoked by uid 48); 13 Dec 2017 21:17:41 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22600] GDB doesn't handle bitfield offsets on big-endian architectures Date: Wed, 13 Dec 2017 21:17: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com 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: 2017-q4/txt/msg00299.txt.bz2 Content-length: 365 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22600 --- Comment #1 from Sergio Durigan Junior --- To be clear: the problem here is that all of the bitfields must be -1. "e.= a5" contains a strange value, but that is because it was never initialized. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22256-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 13 21:24:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 65836 invoked by alias); 13 Dec 2017 21:24:28 -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 65806 invoked by uid 48); 13 Dec 2017 21:24:28 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22600] GDB doesn't handle bitfield offsets on big-endian architectures Date: Wed, 13 Dec 2017 21:24: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com 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: 2017-q4/txt/msg00300.txt.bz2 Content-length: 456 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22600 --- Comment #2 from Sergio Durigan Junior --- New examples, with a5 initialized to 0: x86_64: $1 =3D {a1 =3D -1, a2 =3D -1, a3 =3D -1, a4 =3D -1 '\377', a5 =3D 0, a6 =3D= -1, a7 =3D -1} PPC64BE: $1 =3D {a1 =3D -1, a2 =3D 3, a3 =3D 3, a4 =3D 3 '\003', a5 =3D 0, a6 =3D -1= , a7 =3D -1} --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22257-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 13 21:36:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 72672 invoked by alias); 13 Dec 2017 21:36:22 -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 72650 invoked by uid 48); 13 Dec 2017 21:36:22 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22600] GDB doesn't handle bitfield offsets on big-endian architectures Date: Wed, 13 Dec 2017 21:36: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00301.txt.bz2 Content-length: 768 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22600 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Sergio Durigan Junior --- There were problems with the testcase. See: https://sourceware.org/ml/gdb-patches/2017-12/msg00322.html https://sourceware.org/ml/gdb-patches/2017-12/msg00323.html https://sourceware.org/ml/gdb-patches/2017-12/msg00324.html Closing as INVALID. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22258-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 14 00:57:11 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 45801 invoked by alias); 14 Dec 2017 00:57:11 -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 44358 invoked by uid 48); 14 Dec 2017 00:57:10 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/19681] Attempting to set a breakpoint at a label in a C++ constructor causes internal-error: decode_line_full Date: Thu, 14 Dec 2017 00:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: keiths at redhat dot com 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00302.txt.bz2 Content-length: 825 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19681 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Keith Seitz --- Looks like this has been long been fixed. I checked back to Jul 2016, and i= t's been working since at least then: (gdb) b A::A(int):labeldude Breakpoint 1 at 0x4004d9: file 19681.cc, line 5. (gdb) i b Num Type Disp Enb Address What 1 breakpoint keep y 0x00000000004004d9 A::A(int):labeldude --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22259-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 14 11:11:37 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 45095 invoked by alias); 14 Dec 2017 11:11:36 -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 45030 invoked by uid 48); 14 Dec 2017 11:11:36 -0000 From: "jonah at kichwacoders dot com" To: gdb-prs@sourceware.org Subject: [Bug exp/22487] `51-var-list-children var3` is not returning within 10 seconds Date: Thu, 14 Dec 2017 11:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: exp X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jonah at kichwacoders dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00303.txt.bz2 Content-length: 350 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22487 --- Comment #3 from Jonah Graham --- I am wondering if this happens due to some Python pretty-printers getting themselves in an infinite loop? Can you test with no pretty printers. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22260-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 14 12:01:34 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 101638 invoked by alias); 14 Dec 2017 12:01:33 -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 101571 invoked by uid 48); 14 Dec 2017 12:01:33 -0000 From: "klausman-glibc at schwarzvogel dot de" To: gdb-prs@sourceware.org Subject: [Bug gdb/19061] gdb-7.10 hangs/spins-on-cpu when debugging any program on Alpha Date: Thu, 14 Dec 2017 12:01: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.10 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: klausman-glibc at schwarzvogel dot de 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: 2017-q4/txt/msg00304.txt.bz2 Content-length: 652 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19061 --- Comment #8 from Tobias Klausmann --- (In reply to Tobias Klausmann from comment #7) > I *think* this may be fixed in gdb-8. I just checked out gdb-8.0.1-release > from git and I have been unable to reproduce the hang. I will keep using = it > for everyday stuff and report back if anything breaks. I spoke too soon: I can now reliably make it hang on commit gdb-8.0.1-relea= se aka 2dcf9205c32aa69c102640962ff03746d04c02cc using ls or a trivial hello wo= rld program. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22261-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 14 17:44:36 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 107593 invoked by alias); 14 Dec 2017 17:44:36 -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 107568 invoked by uid 48); 14 Dec 2017 17:44:36 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22608] New: operator<< completion clips to operator< Date: Thu, 14 Dec 2017 17:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00305.txt.bz2 Content-length: 1425 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22608 Bug ID: 22608 Summary: operator<< completion clips to operator< Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: keiths at redhat dot com Target Milestone: --- Source: $ cat >oplt.cc << EOF template class Empty { }; template bool operator< (T &lhs, T &rhs) { return false; } template int operator<< (T &obj, T &val) { return 0; } int main () { Empty ei; bool b =3D ei < ei; int i =3D ei << ei; return 0; } EOF $ g++ -g oplt.cc -o oplt $ gdb -q oplt Reading symbols from /home/keiths/tmp/oplt...done. (gdb) complete break operator< break operator< >(Empty&, Empty&) break operator<< >(Empty&, Empty&) /* correct */ (gdb) complete break operator<< break operator< >(Empty&, Empty&) break operator<< >(Empty&, Empty&) /* /not/ correct */ (gdb) break operator<<[TAB] break operator< >(Empty&, Empty&) break operator<< >(Empty&, Empty&) (gdb) break operator< /* notice the output clipped the last `<' */ --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22262-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 14 20:00:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 54850 invoked by alias); 14 Dec 2017 20:00:40 -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 53798 invoked by uid 48); 14 Dec 2017 20:00:39 -0000 From: "pinskia at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/18653] spawn changes SIGPIPE SIG_DFL to SIG_IGN Date: Thu, 14 Dec 2017 20:00: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.12 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00306.txt.bz2 Content-length: 775 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18653 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pinskia at gcc dot gnu.org --- Comment #7 from Andrew Pinski --- Also this causes gdb to be useless if you LD_PRELOAD of libSegFault.so. You get an internal error right at the beginning of running gdb. Is this by de= sign and maybe the internal error should be changed to be sorry if the address of the function is not located in gdb itself or rather in a shared library. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22263-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 14 23:56:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 55303 invoked by alias); 14 Dec 2017 23:56:27 -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 55273 invoked by uid 48); 14 Dec 2017 23:56:26 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18653] spawn changes SIGPIPE SIG_DFL to SIG_IGN Date: Thu, 14 Dec 2017 23:56: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.12 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: 2017-q4/txt/msg00307.txt.bz2 Content-length: 2195 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18653 --- Comment #8 from Pedro Alves --- Indeed, we get: (top-gdb) bt #0 0x000000000056b001 in internal_error(char const*, int, char const*, ...) (file=3D0xaf5f38 "src/gdb/common/signals-state-save-restore.c", line=3D64, fmt=3D0xaf5f18 "unexpected signal handler") at src/gdb/common/errors.c:54 #1 0x00000000005752c9 in save_original_signals_state() () at src/gdb/common/signals-state-save-restore.c:64 #2 0x00000000007425de in captured_main_1(captured_main_args*) (context=3D0x7fffffffd860) at src/gdb/main.c:509 #3 0x0000000000743622 in captured_main(void*) (data=3D0x7fffffffd860) at src/gdb/main.c:1145 During symbol reading, cannot get low and high bounds for subprogram DIE at 24065. #4 0x00000000007436f9 in gdb_main(captured_main_args*) (args=3D0x7fffffffd= 860) at src/gdb/main.c:1171 #5 0x0000000000413acd in main(int, char**) (argc=3D1, argv=3D0x7fffffffd96= 8) at src/gdb/gdb.c:32 How about this? Too noisy? ~~~~~~~~~~~~~~~~~~~~~ $ LD_PRELOAD=3D/usr/lib64/libSegFault.so ./gdb ~/gdb/tests/threads warning: Found custom handler for signal 11 (Segmentation fault) preinstall= ed. Some signal dispositions inherited from the environment (SIG_DFL/SIG_IGN) won't be propagated to spawned programs. GNU gdb (GDB) 8.0.50.20171213-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /home/pedro/gdb/tests/threads...done. (gdb) ~~~~~~~~~~~~~~~~~~~~~ --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22264-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 14 23:58:33 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 56451 invoked by alias); 14 Dec 2017 23:58:33 -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 56422 invoked by uid 48); 14 Dec 2017 23:58:33 -0000 From: "pinskia at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/18653] spawn changes SIGPIPE SIG_DFL to SIG_IGN Date: Thu, 14 Dec 2017 23:58: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.12 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: 2017-q4/txt/msg00308.txt.bz2 Content-length: 330 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18653 --- Comment #9 from Andrew Pinski --- (In reply to Pedro Alves from comment #8) > How about this? Too noisy? As long as -q disables the message this is ok to me. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22265-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 15 09:36:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 35011 invoked by alias); 15 Dec 2017 09:36: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 34725 invoked by uid 48); 15 Dec 2017 09:36:51 -0000 From: "kryukov at frtk dot ru" To: gdb-prs@sourceware.org Subject: [Bug build/22495] remote-sim.c should be built with -Wno-format-nonliteral Date: Fri, 15 Dec 2017 09:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kryukov at frtk dot ru X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00309.txt.bz2 Content-length: 401 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22495 Pavel I. Kryukov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at sourceware dot o= rg --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22266-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 15 10:00:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 30444 invoked by alias); 15 Dec 2017 10:00:40 -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 30412 invoked by uid 48); 15 Dec 2017 10:00:39 -0000 From: "kryukov at frtk dot ru" To: gdb-prs@sourceware.org Subject: [Bug build/22612] New: check_dwarf64_offsets () always returns false Date: Fri, 15 Dec 2017 10:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kryukov at frtk dot ru X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00310.txt.bz2 Content-length: 1370 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22612 Bug ID: 22612 Summary: check_dwarf64_offsets () always returns false Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: kryukov at frtk dot ru Target Milestone: --- Clang warns that 'true' is returned from check_dwarf64_offsets () only if 'unsigned int' is greater than (1 << 32) which is not possible if sizeof(unsigned int) =3D=3D 4: > dwarf2read.c:26610:43: error: comparison of constant 4294967296 with expr= ession > of type 'typename std::underlying_type::type' > (aka 'unsigned int') is always false > [-Werror,-Wtautological-constant-out-of-range-compare] > if (to_underlying (per_cu.sect_off) >=3D (static_cast (1)= << 32)) > dwarf2read.c:26618:43: error: comparison of constant 4294967296 with expr= ession > of type 'typename std::underlying_type::type' > (aka 'unsigned int') is always false > [-Werror,-Wtautological-constant-out-of-range-compare] > if (to_underlying (per_cu.sect_off) >=3D (static_cast (1)= << 32)) --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22267-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 15 10:01:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 32594 invoked by alias); 15 Dec 2017 10:01:24 -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 32563 invoked by uid 48); 15 Dec 2017 10:01:23 -0000 From: "kryukov at frtk dot ru" To: gdb-prs@sourceware.org Subject: [Bug build/22612] check_dwarf64_offsets () always returns false Date: Fri, 15 Dec 2017 10:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kryukov at frtk dot ru X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00311.txt.bz2 Content-length: 401 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22612 Pavel I. Kryukov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at sourceware dot o= rg --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22268-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 15 10:23:40 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 23623 invoked by alias); 15 Dec 2017 10:23:40 -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 23595 invoked by uid 48); 15 Dec 2017 10:23:39 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug build/22612] check_dwarf64_offsets () always returns false Date: Fri, 15 Dec 2017 10:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2017-q4/txt/msg00312.txt.bz2 Content-length: 526 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22612 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- Context: https://sourceware.org/ml/gdb-patches/2017-12/msg00276.html --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22269-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 15 13:30:56 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 64391 invoked by alias); 15 Dec 2017 13:30:56 -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 64366 invoked by uid 48); 15 Dec 2017 13:30:55 -0000 From: "matz at suse dot de" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/22613] New: assert in inferior_thread from tui_on_normal_stop Date: Fri, 15 Dec 2017 13:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: matz at suse dot de 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q4/txt/msg00313.txt.bz2 Content-length: 4685 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22613 Bug ID: 22613 Summary: assert in inferior_thread from tui_on_normal_stop Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: matz at suse dot de Target Milestone: --- Created attachment 10690 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10690&action=3Ded= it script showing problem Place script in gdb build directory, then: % ./gdb-crash.sh 50 This is a bug, please report it. For instructions, see: . ./gdb-crash.sh: line 50: 4560 Aborted (core dumped) ../gdb= /gdb --data-directory ../gdb/data-directory -nx --batch-silent -return-child-res= ult --eval-command=3D"break '$break_line'" --eval-command=3D'source bp.py' --eval-command=3D"run a b c" --eval-command=3D'quit' ./prog (core file is strange, so use gdb directly, then from the tmp dir created by script:) % gdb --args ../gdb/gdb --data-directory ../gdb/data-directory -nx --batch-silent -return-child-result --eval-command=3D"break '$break_line'" --eval-command=3D'source bp.py' --eval-command=3D"run a b c" --eval-command= =3D'quit' ./prog (gdb) r ... (gdb) bt #0 0x00007ffff64bc3d5 in __GI_raise (sig=3Dsig@entry=3D6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007ffff64bd858 in __GI_abort () at abort.c:90 #2 0x000000000083b056 in dump_core () at ../../gdb/utils.c:284 #3 0x000000000083b526 in internal_vproblem(internal_problem *, const char = *, int, const char *, typedef __va_list_tag __va_list_tag *) ( problem=3D0x10281a0 ,=20 file=3D0xb42136 "../../gdb/thread.c", line=3D93,=20 fmt=3D0xb420cb "%s: Assertion `%s' failed.", ap=3D0x7fffffffcf58) at ../../gdb/utils.c:493 #4 0x000000000083b5f9 in internal_verror (file=3D0xb42136 "../../gdb/threa= d.c",=20 line=3D93, fmt=3D0xb420cb "%s: Assertion `%s' failed.", ap=3D0x7fffffff= cf58) at ../../gdb/utils.c:518 #5 0x0000000000543c71 in internal_error (file=3D0xb42136 "../../gdb/thread= .c",=20 line=3D93, fmt=3D0xb420cb "%s: Assertion `%s' failed.") at ../../gdb/common/errors.c:55 #6 0x000000000080ddc3 in inferior_thread () at ../../gdb/thread.c:93 #7 0x00000000004a4ebf in tui_on_normal_stop (bs=3D0x1344f50, print_frame= =3D1) at ../../gdb/tui/tui-interp.c:97 #8 0x000000000073ae51 in observer_normal_stop_notification_stub ( data=3D0x4a4e61 ,=20 args_data=3D0x7fffffffd120) at ./observer.inc:36 #9 0x000000000073ad56 in generic_observer_notify (subject=3D0x1215780,=20 args=3D0x7fffffffd120) at ../../gdb/observer.c:167 #10 0x000000000073aeef in observer_notify_normal_stop (bs=3D0x1344f50,=20 print_frame=3D1) at ./observer.inc:61 #11 0x00000000006f12b9 in normal_stop () at ../../gdb/infrun.c:8309 #12 0x00000000006e8a28 in fetch_inferior_event (client_data=3D0x0) at ../../gdb/infrun.c:3942 #13 0x00000000006d7112 in inferior_event_handler (event_type=3DINF_REG_EVEN= T,=20 client_data=3D0x0) at ../../gdb/inf-loop.c:43 #14 0x000000000045d9a3 in handle_target_event (error=3D0, client_data=3D0x0) at ../../gdb/linux-nat.c:4521 #15 0x0000000000695165 in handle_file_event (file_ptr=3D0x1330500, ready_ma= sk=3D1) at ../../gdb/event-loop.c:733 #16 0x0000000000695708 in gdb_wait_for_event (block=3D0) at ../../gdb/event-loop.c:859 #17 0x0000000000694588 in gdb_do_one_event () at ../../gdb/event-loop.c:322 #18 0x0000000000816899 in wait_sync_command_done () at ../../gdb/top.c:503 #19 0x0000000000816911 in maybe_wait_sync_command_done (was_sync=3D0) at ../../gdb/top.c:520 #20 0x0000000000816ce5 in execute_command (p=3D0x7fffffffdfbb "c", from_tty= =3D0) at ../../gdb/top.c:632 #21 0x0000000000714416 in catch_command_errors ( command=3D0x81692a ,=20 arg=3D0x7fffffffdfb3 "run a b c", from_tty=3D0) at ../../gdb/main.c:378 #22 0x0000000000715596 in captured_main_1 (context=3D0x7fffffffd8e0) at ../../gdb/main.c:1124 #23 0x00000000007156ab in captured_main (data=3D0x7fffffffd8e0) at ../../gdb/main.c:1145 #24 0x0000000000715782 in gdb_main (args=3D0x7fffffffd8e0) at ../../gdb/main.c:1171 #25 0x000000000041120d in main (argc=3D10, argv=3D0x7fffffffd9e8) at ../../gdb/gdb.c:32 So it doesn't find the thread to continue when called from inside the breakpoint handler. Whatever should happen here, gdb shouldn't crash. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22270-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 15 16:59:04 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 30071 invoked by alias); 15 Dec 2017 16:59:04 -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 30044 invoked by uid 48); 15 Dec 2017 16:59:04 -0000 From: "vladilen.kozin at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/11403] Failed to set controlling terminal Date: Fri, 15 Dec 2017 16:59: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.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vladilen.kozin at gmail dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2017-q4/txt/msg00314.txt.bz2 Content-length: 1013 https://sourceware.org/bugzilla/show_bug.cgi?id=3D11403 Vlad changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vladilen.kozin at gmail do= t com --- Comment #4 from Vlad --- Looks like the same issue plagues GDB 7.11.1. Reported on emacs mailing list https://lists.gnu.org/archive/html/help-gnu-emacs/2017-12/msg00114.html sin= ce I thought the issue might be with Tramp. This was reported for older Linux box with GDB 7.7, but I later reproduced on Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-104-generic x86_64) and GDB 7.11.1 When debugging on local machine this is usually benign, but it does appear = to break attempt to debug with I/O when debugging remotely say over TRAMP. See= the mailing list post above for details. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22271-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 15 18:21:55 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 19246 invoked by alias); 15 Dec 2017 18:21:55 -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 19223 invoked by uid 55); 15 Dec 2017 18:21:55 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/19061] gdb-7.10 hangs/spins-on-cpu when debugging any program on Alpha Date: Fri, 15 Dec 2017 18:21: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.10 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: 2017-q4/txt/msg00315.txt.bz2 Content-length: 1468 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19061 --- Comment #9 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Pedro Alves : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D68f81d60196e= b201b209873cf53258f13b0046b9 commit 68f81d60196eb201b209873cf53258f13b0046b9 Author: Richard Henderson Date: Fri Dec 15 18:19:42 2017 +0000 Fix PR19061, gdb hangs/spins-on-cpu when debugging any program on Alpha This fixes PR19061, where gdb hangs/spins-on-cpu when debugging any program on Alpha. (This patch is Uros' forward port of the patch from comment #5 of the PR [1].) Patch was tested on alphaev68-linux-gnu, also tested with gcc's testsuite, where it fixed all hangs in guality.exp and simulate-thread.exp testcases. [1] https://sourceware.org/bugzilla/show_bug.cgi?id=3D19061#c5 gdb/ChangeLog: 2017-12-15 Richard Henderson Uros Bizjak PR gdb/19061 * alpha-tdep.c (alpha_software_single_step): Call alpha_deal_with_atomic_sequence here. (set_gdbarch_software_single_step): Set to alpha_software_single_step. * nat/linux-ptrace.h [__alpha__]: Define GDB_ARCH_IS_TRAP_BRKPT and GDB_ARCH_IS_TRAP_HWBKPT. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22272-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 15 20:10:24 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 22618 invoked by alias); 15 Dec 2017 20:10:24 -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 22593 invoked by uid 55); 15 Dec 2017 20:10:24 -0000 From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug cli/16224] add "pahole" functionality to ptype Date: Fri, 15 Dec 2017 20:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: 8.1 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: 2017-q4/txt/msg00316.txt.bz2 Content-length: 5089 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16224 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Sergio Durigan Junior : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D7c1618381fda= a0697a211721ac31844f884797ac commit 7c1618381fdaa0697a211721ac31844f884797ac Author: Sergio Durigan Junior Date: Mon Nov 20 16:34:59 2017 -0500 Implement pahole-like 'ptype /o' option This commit implements the pahole-like '/o' option for 'ptype', which prints the offsets and sizes of struct fields, reporting whenever there is a hole found. The output is heavily based on pahole(1), with a few modifications here and there to adjust it to our reality. Here's an example: /* offset | size */ type =3D struct wer : public tuv { public: /* 32 | 24 */ struct tyu { /* 32:31 | 4 */ int a1 : 1; /* 32:28 | 4 */ int a2 : 3; /* 32: 5 | 4 */ int a3 : 23; /* 35: 3 | 1 */ char a4 : 2; /* XXX 3-bit hole */ /* XXX 4-byte hole */ /* 40 | 8 */ int64_t a5; /* 48:27 | 4 */ int a6 : 5; /* 48:56 | 8 */ int64_t a7 : 3; /* total size (bytes): 24 */ } a1; /* total size (bytes): 56 */ } A big part of this patch handles the formatting logic of 'ptype', which is a bit messy. The code to handle bitfield offsets, however, took some time to craft. My thanks to Pedro Alves for figuring things out and pointing me to the right direction, as well as coming up with a way to inspect the layout of structs with bitfields (see testcase for comments). After many discussions both on IRC and at the mailing list, I tried to implement printing vtables and inherited classes. Unfortunately the code grew too complex and there were still a few corner cases failing so I had to drop the attempt. This should be implemented in a future patch. This patch is the start of a long-term work I'll do to flush the local patches we carry for Fedora GDB. In this specific case, I'm aiming at upstreaming the feature implemented by the 'pahole.py' script that is shipped with Fedora GDB: =20=20=20=20=20 This has been regression-tested on the BuildBot. There's a new testcase for it, along with an update to the documentation. I also thought it was worth mentioning this feature in the NEWS file. gdb/ChangeLog: 2017-12-15 Sergio Durigan Junior Pedro Alves PR cli/16224 * NEWS (Changes since GDB 8.0): Mention new '/o' flag. * c-typeprint.c (OFFSET_SPC_LEN): New define. (c_type_print_varspec_prefix): New argument 'struct print_offset_data *'. (c_type_print_base_1): New function and prototype. (c_print_type_1): New function, with code from 'c_print_type'. (c_print_type): Use 'c_print_type_1'. (c_type_print_varspec_prefix): New argument 'struct print_offset_data *'. Use it. Call 'c_type_print_base_1' instead of 'c_print_type_base'. (print_spaces_filtered_with_print_options): New function. (output_access_specifier): Take new argument FLAGS. Modify function to call 'print_spaces_filtered_with_print_options'. (c_print_type_vtable_offset_marker): New function. (c_print_type_union_field_offset): New function. (c_print_type_struct_field_offset): New function. (c_print_type_no_offsets): New function. (c_type_print_base_struct_union): New argument 'struct print_offset_data *'. Print offsets and sizes for struct/union/class fields. * typeprint.c (const struct type_print_options type_print_raw_options): Initialize 'print_offsets'. (static struct type_print_options default_ptype_flags): Likewise. (struct print_offset_data print_offset_default_data): New variable. (whatis_exp): Handle '/o' option. (_initialize_typeprint): Add '/o' flag to ptype's help. * typeprint.h (struct print_offset_data): New struct. (struct type_print_options) : New field. gdb/testsuite/ChangeLog: 2017-12-15 Sergio Durigan Junior PR cli/16224 * gdb.base/ptype-offsets.cc: New file. * gdb.base/ptype-offsets.exp: New file. gdb/doc/ChangeLog: 2017-12-15 Sergio Durigan Junior PR cli/16224 * gdb.texinfo (ptype): Add documentation for new flag '/o'. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22274-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 15 20:12:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 26285 invoked by alias); 15 Dec 2017 20:12:17 -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 26165 invoked by uid 48); 15 Dec 2017 20:12:16 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/22574] support ptype/o in rust Date: Fri, 15 Dec 2017 20:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: dep_changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com 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: bug_status resolution 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: 2017-q4/txt/msg00318.txt.bz2 Content-length: 547 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22574 Bug 22574 depends on bug 16224, which changed state. Bug 16224 Summary: add "pahole" functionality to ptype https://sourceware.org/bugzilla/show_bug.cgi?id=3D16224 What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22273-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 15 20:12:16 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 26126 invoked by alias); 15 Dec 2017 20:12:16 -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 26101 invoked by uid 48); 15 Dec 2017 20:12:16 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/16224] add "pahole" functionality to ptype Date: Fri, 15 Dec 2017 20:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: sergiodj at redhat dot com X-Bugzilla-Target-Milestone: 8.1 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00317.txt.bz2 Content-length: 545 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16224 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Sergio Durigan Junior --- Patches have been pushed. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22275-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Dec 16 16:53:50 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 41981 invoked by alias); 16 Dec 2017 16:53:50 -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 41956 invoked by uid 48); 16 Dec 2017 16:53:49 -0000 From: "jreiser at BitWagon dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22616] New: gdb will not set program counter $pc to mmap()ed region Date: Sat, 16 Dec 2017 16:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jreiser at BitWagon dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00319.txt.bz2 Content-length: 2672 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22616 Bug ID: 22616 Summary: gdb will not set program counter $pc to mmap()ed region Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jreiser at BitWagon dot com Target Milestone: --- gdb won't set the program counter $pc to point to an mmap()ed region. Reproducible test case under Linux on armv7l (RaspberryPi-3B in 32-bit mode= ): =3D=3D=3D=3D=3D gdbbug.c #include #include int main(int argc, char *argv[]) { int *addr =3D mmap(0, 4096, PROT_EXEC|PROT_WRITE|PROT_READ, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0); *addr =3D 0xe24dd004; // sub sp,sp,#4 return 0; } =3D=3D=3D=3D=3D end gdbbug.c $ uname -a Linux host.domain 4.14.5-300.fc27.armv7hl #1 SMP Mon Dec 11 17:29:37 UTC 20= 17 armv7l armv7l armv7l GNU/Linux $ gcc --version gcc (GCC) 7.2.1 20170915 (Red Hat 7.2.1-2) $ gcc -g -o gdbbug gdbbug.c $ gdb gdbbug GNU gdb (GDB) 8.0.50.20171216-git <> (gdb) b main Breakpoint 1 at 0x10418: file gdbbug.c, line 7. (gdb) run Starting program: /path/to/gdbbug=20 Cannot parse expression `.L1199 4@r4'. warning: Probes-based dynamic linker interface failed. Reverting to original interface. Breakpoint 1, main (argc=3D0x1, argv=3D0xbefff464) at gdbbug.c:7 7 int *addr =3D mmap(0, 4096, PROT_EXEC|PROT_WRITE|PROT_READ, (gdb) n 9 *addr =3D 0xe24dd004; // sub sp,sp,#4 (gdb) n 10 return 0; (gdb) x/i $pc ## current value =3D> 0x10450 : mov r3, #0 (gdb) x/i addr ## mmap()ed region 0xb6ffa000: sub sp, sp, #4 (gdb) set $pc =3D $_ ## attempt to set $pc; no complaint (gdb) x/i $pc ## but value did not change =3D> 0x1043c : str r0, [r11, #-8] (gdb) set $pc =3D 0xb6ffa000 ## stronger attempt to set $pc Attempt to assign to an unmodifiable value. ## very strange (gdb) x/i $pc ## value did not change =3D> 0x1043c : str r0, [r11, #-8] (gdb) =3D=3D=3D=3D=3D gdb was built from git tip: =3D=3D=3D=3D=3D $ git log commit 09da3ecf04d75084ea7d9c43e3cc0b18b2443ea3 (HEAD -> master, origin/mas= ter, origin/HEAD) Author: GDB Administrator Date: Sat Dec 16 00:00:33 2017 +0000 Automatic date update in version.in =3D=3D=3D=3D=3D A preliminary version of this bugzilla report was filed as=20 https://bugzilla.redhat.com/show_bug.cgi?id=3D1526617 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22276-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Dec 16 17:05:02 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 92201 invoked by alias); 16 Dec 2017 17:05:02 -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 92175 invoked by uid 48); 16 Dec 2017 17:05:01 -0000 From: "jreiser at BitWagon dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22617] New: RFE: parallelize ./configure Date: Sat, 16 Dec 2017 17:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jreiser at BitWagon dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00320.txt.bz2 Content-length: 863 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22617 Bug ID: 22617 Summary: RFE: parallelize ./configure Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jreiser at BitWagon dot com Target Milestone: --- Request For Enhancement ("RFE"): Please parallelize the "checking for ..." = and "checking whether ..." pieces of running ./configure for gdb. There are hundreds of them, they are all independent, yet they run serially in separa= te processes. Auto-parallelizing these tests, or obeying a "-jN" command-line argument like 'make', would save minutes of developer time. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22277-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Dec 16 17:35:17 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 21811 invoked by alias); 16 Dec 2017 17:35:17 -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 21786 invoked by uid 48); 16 Dec 2017 17:35:17 -0000 From: "jreiser at BitWagon dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22618] New: bad diagnosis and recovery suggestion when bison or flex is missing Date: Sat, 16 Dec 2017 17:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jreiser at BitWagon dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00321.txt.bz2 Content-length: 4817 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22618 Bug ID: 22618 Summary: bad diagnosis and recovery suggestion when bison or flex is missing Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jreiser at BitWagon dot com Target Milestone: --- When building gdb on a system where bison or flex is not found in $PATH, th= en the error diagnosis and recovery suggestion is incomplete. The suggestion forgets to say: Run "make clean" after installing [bison or flex] before continuing. This causes needless bewilderment and lost time when subsequent 'make' complains about a missing file syslex.c. Maintainers of the gdb package in various Linux distributions often encourage "file bug reports upstream" [namely, here at sourceware.org instead of at the distribution level]. Thus "gdb developer" often includes "ordinary users" who encounter problems with distributed packaged gdb. Furthermore, checking for bison and flex should be part of the top-level ./configure for gdb, and not [only] in lower-level .../configure scripts. = By default, a complete top-level build does require both bison and flex; suppl= ying them at first will avoid the necessity of "tending" the top-level 'make' interactively. Add options "--without bison" and "--without flex" to the top-level 'configure' if desired to please those experienced developers who manage to avoid using bison and flex by excluding various sub-packages of g= db. When doing a complete top-level build of gdb, then the bison diagnosis is: =3D=3D=3D=3D=3D Making all in po /home/jreiser/binutils-gdb/missing: line 81: bison: command not found make[4]: Entering directory '/home/jreiser/binutils-gdb/gprof/po' file=3D`echo bg | sed 's,.*/,,'`.gmo \ && rm -f $file && PATH=3D../src:$PATH /usr/bin/msgfmt -o $file bg.po WARNING: 'bison' is missing on your system. You should only need it if you modified a '.y' file. You may want to install the GNU Bison package: make[2]: *** [Makefile:986: arparse.c] Error 127 make[2]: *** Waiting for unfinished jobs.... file=3D`echo da | sed 's,.*/,,'`.gmo \ && rm -f $file && PATH=3D../src:$PATH /usr/bin/msgfmt -o $file da.po /home/jreiser/binutils-gdb/missing: line 81: bison: command not found file=3D`echo de | sed 's,.*/,,'`.gmo \ && rm -f $file && PATH=3D../src:$PATH /usr/bin/msgfmt -o $file de.po WARNING: 'bison' is missing on your system. You should only need it if you modified a '.y' file. You may want to install the GNU Bison package: make[2]: *** [Makefile:986: sysinfo.c] Error 127 make[2]: Leaving directory '/home/jreiser/binutils-gdb/binutils' =3D=3D=3D=3D=3D After installing bison, then re-running 'make' gives the flex diagnosis: =3D=3D=3D=3D=3D /home/jreiser/binutils-gdb/missing: line 81: flex: command not found updating sysinfo.h WARNING: 'flex' is missing on your system. You should only need it if you modified a '.l' file. You may want to install the Fast Lexical Analyzer package: make[2]: *** [Makefile:983: syslex.c] Error 127 make[2]: *** Waiting for unfinished jobs.... gcc -DHAVE_CONFIG_H -DWITH_DEFAULT_ALIGNMENT=3DSTRICT_ALIGNMENT=20=20=20=20 -DDEFAULT_INLINE=3D0 -Wall -Wdeclaration-after-statement -Wpointer-arith -Wpointer-sign -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wmissing-prototypes -Wdeclaration-after-statement -Wempty-body -Wmissing-parameter-type -Wold-style-declaration -Wold-style-definition -Wformat-nonliteral -DMODET -I. -I. -I../common -I./../common -I../../include -I./../../include -I../../bfd -I./../../bfd -I../../opcodes -I./../../opcodes -g -O2 -c -o version.o -MT version.o -MMD -MP -MF .deps/version.Tpo version.c make[2]: Leaving directory '/home/jreiser/binutils-gdb/binutils' =3D=3D=3D=3D=3D After installing flex, then re-running 'make' gives the error: =3D=3D=3D=3D=3D gcc -c -I. -I. -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=3D262144 -Werror -I./../zlib -g -O2 -Wno-error ./syslex_wrap.c ./syslex_wrap.c:25:10: fatal error: syslex.c: No such file or directory #include "syslex.c" ^~~~~~~~~~ compilation terminated. make[2]: *** [Makefile:1375: syslex_wrap.o] Error 1 make[2]: Leaving directory '/home/jreiser/binutils-gdb/binutils' =3D=3D=3D=3D=3D That error takes a while to figure out. The top-level ./configure should diagnose the lack of bison and flex. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22278-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Dec 16 17:37:51 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 53309 invoked by alias); 16 Dec 2017 17:37:51 -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 52300 invoked by uid 48); 16 Dec 2017 17:37:50 -0000 From: "jreiser at BitWagon dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22618] bad diagnosis and recovery suggestion when bison or flex is missing Date: Sat, 16 Dec 2017 17:37: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jreiser at BitWagon dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00322.txt.bz2 Content-length: 489 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22618 --- Comment #1 from John Reiser --- Source was git tip as of: =3D=3D=3D=3D=3D commit 09da3ecf04d75084ea7d9c43e3cc0b18b2443ea3 (HEAD -> master, origin/mas= ter, origin/HEAD) Author: GDB Administrator Date: Sat Dec 16 00:00:33 2017 +0000 Automatic date update in version.in =3D=3D=3D=3D=3D --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22279-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Dec 16 17:49:10 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 40275 invoked by alias); 16 Dec 2017 17:49:10 -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 40241 invoked by uid 48); 16 Dec 2017 17:49:10 -0000 From: "jreiser at BitWagon dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22619] New: repeat count is forgotten by newline to extend previous 'x' command (examine memory) Date: Sat, 16 Dec 2017 17:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jreiser at BitWagon dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00323.txt.bz2 Content-length: 1558 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22619 Bug ID: 22619 Summary: repeat count is forgotten by newline to extend previous 'x' command (examine memory) Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jreiser at BitWagon dot com Target Milestone: --- The command sequence (gdb) x/12xw $sp (gdb) ## newline to show the next 12 words forgets the repeat count "12"; it displays only one word instead of the expected 12. Example: $ gdb hello GNU gdb (GNU gdb (GDB) 8.0.50.20171216-git <> (gdb) b main (gdb) run Breakpoint 1, main (argc=3D0x1, argv=3D0xbefff454) at hello.c:5 (gdb) x/12xw $sp 0xbefff2e8: 0x00010460 0x00000000 0xbefff454 0x00000001 0xbefff2f8: 0x00000000 0x00000000 0x00000000 0xb6e63c40 0xbefff308: 0xb6fb5000 0xbefff454 0x00000001 0x00010404 (gdb) ## type or to ask for the next 12 words 0xbefff318: 0x9fea1ea9 ## only one (1) word shown instead of twelve (= 12) (gdb) gdb was built from git tip: commit 09da3ecf04d75084ea7d9c43e3cc0b18b2443ea3 (HEAD -> master, origin/mas= ter, origin/HEAD) Author: GDB Administrator Date: Sat Dec 16 00:00:33 2017 +0000 Automatic date update in version.in --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22280-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Dec 16 20:10:52 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 89100 invoked by alias); 16 Dec 2017 20:10: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 89073 invoked by uid 48); 16 Dec 2017 20:10:52 -0000 From: "sergiodj at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22617] RFE: parallelize ./configure Date: Sat, 16 Dec 2017 20:10: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sergiodj at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WONTFIX 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 cc resolution 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: 2017-q4/txt/msg00324.txt.bz2 Content-length: 948 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22617 Sergio Durigan Junior changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |sergiodj at redhat dot com Resolution|--- |WONTFIX --- Comment #1 from Sergio Durigan Junior --- Sorry, but this bug should be filed against autotools, and not GDB. Running "configure" in parallel is not supported by autotools, and I don't know any project that implements this by themselves. GDB's configure uses whatever = it can to speed things up (e.g., cache), so anything else should be implemente= d by autotools IMO. Closing as WONTFIX. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22281-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Dec 17 05:02:27 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 82724 invoked by alias); 17 Dec 2017 05:02:26 -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 80717 invoked by uid 48); 17 Dec 2017 05:02:23 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22621] New: Missing completion of std::__c Date: Sun, 17 Dec 2017 05:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00325.txt.bz2 Content-length: 875 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22621 Bug ID: 22621 Summary: Missing completion of std::__c Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: simon.marchi at ericsson dot com Target Milestone: --- While stopped in a C++ program, I can complete std::__, there are many resu= lts, including some starting with std::__c (gdb) complete b std::__ ... b std::__cxx11::basic_string... ... When I try to complete std::__c, I would expect to have at least the result shown above. However, I get an empty list when I do (gdb) complete b std::__c Same when using the tab key. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22282-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 18 14:22:59 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 80602 invoked by alias); 18 Dec 2017 14:22:58 -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 80571 invoked by uid 48); 18 Dec 2017 14:22:58 -0000 From: "abdul.basitijaz at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22629] New: GDB on MacOS is leaving an orphaned debuggee process running Date: Mon, 18 Dec 2017 14:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: abdul.basitijaz at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00326.txt.bz2 Content-length: 1402 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22629 Bug ID: 22629 Summary: GDB on MacOS is leaving an orphaned debuggee process running Product: gdb Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: abdul.basitijaz at gmail dot com Target Milestone: --- GDB on MacOS(10.12.3) is leaving an orphaned debuggee process running on the system after gdb exits.=20 Issue can be verified with any cpp executable out file. To reproduce, compile any cpp program then run it under gdb, then quit gdb during debugging : For compilation :=20 g++ -g -c .cpp g++ -g .o -o .exe For debugging :=20 > gdb=20 >> file .exe >> b main >> r After break point is hit quit the GDB and verify the process list=20 >> r or q (for both f these commands GDB shows that inferior process will = be killed but it is not getting killed ) > ps ax |grep .exe .exe will be shown that it is still running . So as many times you perform above steps process will keep adding here=20 Test Environment info :=20 macOS 10.12.3 Kernel Version: Darwin 16.4.0 GNU gdb (GDB) 8.0.1 --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22283-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 18 16:23:44 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 68332 invoked by alias); 18 Dec 2017 16:23:44 -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 68194 invoked by uid 48); 18 Dec 2017 16:23:43 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22556] Regression: gdb.threads/names.exp with --target_board=native-gdbserver Date: Mon, 18 Dec 2017 16:23: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson 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: 8.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution 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: 2017-q4/txt/msg00327.txt.bz2 Content-length: 624 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22556 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |simon.marchi at ericsson d= ot com Resolution|--- |FIXED --- Comment #3 from Simon Marchi --- Fixed by the above commit. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22284-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 18 22:36:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 80524 invoked by alias); 18 Dec 2017 22:36:37 -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 80485 invoked by uid 48); 18 Dec 2017 22:36:37 -0000 From: "weimin.pan at oracle dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/8748] gdb Date: Mon, 18 Dec 2017 22:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: weimin.pan at oracle dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jimb 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: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00328.txt.bz2 Content-length: 420 https://sourceware.org/bugzilla/show_bug.cgi?id=3D8748 weimin.pan at oracle dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|SUSPENDED |RESOLVED Resolution|--- |FIXED --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22285-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 19 20:20:22 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 58992 invoked by alias); 19 Dec 2017 20:20:22 -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 58963 invoked by uid 48); 19 Dec 2017 20:20:22 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug remote/22633] New: documentation for qOffsets Date: Tue, 19 Dec 2017 20:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00329.txt.bz2 Content-length: 751 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22633 Bug ID: 22633 Summary: documentation for qOffsets Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: remote Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- In https://github.com/luser/rust-gdb-remote-protocol/issues/11#issuecomment-35= 2842771 we were discussing whether the remote can return '' or 'Enn' in response to qOffsets. This appears not to be documented properly in the manual. gdbserver seems to return ''. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22286-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 19 20:24:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 71643 invoked by alias); 19 Dec 2017 20:24:35 -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 71575 invoked by uid 48); 19 Dec 2017 20:24:33 -0000 From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug remote/22633] documentation for qOffsets Date: Tue, 19 Dec 2017 20:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: 2017-q4/txt/msg00330.txt.bz2 Content-length: 544 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22633 --- Comment #1 from Tom Tromey --- The overview (https://sourceware.org/gdb/onlinedocs/gdb/Overview.html#Overv= iew) makes it clear that any command can have an empty response. But seeing as the other commands here explicitly mention this, perhaps it would be good to either fix this one as well, or to remove them all and have a parag= raph in this node re-explaining that. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22288-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 20 23:36:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 88741 invoked by alias); 20 Dec 2017 23:36:35 -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 88712 invoked by uid 48); 20 Dec 2017 23:36:35 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug cli/22640] Extend ptype /o to support offsets and sizes in hex rather than decimal Date: Wed, 20 Dec 2017 23:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jhb at FreeBSD dot org 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: cc 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: 2017-q4/txt/msg00332.txt.bz2 Content-length: 378 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22640 jhb at FreeBSD dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at redhat dot com --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22287-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 20 23:36:13 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 87850 invoked by alias); 20 Dec 2017 23:36:13 -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 87817 invoked by uid 48); 20 Dec 2017 23:36:12 -0000 From: "jhb at FreeBSD dot org" To: gdb-prs@sourceware.org Subject: [Bug cli/22640] New: Extend ptype /o to support offsets and sizes in hex rather than decimal Date: Wed, 20 Dec 2017 23:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jhb at FreeBSD dot org 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00331.txt.bz2 Content-length: 821 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22640 Bug ID: 22640 Summary: Extend ptype /o to support offsets and sizes in hex rather than decimal Product: gdb Version: unknown Status: NEW Severity: enhancement Priority: P2 Component: cli Assignee: unassigned at sourceware dot org Reporter: jhb at FreeBSD dot org Target Milestone: --- Having used the recently added 'ptype /o' today, it would be nice to have an option to output offsets (and probably sizes) in hexadecimal. I mostly care about the offsets, but it would probably be most consistent to use the same output base for both offsets and sizes. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22289-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 26 04:03:29 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 77279 invoked by alias); 26 Dec 2017 04:03:29 -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 77253 invoked by uid 48); 26 Dec 2017 04:03:28 -0000 From: "jreiser at BitWagon dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22645] New: gdb hangs on 32-bit ARM armv7l at SIGTRAP from "bkpt" instruction 0xe1200070 Date: Tue, 26 Dec 2017 04:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jreiser at BitWagon dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2017-q4/txt/msg00333.txt.bz2 Content-length: 10186 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22645 Bug ID: 22645 Summary: gdb hangs on 32-bit ARM armv7l at SIGTRAP from "bkpt" instruction 0xe1200070 Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jreiser at BitWagon dot com Target Milestone: --- gdb hangs in an infinite loop instead of stopping upon SIGTRAP when an infe= rior on 32-bit ARM architecture 'armv7l' (such as RaspberryPi-3B in 32-bit mode) executes the instruction "bkpt", which is 0xe1200070. The Linux kernel sen= ds SIGTRAP, but gdb processing tries PTRACE_CONT, which re-triggers the SIGTRA= P.=20 Interrupting the gdb hang with SIGINT (ctrl-C) revives gdb, and the output = for SIGINT looks like the way gdb should have responded in the first place to t= he SIGTRAP. Here is an annotated transcript of a console terminal session which contain= s a 4-line reproducible test case plus recipe, as well as some 'strace' debuggi= ng of the ptrace() calls used by gdb. =3D=3D=3D=3D=3D $ uname -a ## the hardware and operating system environment Linux host 4.14.7-300.fc27.armv7hl #1 SMP Mon Dec 18 17:10:15 UTC 2017 armv= 7l armv7l armv7l GNU/Linux $ cat bkpt.S ## the test case .globl _start _start: bkpt nop $ gcc -o bkpt -nostartfiles -nostdlib bkpt.S ## the build recipe $ ./bkpt ## bare execution gets SIGTRAP Trace/breakpoint trap (core dumped) $ echo $? ## shell exit code of previous process in this shell 133 ## 133 =3D 128 + 5; 5 =3D=3D> SIGTRAP $ strace ./bkpt execve("./bkpt", ["./bkpt"], 0xbeebe4c0 /* 28 vars */) =3D 0 --- SIGTRAP {si_signo=3DSIGTRAP, si_code=3DTRAP_HWBKPT, si_pid=3D65688, si_= uid=3D0} --- +++ killed by SIGTRAP (core dumped) +++ Trace/breakpoint trap (core dumped) $ gdb --version GNU gdb (GDB) 8.0.50.20171216-git $ gdb bkpt ## gdb hangs (gdb) x/12i _start ## verify correct assembly 0x10098 <_start>: bkpt 0x0000 0x1009c <_start+4>: nop {0} 0x100a0: Cannot access memory at address 0x100a0 (gdb) x/12x _start 0x10098 <_start>: 0xe1200070 0xe320f000 Cannot access memor= y at address 0x100a0 (gdb) run Starting program: /path/to/bkpt ^C ## session appears to be hung (gdb "unhealthy"), so send SIGINT from console Program received signal SIGINT, Interrupt. 0x00010098 in _start () ## gdb acts healthy for SIGINT; why not for SIGTR= AP? (gdb) x/i $pc =3D> 0x10098 <_start>: bkpt 0x0000 ## the correct place (gdb) 0x1009c <_start+4>: nop {0} (gdb) q $ dmesg | tail ## what happened while SIGTRAP under gdb [ 483.287100] Unhandled prefetch abort: breakpoint debug exception (0x002)= at 0x00010098 [ 483.295547] Unhandled prefetch abort: breakpoint debug exception (0x002)= at 0x00010098 [ 483.303960] Unhandled prefetch abort: breakpoint debug exception (0x002)= at 0x00010098 $ strace -e trace=3Dptrace -o strace-gdb.out gdb ./bkpt ## note strange PTRACE_CONT after SIGTRAP (33 lines below; "what is this?") --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_EXITED, si_pid=3D1307, si_ui= d=3D1000, si_status=3D0, si_utime=3D0, si_stime=3D0} --- --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_TRAPPED, si_pid=3D1308, si_u= id=3D1000, si_status=3DSIGTRAP, si_utime=3D0, si_stime=3D0} --- ptrace(PTRACE_GETREGS, 1308, NULL, 0xbe84ec60) =3D 0 ptrace(PTRACE_GETSIGINFO, 1308, NULL, {si_signo=3DSIGTRAP, si_code=3DSI_USE= R, si_pid=3D1308, si_uid=3D1000}) =3D 0 ptrace(PTRACE_CONT, 1308, 0x1, SIG_0) =3D 0 --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_TRAPPED, si_pid=3D1308, si_u= id=3D1000, si_status=3DSIGTRAP, si_utime=3D0, si_stime=3D0} --- ptrace(PTRACE_GETREGS, 1308, NULL, 0xbe84ec60) =3D 0 ptrace(PTRACE_GETSIGINFO, 1308, NULL, {si_signo=3DSIGTRAP, si_code=3DSI_USE= R, si_pid=3D1308, si_uid=3D1000}) =3D 0 --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_TRAPPED, si_pid=3D1309, si_u= id=3D1000, si_status=3DSIGSTOP, si_utime=3D0, si_stime=3D0} --- ptrace(PTRACE_SETOPTIONS, 1309, NULL, PTRACE_O_TRACESYSGOOD) =3D 0 ptrace(PTRACE_SETOPTIONS, 1309, NULL, PTRACE_O_TRACEFORK) =3D 0 ptrace(PTRACE_SETOPTIONS, 1309, NULL, PTRACE_O_TRACEFORK|PTRACE_O_TRACEVFORKDONE) =3D 0 ptrace(PTRACE_CONT, 1309, NULL, SIG_0) =3D 0 --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_TRAPPED, si_pid=3D1309, si_u= id=3D1000, si_status=3DSIGTRAP, si_utime=3D0, si_stime=3D0} --- ptrace(PTRACE_GETEVENTMSG, 1309, NULL, [1310]) =3D 0 ptrace(PTRACE_KILL, 1310) =3D 0 --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_KILLED, si_pid=3D1310, si_ui= d=3D1000, si_status=3DSIGKILL, si_utime=3D0, si_stime=3D0} --- ptrace(PTRACE_SETOPTIONS, 1309, NULL, PTRACE_O_EXITKILL) =3D 0 ptrace(PTRACE_KILL, 1309) =3D 0 --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_TRAPPED, si_pid=3D1309, si_u= id=3D1000, si_status=3DSIGCHLD, si_utime=3D0, si_stime=3D0} --- ptrace(PTRACE_KILL, 1309) =3D 0 --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_KILLED, si_pid=3D1309, si_ui= d=3D1000, si_status=3DSIGKILL, si_utime=3D0, si_stime=3D0} --- ptrace(PTRACE_SETOPTIONS, 1308, NULL, PTRACE_O_TRACESYSGOOD|PTRACE_O_TRACEFORK|PTRACE_O_TRACEVFORK|PTRACE_O_TRACE= CLONE|PTRACE_O_TRACEEXEC|PTRACE_O_TRACEVFORKDONE|PTRACE_O_EXITKILL) =3D 0 ptrace(PTRACE_GETREGSET, 1308, NT_PRSTATUS, [{iov_base=3D0xbe84efa8, iov_len=3D72}]) =3D 0 ptrace(PTRACE_GETVFPREGS, 1308, NULL, 0xbe84ee88) =3D 0 ptrace(PTRACE_GETREGSET, 1308, NT_PRSTATUS, [{iov_base=3D0xbe84ef70, iov_len=3D72}]) =3D 0 ptrace(PTRACE_CONT, 1308, 0x1, SIG_0) =3D 0 --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_TRAPPED, si_pid=3D1308, si_u= id=3D1000, si_status=3DSIGTRAP, si_utime=3D0, si_stime=3D0} --- ptrace(PTRACE_GETREGSET, 1308, NT_PRSTATUS, [{iov_base=3D0xbe84ede8, iov_len=3D72}]) =3D 0 ptrace(PTRACE_GETSIGINFO, 1308, NULL, {si_signo=3DSIGTRAP, si_code=3DTRAP_H= WBKPT, si_pid=3D65688, si_uid=3D0, si_value=3D{int=3D1308, ptr=3D0x51c}}) =3D 0 ptrace(PTRACE_GETSIGINFO, 1308, NULL, {si_signo=3DSIGTRAP, si_code=3DTRAP_H= WBKPT, si_pid=3D65688, si_uid=3D0}) =3D 0 ptrace(PTRACE_GETHBPREGS, 1308, NULL, 0xbe84edec) =3D 0 ptrace(PTRACE_CONT, 1308, 0x1, SIG_0) =3D 0 ## what is this? --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_TRAPPED, si_pid=3D1308, si_u= id=3D1000, si_status=3DSIGTRAP, si_utime=3D0, si_stime=3D0} --- ptrace(PTRACE_GETREGSET, 1308, NT_PRSTATUS, [{iov_base=3D0xbe84ede8, iov_len=3D72}]) =3D 0 ptrace(PTRACE_GETSIGINFO, 1308, NULL, {si_signo=3DSIGTRAP, si_code=3DTRAP_H= WBKPT, si_pid=3D65688, si_uid=3D0, si_value=3D{int=3D1308, ptr=3D0x51c}}) =3D 0 ptrace(PTRACE_GETSIGINFO, 1308, NULL, {si_signo=3DSIGTRAP, si_code=3DTRAP_H= WBKPT, si_pid=3D65688, si_uid=3D0}) =3D 0 ptrace(PTRACE_CONT, 1308, 0x1, SIG_0) =3D 0 --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_TRAPPED, si_pid=3D1308, si_u= id=3D1000, si_status=3DSIGTRAP, si_utime=3D0, si_stime=3D0} --- ptrace(PTRACE_GETREGSET, 1308, NT_PRSTATUS, [{iov_base=3D0xbe84ede8, iov_len=3D72}]) =3D 0 ptrace(PTRACE_GETSIGINFO, 1308, NULL, {si_signo=3DSIGTRAP, si_code=3DTRAP_H= WBKPT, si_pid=3D65688, si_uid=3D0, si_value=3D{int=3D1308, ptr=3D0x51c}}) =3D 0 ptrace(PTRACE_GETSIGINFO, 1308, NULL, {si_signo=3DSIGTRAP, si_code=3DTRAP_H= WBKPT, si_pid=3D65688, si_uid=3D0}) =3D 0 ptrace(PTRACE_CONT, 1308, 0x1, SIG_0) =3D 0 --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_TRAPPED, si_pid=3D1308, si_u= id=3D1000, si_status=3DSIGTRAP, si_utime=3D0, si_stime=3D1} --- ptrace(PTRACE_GETREGSET, 1308, NT_PRSTATUS, [{iov_base=3D0xbe84ede8, iov_len=3D72}]) =3D 0 ptrace(PTRACE_GETSIGINFO, 1308, NULL, {si_signo=3DSIGTRAP, si_code=3DTRAP_H= WBKPT, si_pid=3D65688, si_uid=3D0, si_value=3D{int=3D1308, ptr=3D0x51c}}) =3D 0 ptrace(PTRACE_GETSIGINFO, 1308, NULL, {si_signo=3DSIGTRAP, si_code=3DTRAP_H= WBKPT, si_pid=3D65688, si_uid=3D0}) =3D 0 ptrace(PTRACE_CONT, 1308, 0x1, SIG_0) =3D 0 <> --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_TRAPPED, si_pid=3D1308, si_u= id=3D1000, si_status=3DSIGTRAP, si_utime=3D0, si_stime=3D20} --- ptrace(PTRACE_GETREGSET, 1308, NT_PRSTATUS, [{iov_base=3D0xbe84ede8, iov_len=3D72}]) =3D 0 ptrace(PTRACE_GETSIGINFO, 1308, NULL, {si_signo=3DSIGTRAP, si_code=3DTRAP_H= WBKPT, si_pid=3D65688, si_uid=3D0, si_value=3D{int=3D1308, ptr=3D0x51c}}) =3D 0 ptrace(PTRACE_GETSIGINFO, 1308, NULL, {si_signo=3DSIGTRAP, si_code=3DTRAP_H= WBKPT, si_pid=3D65688, si_uid=3D0}) =3D 0 ptrace(PTRACE_CONT, 1308, 0x1, SIG_0) =3D 0 --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_TRAPPED, si_pid=3D1308, si_u= id=3D1000, si_status=3DSIGINT, si_utime=3D0, si_stime=3D20} --- ptrace(PTRACE_GETREGSET, 1308, NT_PRSTATUS, [{iov_base=3D0xbe84ef68, iov_len=3D72}]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10098, [0xe1200070]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10094, [0xbd7e609d]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10098, [0xe1200070]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10094, [0xbd7e609d]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10098, [0xe1200070]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10094, [0xbd7e609d]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10094, [0xbd7e609d]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10098, [0xe1200070]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10094, [0xbd7e609d]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10094, [0xbd7e609d]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10098, [0xe1200070]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10094, [0xbd7e609d]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10098, [0xe1200070]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10094, [0xbd7e609d]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10098, [0xe1200070]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10098, [0xe1200070]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10098, [0xe1200070]) =3D 0 ptrace(PTRACE_PEEKTEXT, 1308, 0x10098, [0xe1200070]) =3D 0 ptrace(PTRACE_KILL, 1308) =3D 0 --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_KILLED, si_pid=3D1308, si_ui= d=3D1000, si_status=3DSIGKILL, si_utime=3D0, si_stime=3D20} --- ptrace(PTRACE_KILL, 1308) =3D -1 ESRCH (No such process) +++ exited with 0 +++ =3D=3D=3D=3D=3D --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22290-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Dec 26 04:15:35 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 70480 invoked by alias); 26 Dec 2017 04:15:34 -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 67506 invoked by uid 48); 26 Dec 2017 04:15:29 -0000 From: "jreiser at BitWagon dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22645] gdb hangs on 32-bit ARM armv7l at SIGTRAP from "bkpt" instruction 0xe1200070 Date: Tue, 26 Dec 2017 04:15: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jreiser at BitWagon dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00334.txt.bz2 Content-length: 719 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22645 --- Comment #1 from John Reiser --- The same bad behavior also occurs when the bkpt is not the first instructio= n: =3D=3D=3D=3D=3D .globl _start _start: nop bkpt nop =3D=3D=3D=3D=3D In the past gdb has had trouble when the very first instruction after execve generated a trap: https://bugzilla.redhat.com/show_bug.cgi?id=3D162775 "gdb ignores SIGTRAP at entry address" 2008-03-10 [almost ten years ago] but the revised test case above, where the SIGTRAP is at the second instruction, still hangs under gdb. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22291-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Dec 27 05:34:53 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 8130 invoked by alias); 27 Dec 2017 05:34:53 -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 8102 invoked by uid 48); 27 Dec 2017 05:34:52 -0000 From: "jreiser at BitWagon dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/22645] gdb hangs on 32-bit ARM armv7l at SIGTRAP from "bkpt" instruction 0xe1200070 Date: Wed, 27 Dec 2017 05:34: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jreiser at BitWagon dot com X-Bugzilla-Status: UNCONFIRMED 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: 2017-q4/txt/msg00335.txt.bz2 Content-length: 1213 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22645 --- Comment #2 from John Reiser --- Contrasting with the similar "brk #0" (.word 0xd4200000) on 64-bit ARM aarc= h64: gdb stops and reports SIGTRAP the first time (does not silently loop using PTRACE_CONT) and strace shows =3D=3D=3D=3D=3D --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_TRAPPED, si_pid=3D9705, si_u= id=3D1000, si_status=3DSIGTRAP, si_utime=3D1, si_stime=3D0} --- ptrace(PTRACE_GETREGSET, 9705, NT_PRSTATUS, [{iov_base=3D0xffffe5b28e88, iov_len=3D272}]) =3D 0 ptrace(PTRACE_GETSIGINFO, 9705, NULL, {si_signo=3DSIGTRAP, si_code=3DTRAP_B= RKPT, si_pid=3D4194520, si_uid=3D0, si_value=3D{int=3D-441282160, ptr=3D0xffffe5b= 29190}}) =3D 0 ptrace(PTRACE_PEEKTEXT, 9705, 0x4000d8, [0xd503201fd4200000]) =3D 0 ptrace(PTRACE_PEEKTEXT, 9705, 0x4000d8, [0xd503201fd4200000]) =3D 0 ptrace(PTRACE_PEEKTEXT, 9705, 0x4000d0, [0xd503201f155c8bda]) =3D 0 ptrace(PTRACE_PEEKTEXT, 9705, 0x4000d8, [0xd503201fd4200000]) =3D 0 =3D=3D=3D=3D=3D One notable difference is: si_code=3DTRAP_BRKPT on 64-bit ARM si_code=3DTRAP_HWBKPT on 32-bit ARM --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22292-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Dec 28 21:09:38 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 66640 invoked by alias); 28 Dec 2017 21:09:38 -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 66578 invoked by uid 48); 28 Dec 2017 21:09:37 -0000 From: "halbert at halwitz dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/22647] New: Tab completion hangs with a gcc7 LTO elf Date: Thu, 28 Dec 2017 21:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: halbert at halwitz dot org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: 2017-q4/txt/msg00336.txt.bz2 Content-length: 1976 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22647 Bug ID: 22647 Summary: Tab completion hangs with a gcc7 LTO elf Product: gdb Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: halbert at halwitz dot org Target Milestone: --- Created attachment 10701 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D10701&action=3Ded= it gdb-hang-gcc721.elf and gdb-ok-gcc631.elf I have a an arm-none-eabi-gcc 7.2.1 .elf that causes gdb to hang when doing= tab completion. Problem appears with various gdb's I tried: 1. arm-none-eabi-gdb 8.0.50-8.0.50.20171128-git. This gdb came with the GNU Tools for Arm Embedded Processors 7-2017-q4-major release. 2. arm-none-eabi-gdb 7.2.1 20170904 (previous 2017 q2 ARM tools release) 3. gdb 7.11.1 (non-ARM) Ubuntu 7.11.1-0ubuntu1~16.5 A good and a bad .elf are attached in a .zip. To reproduce, do: $ gdb gdb-hang-gcc721.elf (gdb) break mp_cal When you press , gdb will start consuming 100% CPU. I waited for sever= al minutes with no effect. The process must be `kill -9`d to get rid of it. ^C does not work. I tried `set max-completions 5`, which works, and `50`, which still hangs. The good .elf looks like this: $ gdb gdb-ok-gcc631.elf (gdb) break mp_call_ which completes with `l_` immediately (the symbol is still incomplete). You can test this ARM .elf with x64 gdb; you don't need to use an ARM-speci= fic gdb. Both .elf's are from the same large source tree. One was compiled with -flto with arm-none-eabi-gcc 6.3.1, the other with -flto on7.2.1. If I turn off -flto, the problem does not occur, so it's some issue with what -flto is causing to be generated in the elf. Nevertheless, gdb shouldn't hang even if the .elf is bad. --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22293-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Dec 29 10:40:19 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 18688 invoked by alias); 29 Dec 2017 10:40:19 -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 18664 invoked by uid 48); 29 Dec 2017 10:40:19 -0000 From: "dcb314 at hotmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18119] gas/config/tc-arm.c:8874: bad if expression ? Date: Fri, 29 Dec 2017 10:40: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dcb314 at hotmail dot com 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: 2017-q4/txt/msg00337.txt.bz2 Content-length: 331 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18119 --- Comment #1 from dcb --- Still broken a few years later: config/tc-arm.c:9161:50: warning: bitwise comparison always evaluates to tr= ue [-Wtautological-compare] --=20 You are receiving this mail because: You are on the CC list for the bug. >>From gdb-prs-return-22294-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Dec 31 14:42:49 2017 Return-Path: Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 14786 invoked by alias); 31 Dec 2017 14:42:48 -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 14758 invoked by uid 48); 31 Dec 2017 14:42:47 -0000 From: "simon.marchi at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/19558] Trying to attach the same process twice borks gdbserver Date: Sun, 31 Dec 2017 14:42: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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at ericsson dot com 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: 2017-q4/txt/msg00338.txt.bz2 Content-length: 349 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19558 --- Comment #5 from Simon Marchi --- Another consequence of the same bug, if you start gdbserver with --once, gdbserver exits when an attach fails. I don't think that's right. --=20 You are receiving this mail because: You are on the CC list for the bug.