public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/24865] gdb crashes while debugging due to invalid pointer exception in value.c:416.
[not found] <bug-24865-4717@http.sourceware.org/bugzilla/>
@ 2020-01-02 14:49 ` josephschuchart at gmail dot com
2020-03-24 15:49 ` tromey at sourceware dot org
` (2 subsequent siblings)
3 siblings, 0 replies; 4+ messages in thread
From: josephschuchart at gmail dot com @ 2020-01-02 14:49 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=24865
Joseph Schuchart <josephschuchart at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |josephschuchart at gmail dot com
--- Comment #1 from Joseph Schuchart <josephschuchart at gmail dot com> ---
Created attachment 12162
--> https://sourceware.org/bugzilla/attachment.cgi?id=12162&action=edit
Test case for Segfault in value_entirely_covered_by_range_vector
Build:
```
$ g++ -std=c++17 -g test_gdb_optout.cc -o test_gdb_optout
```
Run:
```
$ gdb -ex "b main" -ex r test_gdb_optout
GNU gdb (GDB) 8.3
[...]
Breakpoint 1, main () at test_gdb_optout.cc:69
69 {
(gdb) n
70 X1T<long, int> X{new long[10], 10};
(gdb)
71 foo(X);
(gdb) print X
Segmentation fault (core dumped)
```
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26086-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 02 19:25:19 2020
Return-Path: <gdb-prs-return-26086-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 6521 invoked by alias); 2 Jan 2020 19:25:18 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 6435 invoked by uid 48); 2 Jan 2020 19:25:17 -0000
From: "josephschuchart at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/24865] gdb crashes while debugging due to invalid pointer
exception in value.c:416.
Date: Thu, 02 Jan 2020 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: 8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: josephschuchart 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: <bug-24865-4717-SHWcTLuzxV@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24865-4717@http.sourceware.org/bugzilla/>
References: <bug-24865-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00001.txt
Content-length: 4610
https://sourceware.org/bugzilla/show_bug.cgi?id=24865
--- Comment #2 from Joseph Schuchart <josephschuchart at gmail dot com> ---
Here is the stack trace I get when running the test case inside a second gdb
instance:
(gdb) print X
Program received signal SIGSEGV, Segmentation fault.
value_entirely_covered_by_range_vector (value=value@entry=0x0, ranges=...) at
../../gdb/value.c:416
416 if (value->lazy)
(gdb) bt
#0 value_entirely_covered_by_range_vector (value=value@entry=0x0, ranges=...)
at ../../gdb/value.c:416
#1 0x00005555558ffa2c in value_entirely_optimized_out (value=value@entry=0x0)
at ../../gdb/value.c:441
#2 0x00005555556cb5c7 in cp_print_static_field (options=0x7fffffffd6e0,
recurse=1, stream=0x555555facb40, val=0x0, type=0x55555608e1b0) at
../../gdb/cp-valprint.c:630
#3 cp_print_value_fields (type=<optimized out>,
real_type=real_type@entry=0x5555561080e0, offset=offset@entry=0,
address=address@entry=140737488346512,
stream=0x555555facb40, recurse=0, val=0x555556254060,
options=0x7fffffffd6e0, dont_print_vb=0x0, dont_print_statmem=0) at
../../gdb/cp-valprint.c:332
#4 0x00005555556cbf2d in cp_print_value_fields_rtti (type=<optimized out>,
type@entry=0x5555561080e0, valaddr=valaddr@entry=0x5555563321c0 "",
offset=offset@entry=0,
address=140737488346512, stream=0x555555facb40, recurse=<optimized out>,
val=0x555556254060, options=0x7fffffffd6e0, dont_print_vb=0x0,
dont_print_statmem=0)
at ../../gdb/cp-valprint.c:449
#5 0x000055555567e681 in c_val_print_struct (type=0x5555561080e0,
valaddr=0x5555563321c0 "", embedded_offset=0, address=<optimized out>,
stream=<optimized out>,
recurse=<optimized out>, original_value=0x555556254060,
options=0x7fffffffd6e0) at ../../gdb/c-valprint.c:411
#6 0x000055555567eb80 in c_val_print (type=<optimized out>, embedded_offset=0,
address=140737488346512, stream=0x555555facb40, recurse=0,
original_value=0x555556254060,
options=0x7fffffffd6e0) at ../../gdb/c-valprint.c:532
#7 0x00005555558f78c4 in val_print (type=type@entry=0x555556109b10,
embedded_offset=0, address=address@entry=140737488346512,
stream=stream@entry=0x555555facb40,
recurse=recurse@entry=0, val=val@entry=0x555556254060, options=<optimized
out>, language=0x555555eaa0a0 <cplus_language_defn>) at
../../gdb/valprint.c:1061
#8 0x000055555567f314 in c_value_print (val=0x555556254060,
stream=0x555555facb40, options=<optimized out>) at ../../gdb/c-valprint.c:701
#9 0x00005555558159ad in print_value (val=val@entry=0x555556254060,
fmtp=fmtp@entry=0x7fffffffd8d0) at ../../gdb/printcmd.c:1166
#10 0x0000555555815a65 in print_command_1 (exp=<optimized out>, voidprint=1) at
../../gdb/printcmd.c:1194
#11 0x000055555568aea2 in cmd_func (cmd=<optimized out>, args=<optimized out>,
from_tty=<optimized out>) at ../../gdb/cli/cli-decode.c:1892
#12 0x00005555558cfe25 in execute_command (p=<optimized out>,
p@entry=0x555555f0f8d0 "print X", from_tty=1) at ../../gdb/top.c:630
#13 0x0000555555736bdc in command_handler (command=0x555555f0f8d0 "print X") at
../../gdb/event-top.c:583
#14 0x0000555555736fad in command_line_handler (rl=...) at
../../gdb/event-top.c:770
#15 0x0000555555735c81 in gdb_rl_callback_handler (rl=0x555556253a50 "print X")
at ../../gdb/event-top.c:213
#16 0x000055555591d51f in rl_callback_read_char () at
../../readline/callback.c:220
#17 0x0000555555735b96 in gdb_rl_callback_read_char_wrapper_noexcept () at
../../gdb/event-top.c:175
#18 0x0000555555735c19 in gdb_rl_callback_read_char_wrapper
(client_data=<optimized out>) at ../../gdb/event-top.c:192
#19 0x0000555555736220 in stdin_event_handler (error=<optimized out>,
client_data=0x555555f07870) at ../../gdb/event-top.c:511
#20 0x0000555555734ecd in gdb_wait_for_event (block=block@entry=1) at
../../gdb/event-loop.c:859
#21 0x0000555555735042 in gdb_do_one_event () at ../../gdb/event-loop.c:347
#22 0x00005555557351be in gdb_do_one_event () at ../../gdb/event-loop.c:304
#23 start_event_loop () at ../../gdb/event-loop.c:371
#24 0x00005555557d03e8 in captured_command_loop () at ../../gdb/main.c:331
#25 0x00005555557d15a5 in captured_main (data=<optimized out>) at
../../gdb/main.c:1182
#26 gdb_main (args=<optimized out>) at ../../gdb/main.c:1198
#27 0x00005555556006db in main (argc=<optimized out>, argv=<optimized out>) at
../../gdb/gdb.c:32
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26087-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 03 10:40:05 2020
Return-Path: <gdb-prs-return-26087-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 11793 invoked by alias); 3 Jan 2020 10:40:05 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 11765 invoked by uid 48); 3 Jan 2020 10:40:04 -0000
From: "m_langbe at informatik dot uni-kl.de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/22785] Gdb cannot find assertion failure position
after recompiling, with PIC glibc
Date: Fri, 03 Jan 2020 10:40: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: 8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: m_langbe at informatik dot uni-kl.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: <bug-22785-4717-rDFQwJLID5@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22785-4717@http.sourceware.org/bugzilla/>
References: <bug-22785-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00002.txt
Content-length: 934
https://sourceware.org/bugzilla/show_bug.cgi?id=22785
Max Langbein <m_langbe at informatik dot uni-kl.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |m_langbe at informatik dot uni-kl.
| |de
--- Comment #1 from Max Langbein <m_langbe at informatik dot uni-kl.de> ---
The same happened to me when re-compiling from within gcc, and re-starting:
It does not break any more in raise.c, but at a location where the stack trace
is not any more available.
gcc version 7.4.0
gdb version 8.1.0.20180409-git
gcc flags:
compiler:
-Wextra -Wimplicit-fallthrough -Wnull-dereference -Wall -Wuninitialized -Og
-pedantic -std=c++11
linker:
-Wall -Og
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26088-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 03 10:41:52 2020
Return-Path: <gdb-prs-return-26088-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 12884 invoked by alias); 3 Jan 2020 10:41:51 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 12865 invoked by uid 48); 3 Jan 2020 10:41:51 -0000
From: "m_langbe at informatik dot uni-kl.de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/22785] Gdb cannot find assertion failure position
after recompiling, with PIC glibc
Date: Fri, 03 Jan 2020 10:41: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: 8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: m_langbe at informatik dot uni-kl.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: <bug-22785-4717-dAn55Cz5Q7@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22785-4717@http.sourceware.org/bugzilla/>
References: <bug-22785-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00003.txt
Content-length: 293
https://sourceware.org/bugzilla/show_bug.cgi?id=22785
--- Comment #2 from Max Langbein <m_langbe at informatik dot uni-kl.de> ---
*correction* not "from within gcc" should say "from withing the gdb console"
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26089-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 03 13:17:34 2020
Return-Path: <gdb-prs-return-26089-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 40831 invoked by alias); 3 Jan 2020 13:17:33 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 40807 invoked by uid 48); 3 Jan 2020 13:17:33 -0000
From: "ssbssa at yahoo dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug win32/14529] Make gdb capable of JIT-debugging on W32
Date: Fri, 03 Jan 2020 13:17: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: enhancement
X-Bugzilla-Who: ssbssa 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:
Message-ID: <bug-14529-4717-JgC0CcXgZR@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-14529-4717@http.sourceware.org/bugzilla/>
References: <bug-14529-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00004.txt
Content-length: 1430
https://sourceware.org/bugzilla/show_bug.cgi?id=14529
--- Comment #5 from Hannes Domani <ssbssa at yahoo dot de> ---
(In reply to cvs-commit@gcc.gnu.org from comment #4)
> The master branch has been updated by Eli Zaretskii <eliz@sourceware.org>:
>
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;
> h=463888ab6be549e8dcc9eac36dc07c1c237e2968
>
> commit 463888ab6be549e8dcc9eac36dc07c1c237e2968
> Author: Руслан Ижбулатов <lrn1986@gmail.com>
> Date: Sat Jul 23 11:38:03 2016 +0300
>
> Support JIT debugging on MS-Windows
>
> gdb/ChangeLog:
> 2016-06-30 Руслан Ижбулатов <lrn1986@gmail.com>
>
> PR gdb/14529
> * windows-nat.c (signal_event_command): New command 'signal-event'
> for W32 JIT debug support.
> * NEWS: Add an entry about the new 'signal-event' command.
>
> gdb/doc/ChangeLog:
> 2016-06-30 Руслан Ижбулатов <lrn1986@gmail.com>
>
> * gdb.texinfo (Cygwin Native): Document the new 'signal-event'
> command.
I think this PR should have been closed with this commit.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26090-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 03 19:07:04 2020
Return-Path: <gdb-prs-return-26090-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 93732 invoked by alias); 3 Jan 2020 19:07:04 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 93712 invoked by uid 48); 3 Jan 2020 19:07:04 -0000
From: "b7.10110111 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25342] New: Unicode data in strings conflicts with TUI
Date: Fri, 03 Jan 2020 19: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: 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
Message-ID: <bug-25342-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00005.txt
Content-length: 1199
https://sourceware.org/bugzilla/show_bug.cgi?id=25342
Bug ID: 25342
Summary: Unicode data in strings conflicts with TUI
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tui
Assignee: unassigned at sourceware dot org
Reporter: b7.10110111 at gmail dot com
Target Milestone: ---
Consider the following test C++ program:
```
int main()
{
volatile char buf[]="Привет";
}
```
If you step over the initialization in GDB, and then switch to TUI and type `p
buf`, you'll get a blinking gray text on black background (my normal terminal
background is white). Moreover, the source code is displayed as
```
volatile char buf[]="^^P^�^^Q^�^^P^�^^P^�^^P^�^^Q^�";
```
If you switch off styling, nothing changes. If you go back to CLI mode and type
`p buf` again, the output will be, as expected,
```
$2 = "Привет"
```
Tested on GDB 10.0.50.20191225-git.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26091-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 03 22:17:11 2020
Return-Path: <gdb-prs-return-26091-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 31306 invoked by alias); 3 Jan 2020 22:17:11 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 31282 invoked by uid 48); 3 Jan 2020 22:17:10 -0000
From: "ssbssa at yahoo dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/17521] On Windows-x86_64 GDB runs into infinite loop when
entering small functions generated by RUSTC/LLVM
Date: Fri, 03 Jan 2020 22: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: 7.8
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ssbssa 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: <bug-17521-4717-XpLziRqToJ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17521-4717@http.sourceware.org/bugzilla/>
References: <bug-17521-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00006.txt
Content-length: 1592
https://sourceware.org/bugzilla/show_bug.cgi?id=17521
Hannes Domani <ssbssa at yahoo dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ssbssa at yahoo dot de
--- Comment #4 from Hannes Domani <ssbssa at yahoo dot de> ---
(In reply to Michael Woerister from comment #0)
> Created attachment 7861 [details]
> Source+Executable for reproducing - use 'rb tiny_func' to set breakpoint and
> then 'run'
>
> Using the GDB version coming with [1], GDB seems to get stuck when entering
> some small functions generated by the Rust compiler. Sample backtraces [2]
> seem to suggest that control flow never leaves the
> `amd64_windows_frame_decode_insns()` function.
>
> Attached you can find a small program for reproducing the bug. Just set a
> breakpoint with `rb tiny_func` and then `run`.
>
> Feel free to contact me if you have any further questions.
>
> [1]
> http://sourceforge.net/projects/mingw-w64/files/
> Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.1/threads-
> win32/seh/x86_64-4.9.1-release-win32-seh-rt_v3-rev2.7z/download
>
> [2] https://github.com/rust-lang/rust/issues/17540#issuecomment-60264838
I can reproduce the problem with gdb versions up to 7.10.1.
But with any version beginning with 7.11 upwards, the problem is gone.
PS: All those commits mentioned in here should have been PR17512 I think.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26092-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 03 23:03:12 2020
Return-Path: <gdb-prs-return-26092-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 11874 invoked by alias); 3 Jan 2020 23:03:12 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 11807 invoked by uid 48); 3 Jan 2020 23:03:12 -0000
From: "ssbssa at yahoo dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/24469] gdb: build for python3 on mingw fails due to api
change
Date: Fri, 03 Jan 2020 23: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: 8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ssbssa at yahoo 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: <bug-24469-4717-K0JLQnCFX3@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24469-4717@http.sourceware.org/bugzilla/>
References: <bug-24469-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00007.txt
Content-length: 900
https://sourceware.org/bugzilla/show_bug.cgi?id=24469
Hannes Domani <ssbssa at yahoo dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ssbssa at yahoo dot de
--- Comment #3 from Hannes Domani <ssbssa at yahoo dot de> ---
(In reply to Liviu Ionescu from comment #0)
> Python3 API no longer includes the functions refered in
> `python_run_simple_file()` and the build fails when compiling with `_WIN32`
> (mingw-w64 in my case).
>
> I could not find a simple workaround, I guess the function needs to be
> rewritten.
I think this was fixed with:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=272044897e178835f596c96740c5a1800ec6f9fb
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26093-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 03 23:11:16 2020
Return-Path: <gdb-prs-return-26093-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 69475 invoked by alias); 3 Jan 2020 23:11:16 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 69456 invoked by uid 48); 3 Jan 2020 23:11:16 -0000
From: "ssbssa at yahoo dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/24500] Not able to open debugger windows with 8.0.1 gdb
version of cygwin64.
Date: Fri, 03 Jan 2020 23: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.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: ssbssa at yahoo 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: <bug-24500-4717-MRkBUg8wLP@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24500-4717@http.sourceware.org/bugzilla/>
References: <bug-24500-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00008.txt
Content-length: 727
https://sourceware.org/bugzilla/show_bug.cgi?id=24500
Hannes Domani <ssbssa at yahoo dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ssbssa at yahoo dot de
--- Comment #1 from Hannes Domani <ssbssa at yahoo dot de> ---
> 2) But, Earlier I was able to open debugger in window mode with command
> "gdb -w XXX.exe " of 32 bit cygwin which I attached the screenshots for this
> bug.
This screenshot is actually from insight, not gdb itself.
See https://sourceware.org/insight/ for details.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26094-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 04 11:26:18 2020
Return-Path: <gdb-prs-return-26094-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 113612 invoked by alias); 4 Jan 2020 11:26:18 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 113593 invoked by uid 48); 4 Jan 2020 11:26:18 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] New: Tiny programs (few lines of assembly) cause
GDB's TUI to crash
Date: Sat, 04 Jan 2020 11:26: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: shahab.vahedi 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: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00009.txt
Content-length: 6957
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
Bug ID: 25345
Summary: Tiny programs (few lines of assembly) cause GDB's TUI
to crash
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tui
Assignee: unassigned at sourceware dot org
Reporter: shahab.vahedi at gmail dot com
Target Milestone: ---
Created attachment 12168
--> https://sourceware.org/bugzilla/attachment.cgi?id=12168&action=edit
An example of the bug and 2 illustrations
$$$$$$$$$$$$$$$$$
$$ Environment $$__________________________________________________________
$$$$$$$$$$$$$$$$$
GDB version: 10.0.50.20200103-git
Branch : master
Head commit: b26a3d5 (Fix ld/PR25316 for the ia64 target by ...)
Impacted : Since GDB 9.0 (does not happen in GDB 8.3.1)
Host OS : Archlinux with kernel 4.19.92-1-lts (x86_64)
Target : aarch64 (this problem can happen to ANY baremetal target)
GDB server : QEMU's GDB stub
Configure : --prefix=/path/to/install \
--target=aarch64-linux-gnu \
--disable-binutils \
--disable-ld \
--disable-gold \
--disable-gas \
--disable-sim \
--disable-grpof \
--disable-werror \
CXXFLAGS='-O0 -g3 -fpermissive -fvar-tracking-assignments' \
CFLAGS='-O0 -g3 -fvar-tracking-assignments'
$$$$$$$$$$$$$$$$$$$$$$$$
$$ Steps to reproduce $$___________________________________________________
$$$$$$$$$$$$$$$$$$$$$$$$
To reproduce the problem, use the attached "tiny_example":
0) Make sure you have aarch64-linux toolchain and qemu-aarch64
You can try ANY other target as long as you adapt "tiny.s"
1) Edit the "config" section of the "makefile" to reflect your settings
2) Execute the following commands in 2 separate terminals
> make stub # spawns qemu listening for gdb
> make debug # runs gdb and attaches to qemu
$$$$$$$$$$$$$$$$$$$$$$$$
$$ Problem (Analysis) $$___________________________________________________
$$$$$$$$$$$$$$$$$$$$$$$$
There is a problem in how GDB's assembly TUI handles baremetal programs
comprise of only a few lines of assembly instructions. This problem leads
to a segmentation fault in GDB. See the attached "gdb-lay-asm-crash.gif"
for an illustration of this issue. However, working in source TUI leads
to no trouble (see "gdb-lay-src-ok.gif").
But, where does this happen? It happens in gdb/tui/tui-disasm.c:
1 tui_disasm_window::addr_is_displayed (...)
2 {
3 ...
4 while (i < content.size () - threshold && !is_displayed)
5 {
6 is_displayed
7 = (content[i].line_or_addr.loa == LOA_ADDRESS
8 ...
9 }
At line 7, "content[i]" is the cause of the crash. "i" is 0 but "content"
has no elements. In other words, "content.size()" returns 0.
At line 4, "threshold" is 2 that leads to an overflow in condition check
of "i < content.size() - threshold". Else, the loop wouldn't be entered.
Why "content.size ()" is 0 you may ask. That is because of this piece of
code again in gdb/tui/tui-disasm.c:
1 tui_disasm_window::set_contents (...) {
2 ...
3 /* Window size, excluding highlight box. */
4 max_lines = height - 2;
5 line_width = width - TUI_EXECINFO_SIZE - 2;
6 /* Get temporary table that will hold all strings (addr & insn). */
7 std::vector<tui_asm_line> asm_lines (max_lines);
8 size_t addr_size = 0;
9 tui_disassemble (gdbarch, asm_lines, pc, 0, max_lines, &addr_size);
10 ...
11 content.resize (max_lines);
12 for (i = 0; i < max_lines; i++) {
13 tui_source_element *src = &content[i];
14 ...
15 }
At line 9, "tui_disassemble()" throws an exception without letting
"content" to be filled at all. This exception is also the reason that the
message "Cannot access memory at address ..." is printed in GDB (see
attached GIF files).
The exception is rooted in gdb/disasm.c:
1 gdb_disassembler::print_insn (CORE_ADDR memaddr, ...) {
2 m_err_memaddr = 0;
3
4 int length = gdbarch_print_insn (arch (), memaddr, &m_di);
5
6 if (length < 0)
7 memory_error (TARGET_XFER_E_IO, m_err_memaddr);
8 ...
9 return length;
10 }
At line 4, "gdbarch_print_insn()" returns -1 which leads to execution of
"memory_error()" at line 7, a.k.a. the infamous exception.
"gdb_print_insn()" returns -1 because it is dealt an invalid PC address
that it cannot fetch. This PC address is _just_ after the last
instruction of the inferior program.
###########################################################################
All of these happens because in "tui_disasm_window::set_contents()", the
variable "max_lines" instructs "tui_disassemble()" to decode more than
it should have.
###########################################################################
Under some circumstances, GDB will ask QEMU again to fetch the invalid
addresses. In this case, QEMU returns a stream of 0's. Although the
output of decoding would be garbage, but GDB won't crash.
$$$$$$$$$$$$$$$
$$ Solution? $$____________________________________________________________
$$$$$$$$$$$$$$$
There are 2 things to tackle here:
1. The overflow occuring in "tui_disasm_window::addr_is_displayed". That
must be easily avoidable by converting "content.size() - threshold" to
a signed result explicitly. I will soon submit this patch:
diff --git a/gdb/tui/tui-disasm.c b/gdb/tui/tui-disasm.c
index c72b50730b0..7a3b32696cd 100644
--- a/gdb/tui/tui-disasm.c
+++ b/gdb/tui/tui-disasm.c
@@ -349,10 +349,10 @@ bool
tui_disasm_window::addr_is_displayed (CORE_ADDR addr) const
{
bool is_displayed = false;
- int threshold = SCROLL_THRESHOLD;
+ int nr_of_lines = int(content.size()) - int(SCROLL_THRESHOLD);
int i = 0;
- while (i < content.size () - threshold && !is_displayed)
+ while (i < nr_of_lines && !is_displayed)
{
is_displayed
= (content[i].line_or_addr.loa == LOA_ADDRESS
2. Calculation of "max_lines" in "tui_disasm_window::set_contents".
Ideally, "max_lines" should be:
max_lines = std::min<int>(height-2, number_of_instructions_in_elf);
However, it's not trivial (to me) how to get the number of instructions
that exist there. Any thought on that?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26095-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 04 18:21:14 2020
Return-Path: <gdb-prs-return-26095-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 91985 invoked by alias); 4 Jan 2020 18:21:14 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 91964 invoked by uid 48); 4 Jan 2020 18:21:14 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25283] ASan errors when using "layout next"
Date: Sat, 04 Jan 2020 18:21: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: 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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution target_milestone
Message-ID: <bug-25283-4717-g4rB8cEGfJ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25283-4717@http.sourceware.org/bugzilla/>
References: <bug-25283-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00010.txt
Content-length: 651
https://sourceware.org/bugzilla/show_bug.cgi?id=25283
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |tromey at sourceware dot org
Resolution|--- |FIXED
Target Milestone|--- |10.1
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
This was fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26096-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 04 19:41:28 2020
Return-Path: <gdb-prs-return-26096-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 14328 invoked by alias); 4 Jan 2020 19:41:28 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 14305 invoked by uid 48); 4 Jan 2020 19:41:27 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/24469] gdb: build for python3 on mingw fails due to api
change
Date: Sat, 04 Jan 2020 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: 8.2
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: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-24469-4717-9MQjjO0DxD@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24469-4717@http.sourceware.org/bugzilla/>
References: <bug-24469-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00011.txt
Content-length: 609
https://sourceware.org/bugzilla/show_bug.cgi?id=24469
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.1
--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
Thanks for pointing that out.
I'm going to close this.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26097-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 04 20:38:11 2020
Return-Path: <gdb-prs-return-26097-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 72530 invoked by alias); 4 Jan 2020 20:38:11 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 72508 invoked by uid 48); 4 Jan 2020 20:38:10 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25342] Unicode data in strings conflicts with TUI
Date: Sat, 04 Jan 2020 20: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: 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: <bug-25342-4717-oobxDIJLm9@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25342-4717@http.sourceware.org/bugzilla/>
References: <bug-25342-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00012.txt
Content-length: 952
https://sourceware.org/bugzilla/show_bug.cgi?id=25342
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-04
CC| |tromey at sourceware dot org
Ever confirmed|0 |1
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I looked into this a little.
Aside from being naive about encodings, the TUI also
has some questionable code like:
else if (c < 040 && c != '\t')
{
result.push_back ('^');
result.push_back (c + 0100);
}
... which fails for UTF-8 because "char" is signed on
some platforms.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26098-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 04 21:08:22 2020
Return-Path: <gdb-prs-return-26098-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 15987 invoked by alias); 4 Jan 2020 21:08:22 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 15967 invoked by uid 48); 4 Jan 2020 21:08:22 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25342] Unicode data in strings conflicts with TUI
Date: Sat, 04 Jan 2020 21:08: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: 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: <bug-25342-4717-zbAmZOhzgU@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25342-4717@http.sourceware.org/bugzilla/>
References: <bug-25342-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00013.txt
Content-length: 418
https://sourceware.org/bugzilla/show_bug.cgi?id=25342
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
Replacing the check with ISCNTRL helped a little but
now the string just displays as grey rectangles.
Also I think a bigger refactoring is needed to avoid
splitting the string in the middle of a character sequence.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26099-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 04 21:46:53 2020
Return-Path: <gdb-prs-return-26099-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 77725 invoked by alias); 4 Jan 2020 21:46:53 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 77706 invoked by uid 48); 4 Jan 2020 21:46:53 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/12535] decode_linespec_1 vagrind errors on ""
Date: Sat, 04 Jan 2020 21: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: 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: <bug-12535-4717-smHOSPJcxT@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-12535-4717@http.sourceware.org/bugzilla/>
References: <bug-12535-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00014.txt
Content-length: 572
https://sourceware.org/bugzilla/show_bug.cgi?id=12535
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
Assignee|unassigned at sourceware dot org |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
Sending a patch.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26100-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 04 22:16:37 2020
Return-Path: <gdb-prs-return-26100-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 122846 invoked by alias); 4 Jan 2020 22:16:37 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 122824 invoked by uid 48); 4 Jan 2020 22:16:37 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/13003] unexpected "No such file or directory" warnings
Date: Sat, 04 Jan 2020 22:16: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: 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: <bug-13003-4717-aQAkzS7IJB@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-13003-4717@http.sourceware.org/bugzilla/>
References: <bug-13003-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00015.txt
Content-length: 592
https://sourceware.org/bugzilla/show_bug.cgi?id=13003
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
No response, it seems to work, and the original report is pretty old;
so I'm closing.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26101-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 04 22:18:50 2020
Return-Path: <gdb-prs-return-26101-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 124288 invoked by alias); 4 Jan 2020 22:18:50 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 124263 invoked by uid 48); 4 Jan 2020 22:18:50 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/22928] SIGSEV on `gdb -tui`
Date: Sat, 04 Jan 2020 22: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.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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-22928-4717-HTmt2vQPdF@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22928-4717@http.sourceware.org/bugzilla/>
References: <bug-22928-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00016.txt
Content-length: 738
https://sourceware.org/bugzilla/show_bug.cgi?id=22928
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |tromey at sourceware dot org
Resolution|--- |FIXED
--- Comment #6 from Tom Tromey <tromey at sourceware dot org> ---
>From the log this seems to be a gentoo-specific bug,
and the gentoo bug is closed. So, I'm closing this one.
Please reopen or comment if this is in error.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26102-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 06 09:26:03 2020
Return-Path: <gdb-prs-return-26102-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 87760 invoked by alias); 6 Jan 2020 09:26:03 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 87742 invoked by uid 48); 6 Jan 2020 09:26:03 -0000
From: "b7.10110111 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25347] New: Make it possible to hide function names in
disassembly
Date: Mon, 06 Jan 2020 09:26: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: 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
attachments.created
Message-ID: <bug-25347-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00017.txt
Content-length: 1533
https://sourceware.org/bugzilla/show_bug.cgi?id=25347
Bug ID: 25347
Summary: Make it possible to hide function names in disassembly
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: tui
Assignee: unassigned at sourceware dot org
Reporter: b7.10110111 at gmail dot com
Target Milestone: ---
Created attachment 12170
--> https://sourceware.org/bugzilla/attachment.cgi?id=12170&action=edit
Screenshot of the problem
Consider the following C++ program:
```
#include <iostream>
#include <boost/units/io.hpp>
#include <boost/units/systems/si.hpp>
using namespace boost::units;
void foo(quantity<si::length> L1)
{
std::cout << L1*L1 << '\n';
}
int main()
{
foo(2.5*si::meters);
}
```
If you compile it with -g and run in GDB as
```
gdb ./test -ex 'b foo' -ex r -ex 'layout asm'
```
you'll get quite a useless disassembly view (see the screenshot attached). Yes,
you can spend 15 seconds holding the Right Arrow key to see the actual
instructions, but
1. on the next jump/call the view will reset its scrolling state, and
2. instruction addresses, being to the left of function names, are invisible
when instructions themselves are visible.
So I'd rather simply hide the function names in disassembly, or maybe show them
as a header, like we get in CLI with `disas` command.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26103-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 06 09:52:32 2020
Return-Path: <gdb-prs-return-26103-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 42947 invoked by alias); 6 Jan 2020 09:52:32 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 42927 invoked by uid 48); 6 Jan 2020 09:52:32 -0000
From: "b7.10110111 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25348] New: Segfault on mode switch from TUI to CLI
Date: Mon, 06 Jan 2020 09:52: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: 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: <bug-25348-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00018.txt
Content-length: 3098
https://sourceware.org/bugzilla/show_bug.cgi?id=25348
Bug ID: 25348
Summary: Segfault on mode switch from TUI to CLI
Product: gdb
Version: HEAD
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, run GDB as, e.g.
gdb -ex 'layout src'
Then press <Ctrl>+<x>, <a> to switch to CLI.
GDB segfaults with the following backtrace. If you issue "layout src" in the
command line instead of -ex command, the crash doesn't happen.
#0 0xf7fa2c69 in __kernel_vsyscall ()
#1 0xf737e592 in __libc_signal_restore_set (set=0xffe0382c) at
../sysdeps/unix/sysv/linux/nptl-signals.h:80
#2 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
#3 0xf737f9b7 in __GI_abort () at abort.c:79
#4 0x081d34cb in handle_sigsegv (sig=11) at event-top.c:884
#5 <signal handler called>
#6 __GI__IO_fwrite (buf=0xa3027f0, size=1, count=6, fp=0x0) at iofwrite.c:37
#7 0xf7f438f9 in _rl_output_some_chars (string=0xa3027f0 "(gdb) ", count=6) at
../terminal.c:647
#8 0xf7f3c93e in update_line (old=old@entry=0x9dd7670 "",
new=new@entry=0xa3027f0 "(gdb) ", current_line=current_line@entry=0, omax=209,
nmax=209, inv_botlin=0) at ../display.c:2082
#9 0xf7f3e6cd in rl_redisplay () at ../display.c:1390
#10 0xf7f28d6d in readline_internal_setup () at ../readline.c:447
#11 0xf7f4263e in _rl_callback_newline () at ../callback.c:100
#12 0xf7f426a1 in rl_callback_handler_install (prompt=0x9e41aec "(gdb) ",
linefunc=0x81d49f0 <gdb_rl_callback_handler(char*)>) at ../callback.c:111
#13 0x081d393e in gdb_rl_callback_handler_install (prompt=<optimized out>) at
event-top.c:320
#14 display_gdb_prompt (new_prompt=<optimized out>) at event-top.c:410
#15 0x081d4376 in command_line_handler (rl=...) at event-top.c:775
#16 0x081d4a65 in gdb_rl_callback_handler (rl=0x9ddb8f0 "") at event-top.c:218
#17 0xf7f42bc2 in rl_callback_read_char () at ../callback.c:281
#18 0x081d3526 in gdb_rl_callback_read_char_wrapper_noexcept () at
event-top.c:176
#19 0x081d493f in gdb_rl_callback_read_char_wrapper (client_data=0x9dd5b40) at
event-top.c:193
#20 0x081d33f1 in stdin_event_handler (error=0, client_data=0x9dd5b40) at
event-top.c:515
#21 0x081d1860 in handle_file_event (file_ptr=0xa20fdd0, ready_mask=<optimized
out>) at event-loop.c:731
#22 0x081d1c85 in gdb_wait_for_event (block=block@entry=1) at event-loop.c:857
#23 0x081d1eb6 in gdb_do_one_event () at event-loop.c:346
#24 0x081d2499 in gdb_do_one_event () at event-loop.c:303
#25 start_event_loop () at event-loop.c:370
#26 0x082ca71e in captured_command_loop () at main.c:360
#27 0x082cbe3d in captured_main (data=<optimized out>) at main.c:1203
#28 gdb_main (args=<optimized out>) at main.c:1218
#29 0x0805cf3c in main (argc=4, argv=0xffe047d4) at gdb.c:32
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26104-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 06 14:10:24 2020
Return-Path: <gdb-prs-return-26104-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 79992 invoked by alias); 6 Jan 2020 14:10:24 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 79441 invoked by uid 48); 6 Jan 2020 14:10:23 -0000
From: "davidpel.dev at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/25312] Segmentation fault and/or other unintended
behaivour when setting 'logging redirect' to 'on', and then using gdb.execute
to set logging 'on' or 'off'
Date: Mon, 06 Jan 2020 14:10: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.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: davidpel.dev 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: <bug-25312-4717-LoFxpjs2Gw@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25312-4717@http.sourceware.org/bugzilla/>
References: <bug-25312-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00019.txt
Content-length: 579
https://sourceware.org/bugzilla/show_bug.cgi?id=25312
David <davidpel.dev at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from David <davidpel.dev at gmail dot com> ---
This is solved in gdb 8.3.
Tried upgrading my gdb and now everything is working fine!
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26105-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 06 19:51:50 2020
Return-Path: <gdb-prs-return-26105-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 85855 invoked by alias); 6 Jan 2020 19:51:50 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 85543 invoked by uid 55); 6 Jan 2020 19:51:50 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] Tiny programs (few lines of assembly) cause GDB's
TUI to crash
Date: Mon, 06 Jan 2020 19:51: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: 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: <bug-25345-4717-UibQ7co7Qy@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25345-4717@http.sourceware.org/bugzilla/>
References: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00020.txt
Content-length: 2137
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Pedro Alves <palves@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=cbfa85811792ca8e96ace40bef0aaaf507e54bcc
commit cbfa85811792ca8e96ace40bef0aaaf507e54bcc
Author: Shahab Vahedi <shahab@synopsys.com>
Date: Mon Jan 6 15:27:32 2020 +0100
GDB: Fix the overflow in addr/line_is_displayed()
In tui_disasm_window::addr_is_displayed(), there can be situations
where "content" is empty. For instance, it can happen when the
"content" was not filled in tui_disasm_window::set_contents(),
because tui_disassemble() threw an exception. Usually this exception
is the result of fetching invalid PC addresses like the ones beyond
the end of the program.
Having "content.size ()" zero leads to an overflow in this condition
check inside tui_disasm_window::addr_is_displayed():
int i = 0;
while (i < content.size () - threshold ...) {
... content[i] ...
}
"threshold" is 2 and there are times that "content.size ()" is 0.
This results into an overflow and the loop is entered whereas it
should have been skipped. Finally, "content[i]" access leads to
a segmentation fault.
Same problem applies to tui_source_window::line_is_displayed().
The issue has been discussed at length in bug 25345:
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
This commit avoids the segmentation faults with an early check:
if (content.size () < SCROLL_THRESHOLD)
return false;
Moreover, those functions have been overhauled to a leaner code.
gdb/ChangeLog:
2020-01-06 Shahab Vahedi <shahab@synopsys.com>
* tui/tui-disasm.c (tui_disasm_window::addr_is_displayed): Avoid
overflow by an early check of content vs threshold.
* tui/tui-source.c (tui_source_window::line_is_displayed):
Likewise.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26106-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 06 20:54:17 2020
Return-Path: <gdb-prs-return-26106-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 118657 invoked by alias); 6 Jan 2020 20:54:17 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 118636 invoked by uid 48); 6 Jan 2020 20:54:16 -0000
From: "wilson at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25318] Aarch64-SIM: BLR opcode does not support XLR
register properly.
Date: Mon, 06 Jan 2020 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: wilson 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: <bug-25318-4717-bpwjkzlNFv@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25318-4717@http.sourceware.org/bugzilla/>
References: <bug-25318-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00021.txt
Content-length: 970
https://sourceware.org/bugzilla/show_bug.cgi?id=25318
Jim Wilson <wilson at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilson at gcc dot gnu.org
--- Comment #2 from Jim Wilson <wilson at gcc dot gnu.org> ---
The aarch64 gdb sim port is incomplete and not actively maintained. If you
need a simulator, you are much better off using qemu which is actively
maintained, unless perhaps you want to volunteer to help finish the aarch64 sim
port. If you do want to work on this, then you need an FSF copyright
assignment. I don't see an obvious one for you on file at the FSF, but maybe
your employer has one?
The patch does look OK to me. Maybe it is small enough and obvious enough to
accept without an assignment?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26107-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 07 02:56:52 2020
Return-Path: <gdb-prs-return-26107-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 107641 invoked by alias); 7 Jan 2020 02:56:52 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 107620 invoked by uid 48); 7 Jan 2020 02:56:52 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25350] New: gdb internal-error with assertion status failed
Date: Tue, 07 Jan 2020 02: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
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: <bug-25350-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00022.txt
Content-length: 2593
https://sourceware.org/bugzilla/show_bug.cgi?id=25350
Bug ID: 25350
Summary: gdb internal-error with assertion status failed
Product: gdb
Version: 8.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
Created attachment 12172
--> https://sourceware.org/bugzilla/attachment.cgi?id=12172&action=edit
the source code for debugging
$ gdb -v
GNU gdb (GDB) 8.3.1
Copyright (C) 2019 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.
$ gcc -g -fsanitize=undefined small.c
$ gdb ./a.out
GNU gdb (GDB) 8.3.1
Copyright (C) 2019 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 "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./a.out...
(gdb) break *eh2+0x7e
Breakpoint 1 at 0x13e2: file small.c, line 38.
(gdb) run
Starting program: /home/yibiao/tgdb/a.out
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Breakpoint 1, 0x00005555555553e2 in eh2 (
frame.c:558: internal-error: frame_id get_frame_id(frame_info*): Assertion
`stashed' 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:
<http://www.gnu.org/software/gdb/bugs/>.
frame.c:558: internal-error: frame_id get_frame_id(frame_info*): Assertion
`stashed' 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] 12493 abort (core dumped) gdb ./a.out
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26108-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 07 16:46:17 2020
Return-Path: <gdb-prs-return-26108-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 14049 invoked by alias); 7 Jan 2020 16:46:17 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 14028 invoked by uid 55); 7 Jan 2020 16:46:17 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/24937] "default initialization of an object of const type
without a user-provided default constructor" is not checked at configure time
Date: Tue, 07 Jan 2020 16:46: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.2.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: tromey at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-24937-4717-VrrluRagAk@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24937-4717@http.sourceware.org/bugzilla/>
References: <bug-24937-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00023.txt
Content-length: 1338
https://sourceware.org/bugzilla/show_bug.cgi?id=24937
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4212d5091457541bd7e7eff0591805ef7b7333e3
commit 4212d5091457541bd7e7eff0591805ef7b7333e3
Author: Tom Tromey <tromey@adacore.com>
Date: Thu Dec 19 11:35:22 2019 -0700
Add constructor to stap_static_probe_ops
PR build/24937 concerns an error given by the clang provided by a
particular version of macOS. In particular, it reports
error: default initialization of an object of const type 'const
stap_static_probe_ops' without a user-provided default constructor
Although (at least according to sources I found online) this was
resolved as a bug in the standard, it seemed simple enough to work
around this.
Given that this is a trivial build fix, I think it should go on the
gdb 9 branch as well.
gdb/ChangeLog
2020-01-07 Tom Tromey <tromey@adacore.com>
PR build/24937:
* stap-probe.c (class stap_static_probe_ops): Add constructor.
Change-Id: I18f180c17850f420e9b66afc67f9cb3d8dceb0b3
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26109-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 07 16:50:08 2020
Return-Path: <gdb-prs-return-26109-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 19493 invoked by alias); 7 Jan 2020 16:50:08 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 19472 invoked by uid 55); 7 Jan 2020 16:50:08 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/24937] "default initialization of an object of const type
without a user-provided default constructor" is not checked at configure time
Date: Tue, 07 Jan 2020 16:50: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.2.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: tromey at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-24937-4717-vWkosk650S@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24937-4717@http.sourceware.org/bugzilla/>
References: <bug-24937-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00024.txt
Content-length: 1328
https://sourceware.org/bugzilla/show_bug.cgi?id=24937
--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The gdb-9-branch branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=3c473fad8f153feee08dce0d79f0b1119a7be2a6
commit 3c473fad8f153feee08dce0d79f0b1119a7be2a6
Author: Tom Tromey <tromey@adacore.com>
Date: Thu Dec 19 11:35:22 2019 -0700
Add constructor to stap_static_probe_ops
PR build/24937 concerns an error given by the clang provided by a
particular version of macOS. In particular, it reports
error: default initialization of an object of const type 'const
stap_static_probe_ops' without a user-provided default constructor
Although (at least according to sources I found online) this was
resolved as a bug in the standard, it seemed simple enough to work
around this.
Given that this is a trivial build fix, I think it should go on the
gdb 9 branch as well.
2020-01-07 Tom Tromey <tromey@adacore.com>
PR build/24937:
* stap-probe.c (class stap_static_probe_ops): Add constructor.
Change-Id: I18f180c17850f420e9b66afc67f9cb3d8dceb0b3
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26110-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 07 16:51:21 2020
Return-Path: <gdb-prs-return-26110-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 20471 invoked by alias); 7 Jan 2020 16:51:21 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 20451 invoked by uid 48); 7 Jan 2020 16:51:20 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/24937] "default initialization of an object of const type
without a user-provided default constructor" is not checked at configure time
Date: Tue, 07 Jan 2020 16: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.2.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: tromey at sourceware dot org
X-Bugzilla-Target-Milestone: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-24937-4717-fZ4Cki0CH5@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24937-4717@http.sourceware.org/bugzilla/>
References: <bug-24937-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00025.txt
Content-length: 602
https://sourceware.org/bugzilla/show_bug.cgi?id=24937
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.1
--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
I worked around this by adding the constructor.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26111-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 07 23:57:40 2020
Return-Path: <gdb-prs-return-26111-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 113253 invoked by alias); 7 Jan 2020 23:57:39 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 113235 invoked by uid 48); 7 Jan 2020 23:57:39 -0000
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/25353] New: Crash on bad location list data
Date: Tue, 07 Jan 2020 23: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: 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: <bug-25353-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00026.txt
Content-length: 4074
https://sourceware.org/bugzilla/show_bug.cgi?id=25353
Bug ID: 25353
Summary: Crash on bad location list data
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: ---
The following Rust program crashes GDB. The problem is that Rust is generating
location list data that is bad: It specifies that a large value is living in a
register (as opposed to living at an address contained in the register). GDB
crashes because it keeps trying to read consecutive registers trying to read
the value (a dodgey thing to begin with) and runs off the end of the array (or
hits an assert failure).
The bad debug info can be seen in the output of readelf -w of course.
There are two failure modes here. One is running off the end of the cache->reg
array. The other is an assert catching the fact that regnum is too large (more
than the number of registers on the arch).
const ARRAY_SIZE: usize = 1024;
struct Foo {
x: [u64; ARRAY_SIZE],
}
fn foo(a: Foo, i: usize) -> u64 {
a.x[i]
}
fn main() {
println!("Hello, world!");
println!("{}", foo(Foo{x: [0; ARRAY_SIZE]}, 42));
}
bash$ cargo build
bash$ gdb target/debug/location-lists
(gdb) b location_lists::foo
(gdb) r
...
Breakpoint 1, location_lists::foo (a=..., i=42) at src/main.rs:8
8 a.x[i]
(gdb) info addr a
Symbol "a" is multi-location:
Range 0x555555558469-0x55555555847f: a complex DWARF expression:
0: DW_OP_breg5 0 [$rdi]
Range 0x55555555847f-0x555555558490: a complex DWARF expression:
0: DW_OP_breg7 8 [$rsp]
2: DW_OP_deref
Range 0x555555558490-0x555555558499: a variable in $rcx
Range 0x555555558499-0x5555555584b0: a complex DWARF expression:
0: DW_OP_breg7 8 [$rsp]
2: DW_OP_deref
Range 0x5555555584b0-0x5555555584b2: a variable in $rsi
Note the range where a lives in $rcx.
Step forward until $pc is in that range:
(gdb) disp/i $pc
(gdb) si
(gdb) si
...
(gdb) si
0x0000555555558490 8 a.x[i]
1: x/i $pc
=> 0x555555558490 <location_lists::foo+48>: mov (%rax,%rcx,8),%rax
(gdb) p &a
/build/work/ae7a9562e88647253b179b920940a9eead3d/google3/third_party/gdb/source/gdb-8.3.x/gdb/regcache.c:620:
internal-error: struct value *readable_regcache::cooked_read_value(int):
Assertion `regnum < m_descr->nr_cooked_registers' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
I haven't been able to repro the other failure mode, running off the end of the
array with a small enough, and publishable, testcase. What happens is we get
here:
dwarf2-frame.c:dwarf2_frame_prev_register:
internal_error (__FILE__, __LINE__, _("Unknown register rule."));
called from here:
findvar.c:read_frame_register_value:
/* Copy the data. */
while (len > 0)
{
struct value *regval = get_frame_register_value (frame, regnum);
int reg_len = type_length_units (value_type (regval)) - reg_offset;
/* If the register length is larger than the number of bytes
remaining to copy, then only copy the appropriate bytes. */
if (reg_len > len)
reg_len = len;
value_contents_copy (value, offset, regval, reg_offset, reg_len);
offset += reg_len;
len -= reg_len;
reg_offset = 0;
regnum++;
}
Note that we keep reading until we have the entire value, regardless of whether
there is enough registers to contain that value (and regardless of whether
regnum++ makes sense to collect the value - maybe it does for all the cases
that actually use it).
I'm not sure where the best place is to watch for this kind of bad debug info.
Ideally during reading of course, just not sure at the moment if the reader
will always have enough info.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26112-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 08 15:43:16 2020
Return-Path: <gdb-prs-return-26112-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 51888 invoked by alias); 8 Jan 2020 15:43:15 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 51867 invoked by uid 48); 8 Jan 2020 15:43:15 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] Tiny programs (few lines of assembly) cause GDB's
TUI to crash
Date: Wed, 08 Jan 2020 15:43: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: shahab.vahedi 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: <bug-25345-4717-TBCdahbRJo@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25345-4717@http.sourceware.org/bugzilla/>
References: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00027.txt
Content-length: 344
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
--- Comment #2 from Shahab <shahab.vahedi at gmail dot com> ---
Created attachment 12175
--> https://sourceware.org/bugzilla/attachment.cgi?id=12175&action=edit
GDB crash after reaching end of line.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26113-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 08 15:43:51 2020
Return-Path: <gdb-prs-return-26113-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 52370 invoked by alias); 8 Jan 2020 15:43:51 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 52352 invoked by uid 48); 8 Jan 2020 15:43:51 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] Tiny programs (few lines of assembly) cause GDB's
TUI to crash
Date: Wed, 08 Jan 2020 15:43: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: shahab.vahedi 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: <bug-25345-4717-zAnKuhSgpz@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25345-4717@http.sourceware.org/bugzilla/>
References: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00028.txt
Content-length: 324
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
--- Comment #3 from Shahab <shahab.vahedi at gmail dot com> ---
Created attachment 12176
--> https://sourceware.org/bugzilla/attachment.cgi?id=12176&action=edit
GDB after the fix
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26114-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 08 15:54:56 2020
Return-Path: <gdb-prs-return-26114-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 116063 invoked by alias); 8 Jan 2020 15:54:56 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 116043 invoked by uid 48); 8 Jan 2020 15:54:56 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] Tiny programs (few lines of assembly) cause GDB's
TUI to crash
Date: Wed, 08 Jan 2020 15:54: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: shahab.vahedi 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: <bug-25345-4717-J3zNCMMFbD@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25345-4717@http.sourceware.org/bugzilla/>
References: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00029.txt
Content-length: 1516
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
--- Comment #4 from Shahab <shahab.vahedi at gmail dot com> ---
The fix for point 1 is in. I also implemented a solution for point 2 as
suggested by Andrew:
diff --git a/gdb/tui/tui-disasm.c b/gdb/tui/tui-disasm.c
index 98c691f3387..7faaa45f039 100644
--- a/gdb/tui/tui-disasm.c
+++ b/gdb/tui/tui-disasm.c
@@ -226,7 +226,18 @@ tui_disasm_window::set_contents (struct gdbarch *arch,
/* Get temporary table that will hold all strings (addr & insn). */
std::vector<tui_asm_line> asm_lines (max_lines);
size_t addr_size = 0;
- tui_disassemble (gdbarch, asm_lines, pc, 0, max_lines, &addr_size);
+ try
+ {
+ tui_disassemble (gdbarch, asm_lines, pc, 0, max_lines, &addr_size);
+ }
+ catch (const gdb_exception &except)
+ {
+ /* In cases where max_lines is asking tui_disassemble() to fetch
+ too much, like when PC goes past the valid address range, a
+ MEMORY_ERROR is thrown, but it is alright. */
+ if (except.error != MEMORY_ERROR)
+ throw;
+ }
/* Align instructions to the same column. */
insn_pos = (1 + (addr_size / tab_len)) * tab_len;
It does work (see attachments: "GDB crash after reaching end of line" vs "GDB
after the fix"). However, it moves on to another issue. GDB terminates when it
reaches a state where there is no valid line in TUI anymore (as "GDB after the
fix" illustrates).
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26115-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 08 16:08:10 2020
Return-Path: <gdb-prs-return-26115-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 21473 invoked by alias); 8 Jan 2020 16:08:10 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 21454 invoked by uid 48); 8 Jan 2020 16:08:10 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25347] Make it possible to hide function names in
disassembly
Date: Wed, 08 Jan 2020 16:08: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: 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: <bug-25347-4717-IBzIKKCkKs@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25347-4717@http.sourceware.org/bugzilla/>
References: <bug-25347-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00030.txt
Content-length: 662
https://sourceware.org/bugzilla/show_bug.cgi?id=25347
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-08
CC| |tromey at sourceware dot org
Ever confirmed|0 |1
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
Seems like a good idea to me.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26116-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 08 16:23:03 2020
Return-Path: <gdb-prs-return-26116-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 89481 invoked by alias); 8 Jan 2020 16:23:03 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 89463 invoked by uid 48); 8 Jan 2020 16:23:03 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] Tiny programs (few lines of assembly) cause GDB's
TUI to crash
Date: Wed, 08 Jan 2020 16:23: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: shahab.vahedi 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: <bug-25345-4717-mbLAjXmZX8@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25345-4717@http.sourceware.org/bugzilla/>
References: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00031.txt
Content-length: 273
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
--- Comment #5 from Shahab <shahab.vahedi at gmail dot com> ---
seems related to https://sourceware.org/bugzilla/show_bug.cgi?id=9765
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26117-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 09 08:58:23 2020
Return-Path: <gdb-prs-return-26117-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 74176 invoked by alias); 9 Jan 2020 08:58:23 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 74149 invoked by uid 48); 9 Jan 2020 08:58:23 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/9765] Scrolling to end of program in asm layout is broken
Date: Thu, 09 Jan 2020 08:58: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: shahab.vahedi at gmail 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: cc
Message-ID: <bug-9765-4717-qI4QIUVkhN@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-9765-4717@http.sourceware.org/bugzilla/>
References: <bug-9765-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00032.txt
Content-length: 552
https://sourceware.org/bugzilla/show_bug.cgi?id=9765
Shahab <shahab.vahedi at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |shahab.vahedi at gmail dot com
--- Comment #10 from Shahab <shahab.vahedi at gmail dot com> ---
a work-in-progress patch:
https://sourceware.org/ml/gdb-patches/2020-01/msg00179.html
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26118-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 09 11:47:26 2020
Return-Path: <gdb-prs-return-26118-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 11074 invoked by alias); 9 Jan 2020 11:47:25 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 11050 invoked by uid 48); 9 Jan 2020 11:47:25 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] Tiny programs (few lines of assembly) cause GDB's
TUI to crash
Date: Thu, 09 Jan 2020 11: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: shahab.vahedi 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: <bug-25345-4717-vGyPY9lJOV@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25345-4717@http.sourceware.org/bugzilla/>
References: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00033.txt
Content-length: 1554
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
--- Comment #6 from Shahab <shahab.vahedi at gmail dot com> ---
Created attachment 12178
--> https://sourceware.org/bugzilla/attachment.cgi?id=12178&action=edit
Fix 2: no highlights, no crash.
This fix comes from the following changes:
diff --git a/gdb/tui/tui-disasm.c b/gdb/tui/tui-disasm.c
index 98c691f3387..3dfe70bc480 100644
--- a/gdb/tui/tui-disasm.c
+++ b/gdb/tui/tui-disasm.c
@@ -114,7 +114,18 @@ tui_disassemble (struct gdbarch *gdbarch,
asm_lines[pos + i].addr_size = new_size;
}
- pc = pc + gdb_print_insn (gdbarch, pc, &gdb_dis_out, NULL);
+ try
+ {
+ pc = pc + gdb_print_insn (gdbarch, pc, &gdb_dis_out, NULL);
+ }
+ catch (const gdb_exception &except)
+ {
+ /* In cases where max_lines is asking tui_disassemble() to fetch
+ too much, like when PC goes past the valid address range, a
+ MEMORY_ERROR is thrown, but it is alright. */
+ if (except.error != MEMORY_ERROR)
+ throw;
+ }
asm_lines[pos + i].insn = std::move (gdb_dis_out.string ());
It does not highlight the empty lines anymore or crash when goes one window
beyond the last instructions. Moreover, going to the top is fine too.
The only downside is that last invalid address (the address just after the
_last_ valid address) is repeated. If I try to remove it, the highlight issue
comes back.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26119-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 09 23:18:12 2020
Return-Path: <gdb-prs-return-26119-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 39455 invoked by alias); 9 Jan 2020 23:18:12 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 39432 invoked by uid 55); 9 Jan 2020 23:18:12 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/18932] list command doesn't work in TUI any more
Date: Thu, 09 Jan 2020 23: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: 7.10
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: tromey at sourceware dot org
X-Bugzilla-Target-Milestone: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-18932-4717-7IKSHrNH79@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-18932-4717@http.sourceware.org/bugzilla/>
References: <bug-18932-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00034.txt
Content-length: 1735
https://sourceware.org/bugzilla/show_bug.cgi?id=18932
--- Comment #13 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9ae6bf640dc7c950e6f36097a3d2d760a132a542
commit 9ae6bf640dc7c950e6f36097a3d2d760a132a542
Author: Tom Tromey <tom@tromey.com>
Date: Sun Dec 22 16:52:56 2019 -0700
gdb: Fix scrolling in TUI
Hannes Domani pointed out that my previous patch to fix the "list"
command in the TUI instead broke vertical scrolling. While looking at
this, I found that do_scroll_vertical calls print_source_lines, which
seems like a very roundabout way to change the source window. This
patch removes this oddity and fixes the bug at the same time.
I've added a new test case. This is somewhat tricky, because the
obvious approach of sending a dummy command after the scroll did not
work -- due to how the TUI works, sennding a command causes the scroll
to take effect.
gdb/ChangeLog
2019-12-22 Tom Tromey <tom@tromey.com>
PR tui/18932:
* tui/tui-source.c (tui_source_window::do_scroll_vertical): Call
update_source_window, not print_source_lines.
gdb/testsuite/ChangeLog
2019-12-22 Tom Tromey <tom@tromey.com>
PR tui/18932:
* lib/tuiterm.exp (Term::wait_for): Rename from _accept. Return a
meangingful value.
(Term::command, Term::resize): Update.
* gdb.tui/basic.exp: Add scrolling test.
Change-Id: I9636a7c8a8cade37431c6165ee996a9d556ef1c8
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26120-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 10 09:35:15 2020
Return-Path: <gdb-prs-return-26120-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 21335 invoked by alias); 10 Jan 2020 09:35:14 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 21275 invoked by uid 48); 10 Jan 2020 09:35:14 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25359] New: local function is not showed when examing
memory for its instructions
Date: Fri, 10 Jan 2020 09: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25359-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00035.txt
Content-length: 2988
https://sourceware.org/bugzilla/show_bug.cgi?id=25359
Bug ID: 25359
Summary: local function is not showed when examing memory for
its instructions
Product: gdb
Version: 8.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
$ gdb --version
GNU gdb (GDB) 8.3.1
Copyright (C) 2019 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.
$ cat small.c
f (void (*func) ())
{
func ();
}
main ()
{
void t0 () {}
void t1 () { f (t0); }
t1 ();
}
$ gcc -g small.c
$ $ gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) break *f+0x15
Breakpoint 1 at 0x114e: file small.c, line 3.
(gdb) run
Starting program: /home/yibiao/tgdb/a.out
Breakpoint 1, 0x000055555555514e in f (func=0x7fffffffde70) at small.c:3
3 func ();
(gdb) x/i $pc
=> 0x55555555514e <f+21>: callq *%rdx
(gdb) stepi
0x00007fffffffde70 in ?? ()
(gdb) x/i $pc
=> 0x7fffffffde70: movabs $0x555555555153,%r11
(gdb) disas f
Dump of assembler code for function f:
0x0000555555555139 <+0>: push %rbp
0x000055555555513a <+1>: mov %rsp,%rbp
0x000055555555513d <+4>: sub $0x10,%rsp
0x0000555555555141 <+8>: mov %rdi,-0x8(%rbp)
0x0000555555555145 <+12>: mov -0x8(%rbp),%rdx
0x0000555555555149 <+16>: mov $0x0,%eax
0x000055555555514e <+21>: callq *%rdx
0x0000555555555150 <+23>: nop
0x0000555555555151 <+24>: leaveq
0x0000555555555152 <+25>: retq
End of assembler dump.
#######################################################
Here, function "t0" is defined inside the main function. when ``stepi`` to this
function, it is in "??". When examining the memory address, it does not show
which function the corresponding instruction belongs to.
When function "t0" defined outside the main function, gdb can successfully
examining the memory as follows:
#######################################################
$ cat small2.c
f (void (*func) ())
{
func ();
}
void t0 () {}
main ()
{
void t1 () { f (t0); }
t1 ();
}
$ gcc -g small2.c -o a2.out
$ gdb -q ./a2.out
Reading symbols from ./a2.out...
(gdb) break *f+0x15
Breakpoint 1 at 0x114e: file small.c, line 3.
(gdb) run
Starting program: /home/yibiao/tgdb/a.out
Breakpoint 1, 0x000055555555514e in f (func=0x555555555153 <t0>) at small.c:3
3 func ();
(gdb) x/i $pc
=> 0x55555555514e <f+21>: callq *%rdx
(gdb) stepi
t0 () at small.c:6
6 void t0 () {}
(gdb) x/i $pc
=> 0x555555555153 <t0>: push %rbp
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26121-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 10 15:30:06 2020
Return-Path: <gdb-prs-return-26121-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 36204 invoked by alias); 10 Jan 2020 15:30:04 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 36111 invoked by uid 48); 10 Jan 2020 15:30:02 -0000
From: "b7.10110111 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25348] Segfault on mode switch from TUI to CLI
Date: Fri, 10 Jan 2020 15:30: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: 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: <bug-25348-4717-d2J8IDCxh2@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25348-4717@http.sourceware.org/bugzilla/>
References: <bug-25348-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00036.txt
Content-length: 280
https://sourceware.org/bugzilla/show_bug.cgi?id=25348
--- Comment #1 from Ruslan <b7.10110111 at gmail dot com> ---
This didn't happen on GDB 8.3.50.20190827-git, but does on
10.0.50.20200110-git.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26122-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 10 20:10:09 2020
Return-Path: <gdb-prs-return-26122-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 13768 invoked by alias); 10 Jan 2020 20:10:08 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 13742 invoked by uid 55); 10 Jan 2020 20:10:08 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18050] gdb crash on target remote, w/ two inferiors,
current inferior is live
Date: Fri, 10 Jan 2020 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: 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: <bug-18050-4717-COMstwxGUV@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-18050-4717@http.sourceware.org/bugzilla/>
References: <bug-18050-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00037.txt
Content-length: 4041
https://sourceware.org/bugzilla/show_bug.cgi?id=18050
--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Pedro Alves <palves@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=78f2c40a12179d26d3065c09f054b7e751b2732f
commit 78f2c40a12179d26d3065c09f054b7e751b2732f
Author: Pedro Alves <palves@redhat.com>
Date: Fri Jan 10 20:05:53 2020 +0000
Fix reconnecting to a gdbserver already debugging multiple processes, I
The multi-target patch will change the remote target's behavior when:
- the current inferior is connected to an extended-remote target.
- the current inferior is attached to any process.
- some other inferior than than the current one is live.
In current master, we get:
(gdb) tar extended-remote :9999
A program is being debugged already. Kill it? (y or n)
While after multi-target, since each inferior may have its own target
connection, we'll get:
(gdb) tar extended-remote :9999
Already connected to a remote target. Disconnect? (y or n)
That change made gdb.server/extended-remote-restart.exp expose a gdb
bug, because it made "target remote", via gdb_reconnect, just
disconnect from the previous connection, while in current master that
command would kill the inferior before disconnecting. In turn, that
would make a multi-target gdb find processes already running under
control of gdbserver as soon as it reconnects, while in current master
there is never any process around when gdb reconnects, since they'd
all been killed prior to disconnection.
The bug this exposed is that remote_target::remote_add_inferior was
always reusing current_inferior() for the new process, even if the
current inferior was already bound to a process. In the testcase's
case, when we reconnect, the remote is debugging two processes. So
we'd bind the first remote process to the empty current inferior the
first time, and then bind the second remote process to the same
inferior again, essencially losing track of the first process. That
resulted in failed assertions when we look up the inferior for the
first process by PID. The fix is to still prefer binding to the
current inferior (so that plain "target remote" keeps doing what you'd
expect), but not reuse the current inferior if it is already bound to
a process.
This patch tweaks the test to explicitly disconnect before
reconnecting, to avoid GDB killing processes, thus making current GDB
behave the same as it will behave when the multi-target work lands.
That change alone without the GDB fix exposes the bug like so:
(gdb) PASS: gdb.server/extended-remote-restart.exp: kill: 0, follow-child
0: disconnect
target extended-remote localhost:2350
Remote debugging using localhost:2350
src/gdb/thread.c:93: 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)
The original bug that the testcase was written for was related to
killing, (git 9d4a934ce604 ("gdb: Fix assert for extended-remote
target (PR gdb/18050)")), but since the testcase tries reconnecting
with both explicitly killing and not explicitly killing, I think we're
covering the original bug with this testcase change.
gdb/ChangeLog:
2020-01-10 Pedro Alves <palves@redhat.com>
* remote.c (remote_target::remote_add_inferior): Don't bind a
process to the current inferior if the current inferior is already
bound to a process.
gdb/testsuite/ChangeLog:
2020-01-10 Pedro Alves <palves@redhat.com>
* gdb.server/extended-remote-restart.exp (test_reload): Explicitly
disconnect before reconnecting.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26123-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 11 01:03:43 2020
Return-Path: <gdb-prs-return-26123-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 93227 invoked by alias); 11 Jan 2020 01:03:42 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 93202 invoked by uid 48); 11 Jan 2020 01:03:42 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25348] Segfault on mode switch from TUI to CLI
Date: Sat, 11 Jan 2020 01: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-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: <bug-25348-4717-ISndmgN6qI@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25348-4717@http.sourceware.org/bugzilla/>
References: <bug-25348-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00038.txt
Content-length: 655
https://sourceware.org/bugzilla/show_bug.cgi?id=25348
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-11
CC| |simark at simark dot ca
Ever confirmed|0 |1
--- Comment #2 from Simon Marchi <simark at simark dot ca> ---
I was able to reproduce this crash.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26124-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 11 01:06:21 2020
Return-Path: <gdb-prs-return-26124-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 94888 invoked by alias); 11 Jan 2020 01:06:21 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 94869 invoked by uid 48); 11 Jan 2020 01:06:21 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/18932] list command doesn't work in TUI any more
Date: Sat, 11 Jan 2020 01: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: 7.10
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: tromey at sourceware dot org
X-Bugzilla-Target-Milestone: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-18932-4717-vBvDAMXx4b@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-18932-4717@http.sourceware.org/bugzilla/>
References: <bug-18932-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00039.txt
Content-length: 476
https://sourceware.org/bugzilla/show_bug.cgi?id=18932
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simark at simark dot ca
--- Comment #14 from Simon Marchi <simark at simark dot ca> ---
Can this be closed?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26125-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 11 01:53:53 2020
Return-Path: <gdb-prs-return-26125-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 15880 invoked by alias); 11 Jan 2020 01:53:53 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 15861 invoked by uid 48); 11 Jan 2020 01:53:53 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/18932] list command doesn't work in TUI any more
Date: Sat, 11 Jan 2020 01:53: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.10
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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-18932-4717-EQKX6oelvI@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-18932-4717@http.sourceware.org/bugzilla/>
References: <bug-18932-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00040.txt
Content-length: 507
https://sourceware.org/bugzilla/show_bug.cgi?id=18932
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #15 from Tom Tromey <tromey at sourceware dot org> ---
Yep!
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26126-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 14 13:19:37 2020
Return-Path: <gdb-prs-return-26126-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 63559 invoked by alias); 14 Jan 2020 13:19:37 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 63524 invoked by uid 48); 14 Jan 2020 13:19:35 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] Tiny programs (few lines of assembly) cause GDB's
TUI to crash
Date: Tue, 14 Jan 2020 13: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: shahab.vahedi 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: <bug-25345-4717-bVC9XBMjiY@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25345-4717@http.sourceware.org/bugzilla/>
References: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00041.txt
Content-length: 279
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
--- Comment #7 from Shahab <shahab.vahedi at gmail dot com> ---
another attempt:
https://sourceware.org/ml/gdb-patches/2020-01/msg00354.html
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26127-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 14 13:34:57 2020
Return-Path: <gdb-prs-return-26127-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 18167 invoked by alias); 14 Jan 2020 13:34:57 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 18147 invoked by uid 48); 14 Jan 2020 13:34:57 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] Tiny programs (few lines of assembly) cause GDB's
TUI to crash
Date: Tue, 14 Jan 2020 13:34: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: shahab.vahedi 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: <bug-25345-4717-ZcGXthdAVq@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25345-4717@http.sourceware.org/bugzilla/>
References: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00042.txt
Content-length: 348
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
--- Comment #8 from Shahab <shahab.vahedi at gmail dot com> ---
Created attachment 12199
--> https://sourceware.org/bugzilla/attachment.cgi?id=12199&action=edit
A simple x86_64 program to open under GDB
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26128-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 14 13:36:38 2020
Return-Path: <gdb-prs-return-26128-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 36053 invoked by alias); 14 Jan 2020 13:36:37 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 36031 invoked by uid 48); 14 Jan 2020 13:36:37 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] Tiny programs (few lines of assembly) cause GDB's
TUI to crash
Date: Tue, 14 Jan 2020 13:36: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: shahab.vahedi 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: <bug-25345-4717-OTvMUXNS2C@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25345-4717@http.sourceware.org/bugzilla/>
References: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00043.txt
Content-length: 337
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
--- Comment #9 from Shahab <shahab.vahedi at gmail dot com> ---
Created attachment 12200
--> https://sourceware.org/bugzilla/attachment.cgi?id=12200&action=edit
Going up when in garbage bytes
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26129-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 14 13:39:24 2020
Return-Path: <gdb-prs-return-26129-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 56594 invoked by alias); 14 Jan 2020 13:39:23 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 56576 invoked by uid 48); 14 Jan 2020 13:39:23 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] Tiny programs (few lines of assembly) cause GDB's
TUI to crash
Date: Tue, 14 Jan 2020 13: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: shahab.vahedi 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: <bug-25345-4717-d9D4depw8t@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25345-4717@http.sourceware.org/bugzilla/>
References: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00044.txt
Content-length: 337
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
--- Comment #10 from Shahab <shahab.vahedi at gmail dot com> ---
Created attachment 12201
--> https://sourceware.org/bugzilla/attachment.cgi?id=12201&action=edit
Using PageUp when reached EOF
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26130-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 14 13:40:57 2020
Return-Path: <gdb-prs-return-26130-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 61630 invoked by alias); 14 Jan 2020 13:40:56 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 61538 invoked by uid 48); 14 Jan 2020 13:40:56 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] Tiny programs (few lines of assembly) cause GDB's
TUI to crash
Date: Tue, 14 Jan 2020 13: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: shahab.vahedi 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: <bug-25345-4717-Yv9reuuL5J@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25345-4717@http.sourceware.org/bugzilla/>
References: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00045.txt
Content-length: 333
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
--- Comment #11 from Shahab <shahab.vahedi at gmail dot com> ---
Created attachment 12202
--> https://sourceware.org/bugzilla/attachment.cgi?id=12202&action=edit
ArrowUp near the begining
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26131-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 14 17:03:10 2020
Return-Path: <gdb-prs-return-26131-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 114487 invoked by alias); 14 Jan 2020 17:03:10 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 114425 invoked by uid 48); 14 Jan 2020 17:03:10 -0000
From: "bugzilla at myosotissp dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/22748] crash from custom unwinder
Date: Tue, 14 Jan 2020 17: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: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugzilla at myosotissp 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: <bug-22748-4717-VMRzd43qkQ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22748-4717@http.sourceware.org/bugzilla/>
References: <bug-22748-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00046.txt
Content-length: 592
https://sourceware.org/bugzilla/show_bug.cgi?id=22748
Mark <bugzilla at myosotissp dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugzilla at myosotissp dot com
--- Comment #6 from Mark <bugzilla at myosotissp dot com> ---
Created attachment 12206
--> https://sourceware.org/bugzilla/attachment.cgi?id=12206&action=edit
Fix for fi->level assert
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26133-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 14 17:04:45 2020
Return-Path: <gdb-prs-return-26133-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 118575 invoked by alias); 14 Jan 2020 17:04:45 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 118556 invoked by uid 48); 14 Jan 2020 17:04:44 -0000
From: "bugzilla at myosotissp dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/22748] crash from custom unwinder
Date: Tue, 14 Jan 2020 17: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: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugzilla at myosotissp 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: <bug-22748-4717-DYK8YorqqP@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22748-4717@http.sourceware.org/bugzilla/>
References: <bug-22748-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00048.txt
Content-length: 342
https://sourceware.org/bugzilla/show_bug.cgi?id=22748
--- Comment #8 from Mark <bugzilla at myosotissp dot com> ---
Created attachment 12208
--> https://sourceware.org/bugzilla/attachment.cgi?id=12208&action=edit
python unwinder to help repro the bug
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26132-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 14 17:04:12 2020
Return-Path: <gdb-prs-return-26132-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 118042 invoked by alias); 14 Jan 2020 17:04:12 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 118024 invoked by uid 48); 14 Jan 2020 17:04:12 -0000
From: "bugzilla at myosotissp dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/22748] crash from custom unwinder
Date: Tue, 14 Jan 2020 17: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: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugzilla at myosotissp 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: <bug-22748-4717-RLGJmggwOo@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22748-4717@http.sourceware.org/bugzilla/>
References: <bug-22748-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00047.txt
Content-length: 335
https://sourceware.org/bugzilla/show_bug.cgi?id=22748
--- Comment #7 from Mark <bugzilla at myosotissp dot com> ---
Created attachment 12207
--> https://sourceware.org/bugzilla/attachment.cgi?id=12207&action=edit
c++ file to help repro the bug
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26134-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 14 17:08:11 2020
Return-Path: <gdb-prs-return-26134-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 126249 invoked by alias); 14 Jan 2020 17:08:11 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 126224 invoked by uid 48); 14 Jan 2020 17:08:09 -0000
From: "bugzilla at myosotissp dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/22748] crash from custom unwinder
Date: Tue, 14 Jan 2020 17:08: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: bugzilla at myosotissp 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: <bug-22748-4717-OGcwAbA83o@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22748-4717@http.sourceware.org/bugzilla/>
References: <bug-22748-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00049.txt
Content-length: 1773
https://sourceware.org/bugzilla/show_bug.cgi?id=22748
--- Comment #9 from Mark <bugzilla at myosotissp dot com> ---
The bug happens because inline frames don't get a frame id until their caller
does, but value_of_register_lazy needs a frame id so that value_fetch_lazy can
find the frame again.
But there's no need to do things lazily, so we can just fetch the value
directly, bypassing the need for a frame id.
To repro the bug:
% g++ -O2 bug.cpp -o bug -g2
% gdb -ex "source bug.py" -ex "b printf" -ex run -ex bt bug
GNU gdb (GDB) 10.0.50.20200114-git
Copyright (C) 2020 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 "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from bug...
Breakpoint 1 at 0x400420
Starting program: /data/users/mwilliams/hphp-7/fbcode/foobar/bug
Breakpoint 1, 0x00007ffff7242290 in printf () from /lib64/libc.so.6
../../gdb/frame.c:579: internal-error: frame_id get_frame_id(frame_info*):
Assertion `fi->level == 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26135-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 14 18:17:28 2020
Return-Path: <gdb-prs-return-26135-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 11745 invoked by alias); 14 Jan 2020 18:17:28 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 11725 invoked by uid 48); 14 Jan 2020 18:17:27 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug win32/25302] Mismatching fstat() function calls in
gdb_bfd_open() and cache_bstat()
Date: Tue, 14 Jan 2020 18:17: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: 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 cc assigned_to
everconfirmed
Message-ID: <bug-25302-4717-yOk1jRur0a@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25302-4717@http.sourceware.org/bugzilla/>
References: <bug-25302-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00050.txt
Content-length: 740
https://sourceware.org/bugzilla/show_bug.cgi?id=25302
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-14
CC| |tromey at sourceware dot org
Assignee|unassigned at sourceware dot org |tromey at sourceware dot org
Ever confirmed|0 |1
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I'm testing a patch.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26136-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 14 21:11:18 2020
Return-Path: <gdb-prs-return-26136-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 4306 invoked by alias); 14 Jan 2020 21:11:18 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 4285 invoked by uid 48); 14 Jan 2020 21:11:17 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug win32/25302] Mismatching fstat() function calls in
gdb_bfd_open() and cache_bstat()
Date: Tue, 14 Jan 2020 21:11: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: 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: <bug-25302-4717-6Iv1CtBsJf@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25302-4717@http.sourceware.org/bugzilla/>
References: <bug-25302-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00051.txt
Content-length: 263
https://sourceware.org/bugzilla/show_bug.cgi?id=25302
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
https://sourceware.org/ml/gdb-patches/2020-01/msg00386.html
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26137-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 15 00:58:39 2020
Return-Path: <gdb-prs-return-26137-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 40955 invoked by alias); 15 Jan 2020 00:58:39 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 40934 invoked by uid 55); 15 Jan 2020 00:58:39 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/12535] decode_linespec_1 vagrind errors on ""
Date: Wed, 15 Jan 2020 00:58: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: 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: <bug-12535-4717-YZgBBOC6Pc@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-12535-4717@http.sourceware.org/bugzilla/>
References: <bug-12535-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00052.txt
Content-length: 1280
https://sourceware.org/bugzilla/show_bug.cgi?id=12535
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ff47f4f06d296b672337e2c7363a745cd2725f58
commit ff47f4f06d296b672337e2c7363a745cd2725f58
Author: Tom Tromey <tom@tromey.com>
Date: Sat Dec 21 09:51:05 2019 -0700
Fix valgrind error from gdb.decode_line
PR symtab/12535 points out that gdb.decode_line("") will cause a
valgrind report.
I think the empty linespec does not really make sense. So, this patch
changes gdb.decode_line to treat a whitespace-only linespec the same
as a non-existing argument.
gdb/ChangeLog
2020-01-14 Tom Tromey <tom@tromey.com>
PR symtab/12535:
* python/python.c (gdbpy_decode_line): Treat empty string the same
as no argument.
gdb/testsuite/ChangeLog
2020-01-14 Tom Tromey <tom@tromey.com>
PR symtab/12535:
* gdb.python/python.exp: Test decode_line with empty string
argument.
Change-Id: I1d95812b4b7a21d69a3e9afd05b9e3141a931897
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26138-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 15 00:59:06 2020
Return-Path: <gdb-prs-return-26138-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 41471 invoked by alias); 15 Jan 2020 00:59:06 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 41450 invoked by uid 48); 15 Jan 2020 00:59:05 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/12535] decode_linespec_1 vagrind errors on ""
Date: Wed, 15 Jan 2020 00:59: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: 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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-12535-4717-ehYRpZLriY@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-12535-4717@http.sourceware.org/bugzilla/>
References: <bug-12535-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00053.txt
Content-length: 562
https://sourceware.org/bugzilla/show_bug.cgi?id=12535
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.1
--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
Fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26139-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 15 05:31:22 2020
Return-Path: <gdb-prs-return-26139-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 122645 invoked by alias); 15 Jan 2020 05:31:22 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 122621 invoked by uid 48); 15 Jan 2020 05:31:21 -0000
From: "lockywolf at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/25388] New: Leaving the python-interactive pyton
interpreter without EOF
Date: Wed, 15 Jan 2020 05:31: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: lockywolf 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: <bug-25388-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00054.txt
Content-length: 1035
https://sourceware.org/bugzilla/show_bug.cgi?id=25388
Bug ID: 25388
Summary: Leaving the python-interactive pyton interpreter
without EOF
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: python
Assignee: unassigned at sourceware dot org
Reporter: lockywolf at gmail dot com
Target Milestone: ---
In a running gdb session it is possible to enter a python REPL by typing
python-interactive or pi.
If you type quit in the new prompt, the interpreter responds:
>>> quit
Use quit() or Ctrl-D (i.e. EOF) to exit
Ctrl-D indeed leaves the python interpreter and returns you to the gdb
interpreter.
However, quit() leaves the whole gdb. If this is intended, then I would ask to
correct the message. If this is not intended, then please, could you make
quit() return to the gdb prompt?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26140-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 15 12:59:03 2020
Return-Path: <gdb-prs-return-26140-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 9625 invoked by alias); 15 Jan 2020 12:59:03 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 9601 invoked by uid 48); 15 Jan 2020 12:59:03 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/25390] New: Segmentation fault when setting
breakpoint at a valid address
Date: Wed, 15 Jan 2020 12:59: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25390-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00055.txt
Content-length: 2307
https://sourceware.org/bugzilla/show_bug.cgi?id=25390
Bug ID: 25390
Summary: Segmentation fault when setting breakpoint at a valid
address
Product: gdb
Version: 8.3.1
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: breakpoints
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
$ cat small.c
__attribute__((target_clones("arch=core-avx2","arch=slm","default")))
void foo (float *a, int b) {
*a = (float)b;
}
float a;
int main() {
int i;
for (i = 0; i < 1024; i++)
foo (&a, 5);
}
$ gdb -version
GNU gdb (GDB) 8.3.1
Copyright (C) 2019 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.
$ gcc -g -fsanitize=undefined small.c
$ gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) break *get_available_features+0x171
Breakpoint 1 at 0x11d1
(gdb) run
Starting program: /home/yibiao/tgdb/a.out
Breakpoint 1, 0x00005555555551d1 in get_available_features ()
(gdb) c
Continuing.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
/usr/lib/../lib/../share/gcc-9.2.0/python/libstdcxx/v6/xmethods.py:731:
SyntaxWarning: list indices must be integers or slices, not str; perhaps you
missed a comma?
refcounts = ['_M_refcount']['_M_pi']
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff70f2294 in get_available_features (ecx=<optimized out>,
edx=<optimized out>, max_cpuid_level=22)
at /build/gcc/src/gcc/libgcc/config/i386/cpuinfo.c:409
409 /build/gcc/src/gcc/libgcc/config/i386/cpuinfo.c: No such file or
directory.
======================================
when we set breakpoint at valid address with "break
*get_available_features+0x171"
the program is crashed with segmentation fault.
When directly run the program, no segmentation fault occurred.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26141-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 15 12:59:45 2020
Return-Path: <gdb-prs-return-26141-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 10252 invoked by alias); 15 Jan 2020 12:59:45 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 10226 invoked by uid 48); 15 Jan 2020 12:59:45 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/25390] Segmentation fault when setting breakpoint
on valid address
Date: Wed, 15 Jan 2020 12:59: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: <bug-25390-4717-Dgt6ZFrWyb@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25390-4717@http.sourceware.org/bugzilla/>
References: <bug-25390-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00056.txt
Content-length: 611
https://sourceware.org/bugzilla/show_bug.cgi?id=25390
Yibiao Yang <yangyibiao at hust dot edu.cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yangyibiao at hust dot edu.cn
Summary|Segmentation fault when |Segmentation fault when
|setting breakpoint at a |setting breakpoint on valid
|valid address |address
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26142-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 15 20:54:29 2020
Return-Path: <gdb-prs-return-26142-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 39235 invoked by alias); 15 Jan 2020 20:54:28 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 39212 invoked by uid 48); 15 Jan 2020 20:54:28 -0000
From: "chorig9 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/25393] New: Gdb shows value of variable with local scope
before place of initialization
Date: Wed, 15 Jan 2020 20:54: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.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: chorig9 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: <bug-25393-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00057.txt
Content-length: 1383
https://sourceware.org/bugzilla/show_bug.cgi?id=25393
Bug ID: 25393
Summary: Gdb shows value of variable with local scope before
place of initialization
Product: gdb
Version: 8.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
Assignee: unassigned at sourceware dot org
Reporter: chorig9 at gmail dot com
Target Milestone: ---
Consider the following code:
int main()
{
{
int a[1] = {0};
{
int b = a[0] + 1;
int a[1];
a[0] = 1;
b += a[0];
}
}
return 0;
}
When compiled with g++ (7.4) or clang++ (6.0) with '-g' flag and run under gdb
with following commands:
break 4
run
p &a[0]
n
p &a[0]
I get the following output (for reading address of a):
$1 = (int *) 0x7ffffffee058
$2 = (int *) 0x7ffffffee050
It looks like gdb uses new local variable 'a' as soon as we go into scope where
this second variable is defined. Is this expected behavior? C++ standard
explicitly states that lifetime of a variable begins at the point of
declaration (not beginning of the scope).
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26143-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 15 21:07:12 2020
Return-Path: <gdb-prs-return-26143-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 76008 invoked by alias); 15 Jan 2020 21:07:12 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 75989 invoked by uid 48); 15 Jan 2020 21:07:12 -0000
From: "chorig9 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/25393] Gdb assumes that local variable begins its life at
the begginig of a scope (instead of at a place of initialization)
Date: Wed, 15 Jan 2020 21: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: 8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: chorig9 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: <bug-25393-4717-g9sOwVZsxZ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25393-4717@http.sourceware.org/bugzilla/>
References: <bug-25393-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00058.txt
Content-length: 666
https://sourceware.org/bugzilla/show_bug.cgi?id=25393
chorig9 at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Gdb shows value of variable |Gdb assumes that local
|with local scope before |variable begins its life at
|place of initialization |the begginig of a scope
| |(instead of at a place of
| |initialization)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26144-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 16 05:25:00 2020
Return-Path: <gdb-prs-return-26144-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 95784 invoked by alias); 16 Jan 2020 05:24:58 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 95580 invoked by uid 48); 16 Jan 2020 05:24:46 -0000
From: "bugzilla at myosotissp dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/24480] gdb drops toplevel types with -fdebug-types-section
Date: Thu, 16 Jan 2020 05: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: bugzilla at myosotissp 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: <bug-24480-4717-nVZM1OONfK@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24480-4717@http.sourceware.org/bugzilla/>
References: <bug-24480-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00059.txt
Content-length: 914
https://sourceware.org/bugzilla/show_bug.cgi?id=24480
Mark <bugzilla at myosotissp dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugzilla at myosotissp dot com
--- Comment #4 from Mark <bugzilla at myosotissp dot com> ---
Created attachment 12214
--> https://sourceware.org/bugzilla/attachment.cgi?id=12214&action=edit
Fix for missing top level types with -fdebug-types-section
This fixes the issue.
The problem is it relies on start_symtab to set list_in_scope, but start_symtab
is only called for the first tu that contributes to a symtab. Since each type
is in its own tu, only one type goes into the file scope table. Just set it on
the other paths too.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26145-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 16 11:59:29 2020
Return-Path: <gdb-prs-return-26145-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 17357 invoked by alias); 16 Jan 2020 11:59:29 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 17338 invoked by uid 48); 16 Jan 2020 11:59:29 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25350] gdb internal-error with assertion status failed
Date: Thu, 16 Jan 2020 11: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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: <bug-25350-4717-H2NmFUITve@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25350-4717@http.sourceware.org/bugzilla/>
References: <bug-25350-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00060.txt
Content-length: 381
https://sourceware.org/bugzilla/show_bug.cgi?id=25350
Yibiao Yang <yangyibiao at hust dot edu.cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |critical
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26146-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 16 14:52:52 2020
Return-Path: <gdb-prs-return-26146-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 69368 invoked by alias); 16 Jan 2020 14:52:51 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 69346 invoked by uid 48); 16 Jan 2020 14:52:51 -0000
From: "P at draigBrady dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/24480] gdb drops toplevel types with -fdebug-types-section
Date: Thu, 16 Jan 2020 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: P at draigBrady 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: <bug-24480-4717-vhphNbLXGV@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24480-4717@http.sourceware.org/bugzilla/>
References: <bug-24480-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00061.txt
Content-length: 397
https://sourceware.org/bugzilla/show_bug.cgi?id=24480
Pádraig Brady <P at draigBrady dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |P at draigBrady dot com
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26147-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 16 17:52:35 2020
Return-Path: <gdb-prs-return-26147-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 35297 invoked by alias); 16 Jan 2020 17:52:35 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 35275 invoked by uid 48); 16 Jan 2020 17:52:34 -0000
From: "flymagnus at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25402] New: Asm view can not be restarted
Date: Thu, 16 Jan 2020 17:52: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: flymagnus 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: <bug-25402-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00062.txt
Content-length: 838
https://sourceware.org/bugzilla/show_bug.cgi?id=25402
Bug ID: 25402
Summary: Asm view can not be restarted
Product: gdb
Version: 8.3.1
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: tui
Assignee: unassigned at sourceware dot org
Reporter: flymagnus at gmail dot com
Target Milestone: ---
Turning on "layout asm", and running any program twice in gdb gives SIGSEGV or
SIGABRT. Example output is below, suggesting a possible double free.
Start it from the beginning? (y or n) y
Starting program: /tmp/gdbcrash/a.out
free(): invalid size
fish: “gdb ./a.out” terminated by signal SIGABRT (Abort)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26148-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 16 19:21:05 2020
Return-Path: <gdb-prs-return-26148-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 71567 invoked by alias); 16 Jan 2020 19:21:05 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 71547 invoked by uid 55); 16 Jan 2020 19:21:05 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/24805] gdb loses exported symbols if CFLAGS contain
-fvisibility=hidden
Date: Thu, 16 Jan 2020 19: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: 8.3
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: <bug-24805-4717-rHpzPzqY0H@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24805-4717@http.sourceware.org/bugzilla/>
References: <bug-24805-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00063.txt
Content-length: 1314
https://sourceware.org/bugzilla/show_bug.cgi?id=24805
--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Pedro Alves <palves@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=790f17188a22e722bab9915e1d50307f8cb7c0f9
commit 790f17188a22e722bab9915e1d50307f8cb7c0f9
Author: Pedro Alves <palves@redhat.com>
Date: Thu Jan 16 18:35:30 2020 +0000
Ensure proc-service symbols have default visibility (PR build/24805)
Compiling GDB with '-fvisibility=hidden' removes the symbols that
should be exported.
This patch explicitly marks them as visible.
gdb/ChangeLog:
2020-01-16 Pedro Alves <palves@redhat.com>
Norbert Lange <nolange79@gmail.com>
PR build/24805
* gdbsupport/gdb_proc_service.h (PS_EXPORT): New.
(ps_get_thread_area, ps_getpid, ps_lcontinue, ps_lgetfpregs)
(ps_lgetregs, ps_lsetfpregs, ps_lsetregs, ps_lstop, ps_pcontinue)
(ps_pdread, ps_pdwrite, ps_pglobal_lookup, ps_pstop, ps_ptread)
(ps_ptwrite, ps_lgetxregs, ps_lgetxregsize, ps_lsetxregs)
(ps_plog): Redeclare exported functions with default visibility.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26149-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 16 19:46:26 2020
Return-Path: <gdb-prs-return-26149-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 17540 invoked by alias); 16 Jan 2020 19:46:25 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 17511 invoked by uid 48); 16 Jan 2020 19:46:23 -0000
From: "cbiesinger at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/24480] gdb drops toplevel types with -fdebug-types-section
Date: Thu, 16 Jan 2020 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: cbiesinger 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: cc
Message-ID: <bug-24480-4717-67U4RdRW6y@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24480-4717@http.sourceware.org/bugzilla/>
References: <bug-24480-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00064.txt
Content-length: 631
https://sourceware.org/bugzilla/show_bug.cgi?id=24480
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #5 from Christian Biesinger <cbiesinger at google dot com> ---
Mark, could you send that patch to the gdb-patches@sourceware.org mailing list,
as per https://sourceware.org/gdb/wiki/ContributionChecklist ?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26150-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 17 01:15:48 2020
Return-Path: <gdb-prs-return-26150-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 33272 invoked by alias); 17 Jan 2020 01:15:46 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 29344 invoked by uid 48); 17 Jan 2020 01:15:44 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/25405] New: segmentation fault while breakpoint on
valid address
Date: Fri, 17 Jan 2020 01:15: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: 9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25405-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00065.txt
Content-length: 1769
https://sourceware.org/bugzilla/show_bug.cgi?id=25405
Bug ID: 25405
Summary: segmentation fault while breakpoint on valid address
Product: gdb
Version: 9.1
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: breakpoints
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
$ gdb -v
GNU gdb (GDB) 9.0.50.20191210-git
Copyright (C) 2019 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.
$ cat small.c
__attribute__((target_clones("arch=core-avx2","arch=slm","default")))
void foo (float *a, int b) {
*a = (float)b;
}
float a;
int main() {
int i;
for (i = 0; i < 1024; i++)
foo (&a, 5);
}
$gcc -g -fsanitize=undefined small.c
$ gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) break *get_available_features+0x172
Breakpoint 1 at 0x11d2
(gdb) run
Starting program: /home/yibiao/tgdb/a.out
Breakpoint 1, 0x00005555555551d2 in get_available_features ()
(gdb) c
Continuing.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff70f2294 in get_available_features (ecx=<optimized out>,
edx=<optimized out>, max_cpuid_level=22)
at /build/gcc/src/gcc/libgcc/config/i386/cpuinfo.c:409
409 /build/gcc/src/gcc/libgcc/config/i386/cpuinfo.c: No such file or
directory.
(gdb)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26151-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 17 01:33:56 2020
Return-Path: <gdb-prs-return-26151-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 59438 invoked by alias); 17 Jan 2020 01:33:55 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 59418 invoked by uid 48); 17 Jan 2020 01:33:55 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25350] gdb internal-error with assertion status failed
Date: Fri, 17 Jan 2020 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: 9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: <bug-25350-4717-Sb5vdpkSsW@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25350-4717@http.sourceware.org/bugzilla/>
References: <bug-25350-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00066.txt
Content-length: 1663
https://sourceware.org/bugzilla/show_bug.cgi?id=25350
Yibiao Yang <yangyibiao at hust dot edu.cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|8.3.1 |9.1
--- Comment #1 from Yibiao Yang <yangyibiao at hust dot edu.cn> ---
$ gdb -v
GNU gdb (GDB) 9.0.50.20191210-git
Copyright (C) 2019 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.
$ gcc -g -fsanitize=undefined small.c
$ gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) break *eh2+0x7e
Breakpoint 1 at 0x13e2: file small.c, line 38.
(gdb) run
Starting program: /home/yibiao/tgdb/a.out
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Breakpoint 1, 0x00005555555553e2 in eh2 (
frame.c:587: internal-error: frame_id get_frame_id(frame_info*): Assertion
`stashed' 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:
<http://www.gnu.org/software/gdb/bugs/>.
frame.c:587: internal-error: frame_id get_frame_id(frame_info*): Assertion
`stashed' 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)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26152-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 17 01:41:35 2020
Return-Path: <gdb-prs-return-26152-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 82755 invoked by alias); 17 Jan 2020 01:41:35 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 82735 invoked by uid 48); 17 Jan 2020 01:41:35 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25350] gdb internal-error with assertion status failed
Date: Fri, 17 Jan 2020 01: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: critical
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: <bug-25350-4717-cgnPLcORRY@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25350-4717@http.sourceware.org/bugzilla/>
References: <bug-25350-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00067.txt
Content-length: 377
https://sourceware.org/bugzilla/show_bug.cgi?id=25350
Yibiao Yang <yangyibiao at hust dot edu.cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|9.1 |HEAD
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26153-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 17 01:49:05 2020
Return-Path: <gdb-prs-return-26153-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 88407 invoked by alias); 17 Jan 2020 01:48:37 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 88305 invoked by uid 48); 17 Jan 2020 01:48:26 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/24602] [gdb] gdb wrongly stopped at a breakpoint in an
unexecuted line of code
Date: Fri, 17 Jan 2020 01: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: critical
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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 bug_severity
Message-ID: <bug-24602-4717-B8Tk20myS4@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24602-4717@http.sourceware.org/bugzilla/>
References: <bug-24602-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00068.txt
Content-length: 1121
https://sourceware.org/bugzilla/show_bug.cgi?id=24602
Yibiao Yang <yangyibiao at hust dot edu.cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|8.1 |HEAD
Severity|normal |critical
--- Comment #1 from Yibiao Yang <yangyibiao at hust dot edu.cn> ---
This problem is still exist in latest development version of gdb
$ gdb -v
GNU gdb (GDB) 9.0.50.20191210-git
Copyright (C) 2019 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.
$ gdb ./a.out -q
Reading symbols from ./a.out...
(gdb) break 8
Breakpoint 1 at 0x1148: file small.c, line 8.
(gdb) run
Starting program: /home/yibiao/tgdb/a.out
Breakpoint 1, main (argc=1, argv=0x7fffffffe008) at small.c:8
8 label:
(gdb)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26154-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 17 07:31:10 2020
Return-Path: <gdb-prs-return-26154-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 98821 invoked by alias); 17 Jan 2020 07:31:08 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 98783 invoked by uid 48); 17 Jan 2020 07:31:07 -0000
From: "jwdevel at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/15163] Vi settings within ~/.inputrc prevent
entering/exiting TUI via C-x a
Date: Fri, 17 Jan 2020 07: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.5
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jwdevel 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-15163-4717-OCbi9vp6A5@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-15163-4717@http.sourceware.org/bugzilla/>
References: <bug-15163-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00069.txt
Content-length: 3058
https://sourceware.org/bugzilla/show_bug.cgi?id=15163
John W. <jwdevel at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jwdevel at gmail dot com
--- Comment #9 from John W. <jwdevel at gmail dot com> ---
I recently dealt with this a bit, so here are my notes:
Short version: It *mostly* works. With a few workarounds, I have a decent
experience with vi-mode in GDB+TUI.
Details:
$ gdb --version
GNU gdb (Debian 8.2.1-2+b3) 8.2.1
As far as I could tell, GDB does not have default mappings for the tui-xxx
readline bindings.
Certainly, using C-x,C-a or similar did nothing (just printed "^X^A" for me),
but I'm unaware of any other mapping established.
This is my first gripe: there seems to be no way to dump out the mappings, to
know what I'm working with
Regardless, I created a file ".inputrc.gdb" with these contents:
set editing-mode vi
# GDB only maps this stuff in emacs mode.
# So, we just do the same for vi-mode.
set keymap vi-insert
"\C-x\C-a": tui-switch-mode
"\C-xa": tui-switch-mode
"\C-xA": tui-switch-mode
"\C-x1": tui-delete-other-windows
"\C-x2": tui-change-windows
"\C-xo": tui-other-window
"\C-xs": next-keymap
set keymap vi-command
"\C-x\C-a": tui-switch-mode
"\C-xa": tui-switch-mode
"\C-xA": tui-switch-mode
"\C-x1": tui-delete-other-windows
"\C-x2": tui-change-windows
"\C-xo": tui-other-window
"\C-xs": next-keymap
Then, I run gdb with:
$ INPUTRC=.inputrc.gdb gdb path/to/my/program
However, this did not immediately work!
I still got literal "^X^A" when I tried to use it.
I got to wondering if somehow GDB was *stripping* my mappings on startup, when
it configures its own readline internally.
I haven't confirmed this, but it seems plausible given the next thing I tried:
(1) I added this line to my .inputrc.gdb:
"\C-x\C-r": re-read-init-file
[That line appears twice - once under 'vi-insert' keymap, and once under
'vi-command']
(2) After gdb starts up (same commandline as used above), I first do C-x,C-r to
reload my config.
Then, after that, my C-x,C-a bindings work! I can switch to TUI, while still
staying in vi mode.
Single key mode works too.
Some other comments:
* You must type C-x,<whatever> quickly. The default timeout is 500ms. You can
change that in readline with keyseq-timeout.
* The need to re-load the config after startup is strange and confusing. Seems
like a bug to me.
* Comment #7 has a point that the C-X mappings are not very idiomatic for vi.
At present, there simply are zero mappings, so I guess that sidestepps the
issue. But that fact is not obvious from the GDB docs; they don't discuss edit
mode differences. [aside, re: last sentence of Comment #7: comma *does* have a
meaning in original vi - do ';' but in reverse)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26155-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 17 09:38:07 2020
Return-Path: <gdb-prs-return-26155-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 72436 invoked by alias); 17 Jan 2020 09:38:06 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 72352 invoked by uid 48); 17 Jan 2020 09:38:05 -0000
From: "byron.c.hawkins at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25407] New: Abort with failed assertion on TUI assembly
layout
Date: Fri, 17 Jan 2020 09: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: 8.3
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: byron.c.hawkins 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: <bug-25407-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00070.txt
Content-length: 1313
https://sourceware.org/bugzilla/show_bug.cgi?id=25407
Bug ID: 25407
Summary: Abort with failed assertion on TUI assembly layout
Product: gdb
Version: 8.3
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: byron.c.hawkins at gmail dot com
Target Milestone: ---
Steps to reproduce:
> gdb ls
> br main
> r
[at breakpoint]
> foc cmd
> lay asm
> si
Result:
/usr/include/c++/9/bits/stl_vector.h:1060: std::vector<_Tp,
_Alloc>::const_reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp,
_Alloc>::size_type) const [with _Tp = tui_source_element; _Alloc =
std::allocator<tui_source_element>; std::vector<_Tp, _Alloc>::const_reference =
const tui_source_element&; std::vector<_Tp, _Alloc>::size_type = long unsigned
int]: Assertion '__builtin_expect(__n < this->size(), true)' failed.
Environment:
> gdb --version
GNU gdb (GDB) Fedora 8.3.50.20190824-26.fc31
> uname -a
Linux nickel.localhost 5.3.13-300.fc31.x86_64 #1 SMP Mon Nov 25 17:25:25
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26156-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 17 09:39:02 2020
Return-Path: <gdb-prs-return-26156-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 7086 invoked by alias); 17 Jan 2020 09:39:01 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 6184 invoked by uid 48); 17 Jan 2020 09:39:01 -0000
From: "byron.c.hawkins at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25407] Abort with failed assertion on TUI assembly layout
Date: Fri, 17 Jan 2020 09: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: 8.3
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: byron.c.hawkins 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: <bug-25407-4717-XSJRrnGMK7@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25407-4717@http.sourceware.org/bugzilla/>
References: <bug-25407-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00071.txt
Content-length: 268
https://sourceware.org/bugzilla/show_bug.cgi?id=25407
--- Comment #1 from Byron Hawkins <byron.c.hawkins at gmail dot com> ---
Tested on two machines:
1. Intel i5-6300U
2. Intel J5005
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26157-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 17 10:16:03 2020
Return-Path: <gdb-prs-return-26157-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 37857 invoked by alias); 17 Jan 2020 10:16:03 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 37839 invoked by uid 48); 17 Jan 2020 10:16:03 -0000
From: "sergey.belyashov at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25408] New: Automatic overlay debugging is not optimal
Date: Fri, 17 Jan 2020 10:16: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: sergey.belyashov 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: <bug-25408-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00072.txt
Content-length: 2216
https://sourceware.org/bugzilla/show_bug.cgi?id=25408
Bug ID: 25408
Summary: Automatic overlay debugging is not optimal
Product: gdb
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: sergey.belyashov at gmail dot com
Target Milestone: ---
First, currently automatic overlay debugging is poorly documented. It does not
clear how many entries should have _ovly_table: number of overlays itself or
number of overlayed areas. After some investigation I found answer: worst case
for me: number of overlays.
Now I describe why it is worst.
My project have 2 overlay areas. One for code (256 overlays by 16KB) and one
for data (32 overlays by 4KB). Statically mapped RAM is very low: 8KB.
One entry of _ovly_table requires 4*4=16 bytes. So table will be 16*(256+32) =
4.5KB. It is not acceptable because it is more than a half of available RAM.
My suggestion is to add support for new approach. Where root is address space
area of the process but not overlay itself.
For example:
_ovly_areas_table:
This variable must be an array of the following structures:
struct
{
/* The area address. */
unsigned long address;
/* The area size (0 for unmapped area), in bytes. */
unsigned long size;
/* The mapped overlay's load address. */
unsigned long lma;
/* Mapped overlay index. */
unsigned long index;
}
_ovly_areas_n:
This variable must be a four-byte unsigned integer, holding the total number of
elements in _ovly_areas_table.
unsigned long _ovly_areas_n = 2;
unsigned long _ovly_table[_ovly_areas_n][4] = {
{0x8000, 0x4000, 0x01008000, 0x0001},
{0xE000, 0x2000, 0x02000000, 0x0001}
};
So this table says:
Overlay N1 is mapped to area 0x8000...0xBFFF from 0x01008000
Overlay N1 is mapped to area 0xE000...0xFFFF from 0x02000000
Table about existing overlays can be stored in special section of binary (or
added special section naming convention), and may not be loaded to target
system.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26158-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 17 10:24:41 2020
Return-Path: <gdb-prs-return-26158-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 46132 invoked by alias); 17 Jan 2020 10:24:38 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 46050 invoked by uid 48); 17 Jan 2020 10:24:36 -0000
From: "sergey.belyashov at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25408] Automatic overlay debugging is not optimal
Date: Fri, 17 Jan 2020 10: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: sergey.belyashov 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: <bug-25408-4717-8KhISKVYs3@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25408-4717@http.sourceware.org/bugzilla/>
References: <bug-25408-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00073.txt
Content-length: 1146
https://sourceware.org/bugzilla/show_bug.cgi?id=25408
--- Comment #1 from Sergey Belyashov <sergey.belyashov at gmail dot com> ---
This is comment from gdb/symfile.c:
The overlay_update function pokes around in the target's data structures
to see what overlays are mapped, and updates GDB's overlay mapping with
this information.
In this simple implementation, the target data structures are as follows:
unsigned _novlys; /# number of overlay sections #/
unsigned _ovly_table[_novlys][4] = {
{VMA, OSIZE, LMA, MAPPED}, /# one entry per overlay section #/
{..., ..., ..., ...},
}
unsigned _novly_regions; /# number of overlay regions #/
unsigned _ovly_region_table[_novly_regions][3] = {
{VMA, OSIZE, MAPPED_TO_LMA}, /# one entry per overlay region #/
{..., ..., ...},
}
These functions will attempt to update GDB's mappedness state in the
symbol section table, based on the target's mappedness state.
So my idea was already planned by Jason Molenda in 1999 but was not implemented
yet.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26159-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 17 14:42:01 2020
Return-Path: <gdb-prs-return-26159-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 120704 invoked by alias); 17 Jan 2020 14:42:00 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 120681 invoked by uid 48); 17 Jan 2020 14:42:00 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/24805] gdb loses exported symbols if CFLAGS contain
-fvisibility=hidden
Date: Fri, 17 Jan 2020 14: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: 8.3
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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-24805-4717-8njy4Sw55Q@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24805-4717@http.sourceware.org/bugzilla/>
References: <bug-24805-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00074.txt
Content-length: 562
https://sourceware.org/bugzilla/show_bug.cgi?id=24805
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.1
--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
Fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26160-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 17 15:12:30 2020
Return-Path: <gdb-prs-return-26160-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 95116 invoked by alias); 17 Jan 2020 15:12:30 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 94618 invoked by uid 48); 17 Jan 2020 15:12:30 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25410] New: Re-running second inferior fails with
"td_ta_new failed: generic error"
Date: Fri, 17 Jan 2020 15: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: 10.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25410-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00075.txt
Content-length: 1813
https://sourceware.org/bugzilla/show_bug.cgi?id=25410
Bug ID: 25410
Summary: Re-running second inferior fails with "td_ta_new
failed: generic error"
Product: gdb
Version: 10.1
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: simark at simark dot ca
Target Milestone: ---
This fails since the multi-target patch (5b6d1e4fa "Multi-target support).
Starting a first inferior, then trying to run a second inferior twice, gives
this:
(gdb) file /tmp/foo
Reading symbols from /tmp/foo...
(gdb) start
Temporary breakpoint 1 at 0x4004da: file /tmp/foo.c, line 1.
Starting program: /tmp/foo
a
Temporary breakpoint 1, main () at /tmp/foo.c:1
1 int main() { return 0; }
(gdb) add-inferior -exec /bin/ls
[New inferior 2]
Added inferior 2 on connection 1 (native)
Reading symbols from /bin/ls...
(No debugging symbols found in /bin/ls)
(gdb) inferior 2
[Switching to inferior 2 [<null>] (/bin/ls)]
(gdb) run /
Starting program: /bin/ls /
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
bin etc initrd.img.old lib64 media proc sbin tmp vmlinuz
boot home lib libx32 mnt root srv usr
vmlinuz.old
dev initrd.img lib32 lost+found opt run sys var
[Inferior 2 (process 23086) exited normally]
(gdb) run /
Starting program: /tmp/foo /
warning: td_ta_new failed: generic error
[Inferior 2 (process 23087) exited normally]
We would expect the second "run /" to run ls again, listing the files in /.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26161-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 17 15:14:53 2020
Return-Path: <gdb-prs-return-26161-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 31692 invoked by alias); 17 Jan 2020 15:14:53 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 31665 invoked by uid 48); 17 Jan 2020 15:14:53 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25410] Re-running second inferior fails with "td_ta_new
failed: generic error"
Date: Fri, 17 Jan 2020 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: simark at simark dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: version target_milestone
Message-ID: <bug-25410-4717-tNmrvx6PDl@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25410-4717@http.sourceware.org/bugzilla/>
References: <bug-25410-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00076.txt
Content-length: 426
https://sourceware.org/bugzilla/show_bug.cgi?id=25410
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|10.1 |HEAD
Target Milestone|--- |10.1
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26162-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 17 15:49:01 2020
Return-Path: <gdb-prs-return-26162-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 4085 invoked by alias); 17 Jan 2020 15:49:00 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 4052 invoked by uid 48); 17 Jan 2020 15:48:59 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25412] New: thread_info with duplicate ptid added to
inferior thread list
Date: Fri, 17 Jan 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25412-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00077.txt
Content-length: 2330
https://sourceware.org/bugzilla/show_bug.cgi?id=25412
Bug ID: 25412
Summary: thread_info with duplicate ptid added to inferior
thread list
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: simark at simark dot ca
Target Milestone: ---
This problem appeared with the multi-target patch (5b6d1e4fa "Multi-target
support).
I think I found something odd happening starting with this commit. When
the test gdb.threads/tid-reuse.exp runs, we are adding a thread_info to the
inferior's thread list when a thread_info object with the same ptid is
already present. I don't think this is ever supposed to happen, right?
This can be observed by applying the following diff and running
gdb.threads/tid-reuse.exp. Note that some distributions are starting to bump
pid_max to a really large value, so make sure it's not that on your system.
diff --git a/gdb/thread.c b/gdb/thread.c
index 4959f938c7f3..8909e371e2ce 100644
--- a/gdb/thread.c
+++ b/gdb/thread.c
@@ -254,7 +254,10 @@ new_thread (struct inferior *inf, ptid_t ptid)
struct thread_info *last;
for (last = inf->thread_list; last->next != NULL; last = last->next)
- ;
+ gdb_assert (ptid != last->ptid);
+
+ gdb_assert (ptid != last->ptid);
+
last->next = tp;
}
What I have found so far, by breaking at thread.c:274 and stepping into
the "delete_thread" call, is that `inferior_ptid == ptid` is false
(inferior_ptid is (0,0,0)). In delete_thread, we are actually not
deleting the thread because ->deletable () returns false, because
the refcount is 2.
Before this patch, we would enter the `if (inferior_ptid == ptid)`.
If it can help, here is the command line I'm using to debug this, which is
mimicking the test:
./gdb -nx --data-directory=data-directory
testsuite/outputs/gdb.threads/tid-reuse/tid-reuse -iex "set confirm off" -iex
"set pagination off" -ex start -ex "set print thread-events off" -ex "b
after_count" -ex c -ex "b do_nothing_thread_func" -ex c -ex d -ex "b
after_reuse_time" -ex c
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26163-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 17 15:49:43 2020
Return-Path: <gdb-prs-return-26163-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 17548 invoked by alias); 17 Jan 2020 15:49:43 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 17486 invoked by uid 48); 17 Jan 2020 15:49:42 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25412] thread_info with duplicate ptid added to inferior
thread list
Date: Fri, 17 Jan 2020 15: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: simark at simark dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-25412-4717-y2ShQfzugd@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25412-4717@http.sourceware.org/bugzilla/>
References: <bug-25412-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00078.txt
Content-length: 372
https://sourceware.org/bugzilla/show_bug.cgi?id=25412
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.1
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26165-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 18 17:12:05 2020
Return-Path: <gdb-prs-return-26165-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 121294 invoked by alias); 18 Jan 2020 17:12:05 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 121234 invoked by uid 48); 18 Jan 2020 17:12:05 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug guile/21104] 7.12.1 does not compile with latest guile (2.1.6)
Date: Sat, 18 Jan 2020 17:12: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: simark at simark dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
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: <bug-21104-4717-j9tQ7nkQ6k@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-21104-4717@http.sourceware.org/bugzilla/>
References: <bug-21104-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00080.txt
Content-length: 517
https://sourceware.org/bugzilla/show_bug.cgi?id=21104
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |slyfox at inbox dot ru
--- Comment #15 from Simon Marchi <simark at simark dot ca> ---
*** Bug 23918 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26164-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 18 17:12:05 2020
Return-Path: <gdb-prs-return-26164-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 121151 invoked by alias); 18 Jan 2020 17:12:05 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 121132 invoked by uid 48); 18 Jan 2020 17:12:05 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug guile/23918] gdb --with-guile=guile-2.2 fails
as:guile/scm-ports.c:143:10: error: 'scm_new_port_table_entry' was not
declared in this scope
Date: Sat, 18 Jan 2020 17:12: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: 8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
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: <bug-23918-4717-uONjZ1348i@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23918-4717@http.sourceware.org/bugzilla/>
References: <bug-23918-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00079.txt
Content-length: 754
https://sourceware.org/bugzilla/show_bug.cgi?id=23918
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |simark at simark dot ca
Resolution|--- |DUPLICATE
--- Comment #1 from Simon Marchi <simark at simark dot ca> ---
I'll close this as a duplicate of #21104. It's not the same guile version that
is mentioned, but it's the same idea.
*** This bug has been marked as a duplicate of bug 21104 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26166-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 20 01:11:13 2020
Return-Path: <gdb-prs-return-26166-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 32419 invoked by alias); 20 Jan 2020 01:11:12 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 32399 invoked by uid 48); 20 Jan 2020 01:11:12 -0000
From: "lockywolf at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/25388] Leaving the python-interactive pyton interpreter
without EOF (also works strangely with the Emacs interface)
Date: Mon, 20 Jan 2020 01:11: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: lockywolf 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: <bug-25388-4717-1SmhKpXnhp@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25388-4717@http.sourceware.org/bugzilla/>
References: <bug-25388-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00081.txt
Content-length: 660
https://sourceware.org/bugzilla/show_bug.cgi?id=25388
lockywolf at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Leaving the |Leaving the
|python-interactive pyton |python-interactive pyton
|interpreter without EOF |interpreter without EOF
| |(also works strangely with
| |the Emacs interface)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26167-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 20 01:14:34 2020
Return-Path: <gdb-prs-return-26167-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 33774 invoked by alias); 20 Jan 2020 01:14:34 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 33753 invoked by uid 48); 20 Jan 2020 01:14:34 -0000
From: "lockywolf at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/25388] Leaving the python-interactive pyton interpreter
without EOF (also works strangely with the Emacs interface)
Date: Mon, 20 Jan 2020 01: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lockywolf 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: <bug-25388-4717-M49vDb6tsC@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25388-4717@http.sourceware.org/bugzilla/>
References: <bug-25388-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00082.txt
Content-length: 379
https://sourceware.org/bugzilla/show_bug.cgi?id=25388
--- Comment #1 from lockywolf at gmail dot com ---
This bug also intertwines with a bug in Emacs:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39140
Namely, it makes it hard to leave GUD in Emacs.
Neither quit(), nor EOF seem to work.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26169-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 20 07:19:38 2020
Return-Path: <gdb-prs-return-26169-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 51989 invoked by alias); 20 Jan 2020 07:19:38 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 51970 invoked by uid 48); 20 Jan 2020 07:19:38 -0000
From: "amelia01smith at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/25419] Looking for a solution for canon printer error
code b200
Date: Mon, 20 Jan 2020 07:19: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: 10.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amelia01smith 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_file_loc
Message-ID: <bug-25419-4717-Gj5l5LGmAl@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25419-4717@http.sourceware.org/bugzilla/>
References: <bug-25419-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00084.txt
Content-length: 556
https://sourceware.org/bugzilla/show_bug.cgi?id=25419
Amelia smith <amelia01smith at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |https://www.printersupport2
| |4x7.com/questions/how-to-fi
| |x-canon-printer-error-b200/
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26168-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 20 07:19:25 2020
Return-Path: <gdb-prs-return-26168-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 51646 invoked by alias); 20 Jan 2020 07:19:24 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 51626 invoked by uid 48); 20 Jan 2020 07:19:24 -0000
From: "amelia01smith at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/25419] New: Looking for a solution for canon printer
error code b200
Date: Mon, 20 Jan 2020 07:19: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: 10.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amelia01smith 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: <bug-25419-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00083.txt
Content-length: 1272
https://sourceware.org/bugzilla/show_bug.cgi?id=25419
Bug ID: 25419
Summary: Looking for a solution for canon printer error code
b200
Product: gdb
Version: 10.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: amelia01smith at gmail dot com
Target Milestone: ---
You may run over canon printer error B200 while utilizing your printer. The
error emerges because of some issue comes in equipment that is related to the
print head or even with the printer itself. In the event that you stand up to
this error, you will see that your printing employments get blocked. Try not to
irritate right then and there as we have tech-nerds who will help you in the
correct manner. Along these lines, benefit Canon Printer Support by means of
dialing our furnished helpline number and get joined with the experts until you
get quality administrations or arrangements identified with your concern.visit
here:
https://www.printersupport24x7.com/questions/how-to-fix-canon-printer-error-b200/
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26170-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 21 03:28:05 2020
Return-Path: <gdb-prs-return-26170-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 102897 invoked by alias); 21 Jan 2020 03:28:04 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 102878 invoked by uid 48); 21 Jan 2020 03:28:04 -0000
From: "lockywolf at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/25388] Leaving the python-interactive pyton interpreter
without EOF (also works strangely with the Emacs interface)
Date: Tue, 21 Jan 2020 03: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lockywolf 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: <bug-25388-4717-e2b46AdrzC@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25388-4717@http.sourceware.org/bugzilla/>
References: <bug-25388-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00085.txt
Content-length: 325
https://sourceware.org/bugzilla/show_bug.cgi?id=25388
--- Comment #2 from lockywolf at gmail dot com ---
Ctrl-D in gdb -i=mi end both the python interpreter and the gdb interpreter at
the same time.
Not so in plain gdb, without -i=mi.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26171-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 22 00:33:53 2020
Return-Path: <gdb-prs-return-26171-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 72995 invoked by alias); 22 Jan 2020 00:33:52 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 72975 invoked by uid 48); 22 Jan 2020 00:33:52 -0000
From: "tblodt at icloud dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/25435] New: Tab completion of symbols is not always instant
Date: Wed, 22 Jan 2020 00: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: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tblodt at icloud dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25435-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00086.txt
Content-length: 946
https://sourceware.org/bugzilla/show_bug.cgi?id=25435
Bug ID: 25435
Summary: Tab completion of symbols is not always instant
Product: gdb
Version: 8.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cli
Assignee: unassigned at sourceware dot org
Reporter: tblodt at icloud dot com
Target Milestone: ---
In binaries with many symbols, tab completion of symbols for the "break"
command can take a few seconds. The symbols should ideally be stored in some
kind of sorted data structure that allows binary searching to return results
with no noticeable delay.
I've been running into this with Chromium. You can reproduce by building
Chromium with the default settings, loading the binary into gdb, and trying to
use "break" tab completion.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26172-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 22 19:56:23 2020
Return-Path: <gdb-prs-return-26172-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 76127 invoked by alias); 22 Jan 2020 19:56:23 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 76053 invoked by uid 48); 22 Jan 2020 19:56:22 -0000
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25446] New: "list" and missing source, first time vs
subsequent
Date: Wed, 22 Jan 2020 19: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: 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: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25446-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00087.txt
Content-length: 2410
https://sourceware.org/bugzilla/show_bug.cgi?id=25446
Bug ID: 25446
Summary: "list" and missing source, first time vs subsequent
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: palves at redhat dot com
Target Milestone: ---
I noticed that typing "list" when the source file doesn't exist behaves
differently the first time compared to the following times:
$ gdb ./testsuite/outputs/gdb.base/list-missing-source/list-missing-source
...
Reading symbols from
./testsuite/outputs/gdb.base/list-missing-source/list-missing-source...
First time:
(gdb) list main
1
/home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/list-missing-source/main.c:
No such file or directory.
Second and third times:
(gdb) list main
1 in
/home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/list-missing-source/main.c
(gdb) list main
1 in
/home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/list-missing-source/main.c
The first time we don't get the "in", get the strerror error, and there's no
color. The second and following times, there's no error, and the file name is
colorized.
The list-missing-source.exp testcase happens to not notice this difference
because there, the first list is done implicitly by a stop at a breakpoint:
(gdb) run
Starting program:
/home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/list-missing-source/list-missing-source
Breakpoint 1, main () at
/home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/list-missing-source/main.c:5
5
/home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/list-missing-source/main.c:
No such file or directory.
(gdb) list
1 in
/home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/list-missing-source/main.c
If you type "run" a second time, then you get the same behavior as if you had
typed "list" a second time.
Maybe this "error the first time" behavior is by design, but it looked a little
odd to me, particularly the missing "in" and lack of color were what jumped at
me at first.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26173-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 24 00:11:31 2020
Return-Path: <gdb-prs-return-26173-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 109116 invoked by alias); 24 Jan 2020 00:11:31 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 109090 invoked by uid 55); 24 Jan 2020 00:11:30 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/9765] Scrolling to end of program in asm layout is broken
Date: Fri, 24 Jan 2020 00:11: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: cvs-commit at gcc dot gnu.org
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: <bug-9765-4717-0e2qHGTbqS@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-9765-4717@http.sourceware.org/bugzilla/>
References: <bug-9765-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00088.txt
Content-length: 1193
https://sourceware.org/bugzilla/show_bug.cgi?id=9765
--- Comment #11 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2f267673f0fdee9287e6d404ecd4f2d29da0d2f2
commit 2f267673f0fdee9287e6d404ecd4f2d29da0d2f2
Author: Pedro Alves <palves@redhat.com>
Date: Sat Jan 11 01:37:26 2020 +0000
gdb/tui: Prevent exceptions from trying to cross readline
This is triggered by simply scrolling off the end of the dissasembly
window. This commit doesn't fix the actual exception that is being
thrown, which will still need to be fixed, but makes sure that we
don't ever throw an exception out to readline.
gdb/ChangeLog:
yyyy-mm-dd Pedro Alves <palves@redhat.com>
PR tui/9765
* tui/tui-io.c (tui_getc): Rename to ...
(tui_getc_1): ... this.
(tui_get): New, reimplent as try/catch wrapper around tui_getc_1.
Change-Id: I2e32a401ab34404b2132ec82a3e1c17b9b723e41
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26174-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 24 00:11:37 2020
Return-Path: <gdb-prs-return-26174-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 109436 invoked by alias); 24 Jan 2020 00:11:37 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 109417 invoked by uid 55); 24 Jan 2020 00:11:37 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/9765] Scrolling to end of program in asm layout is broken
Date: Fri, 24 Jan 2020 00:11: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: cvs-commit at gcc dot gnu.org
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: <bug-9765-4717-o0sl4bU0uL@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-9765-4717@http.sourceware.org/bugzilla/>
References: <bug-9765-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00089.txt
Content-length: 3681
https://sourceware.org/bugzilla/show_bug.cgi?id=9765
--- Comment #12 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=733d0a679536628eb1be4b4b8aa6384de24ff1f1
commit 733d0a679536628eb1be4b4b8aa6384de24ff1f1
Author: Andrew Burgess <andrew.burgess@embecosm.com>
Date: Sat Jan 11 01:38:28 2020 +0000
gdb/tui: asm window handles invalid memory and scrolls better
This started as a patch to enable the asm window to handle attempts to
disassemble invalid memory, but it ended up expanding into a
significant rewrite of how the asm window handles scrolling. These
two things ended up being tied together as it was impossible to
correctly test scrolling into invalid memory when the asm window would
randomly behave weirdly while scrolling.
Things that should work nicely now; scrolling to the bottom or top of
the listing with PageUp, PageDown, Up Arrow, Down Arrow and we should
be able to scroll past small areas of memory that don't have symbols
associated with them. It should also be possible to scroll to the
start of a section even if there's no symbol at the start of the
section.
Adding tests for this scrolling was a little bit of a problem. First
I would have liked to add tests for PageUp / PageDown, but the tuiterm
library we use doesn't support these commands right now due to only
emulating a basic ascii terminal. Changing this to emulate a more
complex terminal would require adding support for more escape sequence
control codes, so I've not tried to tackle that in this patch.
Next, I would have liked to test scrolling to the start or end of the
assembler listing and then trying to scroll even more, however, this
is a problem because in a well behaving GDB a scroll at the start/end
has no effect. What we need to do is:
- Move to start of assembler listing,
- Send scroll up command,
- Wait for all curses output,
- Ensure the assembler listing is unchanged, we're still at the
start of the listing.
The problem is that there is no curses output, so how long do we wait
at step 3? The same problem exists for scrolling to the bottom of the
assembler listing. However, when scrolling down you can at least see
the end coming, so I added a test for this case, however, this feels
like an area of code that is massively under tested.
gdb/ChangeLog:
PR tui/9765
* minsyms.c (lookup_minimal_symbol_by_pc_section): Update header
comment, add extra parameter, and update to store previous symbol
when appropriate.
* minsyms.h (lookup_minimal_symbol_by_pc_section): Update comment,
add extra parameter.
* tui/tui-disasm.c (tui_disassemble): Update header comment,
remove unneeded parameter, add try/catch around gdb_print_insn,
rewrite to add items to asm_lines vector.
(tui_find_backward_disassembly_start_address): New function.
(tui_find_disassembly_address): Updated throughout.
(tui_disasm_window::set_contents): Update for changes to
tui_disassemble.
(tui_disasm_window::do_scroll_vertical): No need to adjust the
number of lines to scroll.
gdb/testsuite/ChangeLog:
PR tui/9765
* gdb.tui/tui-layout-asm.exp: Add scrolling test for asm window.
Change-Id: I323987c8fd316962c937e73c17d952ccd3cfa66c
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26175-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 24 00:13:03 2020
Return-Path: <gdb-prs-return-26175-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 111510 invoked by alias); 24 Jan 2020 00:13:03 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 111492 invoked by uid 55); 24 Jan 2020 00:13:02 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/23718] Exceptions in gdb.execute("cont") etc. cause a
hang with stdin disabled
Date: Fri, 24 Jan 2020 00: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: 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: <bug-23718-4717-lKTpbgv6eP@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23718-4717@http.sourceware.org/bugzilla/>
References: <bug-23718-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00090.txt
Content-length: 2429
https://sourceware.org/bugzilla/show_bug.cgi?id=23718
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1ba1ac88011703abcd0271e4f5d00927dc69a09a
commit 1ba1ac88011703abcd0271e4f5d00927dc69a09a
Author: Andrew Burgess <andrew.burgess@embecosm.com>
Date: Tue Nov 19 11:17:20 2019 +0000
gdb: Enable stdin on exception in execute_gdb_command
This is an update of this patch:
https://sourceware.org/ml/gdb-patches/2018-09/msg00884.html
This patch attempts to address PR gdb/23718 by re-enabling stdin
whenever an exception is caught during gdb.execute().
When Python gdb.execute() is called, an exception could occur (e.g. the
target disappearing), which is then converted into a Python exception. If
stdin was disabled before the exception is caught, it is not re-enabled,
because the exception doesn't propagate to the top level of the event loop,
whose catch block would otherwise enable it.
The result is that when execution of a Python script completes, GDB does
not prompt or accept input, and is effectively hung.
This change rectifies the issue by re-enabling stdin in the catch block of
execute_gdb_command, prior to converting the exception to a Python
exception.
Since this patch was originally posted I've added a test, and also I
converted the code to re-enable stdin from this:
SWITCH_THRU_ALL_UIS ()
{
async_enable_stdin ();
}
to simply this:
async_enable_stdin ();
My reasoning is that we only need the SWITCH_THRU_ALL_UIS if, at the time
the exception is caught, the current_ui might be different than at the time
we called async_disable_stdin. Within python's execute_gdb_command I think
it should be impossible to switch current_ui, so the SWITCH_THRU_ALL_UIS
isn't needed.
gdb/ChangeLog:
PR gdb/23718
* gdb/python/python.c (execute_gdb_command): Call
async_enable_stdin in catch block.
gdb/testsuite/ChangeLog:
PR gdb/23718
* gdb.server/server-kill-python.exp: New file.
Change-Id: I1cfc36ee9f8484cc1ed82be9be338353db6bc080
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26176-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 24 09:27:26 2020
Return-Path: <gdb-prs-return-26176-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 60925 invoked by alias); 24 Jan 2020 09:27:26 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 60905 invoked by uid 48); 24 Jan 2020 09:27:26 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] Tiny programs (few lines of assembly) cause GDB's
TUI to crash
Date: Fri, 24 Jan 2020 09:27: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: shahab.vahedi 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: <bug-25345-4717-41tHrvG0ri@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25345-4717@http.sourceware.org/bugzilla/>
References: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00091.txt
Content-length: 895
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
Shahab <shahab.vahedi at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #12 from Shahab <shahab.vahedi at gmail dot com> ---
The fixes are in.
gdb/tui: Prevent exceptions from trying to cross readline
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=2f267673f0fdee9287e6d404ecd4f2d29da0d2f2
gdb/tui: asm window handles invalid memory and scrolls better
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=733d0a679536628eb1be4b4b8aa6384de24ff1f1
This issue can be marked as resolved now.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26177-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 24 11:14:56 2020
Return-Path: <gdb-prs-return-26177-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 2184 invoked by alias); 24 Jan 2020 11:14:56 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 2164 invoked by uid 48); 24 Jan 2020 11:14:56 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] Tiny programs (few lines of assembly) cause GDB's
TUI to crash
Date: Fri, 24 Jan 2020 11:14: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: shahab.vahedi 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:
Message-ID: <bug-25345-4717-XkjMK7Fdvu@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25345-4717@http.sourceware.org/bugzilla/>
References: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00092.txt
Content-length: 282
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
--- Comment #13 from Shahab <shahab.vahedi at gmail dot com> ---
yet one tiny issue:
https://sourceware.org/ml/gdb-patches/2020-01/msg00780.html
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26178-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 24 11:17:37 2020
Return-Path: <gdb-prs-return-26178-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 4219 invoked by alias); 24 Jan 2020 11:17:37 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 4200 invoked by uid 48); 24 Jan 2020 11:17:37 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/9765] Scrolling to end of program in asm layout is broken
Date: Fri, 24 Jan 2020 11:17: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: shahab.vahedi at gmail 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: <bug-9765-4717-KCO3YDBsfm@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-9765-4717@http.sourceware.org/bugzilla/>
References: <bug-9765-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00093.txt
Content-length: 283
https://sourceware.org/bugzilla/show_bug.cgi?id=9765
--- Comment #13 from Shahab <shahab.vahedi at gmail dot com> ---
still one tiny issue:
https://sourceware.org/ml/gdb-patches/2020-01/msg00780.html
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26179-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 24 18:54:14 2020
Return-Path: <gdb-prs-return-26179-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 44232 invoked by alias); 24 Jan 2020 18:54:14 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 44213 invoked by uid 55); 24 Jan 2020 18:54:13 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25410] Re-running second inferior fails with "td_ta_new
failed: generic error"
Date: Fri, 24 Jan 2020 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: 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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25410-4717-Pcxr43p4ns@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25410-4717@http.sourceware.org/bugzilla/>
References: <bug-25410-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00094.txt
Content-length: 7826
https://sourceware.org/bugzilla/show_bug.cgi?id=25410
--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Pedro Alves <palves@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=53af73bf5e9bad42a76bcc47cdf44d91bbbc4eb7
commit 53af73bf5e9bad42a76bcc47cdf44d91bbbc4eb7
Author: Pedro Alves <palves@redhat.com>
Date: Fri Jan 24 18:46:20 2020 +0000
Fix re-runs of a second inferior (PR gdb/25410)
This fixes a latent bug exposed by the multi-target patch (5b6d1e4fa
"Multi-target support), and then fixes two other latent bugs exposed
by fixing that first latent bug.
The symptom described in the bug report is that starting a first
inferior, then trying to run a second (multi-threaded) inferior twice,
causes libthread_db to fail to load, along with other erratic
behavior:
(gdb) run
Starting program: /tmp/foo
warning: td_ta_new failed: generic error
Going a bit deeply, I found that if the two inferiors have different
symbols, we can see that just after inferior 2 exits, we are left with
inferior 2 selected, which is correct, but the symbols in scope belong
to inferior 1, which is obviously incorrect...
This problem is that there's a path in
scoped_restore_current_thread::restore() that switches to no thread
selected, and switches the current inferior, but leaves the current
program space as is, resulting in leaving the program space pointing
to the wrong program space (the one of the other inferior). This was
happening after handling TARGET_WAITKIND_NO_RESUMED, which is an event
that triggers after TARGET_WAITKIND_EXITED for the previous inferior
exit. Subsequent symbol lookups find the symbols of the wrong
inferior.
The fix is to use switch_to_inferior_no_thread in that problem spot.
This function was recently added along with the multi-target work
exactly for these situations.
As for testing, this patch adds a new testcase that tests symbol
printing just after inferior exit, which exercises the root cause of
the problem more directly. And then, to cover the use case described
in the bug too, it also exercises the lithread_db.so mis-loading, by
using TLS printing as a proxy for being sure that threaded debugging
was activated sucessfully. The testcase fails without the fix like
this, for the "print symbol just after exit" bits:
...
[Inferior 1 (process 8719) exited normally]
(gdb) PASS: gdb.multi/multi-re-run.exp: re_run_inf=1: iter=1: continue
until exit
print re_run_var_1
No symbol "re_run_var_1" in current context.
(gdb) FAIL: gdb.multi/multi-re-run.exp: re_run_inf=1: iter=1: print
re_run_var_1
...
And like this for the "libthread_db.so loading" bits:
(gdb) run
Starting program:
/home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.multi/multi-re-run/multi-re-run
warning: td_ta_new failed: generic error
[New LWP 27001]
Thread 1.1 "multi-re-run" hit Breakpoint 3, all_started () at
/home/pedro/gdb/binutils-gdb/build/../src/gdb/testsuite/gdb.multi/multi-re-run.c:44
44 }
(gdb) PASS: gdb.multi/multi-re-run.exp: re_run_inf=1: iter=2: running to
all_started in runto
print tls_var
Cannot find thread-local storage for LWP 27000, executable file
/home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.multi/multi-re-run/multi-re-run:
Cannot find thread-local variables on this target
(gdb) FAIL: gdb.multi/multi-re-run.exp: re_run_inf=1: iter=2: print
tls_var
As mentioned, that fix above goes on to expose a couple other latent
bugs. This commit fixes those as well.
The first latent bug exposed is in
infrun.c:handle_vfork_child_exec_or_exit. The current code is leaving
inf->pspace == NULL while calling clone_program_space. The idea was
to make it so that the breakpoints module doesn't use this inferior's
pspace to set breakpoints. With that, any
scoped_restore_current_thread use from within clone_program_space
tries to restore a NULL program space, which hits an assertion:
Attaching after Thread 0x7ffff74b8700 (LWP 27276) vfork to child process
27277]
[New inferior 2 (process 27277)]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
/home/pedro/gdb/binutils-gdb/build/../src/gdb/progspace.c:243:
internal-error: void set_current_program_space(program_space*): Assertion
`pspace != NULL' faile
d.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) FAIL:
gdb.threads/vfork-follow-child-exit.exp: detach-on-fork=off: continue (GDB
internal error)
That NULL pspace idea was legitimate, but it's no longer necessary,
since commit b2e586e850db ("Defer breakpoint reset when cloning
progspace for fork child"). So the fix is to just set the inferior's
program space earlier.
The other latent bug exposed is in exec.c. When exec_close is called
from the program_space destructor, it is purposedly called with a
current program space that is not the current inferior's program
space. The problem is that the multi-target work added some code to
remove_target_sections that loops over all inferiors, and uses
scoped_restore_current_thread to save/restore the previous
thread/inferior/frame state. This makes it so that exec_close returns
with the current program space set to the current inferior's program
space, which is exactly what we did not want. Then the program_space
destructor continues into free_all_objfiles, but it is now running
that method on the wrong program space, resulting in:
Reading symbols from
/home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.threads/fork-plus-threads/fork-plus-threads...
Reading symbols from /usr/lib/debug/usr/lib64/libpthread-2.26.so.debug...
Reading symbols from /usr/lib/debug/usr/lib64/libm-2.26.so.debug...
Reading symbols from /usr/lib/debug/usr/lib64/libc-2.26.so.debug...
Reading symbols from /usr/lib/debug/usr/lib64/ld-2.26.so.debug...
[Inferior 3 (process 9583) exited normally]
/home/pedro/gdb/binutils-gdb/build/../src/gdb/progspace.c:170:
internal-error: void program_space::free_all_objfiles(): Assertion `so->objfile
== 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/fork-plus-threads.exp: detach-on-fork=off: inferior 1 exited (GDB
internal error)
The fix is to use scoped_restore_current_pspace_and_thread instead of
scoped_restore_current_thread.
gdb/ChangeLog:
2020-01-24 Pedro Alves <palves@redhat.com>
PR gdb/25410
* thread.c (scoped_restore_current_thread::restore): Use
switch_to_inferior_no_thread.
* exec.c: Include "progspace-and-thread.h".
(add_target_sections, remove_target_sections):
scoped_restore_current_pspace_and_thread instead of
scoped_restore_current_thread.
* infrun.c (handle_vfork_child_exec_or_exit): Assign the pspace
and aspace to the inferior before calling clone_program_space.
Remove stale comment.
gdb/testsuite/ChangeLog:
2020-01-24 Pedro Alves <palves@redhat.com>
PR gdb/25410
* gdb.multi/multi-re-run-1.c: New.
* gdb.multi/multi-re-run-2.c: New.
* gdb.multi/multi-re-run.exp: New.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26180-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 24 19:00:57 2020
Return-Path: <gdb-prs-return-26180-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 80839 invoked by alias); 24 Jan 2020 19:00:57 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 80821 invoked by uid 48); 24 Jan 2020 19:00:56 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25410] Re-running second inferior fails with "td_ta_new
failed: generic error"
Date: Fri, 24 Jan 2020 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: simark at simark dot ca
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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-25410-4717-YdeVoMdScD@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25410-4717@http.sourceware.org/bugzilla/>
References: <bug-25410-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00095.txt
Content-length: 527
https://sourceware.org/bugzilla/show_bug.cgi?id=25410
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Simon Marchi <simark at simark dot ca> ---
Fixed by patch mentioned above.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26181-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 25 11:20:26 2020
Return-Path: <gdb-prs-return-26181-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 93253 invoked by alias); 25 Jan 2020 11:20:26 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 93100 invoked by uid 55); 25 Jan 2020 11:20:26 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17626] attach, detach, attach did not work
Date: Sat, 25 Jan 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-17626-4717-s3NIsrUZz9@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17626-4717@http.sourceware.org/bugzilla/>
References: <bug-17626-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00096.txt
Content-length: 11387
https://sourceware.org/bugzilla/show_bug.cgi?id=17626
--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Philippe Waroquiers
<philippe@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a2fedca99c622e1b523046d09f573b06de0207a6
commit a2fedca99c622e1b523046d09f573b06de0207a6
Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Date: Sat Dec 21 10:55:11 2019 +0100
Implement 'set/show exec-file-mismatch'.
This option allows to tell GDB to detect and possibly handle mismatched
exec-files.
A recurrent problem with GDB is that GDB uses the wrong exec-file
when using the attach/detach commands successively.
Also, in case the user specifies a file on the command line but attaches
to the wrong PID, this error is not made visible and gives a not user
understandable behaviour.
For example:
$ gdb
...
(gdb) atta 2682 ############################################ PID
running 'sleepers' executable
Attaching to process 2682
[New LWP 2683]
[New LWP 2684]
[New LWP 2685]
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007f5ff829f603 in select () at ../sysdeps/unix/syscall-template.S:84
84 ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) det
Detaching from program:
/home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers, process
2682
[Inferior 1 (process 2682) detached]
(gdb) atta 31069 ############################################ PID
running 'gdb' executable
Attaching to program:
/home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers, process
31069
Reading symbols from /lib64/ld-linux-x86-64.so.2...
Reading symbols from
/usr/lib/debug/.build-id/60/6df9c355103e82140d513bc7a25a635591c153.debug...
0x00007f43c23478a0 in ?? ()
(gdb) bt
#0 0x00007f43c23478a0 in ?? ()
#1 0x0000558909e3ad91 in ?? ()
#2 0x0000202962646700 in ?? ()
#3 0x00007ffc69c74e70 in ?? ()
#4 0x000055890c1d2350 in ?? ()
#5 0x0000000000000000 in ?? ()
(gdb)
The second attach has kept the executable of the first attach.
(in this case, 31069 is the PID of a GDB, that has nothing to do
with the first determined 'sleepers' executable).
Similarly, if specifying an executable, but attaching to a wrong pid,
we get:
gdb /home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers
...
Reading symbols from
/home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers...
(gdb) atta 31069 ############################################ PID
running 'gdb' executable
Attaching to program:
/home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers, process
31069
Reading symbols from /lib64/ld-linux-x86-64.so.2...
Reading symbols from
/usr/lib/debug/.build-id/60/6df9c355103e82140d513bc7a25a635591c153.debug...
0x00007f43c23478a0 in ?? ()
(gdb) bt
#0 0x00007f43c23478a0 in ?? ()
#1 0x0000558909e3ad91 in ?? ()
#2 0x0000202962646700 in ?? ()
#3 0x00007ffc69c74e70 in ?? ()
#4 0x000055890c1d2350 in ?? ()
#5 0x0000000000000000 in ?? ()
(gdb)
And it is unclear to the user what has happened/what is going wrong.
This patch series implements a new option:
(gdb) apropos exec-file-mismatch
set exec-file-mismatch -- Set exec-file-mismatch handling
(ask|warn|off).
show exec-file-mismatch -- Show exec-file-mismatch handling
(ask|warn|off).
(gdb) help set exec-file-mismatch
Set exec-file-mismatch handling (ask|warn|off).
Specifies how to handle a mismatch between the current exec-file name
loaded by GDB and the exec-file name automatically determined when
attaching
to a process:
ask - warn the user and ask whether to load the determined exec-file.
warn - warn the user, but do not change the exec-file.
off - do not check for mismatch.
"ask" means: in case of mismatch between the current exec-file name
and the automatically determined exec-file name of the PID we are attaching
to,
give a warning to the user and ask whether to load the automatically
determined
exec-file.
"warn" means: in case of mismatch, just give a warning to the user.
"off" means: do not check for mismatch.
This fixes PR gdb/17626.
There was a previous trial to fix this PR.
See https://sourceware.org/ml/gdb-patches/2015-07/msg00118.html
This trial was however only fixing the problem for the automatically
determined executable files when doing attach.
It was differentiating the 'user specified executable files' ("sticky")
from the executable files automatically found by GDB.
But such user specified sticky executables are in most cases due
to a wrong manipulation by the user, giving unexpected results
such as backtrace showing no function like in the above example.
This patch ensures that whenever a process executable can be
determined, that the user is warned if there is a mismatch.
The same tests as above then give:
(gdb) atta 2682
Attaching to process 2682
[New LWP 2683]
[New LWP 2684]
[New LWP 2685]
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007f5ff829f603 in select () at ../sysdeps/unix/syscall-template.S:84
84 ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) det
Detaching from program:
/home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers, process
2682
[Inferior 1 (process 2682) detached]
(gdb) atta 31069
Attaching to program:
/home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers, process
31069
warning: Mismatch between current exec-file
/home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers
and automatically determined exec-file
/bd/home/philippe/gdb/git/build_fixes/gdb/gdb
exec-file-mismatch handling is currently "ask"
Load new symbol table from
"/bd/home/philippe/gdb/git/build_fixes/gdb/gdb"? (y or n) y
Reading symbols from /bd/home/philippe/gdb/git/build_fixes/gdb/gdb...
Setting up the environment for debugging gdb.
...
Reading symbols from
/usr/lib/debug/.build-id/60/6df9c355103e82140d513bc7a25a635591c153.debug...
0x00007f43c23478a0 in __poll_nocancel () at
../sysdeps/unix/syscall-template.S:84
84 ../sysdeps/unix/syscall-template.S: No such file or directory.
(top-gdb) bt
During symbol reading: incomplete CFI data; unspecified registers (e.g.,
rax) at 0x7f43c23478ad
During symbol reading: unsupported tag: 'DW_TAG_unspecified_type'
During symbol reading: cannot get low and high bounds for subprogram DIE
at 0x12282a7
During symbol reading: Child DIE 0x12288ba and its abstract origin
0x1228b26 have different parents
During symbol reading: DW_AT_call_target target DIE has invalid low pc,
for referencing DIE 0x1229540 [in module
/bd/home/philippe/gdb/git/build_fixes/gdb/gdb]
#0 0x00007f43c23478a0 in __poll_nocancel () at
../sysdeps/unix/syscall-template.S:84
#1 0x0000558909e3ad91 in poll (__timeout=-1, __nfds=<optimized out>,
__fds=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2 gdb_wait_for_event (block=block@entry=1) at
../../fixes/gdb/event-loop.c:772
#3 0x0000558909e3aef4 in gdb_do_one_event () at
../../fixes/gdb/event-loop.c:347
#4 0x0000558909e3b085 in gdb_do_one_event () at
../../fixes/gdb/common/common-exceptions.h:219
#5 start_event_loop () at ../../fixes/gdb/event-loop.c:371
During symbol reading: Member function "~_Sp_counted_base" (offset
0x1c69bf7) is virtual but the vtable offset is not specified
During symbol reading: Multiple children of DIE 0x1c8f5a0 refer to DIE
0x1c8f0ee as their abstract origin
#6 0x0000558909ed3b78 in captured_command_loop () at
../../fixes/gdb/main.c:331
#7 0x0000558909ed4b6d in captured_main (data=<optimized out>) at
../../fixes/gdb/main.c:1174
#8 gdb_main (args=<optimized out>) at ../../fixes/gdb/main.c:1190
#9 0x0000558909c1e9a8 in main (argc=<optimized out>, argv=<optimized
out>) at ../../fixes/gdb/gdb.c:32
(top-gdb)
gdb /home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers
...
Reading symbols from
/home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers...
(gdb) atta 31069
Attaching to program:
/home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers, process
31069
warning: Mismatch between current exec-file
/home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers
and automatically determined exec-file
/bd/home/philippe/gdb/git/build_fixes/gdb/gdb
exec-file-mismatch handling is currently "ask"
Load new symbol table from
"/bd/home/philippe/gdb/git/build_fixes/gdb/gdb"? (y or n) y
Reading symbols from /bd/home/philippe/gdb/git/build_fixes/gdb/gdb...
Setting up the environment for debugging gdb.
....
In other words, it now works as intuitively expected by the user.
If ever the user gave the correct executable on the command line,
then attached to the wrong pid, then confirmed loading the wrong
executable,
the user can simply fix this by detaching, and attaching to the correct
pid,
GDB will then tell again to the user that the exec-file might better
be loaded.
The default value of "ask" is chosen instead of e.g. "warn" as in most
cases, switching of executable will be the correct action,
and in any case, the user can decide to not load the executable,
as GDB asks a confirmation to the user to load the new executable.
For settings "ask" and "warn", the new function validate_exec_file ()
tries to get the inferior pid exec file and compares it with the current
exec file. In case of mismatch, it warns the user and optionally load
the executable.
This function is called in the attach_command implementation to cover
most cases of attaching to a running process.
It must also be called in remote.c, as the attach command is not supported
for all types of remote gdbserver.
gdb/ChangeLog
2020-01-25 Philippe Waroquiers <philippe.waroquiers@skynet.be>
* exec.c (exec_file_mismatch_names, exec_file_mismatch_mode)
(show_exec_file_mismatch_command, set_exec_file_mismatch_command)
(validate_exec_file): New variables, enums, functions.
(exec_file_locate_attach, print_section_info): Style the filenames.
(_initialize_exec): Install show_exec_file_mismatch_command and
set_exec_file_mismatch_command.
* gdbcore.h (validate_exec_file): Declare.
* infcmd.c (attach_command): Call validate_exec_file.
* remote.c ( remote_target::remote_add_inferior): Likewise.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26182-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 25 12:20:15 2020
Return-Path: <gdb-prs-return-26182-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 25807 invoked by alias); 25 Jan 2020 12:20:15 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 25782 invoked by uid 48); 25 Jan 2020 12:20:15 -0000
From: "fakju666 at o2 dot pl" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25460] New: gdb could read build ID from separate debug
files
Date: Sat, 25 Jan 2020 12: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: fakju666 at o2 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: <bug-25460-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00097.txt
Content-length: 1658
https://sourceware.org/bugzilla/show_bug.cgi?id=25460
Bug ID: 25460
Summary: gdb could read build ID from separate debug files
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: fakju666 at o2 dot pl
Target Milestone: ---
Quoting from
https://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.html :
"For the “build ID” method, GDB looks in the .build-id subdirectory of each one
of the global debug directories for a file named nn/nnnnnnnn.debug, where nn
are the first 2 hex characters of the build ID bit string, and nnnnnnnn are the
rest of the bit string. (Real build ID strings are 32 or more hex characters,
not 10.)"
PROTIP:
gdb can read build ID's from the debug files stored in the directory pointed by
debug-file-directory. Proof of concept:
name@name:~/src/symbols$ readelf -n libxul.so.debug
Displaying notes found in: .note.gnu.build-id
Owner Data size Description
GNU 0x00000014 NT_GNU_BUILD_ID (unique build ID
bitstring)
Build ID: 82756fe906e7c61d27451c9ad7c4ac85b2288096
Currently, for 100 external symbol files, one needs to create up to 101
directories (including .build-id) and rename 100 symbol files (or create a
script that will do it). That is really dumb considering that the build ID is
contained within every symbol file included in debug-file-directory.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26183-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 25 13:37:05 2020
Return-Path: <gdb-prs-return-26183-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 8150 invoked by alias); 25 Jan 2020 13:37:05 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 8132 invoked by uid 48); 25 Jan 2020 13:37:05 -0000
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25460] gdb could read build ID from separate debug files
Date: Sat, 25 Jan 2020 13: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: 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: <bug-25460-4717-WlbC5jHjHm@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25460-4717@http.sourceware.org/bugzilla/>
References: <bug-25460-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00098.txt
Content-length: 355
https://sourceware.org/bugzilla/show_bug.cgi?id=25460
--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
That would require reading each and every file inside debug-file-directory to
find out which of them provides the desired build-id, which doesn't scale.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26184-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 25 14:30:48 2020
Return-Path: <gdb-prs-return-26184-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 58432 invoked by alias); 25 Jan 2020 14:30:47 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 58367 invoked by uid 48); 25 Jan 2020 14:30:36 -0000
From: "fakju666 at o2 dot pl" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25460] gdb could read build ID from separate debug files
Date: Sat, 25 Jan 2020 14: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: fakju666 at o2 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: <bug-25460-4717-gY0QLfV2Sv@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25460-4717@http.sourceware.org/bugzilla/>
References: <bug-25460-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00099.txt
Content-length: 934
https://sourceware.org/bugzilla/show_bug.cgi?id=25460
--- Comment #2 from Joshua Naismith <fakju666 at o2 dot pl> ---
I might be oblivious to specific corner cases that consume more time, but
reading a build ID seems to be a fast operation. It takes about 4 seconds to
scan over 2000 files on a slow VM:
name@name:/usr/bin$ find /usr/bin -type f | wc -l
2231
name@name:/usr/bin$ time find /usr/bin -type f -exec readelf -n {} \;
>/dev/null 2>&1
real 0m3.956s
user 0m2.795s
sys 0m1.121s
This is orders of magnitude faster than creating a directory/filename structure
for the corresponding number of symbol files. I think that would be simpler and
more intuitive for the end user as well (just specifying the dir and dropping
symbols there for gdb to pick up sounds like the most convenient scenario), but
that is not quantifiable.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26185-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Jan 25 23:51:57 2020
Return-Path: <gdb-prs-return-26185-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 77557 invoked by alias); 25 Jan 2020 23:51:57 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 77537 invoked by uid 48); 25 Jan 2020 23:51:57 -0000
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/25419] Looking for a solution for canon printer error
code b200
Date: Sat, 25 Jan 2020 23: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: 10.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fche 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: <bug-25419-4717-tMUZeZGB21@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25419-4717@http.sourceware.org/bugzilla/>
References: <bug-25419-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00100.txt
Content-length: 580
https://sourceware.org/bugzilla/show_bug.cgi?id=25419
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |fche at redhat dot com
Resolution|--- |INVALID
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
spam
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26186-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 10:36:57 2020
Return-Path: <gdb-prs-return-26186-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 45146 invoked by alias); 27 Jan 2020 10:36:57 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 45125 invoked by uid 48); 27 Jan 2020 10:36:57 -0000
From: "dinc.tarkan at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/25467] New: GDB cannot step over a function if the
following lines don't include and decision or branch
Date: Mon, 27 Jan 2020 10:36: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.9
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dinc.tarkan 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: <bug-25467-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00101.txt
Content-length: 4528
https://sourceware.org/bugzilla/show_bug.cgi?id=25467
Bug ID: 25467
Summary: GDB cannot step over a function if the following lines
don't include and decision or branch
Product: gdb
Version: 7.9
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
Assignee: unassigned at sourceware dot org
Reporter: dinc.tarkan at gmail dot com
Target Milestone: ---
I am having problems with debugging (stepping over) in c++ with gdb. I have an
in house developed rtos, runs on powerpc e500mc target. Software versions: gcc
4.9.2, gdb-server 5~(not sure the exact version), gdb 7.9.1 also tried 8.3.1.
Source file compiled with -g and -O0 parameters The problem seems to be
occuring in c++ after stepping over a function if the following lines don't
include any jump, branch instruction for a certain amount, gdb lost track where
to stop at function return and continue running. I've tried the same code on
x86-64 target version, it runs as expected without any issue. First thing
checked gdb-server's target porting part, then logged the messaging between the
host and the target. As you can see below the problem seems to be at gdb side
since gdb itself decides where to put breakpoint.
There is an example code exploits the error, I also added the log file. The
lines starting with "gdb:" are the messages from gdb to target. I don't include
the gdb-server's responses to avoid confusion. Other lines are printed by
target. <..> are the comments added by me later, tells the meaning of the code,
data or address, also what I did at that time. I also include the elf file's
related part to make it more understandable.
Here it what happens. At first I load my program to target, with auto start
disabled. The program is in memory and waiting for my command to run. Then I
attach to process for debugging. Gdb takes over and start communication, after
some handshaking and queries cathes the process. It wasn't running so it cathes
at the very beginnig, initialization code before main function @210106e8. So
gdb knows that i want to stop at my code (main), puts a breakpoint at main's
first instruction after functions stack operations @21010250. Then programs
runs on target and catches a trap exception at breakpoint. When execution stops
gdb removes the breakpoint (trap instruction) and puts back the original
instruction.
Later I do a step over which is line int i=0. Gdb sets on the trace mode and
starts the execution. Program cathes the trace exception after running the
first instruction. Since I am not in instruction stepping mode, gdb starts
execution again until the c line ends Gdb catches the second trace exception
and reaches the end of c line sets of the trace mode.
Now we are at the function call line and stepping over again. Gdb sets on the
trace mode and start executing the program. Program call the function and
catches the trace exception. Gdb sees it's not in the function (main) we are
interested in since we are stepping over, sets a breakpoint for function return
point. The program starts executing prints the message and function returns and
hits the breakpoint @2101025c. So far so good.
It should have stopped here, since my initial command, which is stepping over
function call, is completed but continues.
Now as you can see on the log output gdb starts queries about code block, which
it has done before but not with much greater number, looking for 52
instructions ahead (which are all i++). Gdb removes the breakpoint and sets the
trace mode on and executes the first instruciton of i++ command. After the
first intruction executed and the exception catched, again the 52 instruction
queries. After all this, what gdb should do is to set on the trace mode and
start execeuting. Instead of this, it put a breakpoint before the current pc,
at the address of the instruction it just executed. With trace mode is off,
when the execution starts the program executes to completion since the
breakpoint will not be hit.
If I reduce the number of i++'s to the point, where in 52 instruction query gdb
will see some jump or branch, everything works as expected.
And if the same code compiled as c, not c++, again everything works as
expected.
As I mentioned earlier, same code running on a x86 target, everyting works as
expected.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26187-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 10:40:03 2020
Return-Path: <gdb-prs-return-26187-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 85942 invoked by alias); 27 Jan 2020 10:40:02 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 85924 invoked by uid 48); 27 Jan 2020 10:40:02 -0000
From: "dinc.tarkan at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/25467] GDB cannot step over a function if the following
lines don't include and decision or branch
Date: Mon, 27 Jan 2020 10: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.9
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dinc.tarkan 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: <bug-25467-4717-gXKmDh9O7P@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25467-4717@http.sourceware.org/bugzilla/>
References: <bug-25467-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00102.txt
Content-length: 625
https://sourceware.org/bugzilla/show_bug.cgi?id=25467
Tarkan <dinc.tarkan at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dinc.tarkan at gmail dot com
--- Comment #1 from Tarkan <dinc.tarkan at gmail dot com> ---
Created attachment 12231
--> https://sourceware.org/bugzilla/attachment.cgi?id=12231&action=edit
includes the code, terminal output and part of the elf file
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26188-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 13:06:19 2020
Return-Path: <gdb-prs-return-26188-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 80745 invoked by alias); 27 Jan 2020 13:06:19 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 80726 invoked by uid 48); 27 Jan 2020 13:06:18 -0000
From: "quae at daurnimator dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug varobj/25470] New: Assertion hit in maybe_negate_by_bytes
Date: Mon, 27 Jan 2020 13:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: varobj
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: quae at daurnimator dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25470-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00103.txt
Content-length: 1669
https://sourceware.org/bugzilla/show_bug.cgi?id=25470
Bug ID: 25470
Summary: Assertion hit in maybe_negate_by_bytes
Product: gdb
Version: 8.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: varobj
Assignee: unassigned at sourceware dot org
Reporter: quae at daurnimator dot com
Target Milestone: ---
While debugging a remote riscv program I got the following:
> (gdb) finish
> Run till exit from #0 0x20040e38 in fomu.timer0.TIMER0.value () at /home/daurnimator/src/fomu-workshop/riscv-zig-blink/src/fomu/timer0.zig:86
> Note: CPU is currently in a trap: Supervisor external interrupt at 0x000007c8
> 0x20040c9c in msleep (ms=80) at main.zig:99
> 99 if (fomu.TIMER0.value() == 0) break;
> Value returned is $4 = 1385182720
> (gdb) finish
> Run till exit from #0 0x20040c9c in msleep (ms=80) at main.zig:99
> Note: CPU is currently in a trap: Supervisor external interrupt at 0x000007c8
> main () at main.zig:107
> 107 while (true) : (i +%= 1) {
> Value returned is $5 =
> valprint.c:1607: internal-error: bool maybe_negate_by_bytes(const gdb_byte*, unsigned int, bfd_endian, gdb::byte_vector*): Assertion `len > 0' 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:
> <http://www.gnu.org/software/gdb/bugs/>.
Host machine is linux x86_64 running GNU gdb (GDB) 8.3.1
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26189-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 13:52:01 2020
Return-Path: <gdb-prs-return-26189-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 54680 invoked by alias); 27 Jan 2020 13:52:00 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 54658 invoked by uid 48); 27 Jan 2020 13:52:00 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25471] New: gdb hangs repeating "Couldn't get registers: No
such process" warning after external SIGKILL
Date: Mon, 27 Jan 2020 13:52: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: vries 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: <bug-25471-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00104.txt
Content-length: 2366
https://sourceware.org/bugzilla/show_bug.cgi?id=25471
Bug ID: 25471
Summary: gdb hangs repeating "Couldn't get registers: No such
process" warning after external SIGKILL
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Consider test-case sleep.c:
...
#include <pthread.h>
#include <unistd.h>
#if THREAD
static void *
fun (void *dummy)
{
while (1)
sleep (1);
return NULL;
}
#endif
int
main (void)
{
#if THREAD
pthread_t thread;
pthread_create (&thread, NULL, fun, NULL);
#endif
while (1)
sleep (1);
return 0;
}
...
When compiled as single-threaded app:
...
$ gcc sleep.c -lpthread -DTHREAD=0
...
we get this debug session:
...
$ gdb -q a.out
Reading symbols from a.out...
(gdb) r
Starting program: /data/gdb_versions/devel/a.out
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
^C
Program received signal SIGINT, Interrupt.
0x00007ffff78c50c1 in nanosleep () from /lib64/libc.so.6
(gdb) shell killall -9 a.out
(gdb) c
Continuing.
Program terminated with signal SIGKILL, Killed.
The program no longer exists.
(gdb) q
...
But then, when we upgrade to a multi-threaded app:
...
$ gcc sleep.c -lpthread -DTHREAD=1
...
we get instead:
...
$ gdb -q a.out
Reading symbols from a.out...
(gdb) r
Starting program: /data/gdb_versions/devel/a.out
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff77fe700 (LWP 13587)]
^C
Thread 1 "a.out" received signal SIGINT, Interrupt.
0x00007ffff78c50f0 in nanosleep () from /lib64/libc.so.6
(gdb) shell killall -9 a.out
(gdb) c
Continuing.
Couldn't get registers: No such process.
Couldn't get registers: No such process.
(gdb) Couldn't get registers: No such process.
(gdb) Couldn't get registers: No such process.
(gdb) Couldn't get registers: No such process.
(gdb) Couldn't get registers: No such process.
<repeat>
...
GDB hangs at this point, is unresponsive to ^C, and the only thing left to do
is killall gdb.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26190-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 13:55:53 2020
Return-Path: <gdb-prs-return-26190-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 68014 invoked by alias); 27 Jan 2020 13:55:52 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 67993 invoked by uid 48); 27 Jan 2020 13:55:52 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25471] gdb hangs repeating "Couldn't get registers: No such
process" warning after external SIGKILL
Date: Mon, 27 Jan 2020 13: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: vries 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: <bug-25471-4717-ORbxep2rY4@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25471-4717@http.sourceware.org/bugzilla/>
References: <bug-25471-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00105.txt
Content-length: 1027
https://sourceware.org/bugzilla/show_bug.cgi?id=25471
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
With 8.3 branch, we have instead:
...
$ gdb -q a.out
Reading symbols from a.out...
(gdb) r
Starting program: /data/gdb_versions/devel/a.out
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff77fe700 (LWP 13832)]
^C
Thread 1 "a.out" received signal SIGINT, Interrupt.
0x00007ffff78c50f0 in nanosleep () from /lib64/libc.so.6
(gdb) shell killall -9 a.out
(gdb) c
Continuing.
Couldn't get registers: No such process.
Couldn't get registers: No such process.
(gdb) [Thread 0x7ffff77fe700 (LWP 13832) exited]
Program terminated with signal SIGKILL, Killed.
The program no longer exists.
^CQuit
(gdb) q
...
Here we don't have the repeating warning (other than the initial two), and the
hang is less severe: using ^C gets us back to the gdb prompt.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26191-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 14:19:47 2020
Return-Path: <gdb-prs-return-26191-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 101216 invoked by alias); 27 Jan 2020 14:19:46 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 101195 invoked by uid 48); 27 Jan 2020 14:19:46 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25471] gdb hangs repeating "Couldn't get registers: No such
process" warning after external SIGKILL
Date: Mon, 27 Jan 2020 14: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: vries 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: <bug-25471-4717-yciOHomvGq@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25471-4717@http.sourceware.org/bugzilla/>
References: <bug-25471-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00106.txt
Content-length: 335
https://sourceware.org/bugzilla/show_bug.cgi?id=25471
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> With 8.3 branch, we have instead:
Likewise wise for gdb-9-branch, and its branch point.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26192-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 14:49:41 2020
Return-Path: <gdb-prs-return-26192-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 21656 invoked by alias); 27 Jan 2020 14:49:40 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 21636 invoked by uid 48); 27 Jan 2020 14:49:40 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug varobj/25470] Assertion hit in maybe_negate_by_bytes
Date: Mon, 27 Jan 2020 14:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: varobj
X-Bugzilla-Version: 8.3.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: <bug-25470-4717-TYcqNMMIFJ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25470-4717@http.sourceware.org/bugzilla/>
References: <bug-25470-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00107.txt
Content-length: 1095
https://sourceware.org/bugzilla/show_bug.cgi?id=25470
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to daurnimator from comment #0)
> > (gdb) finish
> > Run till exit from #0 0x20040c9c in msleep (ms=80) at main.zig:99
What is the type of this function?
You can try "ptype msleep" for example.
> > valprint.c:1607: internal-error: bool maybe_negate_by_bytes(const gdb_byte*, unsigned int, bfd_endian, gdb::byte_vector*): Assertion `len > 0' failed.
Obviously this shouldn't happen but I wonder how we get there.
It seems like maybe if the DWARF specified an integer type of 0 width.
Maybe examining the DWARF would be good... how big is the executable?
If it's not too large, can you attach it to the bug?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26193-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 14:58:25 2020
Return-Path: <gdb-prs-return-26193-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 36779 invoked by alias); 27 Jan 2020 14:58:24 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 36760 invoked by uid 48); 27 Jan 2020 14:58:24 -0000
From: "quae at daurnimator dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug varobj/25470] Assertion hit in maybe_negate_by_bytes
Date: Mon, 27 Jan 2020 14:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: varobj
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: quae at daurnimator dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25470-4717-863SsZBADc@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25470-4717@http.sourceware.org/bugzilla/>
References: <bug-25470-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00108.txt
Content-length: 1054
https://sourceware.org/bugzilla/show_bug.cgi?id=25470
--- Comment #2 from daurnimator <quae at daurnimator dot com> ---
(In reply to Tom Tromey from comment #1)
> (In reply to daurnimator from comment #0)
>
> > > (gdb) finish
> > > Run till exit from #0 0x20040c9c in msleep (ms=80) at main.zig:99
>
> What is the type of this function?
> You can try "ptype msleep" for example.
type = void (usize)
> > > valprint.c:1607: internal-error: bool maybe_negate_by_bytes(const gdb_byte*, unsigned int, bfd_endian, gdb::byte_vector*): Assertion `len > 0' failed.
>
> Obviously this shouldn't happen but I wonder how we get there.
> It seems like maybe if the DWARF specified an integer type of 0 width.
This is possible, zig permits 0-sized integers.
> Maybe examining the DWARF would be good... how big is the executable?
> If it's not too large, can you attach it to the bug?
sure. FYI the code is from https://github.com/im-tomu/fomu-workshop/pull/140
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26194-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 14:59:36 2020
Return-Path: <gdb-prs-return-26194-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 47056 invoked by alias); 27 Jan 2020 14:59:35 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 47034 invoked by uid 48); 27 Jan 2020 14:59:35 -0000
From: "quae at daurnimator dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug varobj/25470] Assertion hit in maybe_negate_by_bytes
Date: Mon, 27 Jan 2020 14:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: varobj
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: quae at daurnimator dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: <bug-25470-4717-ycitlUWOjs@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25470-4717@http.sourceware.org/bugzilla/>
References: <bug-25470-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00109.txt
Content-length: 461
https://sourceware.org/bugzilla/show_bug.cgi?id=25470
--- Comment #3 from daurnimator <quae at daurnimator dot com> ---
Created attachment 12233
--> https://sourceware.org/bugzilla/attachment.cgi?id=12233&action=edit
elf file demonstrating issue
riscv-zig-blink: ELF 32-bit LSB executable, UCB RISC-V, version 1 (SYSV),
statically linked, with debug_info, not stripped
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26195-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 15:13:35 2020
Return-Path: <gdb-prs-return-26195-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 71879 invoked by alias); 27 Jan 2020 15:13:34 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 70742 invoked by uid 48); 27 Jan 2020 15:13:34 -0000
From: "narwhalx42 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25297] Segmentation fault when using Python 3.8 gdb.execute
on target extended-remote
Date: Mon, 27 Jan 2020 15: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: narwhalx42 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: <bug-25297-4717-pRvFS1L5E3@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25297-4717@http.sourceware.org/bugzilla/>
References: <bug-25297-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00110.txt
Content-length: 243
https://sourceware.org/bugzilla/show_bug.cgi?id=25297
--- Comment #1 from narwhalx42 at gmail dot com ---
Any ideas? This has been plaguing me for a while now.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26196-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 15:45:30 2020
Return-Path: <gdb-prs-return-26196-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 118481 invoked by alias); 27 Jan 2020 15:45:28 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 115494 invoked by uid 48); 27 Jan 2020 15:45:27 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug varobj/25470] Assertion hit in maybe_negate_by_bytes
Date: Mon, 27 Jan 2020 15:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: varobj
X-Bugzilla-Version: 8.3.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: <bug-25470-4717-RSXoQZBw8t@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25470-4717@http.sourceware.org/bugzilla/>
References: <bug-25470-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00111.txt
Content-length: 831
https://sourceware.org/bugzilla/show_bug.cgi?id=25470
--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
Yeah, that's what is going on:
<1><dc3>: Abbrev Number: 5 (DW_TAG_base_type)
<dc4> DW_AT_name : (indirect string, offset: 0x1f86): void
<dc8> DW_AT_encoding : 5 (signed)
<dc9> DW_AT_byte_size : 0
It's weird to encode "void" this way.
Normally it's done by leaving off the return type;
from DWARF 5, section 3.3.2:
Debugging information entries for C void functions should not have an attribute
for the
return type.
Anyway, that's fine, gdb deals with weird DWARF all the time.
The main question I have is whether 0-sized integers have any
real semantics. Like, do they have a value?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26197-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 15:50:11 2020
Return-Path: <gdb-prs-return-26197-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 74939 invoked by alias); 27 Jan 2020 15:50:10 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 74915 invoked by uid 48); 27 Jan 2020 15:50:10 -0000
From: "quae at daurnimator dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug varobj/25470] Assertion hit in maybe_negate_by_bytes
Date: Mon, 27 Jan 2020 15:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: varobj
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: quae at daurnimator dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25470-4717-rMd3zV4M3Z@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25470-4717@http.sourceware.org/bugzilla/>
References: <bug-25470-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00112.txt
Content-length: 1073
https://sourceware.org/bugzilla/show_bug.cgi?id=25470
--- Comment #5 from daurnimator <quae at daurnimator dot com> ---
(In reply to Tom Tromey from comment #4)
> Yeah, that's what is going on:
>
> <1><dc3>: Abbrev Number: 5 (DW_TAG_base_type)
> <dc4> DW_AT_name : (indirect string, offset: 0x1f86): void
> <dc8> DW_AT_encoding : 5 (signed)
> <dc9> DW_AT_byte_size : 0
>
> It's weird to encode "void" this way.
> Normally it's done by leaving off the return type;
> from DWARF 5, section 3.3.2:
>
> Debugging information entries for C void functions should not have an
> attribute for the
> return type.
>
>
> Anyway, that's fine, gdb deals with weird DWARF all the time.
> The main question I have is whether 0-sized integers have any
> real semantics. Like, do they have a value?
Which symbol/function return type is it you're looking at?
Zig does have different 0 bit types (see
https://ziglang.org/documentation/master/#Zero-Bit-Types )
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26198-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 16:11:39 2020
Return-Path: <gdb-prs-return-26198-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 63165 invoked by alias); 27 Jan 2020 16:11:38 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 63127 invoked by uid 48); 27 Jan 2020 16:11:37 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25471] gdb hangs repeating "Couldn't get registers: No such
process" warning after external SIGKILL
Date: Mon, 27 Jan 2020 16: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: vries 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: <bug-25471-4717-hjosv7cw71@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25471-4717@http.sourceware.org/bugzilla/>
References: <bug-25471-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00113.txt
Content-length: 5290
https://sourceware.org/bugzilla/show_bug.cgi?id=25471
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #2)
> (In reply to Tom de Vries from comment #1)
> > With 8.3 branch, we have instead:
>
> Likewise wise for gdb-9-branch, and its branch point.
bisected change in behaviour to:
commit 873657b9e824943ae44c12966c29cbbcd21c986f
Author: Pedro Alves <palves@redhat.com>
Date: Fri Jan 10 20:05:41 2020 +0000
Preserve selected thread in all-stop w/ background execution
In non-stop mode, if you resume the program in the background (with
"continue&", for example), then gdb makes sure to not switch the
current thread behind your back. That means that you can be sure that
the commands you type apply to the thread you selected, even if some
other thread that was running in the background hits some event just
while you're typing.
In all-stop mode, however, if you resume the program in the
background, gdb let's the current thread switch behind your back.
This is bogus, of course. All-stop and non-stop background
resumptions should behave the same.
This patch fixes that, and adds a testcase that exposes the bad
behavior in current master.
The fork-running-state.exp changes are necessary because that
preexisting testcase was expecting the old behavior:
Before:
continue &
Continuing.
(gdb)
[Attaching after process 8199 fork to child process 8203]
[New inferior 2 (process 8203)]
info threads
Id Target Id Frame
1.1 process 8199 "fork-running-st" (running)
* 2.1 process 8203 "fork-running-st" (running)
(gdb)
After:
continue &
Continuing.
(gdb)
[Attaching after process 24660 fork to child process 24664]
[New inferior 2 (process 24664)]
info threads
Id Target Id Frame
* 1.1 process 24660 "fork-running-st" (running)
2.1 process 24664 "fork-running-st" (running)
(gdb)
Here we see that before this patch GDB switches current inferior to
the new inferior behind the user's back, as a side effect of handling
the fork.
The delete_exited_threads call in inferior_appeared is there to fix an
issue that Baris found in a previous version of this patch. The
fetch_inferior_event change increases the refcount of the current
thread, and in case the fetched inferior event denotes a thread exit,
the thread will not be deleted right away. A non-deleted but exited
thread stays in the inferior's thread list. This, in turn, causes the
"init_thread_list" call in inferior.c to be skipped. A consequence is
that the global thread ID counter is not restarted if the current
thread exits, and then the inferior is restarted:
(gdb) start
Temporary breakpoint 1 at 0x4004d6: file main.c, line 21.
Starting program: /tmp/main
Temporary breakpoint 1, main () at main.c:21
21 foo ();
(gdb) info threads -gid
Id GId Target Id Frame
* 1 1 process 16106 "main" main () at main.c:21
(gdb) c
Continuing.
[Inferior 1 (process 16106) exited normally]
(gdb) start
Temporary breakpoint 2 at 0x4004d6: file main.c, line 21.
Starting program: /tmp/main
Temporary breakpoint 2, main () at main.c:21
21 foo ();
(gdb) info threads -gid
Id GId Target Id Frame
* 1 2 process 16138 "main" main () at main.c:21
^^^
Notice that GId == 2 above. It should have been "1" instead.
The new tids-git-reset.exp testcase exercises the problem above.
gdb/ChangeLog:
2020-01-10 Pedro Alves <palves@redhat.com>
* gdbthread.h (scoped_restore_current_thread)
<dont_restore, restore, m_dont_restore>: Declare.
* thread.c (thread_alive): Add assertion. Return bool.
(switch_to_thread_if_alive): New.
(prune_threads): Switch inferior/thread.
(print_thread_info_1): Switch thread before calling target methods.
(scoped_restore_current_thread::restore): New, factored out from
...
(scoped_restore_current_thread::~scoped_restore_current_thread):
... this.
(scoped_restore_current_thread::scoped_restore_current_thread):
Add assertion.
(thread_apply_all_command, thread_select): Use
switch_to_thread_if_alive.
gdb/testsuite/ChangeLog:
2020-01-10 Pedro Alves <palves@redhat.com>
* gdb.base/fork-running-state.exp (do_test): Adjust expected
output.
* gdb.threads/async.c: New.
* gdb.threads/async.exp: New.
* gdb.multi/tids-gid-reset.c: New.
* gdb.multi/tids-gid-reset.exp: New.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26199-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 16:14:47 2020
Return-Path: <gdb-prs-return-26199-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 71396 invoked by alias); 27 Jan 2020 16:14:47 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 71370 invoked by uid 48); 27 Jan 2020 16:14:47 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug varobj/25470] Assertion hit in maybe_negate_by_bytes
Date: Mon, 27 Jan 2020 16:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: varobj
X-Bugzilla-Version: 8.3.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: <bug-25470-4717-6sNf6cWTJd@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25470-4717@http.sourceware.org/bugzilla/>
References: <bug-25470-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00114.txt
Content-length: 868
https://sourceware.org/bugzilla/show_bug.cgi?id=25470
--- Comment #6 from Tom Tromey <tromey at sourceware dot org> ---
> Which symbol/function return type is it you're looking at?
msleep:
<1><d9f>: Abbrev Number: 14 (DW_TAG_subprogram)
<da0> DW_AT_low_pc : 0x20040c38
<da4> DW_AT_high_pc : 0xac
<da8> DW_AT_frame_base : 1 byte block: 58 (DW_OP_reg8 (r8))
<daa> DW_AT_name : (indirect string, offset: 0x18e8): msleep
<dae> DW_AT_decl_file : 11
<daf> DW_AT_decl_line : 93
<db0> DW_AT_type : <0xdc3>
> Zig does have different 0 bit types (see
> https://ziglang.org/documentation/master/#Zero-Bit-Types )
Thanks.
FWIW I wouldn't be surprised if there are also gdb bugs involving pointers
to 0-bit types.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26200-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Jan 27 16:25:57 2020
Return-Path: <gdb-prs-return-26200-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 83865 invoked by alias); 27 Jan 2020 16:25:56 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 83839 invoked by uid 48); 27 Jan 2020 16:25:56 -0000
From: "andrew at ziglang dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug varobj/25470] Assertion hit in maybe_negate_by_bytes
Date: Mon, 27 Jan 2020 16:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: varobj
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: andrew at ziglang 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: <bug-25470-4717-boQS8qVF2w@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25470-4717@http.sourceware.org/bugzilla/>
References: <bug-25470-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00115.txt
Content-length: 2352
https://sourceware.org/bugzilla/show_bug.cgi?id=25470
--- Comment #7 from Andrew Kelley <andrew at ziglang dot org> ---
I'm not sure whether this is a bug in Zig or LLVM (Zig's backend).
Zig's "void" does use signed 0 bit integer as the debug info to LLVM:
https://github.com/ziglang/zig/blob/d8965002593c111069862e7de06402ee77b2b614/src/codegen.cpp#L8028-L8030
However, that is more of a placeholder. My understanding was that LLVM's API
for creating debug info functions looked for this pattern and emitted the
correct DWARF.
A task on Zig project's end is to examine LLVM API to look for how to specify
void return types properly. Seeing how clang does it would be a good start.
> Anyway, that's fine, gdb deals with weird DWARF all the time.
> The main question I have is whether 0-sized integers have any
> real semantics. Like, do they have a value?
It makes me happy to see gdb devs considering 0 sized integers seriously (and
presumably non-power-of-two sized integers?). Here's how it seems like they
should work to me:
* 16 bit unsigned integer has the range [0, pow(2, 16)), which is [0, 65535]
* 8 bit unsigned integer has the range [0, pow(2, 8)), which is [0, 255]
* 4 bit unsigned integer has the range [0, pow(2, 4)), which is [0, 15]
* 3 bit unsigned integer has the range [0, pow(2, 3)), which is [0, 7]
* 2 bit unsigned integer has the range [0, pow(2, 2)), which is [0, 3]
* 1 bit unsigned integer has the range [0, pow(2, 1)), which is [0, 1]
* 0 bit unsigned integer has the range [0, pow(2, 0)), which is [0, 0]
So a 0 bit unsigned integer would unconditionally have the value 0. (In zig an
integer with 0 bits is always compile-time known to be 0)
Likewise with signed ints:
* 8 bit signed integer has the range [-pow(2, 8 - 1), pow(2, 8 - 1)), which is
[-128, 127]
* 1 bit signed integer has the range [-pow(2, 1 - 1), pow(2, 1 - 1)), which is
[-1, 0]
* 0 bit signed integer has the range [-pow(2, 0 - 1), pow(2, 0 - 1)), which is
[-0.5 to 0.5), which has only 1 integer in the range, which is 0.
A bit more math to justify, but again signed 0 bit integer always has the value
0.
I believe that this can be justified with math, and would be valid for any
programming language. This is not Zig-specific.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26201-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 28 09:26:41 2020
Return-Path: <gdb-prs-return-26201-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 62920 invoked by alias); 28 Jan 2020 09:26:41 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 62897 invoked by uid 48); 28 Jan 2020 09:26:40 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25471] gdb hangs repeating "Couldn't get registers: No such
process" warning after external SIGKILL
Date: Tue, 28 Jan 2020 09: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: vries 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: <bug-25471-4717-rz3hpdU9A4@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25471-4717@http.sourceware.org/bugzilla/>
References: <bug-25471-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00116.txt
Content-length: 996
https://sourceware.org/bugzilla/show_bug.cgi?id=25471
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #3)
> (In reply to Tom de Vries from comment #2)
> > (In reply to Tom de Vries from comment #1)
> > > With 8.3 branch, we have instead:
> >
> > Likewise wise for gdb-9-branch, and its branch point.
>
> bisected change in behaviour to:
>
> commit 873657b9e824943ae44c12966c29cbbcd21c986f
> Author: Pedro Alves <palves@redhat.com>
> Date: Fri Jan 10 20:05:41 2020 +0000
>
> Preserve selected thread in all-stop w/ background execution
>
The difference seems to come from a new exception in:
...
scoped_restore_current_thread::scoped_restore_current_thread ()
...
m_selected_frame_id = get_frame_id (frame);
...
which gets called from fetch_inferior_event.
Catching the exception reverts back the old behaviour.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26202-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 28 09:35:21 2020
Return-Path: <gdb-prs-return-26202-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 76920 invoked by alias); 28 Jan 2020 09:35:20 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 76888 invoked by uid 48); 28 Jan 2020 09:35:18 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25471] gdb hangs repeating "Couldn't get registers: No such
process" warning after external SIGKILL
Date: Tue, 28 Jan 2020 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: vries 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: <bug-25471-4717-DzzCxZmiLa@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25471-4717@http.sourceware.org/bugzilla/>
References: <bug-25471-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00117.txt
Content-length: 1144
https://sourceware.org/bugzilla/show_bug.cgi?id=25471
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
Testing this tentative patch on top of bisected-to commit:
...
diff --git a/gdb/thread.c b/gdb/thread.c
index 630899c8cb8..5a4213e95b9 100644
--- a/gdb/thread.c
+++ b/gdb/thread.c
@@ -1407,6 +1407,8 @@ scoped_restore_current_thread::restore ()
scoped_restore_current_thread::~scoped_restore_current_thread ()
{
+ if (m_inf == NULL)
+ return;
if (!m_dont_restore)
{
try
@@ -1451,7 +1453,17 @@
scoped_restore_current_thread::scoped_restore_current_thread ()
else
frame = NULL;
- m_selected_frame_id = get_frame_id (frame);
+ try
+ {
+ m_selected_frame_id = get_frame_id (frame);
+ }
+ catch (const gdb_exception &ex)
+ {
+ m_inf = NULL;
+ m_selected_frame_id = null_frame_id;
+ m_selected_frame_level = -1;
+ return;
+ }
m_selected_frame_level = frame_relative_level (frame);
tp->incref ();
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26203-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 28 11:19:17 2020
Return-Path: <gdb-prs-return-26203-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 77885 invoked by alias); 28 Jan 2020 11:19:17 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 77867 invoked by uid 48); 28 Jan 2020 11:19:17 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] New: FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Tue, 28 Jan 2020 11:19: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: vries 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: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00118.txt
Content-length: 2291
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
Bug ID: 25475
Summary: FAIL: gdb.server/solib-list.exp: non-stop 0/1: target
remote (got interactive prompt)
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With current master, I see two new failures:
...
FAIL: gdb.server/solib-list.exp: non-stop 0: target remote (got interactive
prompt)
FAIL: gdb.server/solib-list.exp: non-stop 1: target remote (got interactive
prompt)
...
In more detail:
...
(gdb) PASS: gdb.server/solib-list.exp: non-stop 0: file binfile
target remote localhost:2346
Remote debugging using localhost:2346
warning: Mismatch between current exec-file
/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/solib-list/solib-list
and automatically determined exec-file /lib64/ld-2.26.so
exec-file-mismatch handling is currently "ask"
Load new symbol table from "/lib64/ld-2.26.so"? (y or n) n
warning: loading /lib64/ld-2.26.so Not confirmed.
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...
Reading /lib64/ld-2.26.so-2.26-lp151.18.7.x86_64.debug from remote target...
Reading /lib64/.debug/ld-2.26.so-2.26-lp151.18.7.x86_64.debug from remote
target...
Reading
/data/gdb_versions/devel/install/lib64/debug//lib64/ld-2.26.so-2.26-lp151.18.7.x86_64.debug
from remote target...
Reading
/data/gdb_versions/devel/install/lib64/debug/lib64//ld-2.26.so-2.26-lp151.18.7.x86_64.debug
from remote target...
Reading
target:/data/gdb_versions/devel/install/lib64/debug/lib64//ld-2.26.so-2.26-lp151.18.7.x86_64.debug
from remote target...
(No debugging symbols found in target:/lib64/ld-linux-x86-64.so.2)
0x00007ffff7dd7ea0 in ?? ()
(gdb) FAIL: gdb.server/solib-list.exp: non-stop 0: target remote (got
interactive prompt)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26204-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 28 12:44:51 2020
Return-Path: <gdb-prs-return-26204-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 76073 invoked by alias); 28 Jan 2020 12:44:51 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 76045 invoked by uid 48); 28 Jan 2020 12:44:50 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Tue, 28 Jan 2020 12: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: vries 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: <bug-25475-4717-P6TC6PPjRb@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/>
References: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00119.txt
Content-length: 790
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philippe.waroquiers@skynet.
| |be
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Bisect to:
...
a2fedca99c622e1b523046d09f573b06de0207a6 is the first bad commit
commit a2fedca99c622e1b523046d09f573b06de0207a6
Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Date: Sat Dec 21 10:55:11 2019 +0100
Implement 'set/show exec-file-mismatch'.
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26205-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 28 13:14:14 2020
Return-Path: <gdb-prs-return-26205-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 30592 invoked by alias); 28 Jan 2020 13:14:13 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 30570 invoked by uid 48); 28 Jan 2020 13:14:13 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Tue, 28 Jan 2020 13: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: vries 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: <bug-25475-4717-xMiTOxTxnX@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/>
References: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00120.txt
Content-length: 715
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Fixed by:
...
diff --git a/gdb/testsuite/gdb.server/solib-list.exp
b/gdb/testsuite/gdb.server/solib-list.exp
index 5471734e031..45638894f0b 100644
--- a/gdb/testsuite/gdb.server/solib-list.exp
+++ b/gdb/testsuite/gdb.server/solib-list.exp
@@ -47,6 +47,7 @@ foreach nonstop { 0 1 } { with_test_prefix "non-stop
$nonstop" {
# for ${interp_system}.
gdb_exit
gdb_start
+ gdb_test_no_output "set exec-file-mismatch off"
gdb_reinitialize_dir $srcdir/$subdir
gdb_load_shlib ${binlibfile}
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26206-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Jan 28 13:16:17 2020
Return-Path: <gdb-prs-return-26206-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 59986 invoked by alias); 28 Jan 2020 13:16:16 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 59929 invoked by uid 48); 28 Jan 2020 13:16:12 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25471] gdb hangs repeating "Couldn't get registers: No such
process" warning after external SIGKILL
Date: Tue, 28 Jan 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25471-4717-WwfkzEe4qX@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25471-4717@http.sourceware.org/bugzilla/>
References: <bug-25471-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00121.txt
Content-length: 365
https://sourceware.org/bugzilla/show_bug.cgi?id=25471
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #5)
> Testing this tentative patch on top of bisected-to commit:
That went ok, as well as testing on top of current master.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26207-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 08:16:30 2020
Return-Path: <gdb-prs-return-26207-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 76586 invoked by alias); 29 Jan 2020 08:16:28 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 76552 invoked by uid 48); 29 Jan 2020 08:16:27 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25478] New: gdb hangs after external SIGKILL
Date: Wed, 29 Jan 2020 08:16: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: vries 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: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00122.txt
Content-length: 2265
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
Bug ID: 25478
Summary: gdb hangs after external SIGKILL
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Consider the test-case sleep.c from PR25471.
When compiled as multithreaded app:
...
$ gcc sleep.c -lpthread -DTHREAD=1
...
we have this debug session:
...
$ gdb -ex "set prompt (master-gdb) " --args gdb --args a.out
Reading symbols from ./gdb...
(master-gdb) b stop_all_threads
Breakpoint 1 at 0x6d048b: file /data/gdb_versions/devel/src/gdb/infrun.c, line
4683.
(master-gdb) r
Starting program: /data/gdb_versions/devel/gdb --args a.out
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff3581700 (LWP 24930)]
[New Thread 0x7ffff2d80700 (LWP 24931)]
[New Thread 0x7ffff257f700 (LWP 24932)]
[Detaching after vfork from child process 24933]
[New Thread 0x7ffff1a66700 (LWP 24934)]
[New Thread 0x7ffff1265700 (LWP 24935)]
[New Thread 0x7ffff0a64700 (LWP 24936)]
[New Thread 0x7fffe3fff700 (LWP 24937)]
Reading symbols from a.out...
(gdb) r
Starting program: /data/gdb_versions/devel/a.out
[Detaching after vfork from child process 24938]
[Detaching after fork from child process 24939]
[Detaching after fork from child process 24941]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff77fe700 (LWP 24942)]
^C
Thread 1 "gdb" hit Breakpoint 1, stop_all_threads () at
/data/gdb_versions/devel/src/gdb/infrun.c:4683
4683 int iterations = 0;
(master-gdb) shell killall -9 a.out
(master-gdb) c
Continuing.
warning: unable to open /proc file '/proc/24938/status'
^C
Thread 1 "gdb" received signal SIGINT, Interrupt.
0x00007ffff5013a40 in open64 () from /lib64/libc.so.6
(master-gdb)
...
Note: we use the master-gdb to make the killing of a.out happen at the start of
stop_all_threads, which is called to handle the '^C'.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26208-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 08:36:00 2020
Return-Path: <gdb-prs-return-26208-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 45056 invoked by alias); 29 Jan 2020 08:36:00 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 45027 invoked by uid 48); 29 Jan 2020 08:36:00 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25478] gdb hangs after external SIGKILL
Date: Wed, 29 Jan 2020 08: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: vries 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: <bug-25478-4717-btFWCma1kl@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00123.txt
Content-length: 2311
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
The behaviour changed slightly with commit 5b6d1e4fa4f "Multi-target support".
Before that, we also had a hang, but with repeating "Couldn't get registers: No
such process" warning:
...
Reading symbols from ./gdb...
(master-gdb) b stop_all_threads
Breakpoint 1 at 0x6e8a57: file /data/gdb_versions/devel/src/gdb/infrun.c, line
4340.
(master-gdb) r
Starting program: /data/gdb_versions/devel/gdb --args a.out
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff3581700 (LWP 27605)]
[New Thread 0x7ffff2d80700 (LWP 27606)]
[New Thread 0x7ffff257f700 (LWP 27607)]
[Detaching after vfork from child process 27608]
[New Thread 0x7ffff1a66700 (LWP 27609)]
[New Thread 0x7ffff1265700 (LWP 27610)]
[New Thread 0x7ffff0a64700 (LWP 27611)]
[New Thread 0x7fffebfff700 (LWP 27612)]
Reading symbols from a.out...
(gdb) r
Starting program: /data/gdb_versions/devel/a.out
[Detaching after vfork from child process 27613]
[Detaching after fork from child process 27614]
[Detaching after fork from child process 27616]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff77fe700 (LWP 27617)]
Thread 1 "gdb" hit Breakpoint 1, stop_all_threads () at
/data/gdb_versions/devel/src/gdb/infrun.c:4340
4340 int iterations = 0;
(master-gdb) shell killall -9 a.out
(master-gdb) c
Continuing.
warning: unable to open /proc file '/proc/27613/status'
warning: unable to open /proc file '/proc/27613/status'
warning: unable to open /proc file '/proc/27613/status'
<repeat>
warning: unable to open /proc file '/proc/27613/status'
warning: unable to open /proc file '/proc/27613/status'
warning: unable to open /proc file '/proc/27613/status'
<typed control-C>
Thread 1 "gdb" received signal SIGINT, Interrupt.
0x00000000006db4e8 in next_adapter<thread_info,
filtered_iterator<next_iterator<thread_info>, non_exited_thread_filter> >::end
(this=0x7fffffffd098) at
/data/gdb_versions/devel/src/gdb/gdbsupport/next-iterator.h:94
94 return iterator ();
(master-gdb)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26209-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 08:49:25 2020
Return-Path: <gdb-prs-return-26209-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 125729 invoked by alias); 29 Jan 2020 08:49:24 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 125442 invoked by uid 48); 29 Jan 2020 08:49:07 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25478] gdb hangs after external SIGKILL
Date: Wed, 29 Jan 2020 08: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: vries 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: <bug-25478-4717-InwPOQlHgY@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00124.txt
Content-length: 1143
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> The behaviour changed slightly with commit 5b6d1e4fa4f "Multi-target
> support". Before that, we also had a hang, but with repeating "Couldn't get
> registers: No such process" warning:
And that behaviour was introduced with commit aa01bd3689d "Linux native thread
create/exit events support" (there's an extra tcsetpgrp warning though):
...
(master-gdb) c
Continuing.
warning: unable to open /proc file '/proc/22373/status'
[tcsetpgrp failed in terminal_inferior: No such process]
warning: unable to open /proc file '/proc/22373/status'
warning: unable to open /proc file '/proc/22373/status'
warning: unable to open /proc file '/proc/22373/status'
<repeat>
...
[ Note: the commit was build with commit 754653a7c0a "Sync proc_service
definition with GLIBC" applied on top to prevent running into "Cannot find
user-level thread for LWP ###: capability not available" when running a.out. ]
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26210-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 08:52:21 2020
Return-Path: <gdb-prs-return-26210-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 129906 invoked by alias); 29 Jan 2020 08:52:21 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 129885 invoked by uid 48); 29 Jan 2020 08:52:20 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25478] gdb hangs after external SIGKILL
Date: Wed, 29 Jan 2020 08: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: vries 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: <bug-25478-4717-X4FjMoJaeY@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00125.txt
Content-length: 1500
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #2)
> And that behaviour was introduced with commit aa01bd3689d "Linux native
> thread create/exit events support" (there's an extra tcsetpgrp warning
> though):
And before that commit, we have no hang:
...
Reading symbols from ./gdb...done.
(master-gdb) b stop_all_threads
Breakpoint 1 at 0x5f2168: file /data/gdb_versions/devel/src/gdb/infrun.c, line
4466.
(master-gdb) r
Starting program: /data/gdb_versions/devel/gdb --args a.out
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff4e5a700 (LWP 17113)]
[New Thread 0x7ffff4659700 (LWP 17114)]
[New Thread 0x7ffff3e58700 (LWP 17115)]
Reading symbols from a.out...done.
(gdb) r
Starting program: /data/gdb_versions/devel/a.out
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff77fe700 (LWP 17120)]
^C
Thread 1 "gdb" hit Breakpoint 1, stop_all_threads () at
/data/gdb_versions/devel/src/gdb/infrun.c:4466
4466 int iterations = 0;
(master-gdb) shell killall -9 a.out
(master-gdb) c
Continuing.
[Thread 0x7ffff77fe700 (LWP 17120) exited]
Thread 1 received signal SIGINT, Interrupt.
0x00007ffff78c50f0 in nanosleep () from /lib64/libc.so.6
(gdb)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26211-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 08:53:35 2020
Return-Path: <gdb-prs-return-26211-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 11631 invoked by alias); 29 Jan 2020 08:53:34 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 11611 invoked by uid 48); 29 Jan 2020 08:53:34 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25478] gdb hangs after external SIGKILL
Date: Wed, 29 Jan 2020 08: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: vries 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: <bug-25478-4717-ATqZYtDOaH@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00126.txt
Content-length: 393
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26212-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 09:42:30 2020
Return-Path: <gdb-prs-return-26212-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 85102 invoked by alias); 29 Jan 2020 09:42:29 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 85075 invoked by uid 48); 29 Jan 2020 09:42:28 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25478] gdb hangs after external SIGKILL
Date: Wed, 29 Jan 2020 09: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: vries 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: <bug-25478-4717-oLAYoX4kwY@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00127.txt
Content-length: 2642
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
Using this tentative patch on top of master:
...
diff --git a/gdb/infrun.c b/gdb/infrun.c
index 22de42c2ae1..fd9667a0351 100644
--- a/gdb/infrun.c
+++ b/gdb/infrun.c
@@ -4772,8 +4772,12 @@ stop_all_threads (void)
target_pid_to_str (event.ptid).c_str ());
}
- if (event.ws.kind == TARGET_WAITKIND_NO_RESUMED
- || event.ws.kind == TARGET_WAITKIND_THREAD_EXITED
+ if (event.ws.kind == TARGET_WAITKIND_NO_RESUMED)
+ {
+ pass = 2;
+ break;
+ }
+ else if (event.ws.kind == TARGET_WAITKIND_THREAD_EXITED
|| event.ws.kind == TARGET_WAITKIND_EXITED
|| event.ws.kind == TARGET_WAITKIND_SIGNALLED)
{
...
we get rid of the hang:
...
Reading symbols from ./gdb...
(master-gdb) b stop_all_threads
Breakpoint 1 at 0x6d048b: file /data/gdb_versions/devel/src/gdb/infrun.c, line
4683.
(master-gdb) r
Starting program: /data/gdb_versions/devel/gdb --args a.out
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff3581700 (LWP 5459)]
[New Thread 0x7ffff2d80700 (LWP 5460)]
[New Thread 0x7ffff257f700 (LWP 5461)]
[Detaching after vfork from child process 5462]
[New Thread 0x7ffff1a66700 (LWP 5463)]
[New Thread 0x7ffff1265700 (LWP 5464)]
[New Thread 0x7ffff0a64700 (LWP 5465)]
[New Thread 0x7fffebfff700 (LWP 5466)]
Reading symbols from a.out...
(gdb) r
Starting program: /data/gdb_versions/devel/a.out
[Detaching after vfork from child process 5467]
[Detaching after fork from child process 5468]
[Detaching after fork from child process 5470]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff77fe700 (LWP 5471)]
^C
Thread 1 "gdb" hit Breakpoint 1, stop_all_threads () at
/data/gdb_versions/devel/src/gdb/infrun.c:4683
4683 int iterations = 0;
(master-gdb) shell killall -9 a.out
(master-gdb) c
Continuing.
warning: unable to open /proc file '/proc/5467/status'
Thread 1 received signal SIGINT, Interrupt.
0x00007ffff78c50f0 in nanosleep () from /lib64/libc.so.6
(gdb)
...
In other words, we get the same behaviour as before commit aa01bd3689d "Linux
native thread create/exit events support" (as shown in comment 3).
The tentative patch was build on x86_64 and regression tested, no issues found.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26213-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 10:08:12 2020
Return-Path: <gdb-prs-return-26213-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 17950 invoked by alias); 29 Jan 2020 10:08:11 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 17932 invoked by uid 48); 29 Jan 2020 10:08:11 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25479] New: FAIL: gdb.base/reread.exp: opts= "-fPIE"
"ldflags=-pie" : run to foo() second time (GDB internal error)
Date: Wed, 29 Jan 2020 10: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25479-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00128.txt
Content-length: 2004
https://sourceware.org/bugzilla/show_bug.cgi?id=25479
Bug ID: 25479
Summary: FAIL: gdb.base/reread.exp: opts= "-fPIE"
"ldflags=-pie" : run to foo() second time (GDB
internal error)
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With commit ee2a6fc6041 "[gdb/testsuite] Fix gdb.threads/watchpoint-fork.exp
race" and the tentative patch from PR25478 comment 4, I ran into this FAIL:
...
FAIL: gdb.base/reread.exp: opts= "-fPIE" "ldflags=-pie" : run to foo() second
time (GDB internal error)
...
In more detail:
...
(gdb) PASS: gdb.base/reread.exp: opts= "-fPIE" "ldflags=-pie" : run to foo()
shell sleep 1^M
(gdb) run ^M
The program being debugged has been started already.^M
Start it from the beginning? (y or n) y^M
`/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/reread/reread'
has changed; re-reading symbols.^M
Starting program:
/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/reread/reread ^M
/data/gdb_versions/devel/src/gdb/objfiles.c:1119: internal-error: int
filter_overlapping_sections(obj_section**, int): Assertion `sect1_addr <=
sect2_addr' 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.base/reread.exp: opts= "-fPIE"
"ldflags=-pie" : run to foo() second time (GDB internal error)
...
I could not reproduce this when running the test individually.
Also repeating the individual test 10 time in conjunction with stress -c 5
resulted in PASSes only.
Also in a second full test run, the test PASSed.
AFAICT, the failure looks unrelated to the tentative patch.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26214-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 10:36:54 2020
Return-Path: <gdb-prs-return-26214-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 60258 invoked by alias); 29 Jan 2020 10:36:53 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 60220 invoked by uid 48); 29 Jan 2020 10:36:53 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25479] AddressSanitizer: heap-buffer-overflow in
lookup_minimal_symbol_by_pc_name
Date: Wed, 29 Jan 2020 10: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: vries 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: version short_desc
Message-ID: <bug-25479-4717-RoERxgeODN@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25479-4717@http.sourceware.org/bugzilla/>
References: <bug-25479-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00129.txt
Content-length: 16645
https://sourceware.org/bugzilla/show_bug.cgi?id=25479
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unknown |HEAD
Summary|FAIL: gdb.base/reread.exp: |AddressSanitizer:
|opts= "-fPIE" |heap-buffer-overflow in
|"ldflags=-pie" : run to |lookup_minimal_symbol_by_pc
|foo() second time (GDB |_name
|internal error) |
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Setting version to master.
Triggered presumably related problem without the tentative patch, by building
gdb with address sanitizer:
...
14 x++;
(gdb) PASS: gdb.base/reread.exp: opts= "" "" : run to foo()
shell sleep 1
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
`/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/reread/reread'
has changed; re-reading symbols.
=================================================================
==17884==ERROR: AddressSanitizer: heap-buffer-overflow on address
0x612000031200 at pc 0x000001132d59 bp 0x7ffed52efbe0 sp 0x7ffed52efbd8
READ of size 8 at 0x612000031200 thread T0
#0 0x1132d58 in lookup_minimal_symbol_by_pc_name(unsigned long, char
const*, objfile*) /data/gdb_versions/devel/src/gdb/minsyms.c:616
#1 0x142ac34 in fixup_section(general_symbol_info*, unsigned long,
objfile*) /data/gdb_versions/devel/src/gdb/symtab.c:1676
#2 0x142b637 in fixup_symbol_section(symbol*, objfile*)
/data/gdb_versions/devel/src/gdb/symtab.c:1786
#3 0xd5c874 in var_decode_location
/data/gdb_versions/devel/src/gdb/dwarf2read.c:21767
#4 0xd5dac4 in new_symbol
/data/gdb_versions/devel/src/gdb/dwarf2read.c:21959
#5 0xd2e421 in read_variable
/data/gdb_versions/devel/src/gdb/dwarf2read.c:14259
#6 0xd18b0a in process_die
/data/gdb_versions/devel/src/gdb/dwarf2read.c:10688
#7 0xd1d1f6 in read_file_scope
/data/gdb_versions/devel/src/gdb/dwarf2read.c:11594
#8 0xd18614 in process_die
/data/gdb_versions/devel/src/gdb/dwarf2read.c:10601
#9 0xd17269 in process_full_comp_unit
/data/gdb_versions/devel/src/gdb/dwarf2read.c:10366
#10 0xd0ef42 in process_queue
/data/gdb_versions/devel/src/gdb/dwarf2read.c:9640
#11 0xce52dc in dw2_do_instantiate_symtab
/data/gdb_versions/devel/src/gdb/dwarf2read.c:2946
#12 0xd0f29b in dwarf2_psymtab::expand_psymtab(objfile*)
/data/gdb_versions/devel/src/gdb/dwarf2read.c:9682
#13 0xd0e5be in dwarf2_psymtab::read_symtab(objfile*)
/data/gdb_versions/devel/src/gdb/dwarf2read.c:9511
#14 0x11ec654 in psymtab_to_symtab
/data/gdb_versions/devel/src/gdb/psymtab.c:768
#15 0x11eadd1 in psym_lookup_symbol
/data/gdb_versions/devel/src/gdb/psymtab.c:491
#16 0x142ef9a in lookup_symbol_via_quick_fns
/data/gdb_versions/devel/src/gdb/symtab.c:2409
#17 0x142f89b in lookup_symbol_in_objfile
/data/gdb_versions/devel/src/gdb/symtab.c:2558
#18 0x142fb62 in lookup_symbol_global_or_static_iterator_cb
/data/gdb_versions/devel/src/gdb/symtab.c:2605
#19 0x1381e2e in svr4_iterate_over_objfiles_in_search_order
/data/gdb_versions/devel/src/gdb/solib-svr4.c:3258
#20 0xe5df7a in gdbarch_iterate_over_objfiles_in_search_order(gdbarch*, int
(*)(objfile*, void*), void*, objfile*)
/data/gdb_versions/devel/src/gdb/gdbarch.c:4853
#21 0x142ff23 in lookup_global_or_static_symbol
/data/gdb_versions/devel/src/gdb/symtab.c:2650
#22 0x14301f8 in lookup_global_symbol(char const*, block const*,
domain_enum_tag) /data/gdb_versions/devel/src/gdb/symtab.c:2692
#23 0x142f461 in basic_lookup_symbol_nonlocal(language_defn const*, char
const*, block const*, domain_enum_tag)
/data/gdb_versions/devel/src/gdb/symtab.c:2479
#24 0x142d32b in lookup_symbol_aux
/data/gdb_versions/devel/src/gdb/symtab.c:2120
#25 0x142bf4c in lookup_symbol_in_language(char const*, block const*,
domain_enum_tag, language, field_of_this_result*)
/data/gdb_versions/devel/src/gdb/symtab.c:1916
#26 0x142c071 in lookup_symbol(char const*, block const*, domain_enum_tag,
field_of_this_result*) /data/gdb_versions/devel/src/gdb/symtab.c:1928
#27 0xbf4ca2 in inspect_type
/data/gdb_versions/devel/src/gdb/cp-support.c:160
#28 0xbf680f in replace_typedefs
/data/gdb_versions/devel/src/gdb/cp-support.c:475
#29 0xbf6b5e in cp_canonicalize_string_full[abi:cxx11](char const*, char
const* (*)(type*, void*), void*)
/data/gdb_versions/devel/src/gdb/cp-support.c:527
#30 0xbf6e4a in cp_canonicalize_string_no_typedefs[abi:cxx11](char const*)
/data/gdb_versions/devel/src/gdb/cp-support.c:550
#31 0xff0241 in find_linespec_symbols
/data/gdb_versions/devel/src/gdb/linespec.c:3902
#32 0xfe579b in convert_explicit_location_to_linespec
/data/gdb_versions/devel/src/gdb/linespec.c:2407
#33 0xfe5d9d in convert_explicit_location_to_sals
/data/gdb_versions/devel/src/gdb/linespec.c:2448
#34 0xfeae5f in event_location_to_sals
/data/gdb_versions/devel/src/gdb/linespec.c:3185
#35 0xfeb361 in decode_line_full(event_location const*, int,
program_space*, symtab*, int, linespec_result*, char const*, char const*)
/data/gdb_versions/devel/src/gdb/linespec.c:3232
#36 0xa5499c in decode_location_default
/data/gdb_versions/devel/src/gdb/breakpoint.c:13731
#37 0xa4d581 in bkpt_decode_location
/data/gdb_versions/devel/src/gdb/breakpoint.c:12533
#38 0xa531e6 in location_to_sals
/data/gdb_versions/devel/src/gdb/breakpoint.c:13583
#39 0xa5422b in breakpoint_re_set_default
/data/gdb_versions/devel/src/gdb/breakpoint.c:13669
#40 0xa4bcdc in bkpt_re_set
/data/gdb_versions/devel/src/gdb/breakpoint.c:12333
#41 0xa54cb6 in breakpoint_re_set_one
/data/gdb_versions/devel/src/gdb/breakpoint.c:13754
#42 0xa54ec4 in breakpoint_re_set()
/data/gdb_versions/devel/src/gdb/breakpoint.c:13792
#43 0x13fde71 in clear_symtab_users(enum_flags<symfile_add_flag>)
/data/gdb_versions/devel/src/gdb/symfile.c:2893
#44 0x13fc814 in reread_symbols()
/data/gdb_versions/devel/src/gdb/symfile.c:2640
#45 0xf56504 in run_command_1 /data/gdb_versions/devel/src/gdb/infcmd.c:581
#46 0xf573b1 in run_command /data/gdb_versions/devel/src/gdb/infcmd.c:688
#47 0xb2f9a4 in do_const_cfunc
/data/gdb_versions/devel/src/gdb/cli/cli-decode.c:107
#48 0xb3726c in cmd_func(cmd_list_element*, char const*, int)
/data/gdb_versions/devel/src/gdb/cli/cli-decode.c:1952
#49 0x14fd27b in execute_command(char const*, int)
/data/gdb_versions/devel/src/gdb/top.c:653
#50 0xdf07fe in command_handler(char const*)
/data/gdb_versions/devel/src/gdb/event-top.c:587
#51 0xdf10cb in command_line_handler(std::unique_ptr<char,
gdb::xfree_deleter<char> >&&) /data/gdb_versions/devel/src/gdb/event-top.c:772
#52 0xdef460 in gdb_rl_callback_handler
/data/gdb_versions/devel/src/gdb/event-top.c:218
#53 0x16e07a7 in rl_callback_read_char
/data/gdb_versions/devel/src/readline/readline/callback.c:281
#54 0xdef014 in gdb_rl_callback_read_char_wrapper_noexcept
/data/gdb_versions/devel/src/gdb/event-top.c:176
#55 0xdef1f5 in gdb_rl_callback_read_char_wrapper
/data/gdb_versions/devel/src/gdb/event-top.c:193
#56 0xdf03bd in stdin_event_handler(int, void*)
/data/gdb_versions/devel/src/gdb/event-top.c:515
#57 0xdeb0c7 in handle_file_event
/data/gdb_versions/devel/src/gdb/event-loop.c:734
#58 0xdeb8f1 in gdb_wait_for_event
/data/gdb_versions/devel/src/gdb/event-loop.c:860
#59 0xde9824 in gdb_do_one_event()
/data/gdb_versions/devel/src/gdb/event-loop.c:346
#60 0xde98c6 in start_event_loop()
/data/gdb_versions/devel/src/gdb/event-loop.c:370
#61 0x108f90b in captured_command_loop
/data/gdb_versions/devel/src/gdb/main.c:360
#62 0x1092dd5 in captured_main /data/gdb_versions/devel/src/gdb/main.c:1203
#63 0x1092e65 in gdb_main(captured_main_args*)
/data/gdb_versions/devel/src/gdb/main.c:1218
#64 0x9018e0 in main /data/gdb_versions/devel/src/gdb/gdb.c:32
#65 0x7f3e0e5c3f89 in __libc_start_main (/lib64/libc.so.6+0x20f89)
#66 0x9016f9 in _start (/data/gdb_versions/devel/build/gdb/gdb+0x9016f9)
0x612000031200 is located 40 bytes to the right of 280-byte region
[0x6120000310c0,0x6120000311d8)
freed by thread T0 here:
#0 0x7f3e114fc07f in __interceptor_free (/usr/lib64/libasan.so.6+0xac07f)
#1 0x173a643 in _bfd_delete_bfd
/data/gdb_versions/devel/src/bfd/opncls.c:132
#2 0x173bcdd in bfd_close_all_done
/data/gdb_versions/devel/src/bfd/opncls.c:797
#3 0x173bbdc in bfd_close /data/gdb_versions/devel/src/bfd/opncls.c:759
#4 0xe3c936 in gdb_bfd_close_or_warn
/data/gdb_versions/devel/src/gdb/gdb_bfd.c:510
#5 0xe3d11b in gdb_bfd_unref(bfd*)
/data/gdb_versions/devel/src/gdb/gdb_bfd.c:614
#6 0x1176a08 in objfile::~objfile()
/data/gdb_versions/devel/src/gdb/objfiles.c:591
#7 0x1182ce2 in std::_Sp_counted_ptr<objfile*,
(__gnu_cxx::_Lock_policy)2>::_M_dispose()
(/data/gdb_versions/devel/build/gdb/gdb+0x1182ce2)
#8 0xa72e2a in
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release()
/usr/include/c++/10/bits/shared_ptr_base.h:155
#9 0xa6953f in
std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count()
/usr/include/c++/10/bits/shared_ptr_base.h:730
#10 0x117e697 in std::__shared_ptr<objfile,
(__gnu_cxx::_Lock_policy)2>::~__shared_ptr()
/usr/include/c++/10/bits/shared_ptr_base.h:1180
#11 0x117e6b3 in std::shared_ptr<objfile>::~shared_ptr()
/usr/include/c++/10/bits/shared_ptr.h:121
#12 0x11e5289 in void
__gnu_cxx::new_allocator<std::_List_node<std::shared_ptr<objfile> >
>::destroy<std::shared_ptr<objfile> >(std::shared_ptr<objfile>*)
/usr/include/c++/10/ext/new_allocator.h:157
#13 0x11e4fd8 in void
std::allocator_traits<std::allocator<std::_List_node<std::shared_ptr<objfile> >
> >::destroy<std::shared_ptr<objfile>
>(std::allocator<std::_List_node<std::shared_ptr<objfile> > >&,
std::shared_ptr<objfile>*) /usr/include/c++/10/bits/alloc_traits.h:526
#14 0x11e4d74 in std::__cxx11::list<std::shared_ptr<objfile>,
std::allocator<std::shared_ptr<objfile> >
>::_M_erase(std::_List_iterator<std::shared_ptr<objfile> >)
/usr/include/c++/10/bits/stl_list.h:1921
#15 0x11e467e in std::__cxx11::list<std::shared_ptr<objfile>,
std::allocator<std::shared_ptr<objfile> >
>::erase(std::_List_const_iterator<std::shared_ptr<objfile> >)
/usr/include/c++/10/bits/list.tcc:158
#16 0x11e116d in program_space::remove_objfile(objfile*)
/data/gdb_versions/devel/src/gdb/progspace.c:207
#17 0x1176595 in objfile::unlink()
/data/gdb_versions/devel/src/gdb/objfiles.c:505
#18 0x1179d23 in objfile_purge_solibs()
/data/gdb_versions/devel/src/gdb/objfiles.c:912
#19 0x138f8ed in no_shared_libraries(char const*, int)
/data/gdb_versions/devel/src/gdb/solib.c:1247
#20 0x14a6543 in target_pre_inferior(int)
/data/gdb_versions/devel/src/gdb/target.c:1960
#21 0xf564fa in run_command_1 /data/gdb_versions/devel/src/gdb/infcmd.c:571
#22 0xf573b1 in run_command /data/gdb_versions/devel/src/gdb/infcmd.c:688
#23 0xb2f9a4 in do_const_cfunc
/data/gdb_versions/devel/src/gdb/cli/cli-decode.c:107
#24 0xb3726c in cmd_func(cmd_list_element*, char const*, int)
/data/gdb_versions/devel/src/gdb/cli/cli-decode.c:1952
#25 0x14fd27b in execute_command(char const*, int)
/data/gdb_versions/devel/src/gdb/top.c:653
#26 0xdf07fe in command_handler(char const*)
/data/gdb_versions/devel/src/gdb/event-top.c:587
#27 0xdf10cb in command_line_handler(std::unique_ptr<char,
gdb::xfree_deleter<char> >&&) /data/gdb_versions/devel/src/gdb/event-top.c:772
#28 0xdef460 in gdb_rl_callback_handler
/data/gdb_versions/devel/src/gdb/event-top.c:218
#29 0x16e07a7 in rl_callback_read_char
/data/gdb_versions/devel/src/readline/readline/callback.c:281
previously allocated by thread T0 here:
#0 0x7f3e114fc39f in malloc (/usr/lib64/libasan.so.6+0xac39f)
#1 0x1737332 in bfd_malloc /data/gdb_versions/devel/src/bfd/libbfd.c:275
#2 0x1737519 in bfd_zmalloc /data/gdb_versions/devel/src/bfd/libbfd.c:360
#3 0x173a0e2 in _bfd_new_bfd /data/gdb_versions/devel/src/bfd/opncls.c:62
#4 0x173a83e in bfd_fopen /data/gdb_versions/devel/src/bfd/opncls.c:200
#5 0xe3c638 in gdb_bfd_open(char const*, char const*, int)
/data/gdb_versions/devel/src/gdb/gdb_bfd.c:455
#6 0x138b577 in solib_bfd_fopen(char const*, int)
/data/gdb_versions/devel/src/gdb/solib.c:464
#7 0x138b81f in solib_bfd_open(char const*)
/data/gdb_versions/devel/src/gdb/solib.c:501
#8 0x137d837 in enable_break
/data/gdb_versions/devel/src/gdb/solib-svr4.c:2327
#9 0x13814cb in svr4_solib_create_inferior_hook
/data/gdb_versions/devel/src/gdb/solib-svr4.c:3033
#10 0x138f84a in solib_create_inferior_hook(int)
/data/gdb_versions/devel/src/gdb/solib.c:1211
#11 0xf5600e in post_create_inferior(target_ops*, int)
/data/gdb_versions/devel/src/gdb/infcmd.c:460
#12 0xf56fd9 in run_command_1 /data/gdb_versions/devel/src/gdb/infcmd.c:665
#13 0xf573b1 in run_command /data/gdb_versions/devel/src/gdb/infcmd.c:688
#14 0xb2f9a4 in do_const_cfunc
/data/gdb_versions/devel/src/gdb/cli/cli-decode.c:107
#15 0xb3726c in cmd_func(cmd_list_element*, char const*, int)
/data/gdb_versions/devel/src/gdb/cli/cli-decode.c:1952
#16 0x14fd27b in execute_command(char const*, int)
/data/gdb_versions/devel/src/gdb/top.c:653
#17 0xdf07fe in command_handler(char const*)
/data/gdb_versions/devel/src/gdb/event-top.c:587
#18 0xdf10cb in command_line_handler(std::unique_ptr<char,
gdb::xfree_deleter<char> >&&) /data/gdb_versions/devel/src/gdb/event-top.c:772
#19 0xdef460 in gdb_rl_callback_handler
/data/gdb_versions/devel/src/gdb/event-top.c:218
#20 0x16e07a7 in rl_callback_read_char
/data/gdb_versions/devel/src/readline/readline/callback.c:281
#21 0xdef014 in gdb_rl_callback_read_char_wrapper_noexcept
/data/gdb_versions/devel/src/gdb/event-top.c:176
#22 0xdef1f5 in gdb_rl_callback_read_char_wrapper
/data/gdb_versions/devel/src/gdb/event-top.c:193
#23 0xdf03bd in stdin_event_handler(int, void*)
/data/gdb_versions/devel/src/gdb/event-top.c:515
#24 0xdeb0c7 in handle_file_event
/data/gdb_versions/devel/src/gdb/event-loop.c:734
#25 0xdeb8f1 in gdb_wait_for_event
/data/gdb_versions/devel/src/gdb/event-loop.c:860
#26 0xde9824 in gdb_do_one_event()
/data/gdb_versions/devel/src/gdb/event-loop.c:346
#27 0xde98c6 in start_event_loop()
/data/gdb_versions/devel/src/gdb/event-loop.c:370
#28 0x108f90b in captured_command_loop
/data/gdb_versions/devel/src/gdb/main.c:360
#29 0x1092dd5 in captured_main /data/gdb_versions/devel/src/gdb/main.c:1203
SUMMARY: AddressSanitizer: heap-buffer-overflow
/data/gdb_versions/devel/src/gdb/minsyms.c:616 in
lookup_minimal_symbol_by_pc_name(unsigned long, char const*, objfile*)
Shadow bytes around the buggy address:
0x0c247fffe1f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c247fffe200: 00 00 00 00 00 00 00 00 00 00 00 fa fa fa fa fa
0x0c247fffe210: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd
0x0c247fffe220: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c247fffe230: fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa fa
=>0x0c247fffe240:[fa]fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd
0x0c247fffe250: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c247fffe260: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fa
0x0c247fffe270: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd
0x0c247fffe280: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c247fffe290: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==17884==ABORTING
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26215-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 10:49:13 2020
Return-Path: <gdb-prs-return-26215-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 89677 invoked by alias); 29 Jan 2020 10:49:13 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 89626 invoked by uid 48); 29 Jan 2020 10:49:11 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25479] AddressSanitizer: heap-buffer-overflow in
lookup_minimal_symbol_by_pc_name
Date: Wed, 29 Jan 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25479-4717-o210ssd7v9@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25479-4717@http.sourceware.org/bugzilla/>
References: <bug-25479-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00130.txt
Content-length: 334
https://sourceware.org/bugzilla/show_bug.cgi?id=25479
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Does not reproduce with commit 27f7b2f6406 "Fix typo, get_Frame_id ->
get_frame_id" (branch point for gdb-9-branch).
Now bisecting.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26216-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 12:17:34 2020
Return-Path: <gdb-prs-return-26216-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 14248 invoked by alias); 29 Jan 2020 12:17:34 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 14224 invoked by uid 48); 29 Jan 2020 12:17:34 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25479] AddressSanitizer: heap-buffer-overflow in
lookup_minimal_symbol_by_pc_name
Date: Wed, 29 Jan 2020 12: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: vries 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: <bug-25479-4717-ATezdfGWQM@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25479-4717@http.sourceware.org/bugzilla/>
References: <bug-25479-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00131.txt
Content-length: 857
https://sourceware.org/bugzilla/show_bug.cgi?id=25479
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #2)
> Does not reproduce with commit 27f7b2f6406 "Fix typo, get_Frame_id ->
> get_frame_id" (branch point for gdb-9-branch).
>
> Now bisecting.
One of:
...
6a053cb1ff6 Tom Tromey "Change section_offsets to a std::vector"
456e800a63d Tom Tromey "Use std::string in dwarf2read.c"
6dfa2fc2077 Tom Tromey "Use std::vector in abbrev_table_read_table"
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26217-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 12:21:51 2020
Return-Path: <gdb-prs-return-26217-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 25661 invoked by alias); 29 Jan 2020 12:21:51 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 25634 invoked by uid 48); 29 Jan 2020 12:21:51 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25479] AddressSanitizer: heap-buffer-overflow in
lookup_minimal_symbol_by_pc_name
Date: Wed, 29 Jan 2020 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: vries 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: <bug-25479-4717-b9pn7DsRNF@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25479-4717@http.sourceware.org/bugzilla/>
References: <bug-25479-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00132.txt
Content-length: 764
https://sourceware.org/bugzilla/show_bug.cgi?id=25479
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #3)
> (In reply to Tom de Vries from comment #2)
> > Does not reproduce with commit 27f7b2f6406 "Fix typo, get_Frame_id ->
> > get_frame_id" (branch point for gdb-9-branch).
> >
> > Now bisecting.
>
> One of:
> ...
> 6a053cb1ff6 Tom Tromey "Change section_offsets to a std::vector"
> 456e800a63d Tom Tromey "Use std::string in dwarf2read.c"
> 6dfa2fc2077 Tom Tromey "Use std::vector in abbrev_table_read_table"
> ...
Bisect done. This is the offending commit: 6a053cb1ff6 "Change section_offsets
to a std::vector".
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26218-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 13:21:21 2020
Return-Path: <gdb-prs-return-26218-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 79191 invoked by alias); 29 Jan 2020 13:21:20 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 79145 invoked by uid 48); 29 Jan 2020 13:21:19 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25478] gdb hangs after external SIGKILL
Date: Wed, 29 Jan 2020 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: vries 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: <bug-25478-4717-7lcsFpZj8u@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00133.txt
Content-length: 1850
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
Using set debug infrun 1, we can see how we hang:
...
Thread 1 "gdb" hit Breakpoint 1, stop_all_threads () at
/data/gdb_versions/devel/src/gdb/infrun.c:4683
4683 int iterations = 0;
(master-gdb) shell killall -9 a.out
(master-gdb) c
Continuing.
infrun: stop_all_threads
infrun: stop_all_threads, pass=0, iterations=0
infrun: Thread 0x7ffff7fa6740 (LWP 10264) not executing
infrun: Thread 0x7ffff77fe700 (LWP 10268) executing, need stop
infrun: target_wait (-1.0.0, status) =
infrun: 10264.10268.0 [Thread 0x7ffff77fe700 (LWP 10268)],
infrun: status->kind = signalled, signal = GDB_SIGNAL_KILL
infrun: stop_all_threads status->kind = signalled, signal = GDB_SIGNAL_KILL
Thread 0x7ffff77fe700 (LWP 10268)
infrun: Thread 0x7ffff7fa6740 (LWP 10264) not executing
infrun: Thread 0x7ffff77fe700 (LWP 10268) executing, already stopping
warning: unable to open /proc file '/proc/10264/status'
infrun: target_wait (-1.0.0, status) =
infrun: -1.0.0 [process -1],
infrun: status->kind = no-resumed
infrun: infrun_async(0)
infrun: stop_all_threads status->kind = no-resumed process -1
infrun: Thread 0x7ffff7fa6740 (LWP 10264) not executing
infrun: Thread 0x7ffff77fe700 (LWP 10268) executing, already stopping
infrun: stop_all_threads status->kind = no-resumed process -1
infrun: Thread 0x7ffff7fa6740 (LWP 10264) not executing
infrun: Thread 0x7ffff77fe700 (LWP 10268) executing, already stopping
infrun: stop_all_threads status->kind = no-resumed process -1
infrun: Thread 0x7ffff7fa6740 (LWP 10264) not executing
infrun: Thread 0x7ffff77fe700 (LWP 10268) executing, already stopping
<repeat>
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26219-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 13:24:36 2020
Return-Path: <gdb-prs-return-26219-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 82464 invoked by alias); 29 Jan 2020 13:24:35 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 82349 invoked by uid 48); 29 Jan 2020 13:24:23 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25478] gdb hangs after external SIGKILL
Date: Wed, 29 Jan 2020 13: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: vries 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: <bug-25478-4717-0O6SBdweql@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00134.txt
Content-length: 1214
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
With this patch on top of master, we directly detect the SIGKILL and even
manage to get rid of the /proc warning:
...
diff --git a/gdb/infrun.c b/gdb/infrun.c
index 22de42c2ae1..e34ddc83b45 100644
--- a/gdb/infrun.c
+++ b/gdb/infrun.c
@@ -4772,7 +4772,10 @@ stop_all_threads (void)
target_pid_to_str (event.ptid).c_str ());
}
- if (event.ws.kind == TARGET_WAITKIND_NO_RESUMED
+ if (event.ws.kind == TARGET_WAITKIND_SIGNALLED
+ && event.ws.value.sig == GDB_SIGNAL_KILL)
+ goto done;
+ else if (event.ws.kind == TARGET_WAITKIND_NO_RESUMED
|| event.ws.kind == TARGET_WAITKIND_THREAD_EXITED
|| event.ws.kind == TARGET_WAITKIND_EXITED
|| event.ws.kind == TARGET_WAITKIND_SIGNALLED)
@@ -4872,6 +4875,7 @@ stop_all_threads (void)
}
}
+ done:
if (debug_infrun)
fprintf_unfiltered (gdb_stdlog, "infrun: stop_all_threads done\n");
}
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26220-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 14:04:15 2020
Return-Path: <gdb-prs-return-26220-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 47044 invoked by alias); 29 Jan 2020 14:04:14 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 47020 invoked by uid 48); 29 Jan 2020 14:04:14 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/25478] gdb hangs after external SIGKILL
Date: Wed, 29 Jan 2020 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: vries 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: component
Message-ID: <bug-25478-4717-g9HXq57Wys@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00135.txt
Content-length: 376
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|gdb |threads
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26221-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 14:12:41 2020
Return-Path: <gdb-prs-return-26221-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 69161 invoked by alias); 29 Jan 2020 14:12:40 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 69132 invoked by uid 48); 29 Jan 2020 14:12:39 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/25478] gdb hangs after external SIGKILL
Date: Wed, 29 Jan 2020 14: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25478-4717-nB6Pmu9VUA@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00136.txt
Content-length: 352
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
submitted patch for review:
- https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/759
- https://sourceware.org/ml/gdb-patches/2020-01/msg00931.html
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26222-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 14:49:24 2020
Return-Path: <gdb-prs-return-26222-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 100161 invoked by alias); 29 Jan 2020 14:49:22 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 99992 invoked by uid 48); 29 Jan 2020 14:49:08 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/25478] gdb hangs after external SIGKILL
Date: Wed, 29 Jan 2020 14: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25478-4717-QvO4entNBP@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00137.txt
Content-length: 360
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
Related patch submission:
- https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/133
"infrun: handle already-exited threads when attempting to stop"
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26223-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 15:06:45 2020
Return-Path: <gdb-prs-return-26223-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 120495 invoked by alias); 29 Jan 2020 15:06:45 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 120473 invoked by uid 48); 29 Jan 2020 15:06:44 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/25478] gdb hangs after external SIGKILL
Date: Wed, 29 Jan 2020 15: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: vries 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: <bug-25478-4717-Q3vqufjCfc@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00138.txt
Content-length: 499
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
--- Comment #9 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #7)
> submitted patch for review:
> - https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/759
> - https://sourceware.org/ml/gdb-patches/2020-01/msg00931.html
FTR, backporting the patch to gcc-9-branch and gcc-8.3-branch fixes the problem
there as well.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26224-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 21:49:46 2020
Return-Path: <gdb-prs-return-26224-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 37095 invoked by alias); 29 Jan 2020 21:49:45 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 37071 invoked by uid 48); 29 Jan 2020 21:49:45 -0000
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25482] New: New "FAIL: gdb.base/options.exp: test-print:
compile print -pretty -- g_s" when compiling/testing with GCC 10
Date: Wed, 29 Jan 2020 21: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: 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: <bug-25482-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00139.txt
Content-length: 1283
https://sourceware.org/bugzilla/show_bug.cgi?id=25482
Bug ID: 25482
Summary: New "FAIL: gdb.base/options.exp: test-print: compile
print -pretty -- g_s" when compiling/testing with GCC
10
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 is a bug to track a new failure I'm seeing when compiling and testing GDB
HEAD with GCC 10:
FAIL: gdb.base/options.exp: test-print: compile print -pretty -- g_s
The specific excerpt from gdb.log:
(gdb) compile print -pretty -- g_s
warning: Could not find symbol "memcpy" for compiled module
"/tmp/gdbobj-txGJwU/out2.o".
1 symbols were missing, cannot continue.
FAIL: gdb.base/options.exp: test-print: compile print -pretty -- g_s
I don't know if this is a GCC bug (seems like it), but I'm filing it against
GDB just in case. We can reassign to GCC later if needed.
GDB HEAD: c47f70e2ce7b347aadbde873aae6c2df92c42180
gcc (GCC) 10.0.1 20200123 (Red Hat 10.0.1-0.5)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26225-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 21:51:48 2020
Return-Path: <gdb-prs-return-26225-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 38344 invoked by alias); 29 Jan 2020 21:51:48 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 38324 invoked by uid 48); 29 Jan 2020 21:51:47 -0000
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25483] New: New gdb.base/store.exp failures when
compiling/testing with GCC 10
Date: Wed, 29 Jan 2020 21: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: 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: <bug-25483-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00140.txt
Content-length: 1266
https://sourceware.org/bugzilla/show_bug.cgi?id=25483
Bug ID: 25483
Summary: New gdb.base/store.exp failures when compiling/testing
with GCC 10
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 is a bug to track new failures I'm seeing when compiling and testing GDB
HEAD with GCC 10:
FAIL: gdb.base/store.exp: var double l; print old r, expecting -2
FAIL: gdb.base/store.exp: upvar double l; print old r, expecting -2
The specific excerpt from gdb.log:
(gdb) print r
$23 = <optimized out>
FAIL: gdb.base/store.exp: var double l; print old r, expecting -2
...
(gdb) print r
$44 = <optimized out>
FAIL: gdb.base/store.exp: upvar double l; print old r, expecting -2
I don't know if this is a GCC bug (seems like it), but I'm filing it against
GDB just in case. We can reassign to GCC later if needed.
GDB HEAD: c47f70e2ce7b347aadbde873aae6c2df92c42180
gcc (GCC) 10.0.1 20200123 (Red Hat 10.0.1-0.5)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26226-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jan 29 22:36:49 2020
Return-Path: <gdb-prs-return-26226-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 41882 invoked by alias); 29 Jan 2020 22:36:48 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 41861 invoked by uid 48); 29 Jan 2020 22:36:48 -0000
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25484] New: New gdb.fortran/info-modules.exp failures when
compiling/testing with GCC 10
Date: Wed, 29 Jan 2020 22: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: 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: <bug-25484-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00141.txt
Content-length: 1443
https://sourceware.org/bugzilla/show_bug.cgi?id=25484
Bug ID: 25484
Summary: New gdb.fortran/info-modules.exp failures when
compiling/testing with GCC 10
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 is a bug to track a new failure I'm seeing when compiling and testing GDB
HEAD with GCC 10:
FAIL: gdb.fortran/info-modules.exp: info module variables: check for entry
'info-types.f90', '35', 'Type m1t1 mod1::__def_init_mod1_M1t1;'
FAIL: gdb.fortran/info-modules.exp: info module variables: check for entry
'info-types.f90', '35', 'Type __vtype_mod1_M1t1 mod1::__vtab_mod1_M1t1;'
FAIL: gdb.fortran/info-modules.exp: info module variables: check no matches for
'info-types.f90', '.*', and '.*'
FAIL: gdb.fortran/info-modules.exp: info module variables: check no matches for
'info-types.f90', '.*', and '.*'
I don't know if this is a GCC bug (seems like it; I can't reproduce it on older
GCCs), but I'm filing it against GDB just in case. We can reassign to GCC
later if needed.
GDB HEAD: c47f70e2ce7b347aadbde873aae6c2df92c42180
gcc (GCC) 10.0.1 20200123 (Red Hat 10.0.1-0.5)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26227-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 30 17:05:09 2020
Return-Path: <gdb-prs-return-26227-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 108568 invoked by alias); 30 Jan 2020 17:05:09 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 108550 invoked by uid 48); 30 Jan 2020 17:05:09 -0000
From: "iii at linux dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25485] New: "Selected thread is running" when debugging
multithreaded app and using conditional syscall catchpoint
Date: Thu, 30 Jan 2020 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: 8.3
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iii at linux 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: <bug-25485-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00142.txt
Content-length: 9014
https://sourceware.org/bugzilla/show_bug.cgi?id=25485
Bug ID: 25485
Summary: "Selected thread is running" when debugging
multithreaded app and using conditional syscall
catchpoint
Product: gdb
Version: 8.3
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: iii at linux dot ibm.com
Target Milestone: ---
$ gdb --args podman build foo
GNU gdb (GDB) Fedora 8.3.50.20190824-26.fc31
Copyright (C) 2019 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 "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from podman...
Reading symbols from /usr/lib/debug/usr/bin/podman-1.7.0-2.fc31.x86_64.debug...
warning: Missing auto-load script at offset 0 in section .debug_gdb_scripts
of file /usr/lib/debug/usr/bin/podman-1.7.0-2.fc31.x86_64.debug.
Use `info auto-load python-scripts [REGEXP]' to list them.
(gdb) catch syscall openat
Catchpoint 1 (syscall 'openat' [257])
(gdb) r
Starting program: /usr/bin/podman build foo
Catchpoint 1 (call to syscall openat), __GI___open64_nocancel
(file=file@entry=0x7f800cb15a29 "/etc/ld.so.cache", oflag=oflag@entry=524288)
at ../sysdeps/unix/sysv/linux/open64_nocancel.c:45
45 return INLINE_SYSCALL_CALL (openat, AT_FDCWD, file, oflag |
EXTRA_OPEN_FLAGS,
(gdb) condition 1 $_regex((char *)$rsi, ".*/gid_map$")
(gdb) c
Continuing.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7f800a5a4700 (LWP 54488)]
[New Thread 0x7f8001da3700 (LWP 54489)]
[New Thread 0x7f8009da3700 (LWP 54490)]
[New Thread 0x7f80095a2700 (LWP 54491)]
[New Thread 0x7f8008da1700 (LWP 54492)]
[New Thread 0x7f8003fff700 (LWP 54493)]
[New Thread 0x7f80037fe700 (LWP 54494)]
[New Thread 0x7f8002ffd700 (LWP 54495)]
[New Thread 0x7f80027fc700 (LWP 54496)]
[New Thread 0x7f80015a2700 (LWP 54497)]
[New Thread 0x7f8000da1700 (LWP 54498)]
Error while mapping shared library sections:
Could not open `target:/lib64/libnss_sss.so.2' as an executable file: Operation
not permitted
Error while mapping shared library sections:
Could not open `target:/lib64/libnss_files.so.2' as an executable file:
Operation not permitted
Thread 1 "podman" hit Catchpoint 1 (call to syscall openat), syscall.Syscall6
() at /usr/lib/golang/src/syscall/asm_linux_amd64.s:53
53 /usr/lib/golang/src/syscall/asm_linux_amd64.s: No such file or
directory.
Missing separate debuginfos, use: dnf debuginfo-install
gpgme-1.13.1-3.fc31.x86_64 libassuan-2.5.3-2.fc31.x86_64
libgpg-error-1.36-2.fc31.x86_64 libseccomp-2.4.2-2.fc31.x86_64
(gdb) bt
#0 syscall.Syscall6 () at /usr/lib/golang/src/syscall/asm_linux_amd64.s:53
#1 0x00005634d822a5fd in syscall.openat (dirfd=-100, path=..., flags=524288,
mode=0, fd=<optimized out>, err=...) at
/usr/lib/golang/src/syscall/zsyscall_linux_amd64.go:68
#2 0x00005634d8250c91 in syscall.Open (path=..., mode=<optimized out>,
perm=5021504, fd=<optimized out>, err=...) at
/usr/lib/golang/src/syscall/syscall_linux.go:138
#3 os.openFileNolog (name=..., flag=0, perm=0, ~r3=<optimized out>, ~r4=...)
at /usr/lib/golang/src/os/file_unix.go:196
#4 0x00005634d824ec85 in os.OpenFile (name=..., flag=0, perm=0, ~r3=<optimized
out>, ~r4=...) at /usr/lib/golang/src/os/file.go:300
#5 0x00005634d8f88b23 in os.Open (name=...) at
/usr/lib/golang/src/os/file.go:280
#6 github.com/containers/libpod/pkg/rootless.ReadMappingsProc (path=...,
~r1=..., ~r2=...) at
/usr/src/debug/podman-1.7.0-2.fc31.x86_64/_build/src/github.com/containers/libpod/pkg/rootless/rootless_linux.go:521
#7 0x00005634d8f895c0 in
github.com/containers/libpod/pkg/rootless.ConfigurationMatches (~r0=<optimized
out>, ~r1=...)
at
/usr/src/debug/podman-1.7.0-2.fc31.x86_64/_build/src/github.com/containers/libpod/pkg/rootless/rootless_linux.go:592
#8 0x00005634d935aa23 in main.setupRootless (cmd=0x5634dad03660
<main..stmp_118>, args=..., ~r2=...) at
/usr/src/debug/podman-1.7.0-2.fc31.x86_64/_build/src/github.com/containers/libpod/cmd/podman/main_local.go:146
#9 0x00005634d9359462 in main.before (cmd=0x5634dad03660 <main..stmp_118>,
args=..., ~r2=...) at
/usr/src/debug/podman-1.7.0-2.fc31.x86_64/_build/src/github.com/containers/libpod/cmd/podman/main.go:124
#10 0x00005634d939654b in main.glob..func68 (cmd=0x5634dad03660
<main..stmp_118>, args=..., ~r2=...) at
/usr/src/debug/podman-1.7.0-2.fc31.x86_64/_build/src/github.com/containers/libpod/cmd/podman/main.go:78
#11 0x00005634d837427d in
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).execute
(c=0x5634dad03660 <main..stmp_118>, a=..., err=...)
at
/usr/src/debug/podman-1.7.0-2.fc31.x86_64/_build/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:805
#12 0x00005634d8374bcd in
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).ExecuteC
(c=0x5634dad03660 <main..stmp_118>, cmd=<optimized out>, err=...)
at
/usr/src/debug/podman-1.7.0-2.fc31.x86_64/_build/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:914
#13 0x00005634d93596b2 in
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).Execute
(c=0xffffffffffffffda)
at
/usr/src/debug/podman-1.7.0-2.fc31.x86_64/_build/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:864
#14 main.main () at
/usr/src/debug/podman-1.7.0-2.fc31.x86_64/_build/src/github.com/containers/libpod/cmd/podman/main.go:160
(gdb) c
Continuing.
Thread 1 "podman" hit Catchpoint 1 (returned from syscall openat),
syscall.Syscall6 () at /usr/lib/golang/src/syscall/asm_linux_amd64.s:53
53 in /usr/lib/golang/src/syscall/asm_linux_amd64.s
(gdb) c
Continuing.
[Detaching after vfork from child process 54502]
[Detaching after vfork from child process 54503]
STEP 1: FROM bash
[New Thread 0x7f7fdb7fa700 (LWP 54504)]
[Detaching after vfork from child process 54505]
STEP 2: COMMIT
6a4b13a05c1ad77f7adf578faa0dead71f1e091bf7e15b434c0ba1af1f3921db
[Detaching after vfork from child process 54508]
6a4b13a05c1ad77f7adf578faa0dead71f1e091bf7e15b434c0ba1af1f3921db
Couldn't get registers: No such process.
(gdb) bt
Selected thread is running.
(gdb) info threads
Id Target Id Frame
1 Thread 0x7f800c7f6740 (LWP 54483) "podman" (running)
2 Thread 0x7f800a5a4700 (LWP 54488) "podman" (running)
3 Thread 0x7f8001da3700 (LWP 54489) "podman" (running)
4 Thread 0x7f8009da3700 (LWP 54490) "podman" (running)
5 Thread 0x7f80095a2700 (LWP 54491) "podman" (running)
6 Thread 0x7f8008da1700 (LWP 54492) "podman" (running)
7 Thread 0x7f8003fff700 (LWP 54493) "podman" (running)
8 Thread 0x7f80037fe700 (LWP 54494) "podman" (running)
9 Thread 0x7f8002ffd700 (LWP 54495) "podman" (running)
10 Thread 0x7f80027fc700 (LWP 54496) "podman" (running)
11 Thread 0x7f80015a2700 (LWP 54497) "podman" (running)
* 12 Thread 0x7f8000da1700 (LWP 54498) "podman" (running)
13 Thread 0x7f7fdb7fa700 (LWP 54504) "podman" (running)
(gdb) bt
Selected thread is running.
At this point the debugging session is completely stuck.
The same binary can be debugged just fine when not using conditional syscall
catchpoint.
The problem also happens on s390 (that's where I originally hit it), but much
earlier:
(gdb) catch syscall openat
Catchpoint 1 (syscall 'openat' [288])
(gdb) r
Starting program: /usr/bin/podman build foo
Catchpoint 1 (call to syscall openat), __GI___open64_nocancel
(file=file@entry=0x3fffdfa098e "/etc/ld.so.cache", oflag=oflag@entry=524288) at
../sysdeps/unix/sysv/linux/open64_nocancel.c:45
45 ../sysdeps/unix/sysv/linux/open64_nocancel.c: No such file or
directory.
(gdb) condition 1 $_regex((char *)$r3, ".*/gid_map$")
(gdb) c
Continuing.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x3fff94ee910 (LWP 1629482)]
Cannot access memory at address 0x3fffd5014a6
(gdb) c
Cannot execute this command while the selected thread is running.
(gdb) x/a 0x3fffd5014a6
0x3fffd5014a6 <__GI___mmap64+86>: 0xa5aa719f000ec21
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26228-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 30 17:05:40 2020
Return-Path: <gdb-prs-return-26228-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 109773 invoked by alias); 30 Jan 2020 17:05:39 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 109745 invoked by uid 48); 30 Jan 2020 17:05:39 -0000
From: "iii at linux dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25485] "Selected thread is running" when debugging
multithreaded app and using conditional syscall catchpoint
Date: Thu, 30 Jan 2020 17: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.3
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iii at linux 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: cc
Message-ID: <bug-25485-4717-t93zYxIV0V@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25485-4717@http.sourceware.org/bugzilla/>
References: <bug-25485-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00143.txt
Content-length: 480
https://sourceware.org/bugzilla/show_bug.cgi?id=25485
Ilya Leoshkevich <iii at linux dot ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |arnez at linux dot ibm.com,
| |krebbel at linux dot ibm.com
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26229-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 30 18:15:56 2020
Return-Path: <gdb-prs-return-26229-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 2203 invoked by alias); 30 Jan 2020 18:15:54 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 2171 invoked by uid 48); 30 Jan 2020 18:15:53 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/25478] gdb hangs after external SIGKILL
Date: Thu, 30 Jan 2020 18: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25478-4717-5wIqe5O6SB@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00144.txt
Content-length: 843
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tankut.baris.aktemur@intel.
| |com
--- Comment #10 from Tom de Vries <vries at gcc dot gnu.org> ---
FWIW, an easier way to to reproduce (or indeed test a fix) is:
...
$ gdb -ex "set prompt (master-gdb) " -ex "b stop_all_threads" -ex r -ex "shell
killall -9 a.out" -ex c --args gdb -ex "set debug infrun 1" -ex r -ex c -ex c
--args a.out
...
The only manual interaction needed is to press ^C after a.out has been started.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26230-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 00:42:38 2020
Return-Path: <gdb-prs-return-26230-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 48103 invoked by alias); 31 Jan 2020 00:42:37 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 48079 invoked by uid 55); 31 Jan 2020 00:42:37 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/9765] Scrolling to end of program in asm layout is broken
Date: Fri, 31 Jan 2020 00:42: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: cvs-commit at gcc dot gnu.org
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: <bug-9765-4717-IwpIhLNH6f@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-9765-4717@http.sourceware.org/bugzilla/>
References: <bug-9765-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00145.txt
Content-length: 2353
https://sourceware.org/bugzilla/show_bug.cgi?id=9765
--- Comment #14 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=42330a681af23a80d3e1f201d2a65886875e74bd
commit 42330a681af23a80d3e1f201d2a65886875e74bd
Author: Andrew Burgess <andrew.burgess@embecosm.com>
Date: Fri Jan 24 12:46:56 2020 +0000
gdb/tui: Disassembler scrolling of very small programs
In TUI mode, if the disassembly output for the program is less than
one screen long, then currently if the user scrolls down until on the
last assembly instruction is displayed and then tries to scroll up
using Page-Up, the display doesn't update - they are stuck viewing the
last line.
If the user tries to scroll up using the Up-Arrow, then the display
scrolls normally.
What is happening is on the Page-Up we ask GDB to scroll backward the
same number of lines as the height of the TUI ASM window. The back
scanner, which looks for a good place to start disassembling, fails to
find a starting address which will provide the requested number of new
lines before we get back to the original starting address (which is
not surprising, our whole program contains less than a screen height
of instructions), as a result the back scanner gives up and returns
the original starting address.
When we scroll with Up-Arrow we only ask the back scanner to find 1
new instruction, which it manages to do, so this scroll works.
The solution here is, when we fail to find enough instructions, to
return the lowest address we did manage to find. This will ensure we
jump to the lowest possible address in the disassembly output.
gdb/ChangeLog:
PR tui/9765
* tui/tui-disasm.c (tui_find_disassembly_address): If we don't
have enough lines to fill the screen, still return the lowest
address we found.
gdb/testsuite/ChangeLog:
PR tui/9765
* gdb.tui/tui-layout-asm-short-prog.S: New file.
* gdb.tui/tui-layout-asm-short-prog.exp: New file.
Change-Id: I6a6a7972c68a0559e9717fd8d82870b669a40af3
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26231-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 05:11:54 2020
Return-Path: <gdb-prs-return-26231-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 56785 invoked by alias); 31 Jan 2020 05:11:54 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 56755 invoked by uid 48); 31 Jan 2020 05:11:53 -0000
From: "philippe.waroquiers at skynet dot be" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Fri, 31 Jan 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: philippe.waroquiers at skynet dot be
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25475-4717-x63AqcgSLP@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/>
References: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00146.txt
Content-length: 1209
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
--- Comment #3 from philippe.waroquiers at skynet dot be ---
Strange ...
I see no failure on debian 10.2:
...
(gdb) PASS: gdb.server/solib-list.exp: non-stop 1: file binfile
target remote localhost:2347
Remote debugging using localhost:2347
warning: Mismatch between current exec-file
/bd/home/philippe/gdb/git/build_binutils-gdb/gdb/testsuite/outputs/gdb.server/solib-list/solib-list
and automatically determined exec-file /lib/x86_64-linux-gnu/ld-2.28.so
exec-file-mismatch handling is currently "ask"
Reading symbols from /lib/x86_64-linux-gnu/ld-2.28.so...
Reading symbols from
/usr/lib/debug/.build-id/f2/5dfd7b95be4ba386fd71080accae8c0732b711.debug...
Program stopped.
0x00007ffff7fd6090 in _start ()
...
=== gdb Summary ===
# of expected passes 16
Also, it looks strange that the automatically determined exec-file
is /lib64/ld-2.26.so
(that sounds a somewhat strange executable).
Apart of that, the 'set exec-file-mismatch' setting was done
to allow the user to choose the behaviour so the fix looks reasonable
to me.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26232-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 09:39:52 2020
Return-Path: <gdb-prs-return-26232-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 1344 invoked by alias); 31 Jan 2020 09:39:51 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 1323 invoked by uid 48); 31 Jan 2020 09:39:51 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Fri, 31 Jan 2020 09: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: vries 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: <bug-25475-4717-vD7zwwMV5N@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/>
References: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00147.txt
Content-length: 1426
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to philippe.waroquiers from comment #3)
> Strange ...
> I see no failure on debian 10.2:
> ...
> (gdb) PASS: gdb.server/solib-list.exp: non-stop 1: file binfile
> target remote localhost:2347
> Remote debugging using localhost:2347
> warning: Mismatch between current exec-file
> /bd/home/philippe/gdb/git/build_binutils-gdb/gdb/testsuite/outputs/gdb.
> server/solib-list/solib-list
> and automatically determined exec-file /lib/x86_64-linux-gnu/ld-2.28.so
> exec-file-mismatch handling is currently "ask"
So, if there is a mismatch, and the handling is ask ... where is the asking
being done?
If that's missing in your log, does that not indicate a bug in
exec-file-mismatch?
> Reading symbols from /lib/x86_64-linux-gnu/ld-2.28.so...
> Reading symbols from
> /usr/lib/debug/.build-id/f2/5dfd7b95be4ba386fd71080accae8c0732b711.debug...
>
> Program stopped.
> 0x00007ffff7fd6090 in _start ()
> ...
> === gdb Summary ===
>
> # of expected passes 16
>
>
> Also, it looks strange that the automatically determined exec-file
> is /lib64/ld-2.26.so
> (that sounds a somewhat strange executable).
>
Yes, but that's explicitly done by the test-case, and that's the same in both
logs.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26233-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 09:41:51 2020
Return-Path: <gdb-prs-return-26233-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 2594 invoked by alias); 31 Jan 2020 09:41:51 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 2574 invoked by uid 48); 31 Jan 2020 09:41:50 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Fri, 31 Jan 2020 09: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: vries 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: <bug-25475-4717-WAp7j6NsuI@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/>
References: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00148.txt
Content-length: 324
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 12239
--> https://sourceware.org/bugzilla/attachment.cgi?id=12239&action=edit
offending gdb.log
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26234-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 09:42:41 2020
Return-Path: <gdb-prs-return-26234-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 3339 invoked by alias); 31 Jan 2020 09:42:41 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 3319 invoked by uid 48); 31 Jan 2020 09:42:40 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Fri, 31 Jan 2020 09: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: vries 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: <bug-25475-4717-hODzDb6den@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/>
References: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00149.txt
Content-length: 356
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 12240
--> https://sourceware.org/bugzilla/attachment.cgi?id=12240&action=edit
gdb.log with test-case fix mentioned in comment 2
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26235-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 09:44:13 2020
Return-Path: <gdb-prs-return-26235-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 3986 invoked by alias); 31 Jan 2020 09:44:13 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 3964 invoked by uid 48); 31 Jan 2020 09:44:13 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Fri, 31 Jan 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25475-4717-jJcdYt2G0Q@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/>
References: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00150.txt
Content-length: 398
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #4)
> (In reply to philippe.waroquiers from comment #3)
> > Strange ...
> > I see no failure on debian 10.2:
Can you attach the entire gdb.log here as well?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26236-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 10:11:16 2020
Return-Path: <gdb-prs-return-26236-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 62697 invoked by alias); 31 Jan 2020 10:11:16 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 62675 invoked by uid 48); 31 Jan 2020 10:11:15 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/9765] Scrolling to end of program in asm layout is broken
Date: Fri, 31 Jan 2020 10:11: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: shahab.vahedi at gmail 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: <bug-9765-4717-2nj42hvbQx@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-9765-4717@http.sourceware.org/bugzilla/>
References: <bug-9765-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00151.txt
Content-length: 311
https://sourceware.org/bugzilla/show_bug.cgi?id=9765
--- Comment #15 from Shahab <shahab.vahedi at gmail dot com> ---
I can confirm every corner of the issue is resolved with the latest patch.
Please confirm and close this bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26237-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 10:11:59 2020
Return-Path: <gdb-prs-return-26237-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 63222 invoked by alias); 31 Jan 2020 10:11:58 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 63204 invoked by uid 48); 31 Jan 2020 10:11:57 -0000
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25345] Tiny programs (few lines of assembly) cause GDB's
TUI to crash
Date: Fri, 31 Jan 2020 10:11: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: shahab.vahedi 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:
Message-ID: <bug-25345-4717-HFurUjJo3M@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25345-4717@http.sourceware.org/bugzilla/>
References: <bug-25345-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00152.txt
Content-length: 396
https://sourceware.org/bugzilla/show_bug.cgi?id=25345
--- Comment #14 from Shahab <shahab.vahedi at gmail dot com> ---
This patch:
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=42330a681af23a80d3e1f201d2a65886875e74bd
Covers all the corner cases. This issue is completely resolved for good.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26238-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 10:22:42 2020
Return-Path: <gdb-prs-return-26238-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 112309 invoked by alias); 31 Jan 2020 10:22:42 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 111813 invoked by uid 48); 31 Jan 2020 10:22:42 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25488] New: UNRESOLVED:
gdb.server/server-kill-python.exp: ensure inferior is running
Date: Fri, 31 Jan 2020 10:22: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: vries 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: <bug-25488-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00153.txt
Content-length: 1679
https://sourceware.org/bugzilla/show_bug.cgi?id=25488
Bug ID: 25488
Summary: UNRESOLVED: gdb.server/server-kill-python.exp: ensure
inferior is running
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
...
spawn
/data/gdb_versions/devel/build/gdb/testsuite/../../gdb/gdbserver/gdbserver
--once localhost:2390
/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/server-exec-info/server-exec-info
/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/server-kill-python/server-kill-python^M
Process
/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/server-exec-info/server-exec-info
created; pid = 29682^M
Listening on port 2390^M
spawn /data/gdb_versions/devel/build/gdb/testsuite/../../gdb/gdb -nw -nx
-data-directory /data/gdb_versions/devel/build/gdb/testsuite/../data-directory
-quiet -iex set height 0 -iex set width 0 -ex source
/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/server-kill-python/file1.py^M
Remote debugging from host ::1, port 58540^M
^M
Child exited with status 0^M
ERROR: GDB process no longer exists
GDB process exited with wait status 29674 exp47 0 0
UNRESOLVED: gdb.server/server-kill-python.exp: ensure inferior is running
testcase
/data/gdb_versions/devel/src/gdb/testsuite/gdb.server/server-kill-python.exp
completed in 0 seconds
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26239-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 10:28:49 2020
Return-Path: <gdb-prs-return-26239-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 29837 invoked by alias); 31 Jan 2020 10:28:49 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 29243 invoked by uid 48); 31 Jan 2020 10:28:49 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25488] UNRESOLVED: gdb.server/server-kill-python.exp:
ensure inferior is running
Date: Fri, 31 Jan 2020 10:28: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: vries 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: <bug-25488-4717-9iYnBghBDi@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25488-4717@http.sourceware.org/bugzilla/>
References: <bug-25488-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00154.txt
Content-length: 304
https://sourceware.org/bugzilla/show_bug.cgi?id=25488
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Does not reproduce when I run only the testcase, but does reproduce when I run
the gdb.server tests.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26240-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 11:12:24 2020
Return-Path: <gdb-prs-return-26240-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 38160 invoked by alias); 31 Jan 2020 11:12:23 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 38141 invoked by uid 48); 31 Jan 2020 11:12:23 -0000
From: "macro@linux-mips.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/25489] New: RISC-V: NaN boxing not done for assignments to
FPRs
Date: Fri, 31 Jan 2020 11:12: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: 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_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
cf_gcctarget
Message-ID: <bug-25489-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00155.txt
Content-length: 1727
https://sourceware.org/bugzilla/show_bug.cgi?id=25489
Bug ID: 25489
Summary: RISC-V: NaN boxing not done for assignments to FPRs
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: tdep
Assignee: unassigned at sourceware dot org
Reporter: macro@linux-mips.org
Target Milestone: ---
Target: riscv64-*-*
Observed as a failure in testing:
(gdb) FAIL: gdb.base/return-nodebug.exp: float: full width of the returned
result
The culprit is GDB fails to NaN-box floating-point data of the `float'
type when assigning it to a hardware register. Storing an unboxed
datum into an FPR causes hardware to consider it a canonican NaN, e.g.
in this excerpt from `info float':
fa0 {float = -1,
double = 1.5873523201947252e-314} (raw 0x00000000bf800000)
fa1 {float = -1,
double = -nan(0xfffffbf800000)} (raw 0xffffffffbf800000)
we have a correctly boxed `-1.0f' value in $fa1, however the value in
in $fa0 is not boxed (i.e. the upper bits are not all-ones), having
been set by GDB rather than hardware (as with e.g. the FLW instruction),
in this case by requesting a function return with:
(gdb) return (float) -1
Consequently when an attempt is made to transfer the value to another
register with a hardware instruction, such as:
fmv.s fa5,fa0
as in the test case considered, a NaN is instead produced:
fa5 {float = nan(0x400000),
double = -nan(0xfffff7fc00000)} (raw 0xffffffff7fc00000)
which causes the failure reported.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26241-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 13:28:01 2020
Return-Path: <gdb-prs-return-26241-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 54720 invoked by alias); 31 Jan 2020 13:28:01 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 54676 invoked by uid 48); 31 Jan 2020 13:28:00 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25488] UNRESOLVED: gdb.server/server-kill-python.exp:
ensure inferior is running
Date: Fri, 31 Jan 2020 13:28: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: vries 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: <bug-25488-4717-w2GBAcgpHl@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25488-4717@http.sourceware.org/bugzilla/>
References: <bug-25488-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00156.txt
Content-length: 1001
https://sourceware.org/bugzilla/show_bug.cgi?id=25488
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andrew.burgess at embecosm dot com
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Fixed by:
...
diff --git a/gdb/testsuite/gdb.server/server-kill-python.exp
b/gdb/testsuite/gdb.server/server-kill-python.exp
index 28064ca0a46..ae0eb2c11bd 100644
--- a/gdb/testsuite/gdb.server/server-kill-python.exp
+++ b/gdb/testsuite/gdb.server/server-kill-python.exp
@@ -32,6 +32,9 @@ if {[build_executable "failed to prepare" ${testfile} \
return -1
}
+global last_loaded_file
+unset -nocomplain last_loaded_file
+
# Start gdbserver.
set res [gdbserver_spawn "${binfile}"]
set gdbserver_protocol [lindex $res 0]
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26242-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 13:29:39 2020
Return-Path: <gdb-prs-return-26242-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 56004 invoked by alias); 31 Jan 2020 13:29:39 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 55975 invoked by uid 48); 31 Jan 2020 13:29:38 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25488] UNRESOLVED: gdb.server/server-kill-python.exp:
ensure inferior is running
Date: Fri, 31 Jan 2020 13:29: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: vries 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: <bug-25488-4717-vJuBujVphs@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25488-4717@http.sourceware.org/bugzilla/>
References: <bug-25488-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00157.txt
Content-length: 430
https://sourceware.org/bugzilla/show_bug.cgi?id=25488
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
BTW, same test-case needs:
...
@@ -66,7 +69,7 @@ with_spawn_id $server_spawn_id {
pass $gdb_test_name
}
timeout {
- fail $gdb_tst_name
+ fail $gdb_test_name
}
}
}
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26243-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 14:40:59 2020
Return-Path: <gdb-prs-return-26243-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 123181 invoked by alias); 31 Jan 2020 14:40:59 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 123161 invoked by uid 48); 31 Jan 2020 14:40:59 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/9765] Scrolling to end of program in asm layout is broken
Date: Fri, 31 Jan 2020 14: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: 6.50
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: tromey at sourceware dot 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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-9765-4717-3wtPgwYx8C@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-9765-4717@http.sourceware.org/bugzilla/>
References: <bug-9765-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00158.txt
Content-length: 562
https://sourceware.org/bugzilla/show_bug.cgi?id=9765
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.1
--- Comment #16 from Tom Tromey <tromey at sourceware dot org> ---
Fixed!
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26244-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 20:24:51 2020
Return-Path: <gdb-prs-return-26244-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 56228 invoked by alias); 31 Jan 2020 20:24:51 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 56208 invoked by uid 48); 31 Jan 2020 20:24:51 -0000
From: "vk2bea+gdb at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Fri, 31 Jan 2020 20: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: critical
X-Bugzilla-Who: vk2bea+gdb 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: <bug-24915-4717-kfcs1mX7L4@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00159.txt
Content-length: 1996
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
Michael Katzmann <vk2bea+gdb at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vk2bea+gdb at gmail dot com
--- Comment #3 from Michael Katzmann <vk2bea+gdb at gmail dot com> ---
I'm still having an issue.
Using gdb with Eclipse CDT, the breakpoint is set (by the Eclipse GUI) properly
only if it is in the initial file (containing main).
If it is in another source file I get a'<PENDING> address.
e.g. I have a source file (test.c) containing the main entry point and another
(test2.c).
I set a break point in both files... (and looking with the 'Debugger Console'
(gdb) info break
Num Type Disp Enb Address What
2 breakpoint keep y 0x0000000000401134 in main at ../src/test.c:18
3 breakpoint keep y <PENDING>
/home/michael/eclipse-workspace/test/src/test2.c:9
(gdb)
GNU gdb (GDB) Fedora 8.3.50.20190824-27.fc31
(also tried with ...
GNU gdb (GDB) Fedora 9.0.50.20191119-2.fc31
with similar results)
The Eclipse folks say that this is a gdb issue....
I can set the breakpoint with the command line (although it curiously sets 2
additional breakpoints)...
(gdb) break test2.c:8
Breakpoint 4 at 0x401150: file ../src/test2.c, line 8.
(gdb) info break
Num Type Disp Enb Address What
2 breakpoint keep y 0x0000000000401134 in main at ../src/test.c:18
3 breakpoint keep y <PENDING>
/home/michael/eclipse-workspace/test/src/test2.c:9
4 breakpoint keep y 0x0000000000401150 in externalProc at
../src/test2.c:8
5 breakpoint keep y 0x0000000000401150 in externalProc at
../src/test2.c:8
(gdb)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26245-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 20:37:44 2020
Return-Path: <gdb-prs-return-26245-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 90048 invoked by alias); 31 Jan 2020 20:37:44 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 90029 invoked by uid 48); 31 Jan 2020 20:37:44 -0000
From: "jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Fri, 31 Jan 2020 20:37: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: 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: <bug-24915-4717-lZ95cN4LMd@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00160.txt
Content-length: 1134
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #4 from Jonah Graham <jonah at kichwacoders dot com> ---
> I'm still having an issue.
Hi Michael, this is because the GDB in Fedora 31 is not a released GDB, but
rather one from GDB sources that didn't include the now fixed regression.
Therefore this bug report belongs with Fedora I believe.
I reached out to the GDB maintainer, sergiodj, and he was looking for someone
to test. Can you do that on Fedora? I'll email you the conversation and you can
pick it up from there.
Also, if you can confirm that the fix [1] is in fc31's gdb then you may be
running into a different problem and I would like to work with you to resolve
it.
The alternative in the meantime is to do what was done in [2] and compile your
own gdb.
BTW Matthew, are you related to Michael Katzmann, the submitter of the bug in
CDT[2]? If not that is a random coincidence.
[1] https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/82
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=558519#c2
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26246-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 20:44:35 2020
Return-Path: <gdb-prs-return-26246-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 99968 invoked by alias); 31 Jan 2020 20:44:35 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 99945 invoked by uid 55); 31 Jan 2020 20:44:35 -0000
From: "vk2bea at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Fri, 31 Jan 2020 20: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: vk2bea 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: <bug-24915-4717-WfFJRxOqmy@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00161.txt
Content-length: 1794
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #5 from vk2bea at gmail dot com ---
Hi Johnah,
Ha - this is what Sergio said ... Thanks for the heads up, Michael. I
can't look at this right now; can you comment on the upstream bug, please?
It would be good to know if Jonah can confirm this issue, since he works
with CDT.
AFAIK Sergio did fix the initial issue (I'm using the 'testing' RPM
version).
On Fri, Jan 31, 2020 at 3:37 PM jonah at kichwacoders dot com <
sourceware-bugzilla@sourceware.org> wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=24915
>
> --- Comment #4 from Jonah Graham <jonah at kichwacoders dot com> ---
> > I'm still having an issue.
>
> Hi Michael, this is because the GDB in Fedora 31 is not a released GDB, but
> rather one from GDB sources that didn't include the now fixed regression.
> Therefore this bug report belongs with Fedora I believe.
>
> I reached out to the GDB maintainer, sergiodj, and he was looking for
> someone
> to test. Can you do that on Fedora? I'll email you the conversation and
> you can
> pick it up from there.
>
> Also, if you can confirm that the fix [1] is in fc31's gdb then you may be
> running into a different problem and I would like to work with you to
> resolve
> it.
>
> The alternative in the meantime is to do what was done in [2] and compile
> your
> own gdb.
>
> BTW Matthew, are you related to Michael Katzmann, the submitter of the bug
> in
> CDT[2]? If not that is a random coincidence.
>
> [1] https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/82
> [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=558519#c2
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26247-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 20:45:39 2020
Return-Path: <gdb-prs-return-26247-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 105694 invoked by alias); 31 Jan 2020 20:45:38 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 105610 invoked by uid 55); 31 Jan 2020 20:45:32 -0000
From: "vk2bea at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Fri, 31 Jan 2020 20: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: vk2bea 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: <bug-24915-4717-nbrVPYSHlX@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00162.txt
Content-length: 2229
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #6 from vk2bea at gmail dot com ---
This was the bugzilla from Fedora ..
https://bugzilla.redhat.com/show_bug.cgi?id=1785768
On Fri, Jan 31, 2020 at 3:43 PM Michael Katzmann <vk2bea@gmail.com> wrote:
> Hi Johnah,
> Ha - this is what Sergio said ... Thanks for the heads up, Michael. I
> can't look at this right now; can you comment on the upstream bug, please?
> It would be good to know if Jonah can confirm this issue, since he works
> with CDT.
>
> AFAIK Sergio did fix the initial issue (I'm using the 'testing' RPM
> version).
>
> On Fri, Jan 31, 2020 at 3:37 PM jonah at kichwacoders dot com <
> sourceware-bugzilla@sourceware.org> wrote:
>
>> https://sourceware.org/bugzilla/show_bug.cgi?id=24915
>>
>> --- Comment #4 from Jonah Graham <jonah at kichwacoders dot com> ---
>> > I'm still having an issue.
>>
>> Hi Michael, this is because the GDB in Fedora 31 is not a released GDB,
>> but
>> rather one from GDB sources that didn't include the now fixed regression.
>> Therefore this bug report belongs with Fedora I believe.
>>
>> I reached out to the GDB maintainer, sergiodj, and he was looking for
>> someone
>> to test. Can you do that on Fedora? I'll email you the conversation and
>> you can
>> pick it up from there.
>>
>> Also, if you can confirm that the fix [1] is in fc31's gdb then you may be
>> running into a different problem and I would like to work with you to
>> resolve
>> it.
>>
>> The alternative in the meantime is to do what was done in [2] and compile
>> your
>> own gdb.
>>
>> BTW Matthew, are you related to Michael Katzmann, the submitter of the
>> bug in
>> CDT[2]? If not that is a random coincidence.
>>
>> [1] https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/82
>> [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=558519#c2
>>
>> --
>> You are receiving this mail because:
>> You are on the CC list for the bug.
>
>
>
> --
> |\ _,,,---,,_ Michael Katzmann
> /,`.-'`' -. ;-;;,_ NV3Z / VK2BEA / G4NYV
> |,4- ) )-,_. ,\ ( `'-'
> '---''(_/--' `-'\_) vk2bea@gmail.com
>
>
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26248-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 21:25:39 2020
Return-Path: <gdb-prs-return-26248-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 125562 invoked by alias); 31 Jan 2020 21:25:39 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 125543 invoked by uid 48); 31 Jan 2020 21:25:39 -0000
From: "vk2bea+gdb at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Fri, 31 Jan 2020 21: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: vk2bea+gdb 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: <bug-24915-4717-uw8RUtcQct@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00163.txt
Content-length: 339
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #7 from Michael Katzmann <vk2bea+gdb at gmail dot com> ---
OK I just compiled and tried ...
GNU gdb (GDB) 10.0.50.20200131-git
and also see this issue. So no, the problem is not resolved.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26249-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 22:05:12 2020
Return-Path: <gdb-prs-return-26249-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 113133 invoked by alias); 31 Jan 2020 22:05:11 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 113110 invoked by uid 48); 31 Jan 2020 22:05:11 -0000
From: "carlo_bramini at users dot sourceforge.net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25318] Aarch64-SIM: BLR opcode does not support XLR
register properly.
Date: Fri, 31 Jan 2020 22: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: carlo_bramini at users dot sourceforge.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: <bug-25318-4717-xDt61XpH5e@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25318-4717@http.sourceware.org/bugzilla/>
References: <bug-25318-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00164.txt
Content-length: 679
https://sourceware.org/bugzilla/show_bug.cgi?id=25318
--- Comment #3 from Carlo Bramini <carlo_bramini at users dot sourceforge.net> ---
> Maybe it is small enough and obvious enough to accept without an assignment?
I hope that it could be possible.
As you said, it is true that QEMU is more advanced in terms of speed and
compatibility: implementation of some opcodes is also missing inside the
Aarch64 simulator of GDB, but actually it was more than enough for my hobbyist
development and it covered all my needs without using an host OS.
Thank you very much for your time.
Sincerely.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26250-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 22:11:42 2020
Return-Path: <gdb-prs-return-26250-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 120339 invoked by alias); 31 Jan 2020 22:11:41 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 120319 invoked by uid 48); 31 Jan 2020 22:11:41 -0000
From: "jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Fri, 31 Jan 2020 22:11: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: 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: <bug-24915-4717-ZYtHYR2AiL@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00165.txt
Content-length: 588
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #8 from Jonah Graham <jonah at kichwacoders dot com> ---
(In reply to Michael Katzmann from comment #7)
> OK I just compiled and tried ...
>
> GNU gdb (GDB) 10.0.50.20200131-git
>
> and also see this issue. So no, the problem is not resolved.
I will try to reproduce using GDB from source and CDT. Once I have reproduced
(or not) then we'll have a better idea of where to go next. Thanks Michael for
your effort so far on this!
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26251-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 22:18:11 2020
Return-Path: <gdb-prs-return-26251-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 1232 invoked by alias); 31 Jan 2020 22:18:11 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 1207 invoked by uid 48); 31 Jan 2020 22:18:11 -0000
From: "jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Fri, 31 Jan 2020 22: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: critical
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: <bug-24915-4717-uyljbhDuOP@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00166.txt
Content-length: 399
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #9 from Jonah Graham <jonah at kichwacoders dot com> ---
Michael, Can you please provide the MI traces of the failure? See
https://wiki.eclipse.org/CDT/User/NewIn92#Hide_gdb_traces_by_default for how to
turn on MI traces if not on already. Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26252-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 22:25:29 2020
Return-Path: <gdb-prs-return-26252-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 33922 invoked by alias); 31 Jan 2020 22:25:29 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 33903 invoked by uid 48); 31 Jan 2020 22:25:29 -0000
From: "vk2bea+gdb at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Fri, 31 Jan 2020 22: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: vk2bea+gdb 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: <bug-24915-4717-ibZ9DAtbDv@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00167.txt
Content-length: 7163
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #10 from Michael Katzmann <vk2bea+gdb at gmail dot com> ---
427,171 3-environment-cd /home/michael/eclipse-workspace/test
427,172 3^done
427,172 (gdb)
427,172 4-gdb-set breakpoint pending on
427,172 4^done
427,172 (gdb)
427,173 5-gdb-set detach-on-fork on
427,173 5^done
427,173 (gdb)
427,173 6-enable-pretty-printing
427,173 6^done
427,173 (gdb)
427,173 7-gdb-set python print-stack none
427,173 7^done
427,173 (gdb)
427,174 8-gdb-set print object on
427,174 8^done
427,174 (gdb)
427,178 9-gdb-set print sevenbit-strings on
427,178 9^done
427,178 (gdb)
427,179 10-gdb-set host-charset UTF-8
427,179 10^done
427,179 (gdb)
427,179 11-gdb-set target-charset UTF-8
427,179 11^done
427,179 (gdb)
427,179 12-gdb-set target-wide-charset UTF-32
427,180 12^done
427,180 (gdb)
427,180 13-gdb-set dprintf-style call
427,180 13^done
427,180 (gdb)
427,180 14source .gdbinit
427,180 &"source .gdbinit\n"
427,180 &".gdbinit: No such file or directory.\n"
427,181 14^error,msg=".gdbinit: No such file or directory."
427,181 (gdb)
427,181 15-gdb-set target-async on
427,181 15^done
427,181 (gdb)
427,181 16-gdb-set record full stop-at-limit off
427,182 16^done
427,182 (gdb)
427,182 17-list-thread-groups
427,182 17^done,groups=[{id="i1",type="process"}]
427,182 (gdb)
427,183 18-gdb-set auto-solib-add on
427,183 18^done
427,183 (gdb)
427,184 19-file-exec-and-symbols --thread-group i1
/home/michael/eclipse-workspace/test/Debug/test
427,186 19^done
427,186 (gdb)
427,186 20-gdb-show --thread-group i1 language
427,186 20^done,value="auto"
427,186 (gdb)
427,187 21-gdb-set --thread-group i1 language c
427,187 21^done
427,187 (gdb)
427,187 22-interpreter-exec --thread-group i1 console "p/x (char)-1"
427,187 ~"$1 = 0xff\n"
427,187 22^done
427,187 (gdb)
427,188 23-data-evaluate-expression --thread-group i1 "sizeof (void*)"
427,188 23^done,value="8"
427,188 (gdb)
427,188 24-gdb-set --thread-group i1 language auto
427,188 24^done
427,188 (gdb)
427,188 25-interpreter-exec --thread-group i1 console "show endian"
427,188 ~"The target endianness is set automatically (currently little
endian)\n"
427,188 25^done
427,189 (gdb)
427,190 26-break-insert -f /home/michael/eclipse-workspace/test/src/test.c:18
427,190 27-break-insert -f /home/michael/eclipse-workspace/test/src/test2.c:9
427,190
26^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x0000000000401134"\
,func="main",file="../src/test.c",fullname="/home/michael/eclipse-workspace/test/Debug/../src/test.c\
",line="18",thread-groups=["i1"],times="0",original-location="/home/michael/eclipse-workspace/test/s\
rc/test.c:18"}
427,190 (gdb)
427,190 &"No source file named
/home/michael/eclipse-workspace/test/src/test2.c.\n"
427,190
27^done,bkpt={number="2",type="breakpoint",disp="keep",enabled="y",addr="<PENDING>",pending=\
"/home/michael/eclipse-workspace/test/src/test2.c:9",times="0",original-location="/home/michael/ecli\
pse-workspace/test/src/test2.c:9"}
427,190 (gdb)
427,194 28-break-insert -t -f main
427,194
28^done,bkpt={number="3",type="breakpoint",disp="del",enabled="y",addr="0x000000000040112a",\
func="main",file="../src/test.c",fullname="/home/michael/eclipse-workspace/test/Debug/../src/test.c"\
,line="17",thread-groups=["i1"],times="0",original-location="main"}
427,195 (gdb)
427,195 29-inferior-tty-set --thread-group i1 /dev/pts/2
427,195 29^done
427,195 (gdb)
427,204 30-exec-run --thread-group i1
427,205 =thread-group-started,id="i1",pid="421842"
427,205 =thread-created,id="1",group-id="i1"
427,211
=library-loaded,id="/lib64/ld-linux-x86-64.so.2",target-name="/lib64/ld-linux-x86-64.so.2",h\
ost-name="/lib64/ld-linux-x86-64.so.2",symbols-loaded="0",thread-group="i1",ranges=[{from="0x00007ff\
ff7fd3110",to="0x00007ffff7ff2bb4"}]
427,212 31-list-thread-groups
427,220 &"warning: the debug information found in
\"/usr/lib/debug//lib64/ld-2.30.so.debug\" does no\
t match \"/lib64/ld-linux-x86-64.so.2\" (CRC mismatch).\n"
427,220 &"\n"
427,223 &"warning: the debug information found in
\"/usr/lib/debug//usr/lib64/ld-2.30.so.debug\" doe\
s not match \"/lib64/ld-linux-x86-64.so.2\" (CRC mismatch).\n"
427,223 &"\n"
427,273 30^running
427,273 *running,thread-id="all"
427,274 (gdb)
427,274
31^done,groups=[{id="i1",type="process",pid="421842",executable="/home/michael/eclipse-works\
pace/test/Debug/test",cores=["4"]}]
427,274 (gdb)
427,274
=library-loaded,id="/lib64/libc.so.6",target-name="/lib64/libc.so.6",host-name="/lib64/libc.\
so.6",symbols-loaded="0",thread-group="i1",ranges=[{from="0x00007ffff7ddb6b0",to="0x00007ffff7f28bbf\
"}]
427,492
=breakpoint-modified,bkpt={number="3",type="breakpoint",disp="del",enabled="y",addr="0x00000\
0000040112a",func="main",file="../src/test.c",fullname="/home/michael/eclipse-workspace/test/Debug/.\
./src/test.c",line="17",thread-groups=["i1"],times="1",original-location="main"}
427,493 ~"\n"
427,493 ~"Temporary breakpoint 3, main () at ../src/test.c:17\n"
427,493 ~"17\t\tputs(\"!!!Hello World!!!\"); /* prints !!!Hello World!!! */\n"
427,493
*stopped,reason="breakpoint-hit",disp="del",bkptno="3",frame={addr="0x000000000040112a",func\
="main",args=[],file="../src/test.c",fullname="/home/michael/eclipse-workspace/test/Debug/../src/tes\
t.c",line="17",arch="i386:x86-64"},thread-id="1",stopped-threads="all",core="4"
427,493 =breakpoint-deleted,id="3"
427,496 32-list-thread-groups
427,497
32^done,groups=[{id="i1",type="process",pid="421842",executable="/home/michael/eclipse-works\
pace/test/Debug/test",cores=["4"]}]
427,497 (gdb)
427,523 33-list-thread-groups i1
427,523 33^done,threads=[{id="1",target-id="process
421842",name="test",frame={level="0",addr="0x000\
000000040112a",func="main",args=[],file="../src/test.c",fullname="/home/michael/eclipse-workspace/te\
st/Debug/../src/test.c",line="17",arch="i386:x86-64"},state="stopped",core="4"}]
427,523 (gdb)
427,528 34-stack-info-depth --thread 1 11
427,530 34^done,depth="1"
427,530 (gdb)
427,536 35-stack-select-frame --thread 1 0
427,536 35^done
427,536 (gdb)
427,539 36-thread-info 1
427,539 36^done,threads=[{id="1",target-id="process
421842",name="test",frame={level="0",addr="0x000\
000000040112a",func="main",args=[],file="../src/test.c",fullname="/home/michael/eclipse-workspace/te\
st/Debug/../src/test.c",line="17",arch="i386:x86-64"},state="stopped",core="4"}]
427,539 37-list-thread-groups
427,539 (gdb)
427,539
37^done,groups=[{id="i1",type="process",pid="421842",executable="/home/michael/eclipse-works\
pace/test/Debug/test",cores=["4"]}]
427,539 (gdb)
427,557 38-stack-list-locals --thread 1 --frame 0 1
427,557 38^done,locals=[]
427,558 (gdb)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26253-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 23:05:40 2020
Return-Path: <gdb-prs-return-26253-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 97831 invoked by alias); 31 Jan 2020 23:05:39 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 97804 invoked by uid 48); 31 Jan 2020 23:05:39 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25318] Aarch64-SIM: BLR opcode does not support XLR
register properly.
Date: Fri, 31 Jan 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot 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: cc
Message-ID: <bug-25318-4717-oSVfY2Mftr@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25318-4717@http.sourceware.org/bugzilla/>
References: <bug-25318-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00168.txt
Content-length: 665
https://sourceware.org/bugzilla/show_bug.cgi?id=25318
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simark at simark dot ca
--- Comment #4 from Simon Marchi <simark at simark dot ca> ---
Hi Carlo,
Could you please send your patch to the gdb-patches mailing list? This is
where the patch review/handling is done. More details here:
https://sourceware.org/gdb/wiki/ContributionChecklist
Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26254-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 23:09:00 2020
Return-Path: <gdb-prs-return-26254-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 103131 invoked by alias); 31 Jan 2020 23:09:00 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 103111 invoked by uid 48); 31 Jan 2020 23:09:00 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25488] UNRESOLVED: gdb.server/server-kill-python.exp:
ensure inferior is running
Date: Fri, 31 Jan 2020 23:09: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: vries 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: <bug-25488-4717-dctkyNfJ8F@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25488-4717@http.sourceware.org/bugzilla/>
References: <bug-25488-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00169.txt
Content-length: 889
https://sourceware.org/bugzilla/show_bug.cgi?id=25488
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #2)
> Fixed by:
> ...
> diff --git a/gdb/testsuite/gdb.server/server-kill-python.exp
> b/gdb/testsuite/gdb.server/server-kill-python.exp
> index 28064ca0a46..ae0eb2c11bd 100644
> --- a/gdb/testsuite/gdb.server/server-kill-python.exp
> +++ b/gdb/testsuite/gdb.server/server-kill-python.exp
> @@ -32,6 +32,9 @@ if {[build_executable "failed to prepare" ${testfile} \
> return -1
> }
>
> +global last_loaded_file
> +unset -nocomplain last_loaded_file
> +
> # Start gdbserver.
> set res [gdbserver_spawn "${binfile}"]
> set gdbserver_protocol [lindex $res 0]
> ...
Submitted at https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/760
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26255-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Jan 31 23:11:04 2020
Return-Path: <gdb-prs-return-26255-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 105928 invoked by alias); 31 Jan 2020 23:11:04 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 105902 invoked by uid 48); 31 Jan 2020 23:11:03 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25488] UNRESOLVED: gdb.server/server-kill-python.exp:
ensure inferior is running
Date: Fri, 31 Jan 2020 23:11: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: vries 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: <bug-25488-4717-X0SAw45Y2r@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25488-4717@http.sourceware.org/bugzilla/>
References: <bug-25488-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00170.txt
Content-length: 568
https://sourceware.org/bugzilla/show_bug.cgi?id=25488
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #3)
> BTW, same test-case needs:
> ...
> @@ -66,7 +69,7 @@ with_spawn_id $server_spawn_id {
> pass $gdb_test_name
> }
> timeout {
> - fail $gdb_tst_name
> + fail $gdb_test_name
> }
> }
> }
> ...
Comitted: https://sourceware.org/ml/gdb-patches/2020-01/msg01008.html
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26256-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 01 01:43:16 2020
Return-Path: <gdb-prs-return-26256-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 20577 invoked by alias); 1 Feb 2020 01:43:16 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 20553 invoked by uid 48); 1 Feb 2020 01:43:16 -0000
From: "jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Sat, 01 Feb 2020 01:43: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: 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: <bug-24915-4717-yI8qHowqdI@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00171.txt
Content-length: 1730
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #11 from Jonah Graham <jonah at kichwacoders dot com> ---
Yes, I can reproduce this exactly.
In fact you can see the problem in the break insert for main from your MI
script:
427,194 28-break-insert -t -f main
427,194
28^done,bkpt={number="3",type="breakpoint",disp="del",enabled="y",addr="0x000000000040112a",\
func="main",file="../src/test.c",fullname="/home/michael/eclipse-workspace/test/Debug/../src/test.c"\
,line="17",thread-groups=["i1"],times="0",original-location="main"}
fullname should be the canonical absolute path to the file, as it was in gdb
8.2 (trace from my test on gdb 8.2):
249,391 27-break-insert -t -f main
249,391
27^done,bkpt={number="2",type="breakpoint",disp="del",enabled="y",addr="0x00000000000005fe",\
func="main",file="../src/main.c",fullname="/tmp/x/dasdad/main/src/main.c",line="6",thread-groups=["i\
1"],times="0",original-location="main"}
As you can see here the fullname is the canonical absolute path.
What I don't get is why it resolves sometimes (from your trace again):
427,190 26-break-insert -f /home/michael/eclipse-workspace/test/src/test.c:18
427,190
26^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x0000000000401134"\
,func="main",file="../src/test.c",fullname="/home/michael/eclipse-workspace/test/Debug/../src/test.c\
",line="18",thread-groups=["i1"],times="0",original-location="/home/michael/eclipse-workspace/test/s\
rc/test.c:18"}
In this case the breakpoint has resolved, but the fullname is wrong.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26257-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 01 01:43:43 2020
Return-Path: <gdb-prs-return-26257-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 20951 invoked by alias); 1 Feb 2020 01:43:42 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 20932 invoked by uid 48); 1 Feb 2020 01:43:42 -0000
From: "jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Sat, 01 Feb 2020 01:43: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: 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: <bug-24915-4717-bXVMkFvpLu@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00172.txt
Content-length: 271
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #12 from Jonah Graham <jonah at kichwacoders dot com> ---
I'll try to bisect it to see where this problem was introduced.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26258-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 01 01:57:43 2020
Return-Path: <gdb-prs-return-26258-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 109763 invoked by alias); 1 Feb 2020 01:57:40 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 109554 invoked by uid 48); 1 Feb 2020 01:57:38 -0000
From: "vk2bea+gdb at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Sat, 01 Feb 2020 01: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: critical
X-Bugzilla-Who: vk2bea+gdb 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: <bug-24915-4717-ihTlbbeqWv@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00173.txt
Content-length: 891
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #13 from Michael Katzmann <vk2bea+gdb at gmail dot com> ---
(In reply to Jonah Graham from comment #11)
> Yes, I can reproduce this exactly.
>
Glad it 'not just me' 8-)
Actually both the break points in main work (the first is just the default
first line in the program and the second was the explicit one I added.
What fails is the breakpoint in the second file 'test2.c'
427,190 (gdb)
427,190 &"No source file named
/home/michael/eclipse-workspace/test/src/test2.c.\n"
427,190
27^done,bkpt={number="2",type="breakpoint",disp="keep",enabled="y",addr="<PENDING>",pending=\
"/home/michael/eclipse-workspace/test/src/test2.c:9",times="0",original-location="/home/michael/ecli\
pse-workspace/test/src/test2.c:9"}
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26259-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 01 01:59:24 2020
Return-Path: <gdb-prs-return-26259-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 129049 invoked by alias); 1 Feb 2020 01:59:24 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 129030 invoked by uid 48); 1 Feb 2020 01:59:23 -0000
From: "jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Sat, 01 Feb 2020 01:59: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: 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: <bug-24915-4717-pZPhmgksOp@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00174.txt
Content-length: 680
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #14 from Jonah Graham <jonah at kichwacoders dot com> ---
(In reply to Michael Katzmann from comment #13)
> (In reply to Jonah Graham from comment #11)
> > Yes, I can reproduce this exactly.
> >
>
> Glad it 'not just me' 8-)
>
> Actually both the break points in main work (the first is just the default
> first line in the program and the second was the explicit one I added.
They work - but "by accident" the response from GDB is incorrect for the
function breakpoint (or at least different than it has been for years)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26260-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 01 02:38:41 2020
Return-Path: <gdb-prs-return-26260-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 18704 invoked by alias); 1 Feb 2020 02:38:41 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 18636 invoked by uid 48); 1 Feb 2020 02:38:40 -0000
From: "jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Sat, 01 Feb 2020 02: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
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: <bug-24915-4717-mFxTAwzpWg@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00175.txt
Content-length: 906
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #15 from Jonah Graham <jonah at kichwacoders dot com> ---
I have a workaround* - if you do "set basenames-may-differ on" then GDB does
extra work to canonicalize names. Of course in this case the basenames don't
differ!
The problem is indeed caused by
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a0c1ffedcf1988bc13fc5b6d57d3b74a17b60299
- what I don't understand is why the fix done in Bug 24687 fixes it in some
cases, but not others.
* In CDT set the GDB Command file (in launch configuration) to file containing
"set basenames-may-differ on" - AFAICT if GDB has already looked up a given
file then it is too late and the workaround does not work, so the init file way
allows it to be run before the breakpoints are inserted.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26261-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 01 02:49:50 2020
Return-Path: <gdb-prs-return-26261-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 119639 invoked by alias); 1 Feb 2020 02:49:50 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 119617 invoked by uid 48); 1 Feb 2020 02:49:50 -0000
From: "vk2bea+gdb at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Sat, 01 Feb 2020 02:49: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: vk2bea+gdb 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: <bug-24915-4717-KLlNu2XZYT@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00176.txt
Content-length: 473
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #16 from Michael Katzmann <vk2bea+gdb at gmail dot com> ---
(In reply to Jonah Graham from comment #15)
> I have a workaround* - if you do "set basenames-may-differ on" then GDB does
> extra work to canonicalize names. Of course in this case the basenames don't
> differ!
>
Great ...thanks Jonah, that works for me.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26262-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 01 03:11:11 2020
Return-Path: <gdb-prs-return-26262-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 17537 invoked by alias); 1 Feb 2020 03:11:11 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 17518 invoked by uid 48); 1 Feb 2020 03:11:11 -0000
From: "jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Sat, 01 Feb 2020 03:11: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: 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: <bug-24915-4717-Sxn80Sr8v3@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00177.txt
Content-length: 4197
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #17 from Jonah Graham <jonah at kichwacoders dot com> ---
The current code in GDB requires IDEs or similar to know the path the user
compiled that file with to be able to insert breakpoints. This is a change from
GDB 8 and before.
Here is a trace of a session showing the problem using symlinks - the same
thing happens when using .. in paths (trace for that below):
$ pwd
/scratch/gdb/test
$ cat src/main.c
int main(void) {
extern int main2(void);
return main2();
}
$ cat src/main2.c
int main2(void) {
return 0;
}
$ ln -s src src_link
$ cd src_link
$ gcc -g -o main main.c main2.c
$ cd ../src
$ gdb main # Running stock GDB on Ubuntu
GNU gdb (Ubuntu 8.2-0ubuntu1~18.04) 8.2
Copyright (C) 2018 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 "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from main...done.
(gdb) b /scratch/gdb/test/src/main.c:1 # Breakpoint inserts successfully for
both files
Breakpoint 1 at 0x5fe: file main.c, line 3.
(gdb) b /scratch/gdb/test/src/main2.c:1 # Breakpoint inserts successfully for
both files
Breakpoint 2 at 0x609: file main2.c, line 2.
(gdb) quit
$ /scratch/gdb/build-gdb-9/gdb/gdb main # Running gdb-9-branch HEAD
GNU gdb (GDB) 9.0.90.20200201-git
Copyright (C) 2020 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 "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from main...
(gdb) b /scratch/gdb/test/src/main.c:1 # Breakpoint inserts successfully
for this file
Breakpoint 1 at 0x5fe: file main.c, line 3.
(gdb) b /scratch/gdb/test/src/main2.c:1 # Breakpoint FAILs/pending
No source file named /scratch/gdb/test/src/main2.c.
Make breakpoint pending on future shared library load? (y or [n]) n
(gdb) b /scratch/gdb/test/src_link/main2.c:1 # Insert breakpoint on
compilation path works
Breakpoint 2 at 0x609: file main2.c, line 2.
(gdb) del 2
(gdb) b /scratch/gdb/test/src/main2.c:1 # And then it works on this path
# - this command is same as a few
lines up
Breakpoint 3 at 0x609: file main2.c, line 2.
### And here is with .. in the compilation path:
$ pwd
/scratch/gdb/test/src
$ gcc -o main -g ../src/main.c ../src/main2.c
$ gdb --quiet -ex 'b /scratch/gdb/test/src/main2.c:1' -ex 'quit' main
Reading symbols from main...done.
Breakpoint 1 at 0x609: file ../src/main2.c, line 2.
$ /scratch/gdb/build-gdb-9/gdb/gdb --quiet main
Reading symbols from main...
(gdb) b /scratch/gdb/test/src/main2.c:1 ## Breakpoint fails here
No source file named /scratch/gdb/test/src/main2.c.
Make breakpoint pending on future shared library load? (y or [n]) n
(gdb) b main2.c:1
Breakpoint 1 at 0x609: file ../src/main2.c, line 2.
(gdb) b /scratch/gdb/test/src/main2.c:1 ## same command works here
Note: breakpoint 1 also set at pc 0x609.
Breakpoint 2 at 0x609: file ../src/main2.c, line 2.
(gdb) quit
$
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26263-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 01 03:22:17 2020
Return-Path: <gdb-prs-return-26263-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 29344 invoked by alias); 1 Feb 2020 03:22:17 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 29324 invoked by uid 48); 1 Feb 2020 03:22:17 -0000
From: "jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Sat, 01 Feb 2020 03: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: critical
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: <bug-24915-4717-9KOWbnSUpd@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00178.txt
Content-length: 305
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #18 from Jonah Graham <jonah at kichwacoders dot com> ---
I posted my plea for consideration on
https://sourceware.org/ml/gdb-patches/2020-02/msg00005.html
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26264-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 01 11:46:58 2020
Return-Path: <gdb-prs-return-26264-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 81071 invoked by alias); 1 Feb 2020 11:46:58 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 81047 invoked by uid 48); 1 Feb 2020 11:46:58 -0000
From: "brobecker at gnat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Sat, 01 Feb 2020 11: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
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: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc target_milestone
Message-ID: <bug-24915-4717-M25aDFlbXx@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00179.txt
Content-length: 612
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
Joel Brobecker <brobecker at gnat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |brobecker at gnat dot com
Target Milestone|--- |9.1
--- Comment #19 from Joel Brobecker <brobecker at gnat dot com> ---
Accepted as blocking for the GDB 9.1 release, so setting the Target Milestone
accordingly.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26265-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 01 19:29:07 2020
Return-Path: <gdb-prs-return-26265-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 47596 invoked by alias); 1 Feb 2020 19:29:07 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 47577 invoked by uid 48); 1 Feb 2020 19:29:07 -0000
From: "philippe.waroquiers at skynet dot be" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Sat, 01 Feb 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: philippe.waroquiers at skynet dot be
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
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: <bug-25475-4717-jZSkyN2LvN@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/>
References: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00180.txt
Content-length: 369
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
--- Comment #8 from philippe.waroquiers at skynet dot be ---
Created attachment 12244
--> https://sourceware.org/bugzilla/attachment.cgi?id=12244&action=edit
gdb.log of a succesful run of gdb.server/solib-list.exp on Debian
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26266-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 01 19:39:30 2020
Return-Path: <gdb-prs-return-26266-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 83021 invoked by alias); 1 Feb 2020 19:39:30 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 81725 invoked by uid 48); 1 Feb 2020 19:39:29 -0000
From: "philippe.waroquiers at skynet dot be" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Sat, 01 Feb 2020 19: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: philippe.waroquiers at skynet dot be
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25475-4717-lvSgpgEWHy@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/>
References: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00181.txt
Content-length: 1231
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
--- Comment #9 from philippe.waroquiers at skynet dot be ---
Hi Tom,
I have attached the gdb.log of the successful run.
Following your remark about why there was no question
(and no reload) of the newly detected file in what I attached,
I debugged gdb.
The fact that I do not see a question on my system is due to the
below code in symfile.c: symbol_file_add_with_addrs
/* Give user a chance to burp if we'd be
interactively wiping out any existing symbols. */
if ((have_full_symbols () || have_partial_symbols ())
&& mainline
&& from_tty
&& !query (_("Load new symbol table from \"%s\"? "), name))
error (_("Not confirmed."));
I see on my system when loading solib-list in gdb:
(No debugging symbols found in ..../gdb.server/solib-list/solib-list)
I suppose that the 'No debugging symbols' makes the first test fail.
So, the "Load" question is not asked, and the file is loaded unconditionally.
I suppose that on your system, solib-list contains some debug symbols,
which means the "Load" question is asked, and so the test fails for you due
to this.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26267-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 01 21:07:46 2020
Return-Path: <gdb-prs-return-26267-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 33300 invoked by alias); 1 Feb 2020 21:07:46 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 33279 invoked by uid 48); 1 Feb 2020 21:07:45 -0000
From: "ssbssa at yahoo dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/8684] GDB should cache the source files for the executable
being debugged
Date: Sat, 01 Feb 2020 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: 5.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ssbssa at yahoo dot de
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: <bug-8684-4717-lm33TOU1J9@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-8684-4717@http.sourceware.org/bugzilla/>
References: <bug-8684-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00182.txt
Content-length: 508
https://sourceware.org/bugzilla/show_bug.cgi?id=8684
Hannes Domani <ssbssa at yahoo dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ssbssa at yahoo dot de
--- Comment #3 from Hannes Domani <ssbssa at yahoo dot de> ---
Wasn't this basically implemented with source-cache.c?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26268-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 02 10:55:04 2020
Return-Path: <gdb-prs-return-26268-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 59859 invoked by alias); 2 Feb 2020 10:55:04 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 59839 invoked by uid 48); 2 Feb 2020 10:55:03 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Sun, 02 Feb 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25475-4717-PbxWTDBQM0@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/>
References: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00183.txt
Content-length: 1964
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
--- Comment #10 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to philippe.waroquiers from comment #9)
> Hi Tom,
>
> I have attached the gdb.log of the successful run.
>
> Following your remark about why there was no question
> (and no reload) of the newly detected file in what I attached,
> I debugged gdb.
>
> The fact that I do not see a question on my system is due to the
> below code in symfile.c: symbol_file_add_with_addrs
>
> /* Give user a chance to burp if we'd be
> interactively wiping out any existing symbols. */
>
> if ((have_full_symbols () || have_partial_symbols ())
> && mainline
> && from_tty
> && !query (_("Load new symbol table from \"%s\"? "), name))
> error (_("Not confirmed."));
>
> I see on my system when loading solib-list in gdb:
> (No debugging symbols found in ..../gdb.server/solib-list/solib-list)
>
> I suppose that the 'No debugging symbols' makes the first test fail.
> So, the "Load" question is not asked, and the file is loaded unconditionally.
>
> I suppose that on your system, solib-list contains some debug symbols,
> which means the "Load" question is asked, and so the test fails for you due
> to this.
Thanks for the analysis. I can confirm that the solib-list executable does
contain some debug symbols for me, and using this patch:
...
diff --git a/gdb/testsuite/gdb.server/solib-list.exp
b/gdb/testsuite/gdb.server/solib-list.exp
index 5471734e03..d5d73dd630 100644
--- a/gdb/testsuite/gdb.server/solib-list.exp
+++ b/gdb/testsuite/gdb.server/solib-list.exp
@@ -38,6 +38,8 @@ if { [get_compiler_info]
return -1
}
+exec strip --strip-debug ${binfile}
+
set interp_system [section_get ${binfile} .interp]
verbose -log "system interpreter is: $interp_system"
...
I get the same results as you.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26269-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 02 11:06:40 2020
Return-Path: <gdb-prs-return-26269-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 64741 invoked by alias); 2 Feb 2020 11:06:40 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 64721 invoked by uid 48); 2 Feb 2020 11:06:39 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Sun, 02 Feb 2020 11: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: vries 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: <bug-25475-4717-j7F2J8h6Wr@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/>
References: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00184.txt
Content-length: 2954
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
--- Comment #11 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #10)
> (In reply to philippe.waroquiers from comment #9)
> > Hi Tom,
> >
> > I have attached the gdb.log of the successful run.
> >
> > Following your remark about why there was no question
> > (and no reload) of the newly detected file in what I attached,
> > I debugged gdb.
> >
> > The fact that I do not see a question on my system is due to the
> > below code in symfile.c: symbol_file_add_with_addrs
> >
> > /* Give user a chance to burp if we'd be
> > interactively wiping out any existing symbols. */
> >
> > if ((have_full_symbols () || have_partial_symbols ())
> > && mainline
> > && from_tty
> > && !query (_("Load new symbol table from \"%s\"? "), name))
> > error (_("Not confirmed."));
> >
> > I see on my system when loading solib-list in gdb:
> > (No debugging symbols found in ..../gdb.server/solib-list/solib-list)
> >
> > I suppose that the 'No debugging symbols' makes the first test fail.
> > So, the "Load" question is not asked, and the file is loaded unconditionally.
> >
> > I suppose that on your system, solib-list contains some debug symbols,
> > which means the "Load" question is asked, and so the test fails for you due
> > to this.
>
> Thanks for the analysis. I can confirm that the solib-list executable does
> contain some debug symbols for me, and using this patch:
> ...
> diff --git a/gdb/testsuite/gdb.server/solib-list.exp
> b/gdb/testsuite/gdb.server/solib-list.exp
> index 5471734e03..d5d73dd630 100644
> --- a/gdb/testsuite/gdb.server/solib-list.exp
> +++ b/gdb/testsuite/gdb.server/solib-list.exp
> @@ -38,6 +38,8 @@ if { [get_compiler_info]
> return -1
> }
>
> +exec strip --strip-debug ${binfile}
> +
> set interp_system [section_get ${binfile} .interp]
> verbose -log "system interpreter is: $interp_system"
>
> ...
> I get the same results as you.
And conversely, you should be able to see the FAIL I'm seeing by adding "debug"
in the gdb_compile flags:
...
diff --git a/gdb/testsuite/gdb.server/solib-list.exp
b/gdb/testsuite/gdb.server/solib-list.exp
index 5471734e03..2f1f3a2bbb 100644
--- a/gdb/testsuite/gdb.server/solib-list.exp
+++ b/gdb/testsuite/gdb.server/solib-list.exp
@@ -33,7 +33,7 @@ set binlibfile [standard_output_file ${testfile}.so]
if { [get_compiler_info]
|| [gdb_compile_shlib "${srcdir}/${subdir}/${srclibfile}" "${binlibfile}"
{debug}] != ""
- || [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable
"shlib=${binlibfile}"] != "" }
{
+ || [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable
"shlib=${binlibfile} debug"] != "" } {
untested "failed to compile"
return -1
}
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26270-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 02 12:20:19 2020
Return-Path: <gdb-prs-return-26270-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 24786 invoked by alias); 2 Feb 2020 12:20:19 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 24766 invoked by uid 48); 2 Feb 2020 12:20:18 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Sun, 02 Feb 2020 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: vries 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: <bug-25475-4717-RyTXlE8e2S@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/>
References: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00185.txt
Content-length: 2064
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
--- Comment #12 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #4)
> (In reply to philippe.waroquiers from comment #3)
> > Strange ...
> > I see no failure on debian 10.2:
> > ...
> > (gdb) PASS: gdb.server/solib-list.exp: non-stop 1: file binfile
> > target remote localhost:2347
> > Remote debugging using localhost:2347
> > warning: Mismatch between current exec-file
> > /bd/home/philippe/gdb/git/build_binutils-gdb/gdb/testsuite/outputs/gdb.
> > server/solib-list/solib-list
> > and automatically determined exec-file /lib/x86_64-linux-gnu/ld-2.28.so
> > exec-file-mismatch handling is currently "ask"
>
> So, if there is a mismatch, and the handling is ask ... where is the asking
> being done?
>
> If that's missing in your log, does that not indicate a bug in
> exec-file-mismatch?
>
Having figured out the cause of the differences in the logs, I still think this
question is relevant. Posing the same question a bit more elaborately ...
So, looking at the exec-file-mismatch docs:
...
@anchor{set exec-file-mismatch}
If the debugger can determine the name of the executable file running
in the process it is attaching to, and this file name does not match
the name of the current exec-file loaded by @value{GDBN}, the option
@code{exec-file-mismatch} specifies how to handle the mismatch.
...
as well as the 'ask' bit:
...
If @samp{ask}, the default, display a warning
and ask the user whether to load the process executable file;
...
and then looking at the events in the gdb.log:
- gdb can determine the name of the executable file running in the process
it is attaching to
- gdb can determine that that filename does not match the name of the current
exec-file loaded by gdb
- gdb reports this mismatch
- gdb reports the mismatch handling strategy: ask
- gdb doesn't ask
I'd say this is a bug in exec-file-mismatch.
Do you agree with this analysis?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26271-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 02 17:49:17 2020
Return-Path: <gdb-prs-return-26271-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 12909 invoked by alias); 2 Feb 2020 17:49:14 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 12863 invoked by uid 48); 2 Feb 2020 17:49:13 -0000
From: "ssbssa at yahoo dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17659] [win32] GDB failed to get dll names when handling
LOAD_DLL_DEBUG_EVENT event
Date: Sun, 02 Feb 2020 17: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: ssbssa 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: <bug-17659-4717-WIT6J4cYhO@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17659-4717@http.sourceware.org/bugzilla/>
References: <bug-17659-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00186.txt
Content-length: 729
https://sourceware.org/bugzilla/show_bug.cgi?id=17659
Hannes Domani <ssbssa at yahoo dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ssbssa at yahoo dot de
--- Comment #3 from Hannes Domani <ssbssa at yahoo dot de> ---
I think this problem was fixed with
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=94481b8c8f63a2a956d18ac1e6d6134c5334cb24
and
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=ea39ad355eb72b296b30a66bbc81256a071e8f1e.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26272-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 03 09:35:52 2020
Return-Path: <gdb-prs-return-26272-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 40006 invoked by alias); 3 Feb 2020 09:35:52 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 39986 invoked by uid 48); 3 Feb 2020 09:35:52 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Mon, 03 Feb 2020 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: vries 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: <bug-25475-4717-VCGpTCwAOk@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/>
References: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00187.txt
Content-length: 829
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
--- Comment #13 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> (gdb) PASS: gdb.server/solib-list.exp: non-stop 0: file binfile
> target remote localhost:2346
> Remote debugging using localhost:2346
> warning: Mismatch between current exec-file
> /data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/solib-list/
> solib-list
> and automatically determined exec-file /lib64/ld-2.26.so
> exec-file-mismatch handling is currently "ask"
> Load new symbol table from "/lib64/ld-2.26.so"? (y or n) n
I've submitted a patch (
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/761 ) to answer "y"
here, to fix the failure on openSUSE.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26274-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 03 13:04:37 2020
Return-Path: <gdb-prs-return-26274-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 127738 invoked by alias); 3 Feb 2020 13:04:36 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 127720 invoked by uid 48); 3 Feb 2020 13:04:36 -0000
From: "yeyunfeng at huawei dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25496] New: Endless print " warning: unable to open /proc
file '/proc/22703/status' "
Date: Mon, 03 Feb 2020 13: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: yeyunfeng at huawei dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25496-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00189.txt
Content-length: 5736
https://sourceware.org/bugzilla/show_bug.cgi?id=25496
Bug ID: 25496
Summary: Endless print " warning: unable to open /proc file
'/proc/22703/status' "
Product: gdb
Version: 8.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yeyunfeng at huawei dot com
Target Milestone: ---
We meet a problem that endless print warning:
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
...
We can reproduce and reappear through the following methods:
1. write the test code multithread.c:
```
#include <pthread.h>
#include <unistd.h>
void my_thread(void)
{
while (1) {
sleep(1);
}
}
int main(void)
{
pthread_t my_tid;
pthread_create(&my_tid, NULL, (void *)my_thread, NULL);
pthread_join(my_tid, NULL);
return 0;
}
```
2. Build the test code:
gcc -Wall -lpthread -o multithread multithread.c
3. Use gdb to trace gdb, and proceed as follows:
a) Copy gdb to the current dentry, and run:
# ./gdb ./gdb
b) Set prompt、args、breakpoint:
set prompt master(gdb)
set args /root/multithread
b stop_all_threads
c) Run the master gdb and slave gdb
r
r
d) At this moment, multithread is running. the log is like this:
[root@localhost ~]# ./gdb ./gdb
GNU gdb (GDB) 8.3.50.20190227-git
Copyright (C) 2019 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 "aarch64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./gdb...
(gdb)
(gdb)
(gdb)
(gdb) set prompt master(gdb)
master(gdb)
master(gdb)set args /root/multithread
master(gdb)
master(gdb)b stop_all_threads
Breakpoint 1 at 0x58e210: file infrun.c, line 4277.
master(gdb)r
Starting program: /root/gdb /root/multithread
[Detaching after vfork from child process 22688]
GNU gdb (GDB) 8.3.50.20190227-git
Copyright (C) 2019 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 "aarch64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /root/multithread...
(No debugging symbols found in /root/multithread)
(gdb)
(gdb) r
Starting program: /root/multithread
[Detaching after vfork from child process 22703]
[Detaching after fork from child process 22710]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0xffffbf5031e0 (LWP 22712)]
e) Now use "ctrl+c" to stop, it will stop at the breakpoint stop_all_threads(),
the log is like this:
^C
Breakpoint 1, stop_all_threads () at infrun.c:4277
4277 {
master(gdb)
f) Open an other window, kill the multithread process:
[root@localhost ~]#
[root@localhost ~]# killall -9 multithread
g) Go back to the previous window, and continue the master(gdb):
c
master(gdb)
master(gdb)c
Continuing.
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
warning: unable to open /proc file '/proc/22703/status'
......
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26273-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 03 13:04:09 2020
Return-Path: <gdb-prs-return-26273-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 127152 invoked by alias); 3 Feb 2020 13:04:08 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 127130 invoked by uid 48); 3 Feb 2020 13:04:08 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug varobj/25470] Assertion hit in maybe_negate_by_bytes
Date: Mon, 03 Feb 2020 13:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: varobj
X-Bugzilla-Version: 8.3.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: <bug-25470-4717-jb4tXeXlCq@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25470-4717@http.sourceware.org/bugzilla/>
References: <bug-25470-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00188.txt
Content-length: 384
https://sourceware.org/bugzilla/show_bug.cgi?id=25470
--- Comment #8 from Tom Tromey <tromey at sourceware dot org> ---
I looked a bit more and gdb doesn't currently handle
DW_AT_bit_size on a base type. So, that would need to
be implemented to make this work. Fixing this may be
somewhat involved.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26275-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 03 14:37:19 2020
Return-Path: <gdb-prs-return-26275-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 9047 invoked by alias); 3 Feb 2020 14:37:19 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 9026 invoked by uid 48); 3 Feb 2020 14:37:19 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25479] AddressSanitizer: heap-buffer-overflow in
lookup_minimal_symbol_by_pc_name
Date: Mon, 03 Feb 2020 14: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: 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: <bug-25479-4717-zoKw4NcQeb@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25479-4717@http.sourceware.org/bugzilla/>
References: <bug-25479-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00190.txt
Content-length: 712
https://sourceware.org/bugzilla/show_bug.cgi?id=25479
--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
I can confirm this.
I've looked at it a little. I tend to think it is a pre-existing
bug. I suspect Address Sanitizer doesn't understand how to examine
objects allocated on an obstack (neither does valgrind...), which is
why this was never detected.
reread2.c (one of the programs used in reread.exp) says:
/* Ensure the new file will have more sections. It may exploit code not
updating its SECTION_COUNT on reread_symbols. */
... but even before my patch, reread_symbols didn't seem to do this.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26276-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 03 15:28:25 2020
Return-Path: <gdb-prs-return-26276-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 49927 invoked by alias); 3 Feb 2020 15:28:24 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 49675 invoked by uid 48); 3 Feb 2020 15:28:24 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25479] AddressSanitizer: heap-buffer-overflow in
lookup_minimal_symbol_by_pc_name
Date: Mon, 03 Feb 2020 15: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: 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: <bug-25479-4717-1ouJ5gOKzD@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25479-4717@http.sourceware.org/bugzilla/>
References: <bug-25479-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00191.txt
Content-length: 1731
https://sourceware.org/bugzilla/show_bug.cgi?id=25479
--- Comment #6 from Tom Tromey <tromey at sourceware dot org> ---
I am not sure how to fix this.
The main issue is a divergence between syms_from_objfile_1 and
reread_symbols. As Jan pointed out years ago, the fact that
there are separate functions for this is just asking for trouble...
which is what we got.
Essentially, syms_from_objfile_1 calls:
(*objfile->sf->sym_offsets) (objfile, *addrs);
... but reread_symbols, before my patch, did:
- /* We use the same section offsets as from last time. I'm not
- sure whether that is always correct for shared libraries. */
- objfile->section_offsets = (struct section_offsets *)
- obstack_alloc (&objfile->objfile_obstack,
- SIZEOF_N_SECTION_OFFSETS (num_offsets));
- memcpy (objfile->section_offsets, offsets,
- SIZEOF_N_SECTION_OFFSETS (num_offsets));
- objfile->num_sections = num_offsets;
However, this is wrong in the reread.exp case, as that specifically
tests re-reading a file where the number of sections changes.
I couldn't find a patch that regressed this area, so maybe the
test was written but the code was never really correct?
It would be simple to call sym_offsets from reread_symbols; or
even to unify the code here and avoid future problems. However,
it was not clear to me what we should do if the objfile was
created via add-symbol-file.
Now I see that add-symbol-file has a "-o" option to set a default
offset. This isn't preserved, but maybe we could preserve it.
I wonder if there are other cases I am missing.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26277-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 03 15:48:52 2020
Return-Path: <gdb-prs-return-26277-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 70344 invoked by alias); 3 Feb 2020 15:48:50 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 70284 invoked by uid 48); 3 Feb 2020 15:48:46 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17659] [win32] GDB failed to get dll names when handling
LOAD_DLL_DEBUG_EVENT event
Date: Mon, 03 Feb 2020 15: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: 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 resolution
Message-ID: <bug-17659-4717-qNxQ2JkNQt@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17659-4717@http.sourceware.org/bugzilla/>
References: <bug-17659-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00192.txt
Content-length: 528
https://sourceware.org/bugzilla/show_bug.cgi?id=17659
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
Thanks. I'm closing this.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26278-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 03 20:44:16 2020
Return-Path: <gdb-prs-return-26278-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 36279 invoked by alias); 3 Feb 2020 20:44:15 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 36233 invoked by uid 48); 3 Feb 2020 20:44:14 -0000
From: "philippe.waroquiers at skynet dot be" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25475] FAIL: gdb.server/solib-list.exp: non-stop 0/1:
target remote (got interactive prompt)
Date: Mon, 03 Feb 2020 20: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: philippe.waroquiers at skynet dot be
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25475-4717-fRXUUNCnVV@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25475-4717@http.sourceware.org/bugzilla/>
References: <bug-25475-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00193.txt
Content-length: 698
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
--- Comment #14 from philippe.waroquiers at skynet dot be ---
Up to you if you prefer to fix this by detecting the question
and answering, or by your first proposal to set exec-file-mismatch
to off (the second approach is simpler).
Note that I quickly discussed this problem with Pedro at FOSDEM.
He suggested we might remove the condition regarding debug info,
so that the question is asked whatever the current executable status
(with or without debug info).
I will further investigate that to see if there was a very specific
reason to have this condition.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26279-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 16:45:46 2020
Return-Path: <gdb-prs-return-26279-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 59139 invoked by alias); 4 Feb 2020 16:45:37 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 50791 invoked by uid 48); 4 Feb 2020 16:45:06 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25503] New: FAIL:
gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step (pattern 3)
Date: Tue, 04 Feb 2020 16:45: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: vries 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: <bug-25503-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00194.txt
Content-length: 1659
https://sourceware.org/bugzilla/show_bug.cgi?id=25503
Bug ID: 25503
Summary: FAIL:
gdb.threads/signal-while-stepping-over-bp-other-thread
.exp: step (pattern 3)
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With test.sh setup to run test-case
gdb.threads/signal-while-stepping-over-bp-other-thread.exp, and when run in
conjunction with "stress -c 5", I get:
...
$ for n in $(seq 1 50); do ./test.sh 2>&1 | tee TESTLOG.$n; cp gdb.log
gdb.$n.log; cp gdb.sum gdb.$n.sum; done | grep "expected passes"
# of expected passes 22
# of expected passes 22
# of expected passes 22
# of expected passes 22
# of expected passes 22
# of expected passes 22
# of expected passes 22
# of expected passes 22
# of expected passes 22
# of expected passes 22
# of expected passes 22
# of expected passes 21
# of expected passes 22
# of expected passes 21
# of expected passes 22
# of expected passes 22
# of expected passes 22
# of expected passes 22
^C^C
...
And in gdb.12.sum (as well as gdb.14.sum) we find:
...
FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step (pattern
3)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26280-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 16:46:31 2020
Return-Path: <gdb-prs-return-26280-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 59879 invoked by alias); 4 Feb 2020 16:46:16 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 59752 invoked by uid 48); 4 Feb 2020 16:46:14 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25503] FAIL:
gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step (pattern 3)
Date: Tue, 04 Feb 2020 16:46: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: vries 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: <bug-25503-4717-Vdgzk71yr1@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25503-4717@http.sourceware.org/bugzilla/>
References: <bug-25503-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00195.txt
Content-length: 5998
https://sourceware.org/bugzilla/show_bug.cgi?id=25503
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
In more detail:
...
(gdb) PASS: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: set
debug infrun 1
gdb_expect_list pattern: /need to step-over/
step
infrun: clear_proceed_status_thread (Thread 0x7ffff7fa6740 (LWP 22256))
infrun: clear_proceed_status_thread (Thread 0x7ffff74c6700 (LWP 22260))
infrun: clear_proceed_status_thread (Thread 0x7ffff6cc5700 (LWP 22261))
infrun: proceed (addr=0xffffffffffffffff, signal=GDB_SIGNAL_DEFAULT)
infrun: need to step-over [Thread 0x7ffff74c6700 (LWP 22260)] first
infrun: step-over queue now empty
infrun: resuming [Thread 0x7ffff74c6700 (LWP 22260)] for step-over
infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=1, current thread
[Thread 0x7ffff74c6700 (LWP 22260)] at 0x400891
infrun: infrun_async(1)
infrun: prepare_to_wait
infrun: proceed: resuming Thread 0x7ffff7fa6740 (LWP 22256)
infrun: resume (step=0, signal=GDB_SIGNAL_0), trap_expected=0, current thread
[Thread 0x7ffff7fa6740 (LWP 22256)] at 0x4009c3
infrun: prepare_to_wait
infrun: proceed: [Thread 0x7ffff74c6700 (LWP 22260)] resumed
infrun: proceed: resuming Thread 0x7ffff6cc5700 (LWP 22261)
infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=0, current thread
[Thread 0x7ffff6cc5700 (LWP 22261)] at 0x400828
infrun: prepare_to_wait
infrun: target_wait (-1.0.0, status) =
infrun: 22256.22261.0 [Thread 0x7ffff6cc5700 (LWP 22261)],
infrun: status->kind = stopped, signal = GDB_SIGNAL_TRAP
infrun: handle_inferior_event status->kind = stopped, signal = GDB_SIGNAL_TRAP
infrun: stop_pc = 0x40082c
infrun: stepping inside range [0x400828-0x400837]
infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=0, current thread
[Thread 0x7ffff6cc5700 (LWP 22261)] at 0x40082c
infrun: prepare_to_wait
infrun: target_wait (-1.0.0, status) =
infrun: 22256.22261.0 [Thread 0x7ffff6cc5700 (LWP 22261)],
infrun: status->kind = stopped, signal = GDB_SIGNAL_TRAP
infrun: handle_inferior_event status->kind = stopped, signal = GDB_SIGNAL_TRAP
infrun: stop_pc = 0x40082e
infrun: stepping inside range [0x400828-0x400837]
infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=0, current thread
[Thread 0x7ffff6cc5700 (LWP 22261)] at 0x40082e
infrun: prepare_to_wait
infrun: target_wait (-1.0.0, status) =
infrun: 22256.22261.0 [Thread 0x7ffff6cc5700 (LWP 22261)],
infrun: status->kind = stopped, signal = GDB_SIGNAL_TRAP
infrun: handle_inferior_event status->kind = stopped, signal = GDB_SIGNAL_TRAP
infrun: stop_pc = 0x400831
infrun: stepping inside range [0x400828-0x400837]
infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=0, current thread
[Thread 0x7ffff6cc5700 (LWP 22261)] at 0x400831
infrun: prepare_to_wait
infrun: target_wait (-1.0.0, status) =
infrun: 22256.22261.0 [Thread 0x7ffff6cc5700 (LWP 22261)],
infrun: status->kind = stopped, signal = GDB_SIGNAL_TRAP
infrun: handle_inferior_event status->kind = stopped, signal = GDB_SIGNAL_TRAP
infrun: stop_pc = 0x400835
infrun: stepping inside range [0x400828-0x400837]
infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=0, current thread
[Thread 0x7ffff6cc5700 (LWP 22261)] at 0x400835
infrun: prepare_to_wait
infrun: target_wait (-1.0.0, status) =
infrun: 22256.22261.0 [Thread 0x7ffff6cc5700 (LWP 22261)],
infrun: status->kind = stopped, signal = GDB_SIGNAL_TRAP
infrun: handle_inferior_event status->kind = stopped, signal = GDB_SIGNAL_TRAP
infrun: stop_pc = 0x400837
infrun: stepped to a different line
infrun: stop_waiting
infrun: stop_all_threads
infrun: stop_all_threads, pass=0, iterations=0
infrun: Thread 0x7ffff7fa6740 (LWP 22256) executing, need stop
infrun: Thread 0x7ffff74c6700 (LWP 22260) executing, need stop
infrun: Thread 0x7ffff6cc5700 (LWP 22261) not executing
infrun: target_wait (-1.0.0, status) =
infrun: 22256.22256.0 [Thread 0x7ffff7fa6740 (LWP 22256)],
infrun: status->kind = stopped, signal = GDB_SIGNAL_0
infrun: stop_all_threads status->kind = stopped, signal = GDB_SIGNAL_0 Thread
0x7ffff7fa6740 (LWP 22256)
infrun: Thread 0x7ffff7fa6740 (LWP 22256) not executing
infrun: Thread 0x7ffff74c6700 (LWP 22260) executing, already stopping
infrun: Thread 0x7ffff6cc5700 (LWP 22261) not executing
infrun: target_wait (gdb_expect_list pattern: /resume \(step=1/
gdb_expect_list pattern: /signal arrived while stepping over breakpoint/
-1.0.0, status) =
infrun: -1.0.0 [process -1],
infrun: status->kind = ignore
infrun: target_wait (-1.0.0, status) =
infrun: 22256.22260.0 [Thread 0x7ffff74c6700 (LWP 22260)],
infrun: status->kind = stopped, signal = GDB_SIGNAL_USR1
infrun: stop_all_threads status->kind = stopped, signal = GDB_SIGNAL_USR1
Thread 0x7ffff74c6700 (LWP 22260)
infrun: target_wait status->kind = stopped, signal = GDB_SIGNAL_USR1, saving
status for 22256.22260.0
infrun: saving status status->kind = stopped, signal = GDB_SIGNAL_USR1 for
22256.22260.0
infrun: saved stop_pc=0x400891 for Thread 0x7ffff74c6700 (LWP 22260)
(currently_stepping=0)
infrun: Thread 0x7ffff7fa6740 (LWP 22256) not executing
infrun: Thread 0x7ffff74c6700 (LWP 22260) not executing
infrun: Thread 0x7ffff6cc5700 (LWP 22261) not executing
infrun: stop_all_threads, pass=1, iterations=1
infrun: Thread 0x7ffff7fa6740 (LWP 22256) not executing
infrun: Thread 0x7ffff74c6700 (LWP 22260) not executing
infrun: Thread 0x7ffff6cc5700 (LWP 22261) not executing
infrun: stop_all_threads done
51 callme ();
infrun: infrun_async(0)
(gdb) FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step
(pattern 3)
gdb_expect_list pattern: /stepped to a different line/
gdb_expect_list pattern: /callme/
gdb_expect_list pattern: //
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26282-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 16:52:57 2020
Return-Path: <gdb-prs-return-26282-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 74696 invoked by alias); 4 Feb 2020 16:52:57 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 74669 invoked by uid 48); 4 Feb 2020 16:52:56 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25503] FAIL:
gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step (pattern 3)
Date: Tue, 04 Feb 2020 16:52: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: vries 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: <bug-25503-4717-qyj0lyyNMH@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25503-4717@http.sourceware.org/bugzilla/>
References: <bug-25503-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00197.txt
Content-length: 317
https://sourceware.org/bugzilla/show_bug.cgi?id=25503
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 12253
--> https://sourceware.org/bugzilla/attachment.cgi?id=12253&action=edit
gdb.12.log
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26281-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 16:52:40 2020
Return-Path: <gdb-prs-return-26281-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 74344 invoked by alias); 4 Feb 2020 16:52:40 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 74321 invoked by uid 48); 4 Feb 2020 16:52:39 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25503] FAIL:
gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step (pattern 3)
Date: Tue, 04 Feb 2020 16:52: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: vries 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: <bug-25503-4717-28NtAafME8@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25503-4717@http.sourceware.org/bugzilla/>
References: <bug-25503-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00196.txt
Content-length: 316
https://sourceware.org/bugzilla/show_bug.cgi?id=25503
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 12252
--> https://sourceware.org/bugzilla/attachment.cgi?id=12252&action=edit
gdb.1.log
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26283-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 19:13:14 2020
Return-Path: <gdb-prs-return-26283-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 126679 invoked by alias); 4 Feb 2020 19:13:14 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 126660 invoked by uid 48); 4 Feb 2020 19:13:13 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25504] New: FAIL:
gdb.threads/process-dies-while-detaching.exp: single-process: continue:
watchpoint: continue (Couldn't get registers: No such process)
Date: Tue, 04 Feb 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25504-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00198.txt
Content-length: 1608
https://sourceware.org/bugzilla/show_bug.cgi?id=25504
Bug ID: 25504
Summary: FAIL: gdb.threads/process-dies-while-detaching.exp:
single-process: continue: watchpoint: continue
(Couldn't get registers: No such process)
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With test.sh setup to run test-case
gdb.threads/process-dies-while-detaching.exp, and running in conjunction with
stress -c 5, we get:
...
$ for n in $(seq 1 50); do ./test.sh 2>&1 | tee TESTLOG.$n; cp gdb.log
gdb.$n.log; cp gdb.sum gdb.$n.sum; done | grep "expected passes"
# of expected passes 66
# of expected passes 65
# of expected passes 66
# of expected passes 66
# of expected passes 66
# of expected passes 66
...
In gdb.2.sum, we find this fail:
...
FAIL: gdb.threads/process-dies-while-detaching.exp: single-process: continue:
watchpoint: continue
...
In more detail (in gdb.2.log):
...
(gdb) PASS: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: watchpoint: continue to breakpoint: _exit
continue^M
Continuing.^M
Couldn't get registers: No such process.^M
(gdb) FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: watchpoint: continue
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26284-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 19:14:34 2020
Return-Path: <gdb-prs-return-26284-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 127706 invoked by alias); 4 Feb 2020 19:14:33 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 127688 invoked by uid 48); 4 Feb 2020 19:14:33 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25504] FAIL: gdb.threads/process-dies-while-detaching.exp:
single-process: continue: watchpoint: continue (Couldn't get registers: No
such process)
Date: Tue, 04 Feb 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25504-4717-60CeQxQOQv@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25504-4717@http.sourceware.org/bugzilla/>
References: <bug-25504-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00199.txt
Content-length: 316
https://sourceware.org/bugzilla/show_bug.cgi?id=25504
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 12254
--> https://sourceware.org/bugzilla/attachment.cgi?id=12254&action=edit
gdb.1.log
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26285-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 19:14:58 2020
Return-Path: <gdb-prs-return-26285-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 128148 invoked by alias); 4 Feb 2020 19:14:58 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 128129 invoked by uid 48); 4 Feb 2020 19:14:58 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25504] FAIL: gdb.threads/process-dies-while-detaching.exp:
single-process: continue: watchpoint: continue (Couldn't get registers: No
such process)
Date: Tue, 04 Feb 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25504-4717-C5cWvaPr2A@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25504-4717@http.sourceware.org/bugzilla/>
References: <bug-25504-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00200.txt
Content-length: 316
https://sourceware.org/bugzilla/show_bug.cgi?id=25504
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 12255
--> https://sourceware.org/bugzilla/attachment.cgi?id=12255&action=edit
gdb.2.log
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26286-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 19:18:41 2020
Return-Path: <gdb-prs-return-26286-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 3238 invoked by alias); 4 Feb 2020 19:18:41 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 3215 invoked by uid 48); 4 Feb 2020 19:18:40 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25504] FAIL: gdb.threads/process-dies-while-detaching.exp:
single-process: continue: watchpoint: continue (Couldn't get registers: No
such process)
Date: Tue, 04 Feb 2020 19: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: vries 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: <bug-25504-4717-qlR6x3hNRA@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25504-4717@http.sourceware.org/bugzilla/>
References: <bug-25504-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00201.txt
Content-length: 407
https://sourceware.org/bugzilla/show_bug.cgi?id=25504
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Note: there is an identical FAIL line in PR21321 - "AddressSanitizer:
heap-use-after-free in gdbserver/linux-low.c", but there the fail is with
-fsanitize=address and --target_board='native-gdbserver'.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26287-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 20:02:03 2020
Return-Path: <gdb-prs-return-26287-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 52475 invoked by alias); 4 Feb 2020 20:02:02 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 52448 invoked by uid 48); 4 Feb 2020 20:02:02 -0000
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/23643] Update gnulib copy (and fix possible problems)
Date: Tue, 04 Feb 2020 20: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: 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: <bug-23643-4717-elGYJKeOQJ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23643-4717@http.sourceware.org/bugzilla/>
References: <bug-23643-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00202.txt
Content-length: 713
https://sourceware.org/bugzilla/show_bug.cgi?id=23643
Sergio Durigan Junior <sergiodj at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
This bug has been fixed by
commit c0c3707ff46ccfb78ea175dd42d628d8c90dca8b
Author: Christian Biesinger <cbiesinger@google.com>
Date: Sat Nov 16 23:37:06 2019 -0600
Therefore I'm closing it.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26288-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 20:16:14 2020
Return-Path: <gdb-prs-return-26288-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 20303 invoked by alias); 4 Feb 2020 20:16:12 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 20124 invoked by uid 48); 4 Feb 2020 20:15:54 -0000
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/21599] gdb crashes when in TUI mode and terminal window is
made small
Date: Tue, 04 Feb 2020 20:16: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: 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: <bug-21599-4717-N5oCFUvYzN@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-21599-4717@http.sourceware.org/bugzilla/>
References: <bug-21599-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00203.txt
Content-length: 667
https://sourceware.org/bugzilla/show_bug.cgi?id=21599
Sergio Durigan Junior <sergiodj at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
I can't reproduce this anymore. Tom has basically overhauled the TUI code, and
I think this bug got fixed in the process. I'm closing as FIXED.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26289-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 20:18:31 2020
Return-Path: <gdb-prs-return-26289-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 21662 invoked by alias); 4 Feb 2020 20:18:31 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 21628 invoked by uid 48); 4 Feb 2020 20:18:30 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25505] New: FAIL: gdb.threads/ia64-sigill.exp: continue for
the pending signal (GDB internal error)
Date: Tue, 04 Feb 2020 20: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: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25505-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00204.txt
Content-length: 1784
https://sourceware.org/bugzilla/show_bug.cgi?id=25505
Bug ID: 25505
Summary: FAIL: gdb.threads/ia64-sigill.exp: continue for the
pending signal (GDB internal error)
Product: gdb
Version: 8.3.1
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With test.sh setup to run test-case gdb.threads/ia64-sigill.exp, and running in
conjunction with stress -c 20 -i 5 -d 5, we get for gdb-8.3-branch:
...
$ for n in $(seq 1 50); do ./test.sh 2>&1 | tee TESTLOG.$n; cp gdb.log
gdb.$n.log; cp gdb.sum gdb.$n.sum; done | grep "expected passes"
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 7
# of expected passes 6
...
And in gdb.22.sum, we find:
...
FAIL: gdb.threads/ia64-sigill.exp: continue for the pending signal (GDB
internal error)
ERROR: Could not resync from internal error (timeout)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26291-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 20:19:52 2020
Return-Path: <gdb-prs-return-26291-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 22726 invoked by alias); 4 Feb 2020 20:19:51 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 22708 invoked by uid 48); 4 Feb 2020 20:19:51 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25505] FAIL: gdb.threads/ia64-sigill.exp: continue for the
pending signal (GDB internal error)
Date: Tue, 04 Feb 2020 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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25505-4717-PTZmd7pB4h@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25505-4717@http.sourceware.org/bugzilla/>
References: <bug-25505-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00206.txt
Content-length: 316
https://sourceware.org/bugzilla/show_bug.cgi?id=25505
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 12256
--> https://sourceware.org/bugzilla/attachment.cgi?id=12256&action=edit
gdb.1.log
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26290-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 20:19:02 2020
Return-Path: <gdb-prs-return-26290-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 22095 invoked by alias); 4 Feb 2020 20:19:01 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 22049 invoked by uid 48); 4 Feb 2020 20:19:00 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25505] FAIL: gdb.threads/ia64-sigill.exp: continue for the
pending signal (GDB internal error)
Date: Tue, 04 Feb 2020 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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25505-4717-DuilWSztEd@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25505-4717@http.sourceware.org/bugzilla/>
References: <bug-25505-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00205.txt
Content-length: 3824
https://sourceware.org/bugzilla/show_bug.cgi?id=25505
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
More detail in gdb.22.log:
...
(gdb) PASS: gdb.threads/ia64-sigill.exp: delete $sigill_bpnum
continue
Continuing.
infrun: clear_proceed_status_thread (Thread 0x7ffff7fa7c00 (LWP 8165))
infrun: clear_proceed_status_thread (Thread 0x7ffff72be700 (LWP 8169))
infrun: clear_proceed_status_thread: thread Thread 0x7ffff72be700 (LWP 8169)
has pending wait status status->kind = stopped, signal = GDB_SIGNAL_TRAP
(currently_stepping=0).
infrun: clear_proceed_status_thread (Thread 0x7ffff6abd700 (LWP 8170))
infrun: proceed (addr=0xffffffffffffffff, signal=GDB_SIGNAL_DEFAULT)
infrun: proceed: resuming Thread 0x7ffff7fa7c00 (LWP 8165)
infrun: resume (step=0, signal=GDB_SIGNAL_0), trap_expected=0, current thread
[Thread 0x7ffff7fa7c00 (LWP 8165)] at 0x7ffff79b992d
infrun: infrun_async(1)
infrun: prepare_to_wait
infrun: proceed: resuming Thread 0x7ffff72be700 (LWP 8169)
infrun: resume: thread Thread 0x7ffff72be700 (LWP 8169) has pending wait status
status->kind = stopped, signal = GDB_SIGNAL_TRAP (currently_stepping=0).
infrun: prepare_to_wait
infrun: proceed: resuming Thread 0x7ffff6abd700 (LWP 8170)
infrun: resume (step=0, signal=GDB_SIGNAL_0), trap_expected=0, current thread
[Thread 0x7ffff6abd700 (LWP 8170)] at 0x4013bf
infrun: prepare_to_wait
infrun: previous breakpoint of Thread 0x7ffff72be700 (LWP 8169), at 0x4013bf
gone
infrun: pending event of Thread 0x7ffff72be700 (LWP 8169) cancelled.
infrun: Using pending wait status status->kind = spurious for Thread
0x7ffff72be700 (LWP 8169).
infrun: target_wait (-1.0.0, status) =
infrun: 8165.8169.0 [Thread 0x7ffff72be700 (LWP 8169)],
infrun: status->kind = spurious
infrun: TARGET_WAITKIND_SPURIOUS
infrun: Switching context from Thread 0x7ffff6abd700 (LWP 8170) to Thread
0x7ffff72be700 (LWP 8169)
infrun: resume (step=0, signal=GDB_SIGNAL_0), trap_expected=0, current thread
[Thread 0x7ffff72be700 (LWP 8169)] at 0x4013bf
infrun: prepare_to_wait
infrun: target_wait (-1.0.0, status) =
infrun: -1.0.0 [process -1],
infrun: status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
infrun: target_wait (-1.0.0, status) =
infrun: -1.0.0 [process -1],
infrun: status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
[Thread 0x7ffff6abd700 (LWP 8170) exited]
infrun: target_wait (-1.0.0, status) =
infrun: -1.0.0 [process -1],
infrun: status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
infrun: target_wait (-1.0.0, status) =
infrun: 8165.8165.0 [Thread 0x7ffff7fa7c00 (LWP 8165)],
infrun: status->kind = stopped, signal = GDB_SIGNAL_TRAP
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x401c83
infrun: context switch
infrun: Switching context from Thread 0x7ffff72be700 (LWP 8169) to Thread
0x7ffff7fa7c00 (LWP 8165)
infrun: BPSTAT_WHAT_STOP_NOISY
infrun: stop_waiting
infrun: stop_all_threads
infrun: stop_all_threads, pass=0, iterations=0
infrun: Thread 0x7ffff7fa7c00 (LWP 8165) not executing
infrun: Thread 0x7ffff72be700 (LWP 8169) executing, need stop
[Thread 0x7ffff72be700 (LWP 8169) exited]
infrun: target_wait (-1.0.0, status) =
infrun: 8165.8169.0 [LWP 8169],
infrun: status->kind = thread exited, status = 0
infrun: infrun_async(0)
/data/gdb_versions/devel/src/gdb/inferior.c:287: internal-error: inferior*
find_inferior_pid(int): Assertion `pid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) FAIL: gdb.threads/ia64-sigill.exp:
continue for the pending signal (GDB internal error)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26292-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 20:20:25 2020
Return-Path: <gdb-prs-return-26292-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 23661 invoked by alias); 4 Feb 2020 20:20:25 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 23641 invoked by uid 48); 4 Feb 2020 20:20:25 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25505] FAIL: gdb.threads/ia64-sigill.exp: continue for the
pending signal (GDB internal error)
Date: Tue, 04 Feb 2020 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: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25505-4717-UzVncgntPk@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25505-4717@http.sourceware.org/bugzilla/>
References: <bug-25505-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00207.txt
Content-length: 317
https://sourceware.org/bugzilla/show_bug.cgi?id=25505
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 12257
--> https://sourceware.org/bugzilla/attachment.cgi?id=12257&action=edit
gdb.22.log
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26293-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 20:21:36 2020
Return-Path: <gdb-prs-return-26293-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 30258 invoked by alias); 4 Feb 2020 20:21:35 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 30238 invoked by uid 48); 4 Feb 2020 20:21:35 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25505] FAIL: gdb.threads/ia64-sigill.exp: continue for the
pending signal (GDB internal error)
Date: Tue, 04 Feb 2020 20: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: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25505-4717-8Zk0Lgvf6d@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25505-4717@http.sourceware.org/bugzilla/>
References: <bug-25505-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00208.txt
Content-length: 318
https://sourceware.org/bugzilla/show_bug.cgi?id=25505
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
Hopefully fixed by commit c29705b71a "Fix internal error and improve 'set debug
infrun 1'/target wait kind trace".
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26294-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 20:44:16 2020
Return-Path: <gdb-prs-return-26294-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 71789 invoked by alias); 4 Feb 2020 20:44:15 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 71703 invoked by uid 48); 4 Feb 2020 20:44:15 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25505] FAIL: gdb.threads/ia64-sigill.exp: continue for the
pending signal (GDB internal error)
Date: Tue, 04 Feb 2020 20: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25505-4717-muvsedBYRp@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25505-4717@http.sourceware.org/bugzilla/>
References: <bug-25505-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00209.txt
Content-length: 463
https://sourceware.org/bugzilla/show_bug.cgi?id=25505
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #4)
> Hopefully fixed by commit c29705b71a "Fix internal error and improve 'set
> debug infrun 1'/target wait kind trace".
At commit c29705b71a: 50/50 pass.
Before commit c29705b71a: 47/50 pass.
I'd say that's confirmed.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26295-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 04 20:50:13 2020
Return-Path: <gdb-prs-return-26295-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 123029 invoked by alias); 4 Feb 2020 20:50:12 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 122940 invoked by uid 48); 4 Feb 2020 20:50:11 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25505] FAIL: gdb.threads/ia64-sigill.exp: continue for the
pending signal (GDB internal error)
Date: Tue, 04 Feb 2020 20: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-25505-4717-90ND1wgHwY@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25505-4717@http.sourceware.org/bugzilla/>
References: <bug-25505-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00210.txt
Content-length: 805
https://sourceware.org/bugzilla/show_bug.cgi?id=25505
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.1
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
I'd mark this a duplicate, but there doesn't seem to be a PR open for the
fixing commit.
So, marking this fixed instead.
FTR, fixed by:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=c29705b71a8ec966478c0dc4712194a95291c6de
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26296-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 05 10:32:04 2020
Return-Path: <gdb-prs-return-26296-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 22082 invoked by alias); 5 Feb 2020 10:32:04 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 22062 invoked by uid 48); 5 Feb 2020 10:32:03 -0000
From: "andrew.burgess at embecosm dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/25507] New: Add support for location views
Date: Wed, 05 Feb 2020 10: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: andrew.burgess at embecosm 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: <bug-25507-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00211.txt
Content-length: 791
https://sourceware.org/bugzilla/show_bug.cgi?id=25507
Bug ID: 25507
Summary: Add support for location views
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: symtab
Assignee: unassigned at sourceware dot org
Reporter: andrew.burgess at embecosm dot com
Target Milestone: ---
This is a place holder bug for adding support for location views to GDB.
The spec for location views is currently here:
http://dwarfstd.org/ShowIssue.php?issue=170427.1
I know of at least this bug that mentions locations views:
https://sourceware.org/bugzilla/show_bug.cgi?id=24459
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26297-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 05 11:18:19 2020
Return-Path: <gdb-prs-return-26297-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 23293 invoked by alias); 5 Feb 2020 11:18:19 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 23254 invoked by uid 48); 5 Feb 2020 11:18:17 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/25478] gdb hangs after external SIGKILL
Date: Wed, 05 Feb 2020 11: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25478-4717-F2ruh7gVGS@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00212.txt
Content-length: 1437
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
--- Comment #11 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #10)
> FWIW, an easier way to to reproduce (or indeed test a fix) is:
> ...
> $ gdb -ex "set prompt (master-gdb) " -ex "b stop_all_threads" -ex r -ex
> "shell killall -9 a.out" -ex c --args gdb -ex "set debug infrun 1" -ex r -ex
> c -ex c --args a.out
> ...
>
> The only manual interaction needed is to press ^C after a.out has been
> started.
I realized I can let the interrupt be raised by the application itself:
...
$ cat sleep.c
#include <pthread.h>
#include <unistd.h>
#include <signal.h>
static void *
fun (void *dummy)
{
raise (SIGINT);
while (1)
sleep (1);
return NULL;
}
int
main (void)
{
pthread_t thread;
pthread_create (&thread, NULL, fun, NULL);
while (1)
sleep (1);
return 0;
}
$ gcc sleep.c -lpthread
...
Then the hang is reproducible with just this command line (same as before, but
for convenience added "set pagination off" for both gdbs):
...
$ gdb -ex "set pagination off" -ex "set prompt (master-gdb) " -ex "b
stop_all_threads" -ex r -ex "shell killall -9 a.out" -ex c --args gdb -ex "set
pagination off" -ex "set debug infrun 1" -ex r -ex c -ex c --args a.out
...
I'm just not sure yet how to tranfer this into a testsuite test-case.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26298-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 05 12:27:43 2020
Return-Path: <gdb-prs-return-26298-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 32439 invoked by alias); 5 Feb 2020 12:27:42 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 32407 invoked by uid 48); 5 Feb 2020 12:27:40 -0000
From: "yeyunfeng at huawei dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/25478] gdb hangs after external SIGKILL
Date: Wed, 05 Feb 2020 12:27: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: yeyunfeng at huawei 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: <bug-25478-4717-IOIsq3SDH0@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00213.txt
Content-length: 528
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
yeyunfeng at huawei dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yeyunfeng at huawei dot com
--- Comment #12 from yeyunfeng at huawei dot com ---
I meet the same problem with you;
https://sourceware.org/bugzilla/show_bug.cgi?id=25496
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26299-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 05 18:35:10 2020
Return-Path: <gdb-prs-return-26299-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 36769 invoked by alias); 5 Feb 2020 18:35:09 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 36742 invoked by uid 48); 5 Feb 2020 18:35:09 -0000
From: "cbiesinger at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25479] AddressSanitizer: heap-buffer-overflow in
lookup_minimal_symbol_by_pc_name
Date: Wed, 05 Feb 2020 18: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: cbiesinger 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: cc
Message-ID: <bug-25479-4717-kJ7bRyCR5T@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25479-4717@http.sourceware.org/bugzilla/>
References: <bug-25479-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00214.txt
Content-length: 914
https://sourceware.org/bugzilla/show_bug.cgi?id=25479
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #7 from Christian Biesinger <cbiesinger at google dot com> ---
(In reply to Tom Tromey from comment #5)
> I've looked at it a little. I tend to think it is a pre-existing
> bug. I suspect Address Sanitizer doesn't understand how to examine
> objects allocated on an obstack (neither does valgrind...), which is
> why this was never detected.
Offtopic, but Valgrind can be taught this:
http://valgrind.org/docs/manual/mc-manual.html#mc-manual.mempools
I've been meaning to look into that.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26300-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 05 18:52:46 2020
Return-Path: <gdb-prs-return-26300-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 23885 invoked by alias); 5 Feb 2020 18:52:45 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 23807 invoked by uid 48); 5 Feb 2020 18:52:45 -0000
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25510] New: gcore should support sending the corefile to
stdout
Date: Wed, 05 Feb 2020 18:52: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: <bug-25510-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00215.txt
Content-length: 2002
https://sourceware.org/bugzilla/show_bug.cgi?id=25510
Bug ID: 25510
Summary: gcore should support sending the corefile to stdout
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 is related to https://bugzilla.redhat.com/show_bug.cgi?id=1788476. ]
The gcore command doesn't support writing the corefile to /dev/stdout:
(gdb) gcore /dev/stdout
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: Failed to write corefile contents (Illegal seek).
warning: writing note section (Illegal seek)
Saved corefile /dev/stdout
warning: cannot close "/dev/stdout": Illegal seek
GDB (ultimately bfd) tries to perform fseek when writing the corefile, which
doesn't work on stdout. It should be possible to make bfd spit the corefile in
one pass (the Linux kernel can do this), but I don't know how hard this would
be offhand.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26301-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 05 18:54:07 2020
Return-Path: <gdb-prs-return-26301-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 25321 invoked by alias); 5 Feb 2020 18:54:07 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 25301 invoked by uid 48); 5 Feb 2020 18:54:07 -0000
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25510] gcore should support sending the corefile to stdout
Date: Wed, 05 Feb 2020 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: 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: see_also
Message-ID: <bug-25510-4717-uHXuEsAfjC@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25510-4717@http.sourceware.org/bugzilla/>
References: <bug-25510-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00216.txt
Content-length: 483
https://sourceware.org/bugzilla/show_bug.cgi?id=25510
Sergio Durigan Junior <sergiodj at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugzilla.redhat.com
| |/show_bug.cgi?id=1788476
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26302-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 05 19:32:10 2020
Return-Path: <gdb-prs-return-26302-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 44359 invoked by alias); 5 Feb 2020 19:32:09 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 44338 invoked by uid 48); 5 Feb 2020 19:32:09 -0000
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25510] gcore should support sending the corefile to stdout
Date: Wed, 05 Feb 2020 19: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: 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: <bug-25510-4717-9nzrHmpEgi@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25510-4717@http.sourceware.org/bugzilla/>
References: <bug-25510-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00217.txt
Content-length: 4050
https://sourceware.org/bugzilla/show_bug.cgi?id=25510
--- Comment #1 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
This is one of the places the failures happen:
bfd/elf.c:assign_file_positions_except_relocs
6379 /* Write out the program headers. */
6380 alloc = i_ehdrp->e_phnum;
6381 if (alloc != 0)
6382 {
6383 if (bfd_seek (abfd, i_ehdrp->e_phoff, SEEK_SET) != 0
6384 || bed->s->write_out_phdrs (abfd, tdata->phdr, alloc) != 0)
6385 return FALSE;
6386 }
We get here by:
#0 assign_file_positions_except_relocs (abfd=0x2f3dbe0, link_info=0x0) at
../../binutils-gdb/bfd/elf.c:6383
#1 0x0000000000d46b4c in _bfd_elf_compute_section_file_positions
(abfd=0x2f3dbe0, link_info=0x0) at ../../binutils-gdb/bfd/elf.c:4353
#2 0x0000000000d5267d in _bfd_elf_set_section_contents (abfd=0x2f3dbe0,
section=0x3532720, location=0x353f190, offset=0, count=4096) at
../../binutils-gdb/bfd/elf.c:9150
#3 0x0000000000d1d63c in bfd_set_section_contents (abfd=0x2f3dbe0,
section=0x3532720, location=0x353f190, offset=0, count=4096) at
../../binutils-gdb/bfd/section.c:1511
#4 0x00000000006b98cd in gcore_copy_callback (obfd=0x2f3dbe0, osec=0x3532720,
ignored=0x0) at ../../binutils-gdb/gdb/gcore.c:559
#5 0x0000000000d1d411 in bfd_map_over_sections (abfd=0x2f3dbe0,
operation=0x6b972e <gcore_copy_callback(bfd*, asection*, void*)>,
user_storage=0x0) at ../../binutils-gdb/bfd/section.c:1370
#6 0x00000000006b9a19 in gcore_memory_sections (obfd=0x2f3dbe0) at
../../binutils-gdb/gdb/gcore.c:588
#7 0x00000000006b8698 in write_gcore_file_1 (obfd=0x2f3dbe0) at
../../binutils-gdb/gdb/gcore.c:103
#8 0x00000000006b87a8 in write_gcore_file (obfd=0x2f3dbe0) at
../../binutils-gdb/gdb/gcore.c:120
#9 0x00000000006b88e8 in gcore_command (args=0x24838a6 "/dev/stdout",
from_tty=1) at ../../binutils-gdb/gdb/gcore.c:155
#10 0x0000000000556d07 in do_const_cfunc (c=0x2d28ab0, args=0x24838a6
"/dev/stdout", from_tty=1) at ../../binutils-gdb/gdb/cli/cli-decode.c:107
#11 0x0000000000559c91 in cmd_func (cmd=0x2d28ab0, args=0x24838a6
"/dev/stdout", from_tty=1) at ../../binutils-gdb/gdb/cli/cli-decode.c:1952
#12 0x0000000000a9745d in execute_command (p=0x24838b0 "t", from_tty=1) at
../../binutils-gdb/gdb/top.c:653
#13 0x000000000068f486 in command_handler (command=0x24838a0 "gcore
/dev/stdout") at ../../binutils-gdb/gdb/event-top.c:587
#14 0x000000000068f8b4 in command_line_handler (rl=...) at
../../binutils-gdb/gdb/event-top.c:772
#15 0x000000000068ecb9 in gdb_rl_callback_handler (rl=0x2d9feb0 "gcore
/dev/stdout") at ../../binutils-gdb/gdb/event-top.c:218
#16 0x0000000000b79d09 in rl_callback_read_char () at
../../../binutils-gdb/readline/readline/callback.c:281
#17 0x000000000068eb36 in gdb_rl_callback_read_char_wrapper_noexcept () at
../../binutils-gdb/gdb/event-top.c:176
#18 0x000000000068ebbd in gdb_rl_callback_read_char_wrapper
(client_data=0x2481030) at ../../binutils-gdb/gdb/event-top.c:193
#19 0x000000000068f329 in stdin_event_handler (error=0, client_data=0x2481030)
at ../../binutils-gdb/gdb/event-top.c:515
#20 0x000000000068d447 in handle_file_event (file_ptr=0x2f26070, ready_mask=1)
at ../../binutils-gdb/gdb/event-loop.c:734
#21 0x000000000068d9ea in gdb_wait_for_event (block=1) at
../../binutils-gdb/gdb/event-loop.c:860
#22 0x000000000068c8e7 in gdb_do_one_event () at
../../binutils-gdb/gdb/event-loop.c:346
#23 0x000000000068c911 in start_event_loop () at
../../binutils-gdb/gdb/event-loop.c:370
#24 0x00000000007d03cd in captured_command_loop () at
../../binutils-gdb/gdb/main.c:360
#25 0x00000000007d1a84 in captured_main (data=0x7fffffffe020) at
../../binutils-gdb/gdb/main.c:1203
#26 0x00000000007d1aea in gdb_main (args=0x7fffffffe020) at
../../binutils-gdb/gdb/main.c:1218
#27 0x00000000004166ad in main (argc=2, argv=0x7fffffffe128) at
../../binutils-gdb/gdb/gdb.c:32
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26303-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 05 20:29:40 2020
Return-Path: <gdb-prs-return-26303-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 68733 invoked by alias); 5 Feb 2020 20:29:39 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 68699 invoked by uid 48); 5 Feb 2020 20:29:39 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/25478] gdb hangs after external SIGKILL
Date: Wed, 05 Feb 2020 20: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25478-4717-FHD2BjURRR@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00218.txt
Content-length: 432
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
--- Comment #13 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #11)
> I'm just not sure yet how to tranfer this into a testsuite test-case.
Managed to transfer it into a test-case, submitted at
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/759
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26305-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 06 07:47:23 2020
Return-Path: <gdb-prs-return-26305-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 45503 invoked by alias); 6 Feb 2020 07:47:22 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 45363 invoked by uid 48); 6 Feb 2020 07:47:21 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/25478] gdb hangs after external SIGKILL
Date: Thu, 06 Feb 2020 07:47: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: vries 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: <bug-25478-4717-ei0LX2twjE@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25478-4717@http.sourceware.org/bugzilla/>
References: <bug-25478-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00220.txt
Content-length: 264
https://sourceware.org/bugzilla/show_bug.cgi?id=25478
--- Comment #14 from Tom de Vries <vries at gcc dot gnu.org> ---
*** Bug 25496 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26304-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 06 07:47:22 2020
Return-Path: <gdb-prs-return-26304-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 45341 invoked by alias); 6 Feb 2020 07:47:20 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 45306 invoked by uid 48); 6 Feb 2020 07:47:19 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25496] Endless print " warning: unable to open /proc file
'/proc/22703/status' "
Date: Thu, 06 Feb 2020 07: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.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: <bug-25496-4717-urDsVT2VCP@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25496-4717@http.sourceware.org/bugzilla/>
References: <bug-25496-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00219.txt
Content-length: 724
https://sourceware.org/bugzilla/show_bug.cgi?id=25496
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |vries at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
The behaviour in this PR is identical to what has been described at PR25478
comment 1.
*** This bug has been marked as a duplicate of bug 25478 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26306-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 06 10:30:57 2020
Return-Path: <gdb-prs-return-26306-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 14317 invoked by alias); 6 Feb 2020 10:30:55 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 14291 invoked by uid 48); 6 Feb 2020 10:30:55 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25514] New: gdb fails to set all breakpoint locations
Date: Thu, 06 Feb 2020 10: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: vries 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: <bug-25514-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00221.txt
Content-length: 2442
https://sourceware.org/bugzilla/show_bug.cgi?id=25514
Bug ID: 25514
Summary: gdb fails to set all breakpoint locations
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Consider the cc1 executable mentioned here (PR23710 comment 1).
If we grep for do_rpo_vn in the minimal symbol info:
...
$ nm cc1 | grep do_rpo_vn | c++filt
0000000000d42650 T do_rpo_vn(function*, edge_def*, bitmap_head*)
0000000000d40e30 t do_rpo_vn(function*, edge_def*, bitmap_head*, bool, bool)
000000000058659d t do_rpo_vn(function*, edge_def*, bitmap_head*, bool, bool)
[clone .cold.138]
0000000001921d48 r do_rpo_vn(function*, edge_def*, bitmap_head*, bool,
bool)::__FUNCTION__
...
we get 3 function locations (and a "do_rpo_vn" string in the .rodata section).
With lldb, we get a breakpoint for all three locations:
...
$ lldb -batch -o "b do_rpo_vn" -o "break list" cc1
(lldb) target create "cc1"
Current executable set to 'cc1' (x86_64).
(lldb) b do_rpo_vn
Breakpoint 1: 3 locations.
(lldb) break list
Current breakpoints:
1: name = 'do_rpo_vn', locations = 3
1.1: where = cc1`do_rpo_vn(function*, edge_def*, bitmap_head*, bool, bool)
(.cold.138) + 20, address = cc1[0x00000000005865b1], unresolved, hit count = 0
1.2: where = cc1`do_rpo_vn(function*, edge_def*, bitmap_head*) at
tree-ssa-sccvn.c:6703, address = cc1[0x0000000000d42650], unresolved, hit count
= 0
1.3: where = cc1`do_rpo_vn(function*, edge_def*, bitmap_head*, bool, bool) +
20, address = cc1[0x0000000000d40e44], unresolved, hit count = 0
...
With gdb, the "[clone .cold.138]" one is skipped:
...
$ gdb -batch -ex "b do_rpo_vn" -ex "info breakpoints" cc1
Breakpoint 1 at 0xd40e30: do_rpo_vn. (2 locations)
Num Type Disp Enb Address What
1 breakpoint keep y <MULTIPLE>
1.1 y 0x0000000000d40e30 in do_rpo_vn(function*,
edge, bitmap, bool, bool) at /tmp/trunk/gcc/tree-ssa-sccvn.c:6292
1.2 y 0x0000000000d42650 in do_rpo_vn(function*,
edge_def*, bitmap_head*) at /tmp/trunk/gcc/tree-ssa-sccvn.c:6704
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26307-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 06 10:38:15 2020
Return-Path: <gdb-prs-return-26307-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 21986 invoked by alias); 6 Feb 2020 10:38:14 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 21961 invoked by uid 48); 6 Feb 2020 10:38:14 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25514] gdb fails to set all breakpoint locations
Date: Thu, 06 Feb 2020 10: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: vries 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: <bug-25514-4717-4PT6Dix4lU@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25514-4717@http.sourceware.org/bugzilla/>
References: <bug-25514-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00222.txt
Content-length: 1253
https://sourceware.org/bugzilla/show_bug.cgi?id=25514
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Furthermore, if we create a variant with the debug sections stripped:
...
$ objcopy --strip-debug cc1 cc1.stripped
...
we only get two locations with lldb:
...
$ lldb -batch -o "b do_rpo_vn" -o "break list" cc1.stripped
(lldb) target create "cc1.stripped"
Current executable set to 'cc1.stripped' (x86_64).
(lldb) b do_rpo_vn
Breakpoint 1: 2 locations.
(lldb) break list
Current breakpoints:
1: name = 'do_rpo_vn', locations = 2
1.1: where = cc1.stripped`do_rpo_vn(function*, edge_def*, bitmap_head*, bool,
bool), address = cc1.stripped[0x0000000000d40e30], unresolved, hit count = 0
1.2: where = cc1.stripped`do_rpo_vn(function*, edge_def*, bitmap_head*),
address = cc1.stripped[0x0000000000d42650], unresolved, hit count = 0
...
and with gdb we only get one:
...
$ gdb -batch -ex "b do_rpo_vn" -ex "info breakpoints" cc1.stripped
Breakpoint 1 at 0xd42650
Num Type Disp Enb Address What
1 breakpoint keep y 0x0000000000d42650 <do_rpo_vn(function*,
edge_def*, bitmap_head*)>
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26308-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 06 11:05:42 2020
Return-Path: <gdb-prs-return-26308-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 30694 invoked by alias); 6 Feb 2020 11:05:41 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 30671 invoked by uid 48); 6 Feb 2020 11:05:40 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25514] gdb fails to set all breakpoint locations
Date: Thu, 06 Feb 2020 11: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: vries 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: <bug-25514-4717-uWbqQ1YHnc@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25514-4717@http.sourceware.org/bugzilla/>
References: <bug-25514-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00223.txt
Content-length: 2048
https://sourceware.org/bugzilla/show_bug.cgi?id=25514
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Looking in the .debug_info section, it seems there are two abstract/concrete
DIE pairs for do_rpo_vn:
First pair:
...
<1><2869cb3>: Abbrev Number: 40 (DW_TAG_subprogram)
<2869cb4> DW_AT_external : 1
<2869cb4> DW_AT_name : do_rpo_vn
<2869cb8> DW_AT_decl_file : 113
<2869cb9> DW_AT_decl_line : 6702
<2869cbb> DW_AT_decl_column : 1
<2869cbc> DW_AT_linkage_name: do_rpo_vn(function*, edge_def*,
bitmap_head*)
<2869cc0> DW_AT_type : <0x282e0cd>
<2869cc4> DW_AT_sibling : <0x2869cfc>
<1><5072058>: Abbrev Number: 5 (DW_TAG_subprogram)
<5072059> DW_AT_abstract_origin: <0x2869cb3>
<507205d> DW_AT_low_pc : 0xd42650
<5072065> DW_AT_high_pc : 0x23
<507206d> DW_AT_frame_base : 1 byte block: 9c (DW_OP_call_frame_cfa)
<507206f> DW_AT_GNU_all_call_sites: 1
<507206f> DW_AT_sibling : <0x50720e6>
...
Second pair:
...
<1><2869cfc>: Abbrev Number: 33 (DW_TAG_subprogram)
<2869cfd> DW_AT_name : do_rpo_vn
<2869d01> DW_AT_decl_file : 113
<2869d02> DW_AT_decl_line : 6285
<2869d04> DW_AT_decl_column : 1
<2869d05> DW_AT_type : <0x282e0cd>
<2869d09> DW_AT_sibling : <0x286a0fd>
<1><506ec60>: Abbrev Number: 17 (DW_TAG_subprogram)
<506ec61> DW_AT_abstract_origin: <0x2869cfc>
<506ec65> DW_AT_ranges : 0x98fae0
<506ec69> DW_AT_frame_base : 1 byte block: 9c (DW_OP_call_frame_cfa)
<506ec6b> DW_AT_GNU_all_call_sites: 1
<506ec6b> DW_AT_sibling : <0x5072049>
...
with two ranges:
...
0098fae0 0000000000d40e30 0000000000d425d7
0098fae0 000000000058659d 000000000058663d
0098fae0 <End of list>
...
So, the address at 58659d is for an outlined part of the function at d40e30.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26309-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 06 11:11:24 2020
Return-Path: <gdb-prs-return-26309-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 44071 invoked by alias); 6 Feb 2020 11:11:24 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 44051 invoked by uid 48); 6 Feb 2020 11:11:24 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25514] gdb fails to set all breakpoint locations
Date: Thu, 06 Feb 2020 11: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: vries 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: <bug-25514-4717-jIIsDwgdaY@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25514-4717@http.sourceware.org/bugzilla/>
References: <bug-25514-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00224.txt
Content-length: 531
https://sourceware.org/bugzilla/show_bug.cgi?id=25514
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> With lldb, we get a breakpoint for all three locations:
> With gdb, the "[clone .cold.138]" one is skipped:
Hmm, if the "[clone .cold.138]" is in fact not a function entry but an outlined
part of another function, then having two breakpoint locations looks reasonable
after all.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26310-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 06 11:42:42 2020
Return-Path: <gdb-prs-return-26310-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 62261 invoked by alias); 6 Feb 2020 11:42:42 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 62238 invoked by uid 48); 6 Feb 2020 11:42:41 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25514] gdb fails to set all breakpoint locations
Date: Thu, 06 Feb 2020 11: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: vries 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: <bug-25514-4717-OQHDKZU6md@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25514-4717@http.sourceware.org/bugzilla/>
References: <bug-25514-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00225.txt
Content-length: 465
https://sourceware.org/bugzilla/show_bug.cgi?id=25514
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> Furthermore, if we create a variant with the debug sections stripped:
> we only get two locations with lldb:
> and with gdb we only get one:
Still, I wonder if in this case gdb should display more than one location.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26311-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 06 14:29:33 2020
Return-Path: <gdb-prs-return-26311-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 38791 invoked by alias); 6 Feb 2020 14:29:32 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 38763 invoked by uid 48); 6 Feb 2020 14:29:32 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/23710] gdb is slow and memory hungry consuming debug
generated with LTO by GCC
Date: Thu, 06 Feb 2020 14: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.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-23710-4717-0tVnAcX6Fv@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23710-4717@http.sourceware.org/bugzilla/>
References: <bug-23710-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00226.txt
Content-length: 1029
https://sourceware.org/bugzilla/show_bug.cgi?id=23710
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #0)
> gdb takes ~10s to process a LTO bootstrapped cc1 binary and another two
> seconds
> when setting the first breakpoint. It also has allocated 1.6GB memory at
> that point (compared to ~200MB for a non-LTO binary).
There's a setting "maint set/show dwarf max-cache-age" which defaults to 5.
Using a higher setting, I get the following reduction in real execution time:
- 10 : 1.5%
- 100 : 12.5%
- 316 : 16.5%
- 1000 : 16.5%
- 10000 : 16.5%
- 100000: 15.5%
Note: adding the setting to the gdb command line using -iex to make sure it
gets set _before_ loading the exec):
...
$ gdb -q -nw -nx -batch -iex "maint set dwarf max-cache-age $n" -ex "b
do_rpo_vn" cc1
...
Conversely, disabling the cache by setting the value to 0 causes a real
execution time increase of 46%.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26312-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 06 22:49:26 2020
Return-Path: <gdb-prs-return-26312-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 54691 invoked by alias); 6 Feb 2020 22:49:25 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 54670 invoked by uid 48); 6 Feb 2020 22:49:25 -0000
From: "andrew.burgess at embecosm dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/25318] Aarch64-SIM: BLR opcode does not support XLR
register properly.
Date: Thu, 06 Feb 2020 22:49: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: andrew.burgess at embecosm dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: <bug-25318-4717-wyMcU4IKHP@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25318-4717@http.sourceware.org/bugzilla/>
References: <bug-25318-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00227.txt
Content-length: 546
https://sourceware.org/bugzilla/show_bug.cgi?id=25318
Andrew Burgess <andrew.burgess at embecosm dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andrew.burgess at embecosm dot com
| |, vapier at gentoo dot org
Component|gdb |sim
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26313-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 06 22:54:02 2020
Return-Path: <gdb-prs-return-26313-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 76547 invoked by alias); 6 Feb 2020 22:54:01 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 76442 invoked by uid 48); 6 Feb 2020 22:54:00 -0000
From: "peter at lekensteyn dot nl" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug record/23188] Process record does not support instruction 0xc5
(vmovd %esi,%xmm0 / AVX2)
Date: Thu, 06 Feb 2020 22:54: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.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: peter at lekensteyn dot nl
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
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: <bug-23188-4717-jTdwBf9qJp@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23188-4717@http.sourceware.org/bugzilla/>
References: <bug-23188-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00228.txt
Content-length: 1505
https://sourceware.org/bugzilla/show_bug.cgi?id=23188
Peter Wu <peter at lekensteyn dot nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://sourceware.org/bugz
| |illa/show_bug.cgi?id=19365
--- Comment #6 from Peter Wu <peter at lekensteyn dot nl> ---
The problem still exists in GDB 8.3.1.
A workaround for typical programs is described in
https://stackoverflow.com/q/42451492/427545
Bug 19365 is about AVX while this bug is about AVX2.
Full AVX/AVX2 support looks like a ton of work:
- At minimum VEX prefix support (C4 for 3-byte VEX, C5 for 2-byte VEX) [1]
- AVX-specific instructions [2] - currently not supported.
- AVX2-specific instructions [3] - currently not supported.
Luckily AVX-512 is not common yet, the full set of extensions is quite big.[4]
It looks like i386_process_record in i386-tdep.c has to be updated to support
new features. For the original case (vmovd), support for the VEX prefixes (the
'v' in 'vmovd') should be sufficient.
[1]: https://en.wikipedia.org/wiki/VEX_prefix
[2]: https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#New_instructions
[3]:
https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#New_instructions_2
[4]: https://en.wikipedia.org/wiki/AVX-512
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26314-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 06 22:55:43 2020
Return-Path: <gdb-prs-return-26314-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 85237 invoked by alias); 6 Feb 2020 22:55:43 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 85135 invoked by uid 55); 6 Feb 2020 22:55:42 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/25318] Aarch64-SIM: BLR opcode does not support XLR
register properly.
Date: Thu, 06 Feb 2020 22: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: 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: <bug-25318-4717-JKAqHWgC9C@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25318-4717@http.sourceware.org/bugzilla/>
References: <bug-25318-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00229.txt
Content-length: 1278
https://sourceware.org/bugzilla/show_bug.cgi?id=25318
--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=69b1ffdb01106ed84a41a80f6ad2d9c26c4f45a9
commit 69b1ffdb01106ed84a41a80f6ad2d9c26c4f45a9
Author: Carlo Bramini <carlo_bramini@users.sourceforge.net>
Date: Thu Feb 6 22:50:26 2020 +0000
sim/aarch64: Fix register ordering bug in blr (PR sim/25318)
A comment in the implementation of blr says:
/* The pseudo code in the spec says we update LR before fetching.
the value from the rn. */
With 'rn' being the register holding the destination address.
This may have been true at one point, but the ISA manual now clearly
shows the destination register being read before the link register is
written.
This commit updates the implementation of blr to match.
sim/aarch64/ChangeLog:
PR sim/25318
* simulator.c (blr): Read destination register before calling
aarch64_save_LR.
Change-Id: Icb1c556064e3d9c807ac28440475caa205ab1064
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26315-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 03:04:57 2020
Return-Path: <gdb-prs-return-26315-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 118719 invoked by alias); 7 Feb 2020 03:04:56 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 118691 invoked by uid 48); 7 Feb 2020 03:04:56 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25515] New: inconsistency behavior for using loop step and
setting breakpoint
Date: Fri, 07 Feb 2020 03: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25515-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00230.txt
Content-length: 2885
https://sourceware.org/bugzilla/show_bug.cgi?id=25515
Bug ID: 25515
Summary: inconsistency behavior for using loop step and setting
breakpoint
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
$ gdb -v
GNU gdb (GDB) 9.0.50.20191210-git
Copyright (C) 2019 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.
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d --enable-shared
--enable-threads=posix --with-system-zlib --with-isl --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch
--disable-libssp --enable-gnu-unique-object --enable-linker-build-id
--enable-lto --enable-plugin --enable-install-libiberty
--with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib
--disable-werror --enable-checking=release --enable-default-pie
--enable-default-ssp --enable-cet=auto gdc_include_dir=/usr/include/dlang/gdc
Thread model: posix
gcc version 9.2.0 (GCC)
$ cat small.c
int t(int i) { return -1; }
void f(int b)
{
int j = 0;
while(j != -1)
j = t(b);
}
void main(void) { f(0); }
$ gcc -g small.c
$ cat cmmds1
start
while 1
where
step
end
$ gdb -q -batch -ex 'file ./a.out' --command=./cmmds1 | grep -e '#0 '
#0 main () at small.c:11
#0 f (b=0) at small.c:5
#0 f (b=0) at small.c:7
#0 f (b=0) at small.c:8
#0 t (i=0) at small.c:1
#0 f (b=0) at small.c:7
#0 f (b=0) at small.c:9
#0 main () at small.c:11
...
$ cat cmmds2
break small.c:7
run
while 1
where
continue
end
$ gdb -q -batch -ex 'file ./a.out' --command=./cmmds2 | grep -e '#0 '
#0 f (b=0) at small.c:7
...
###############################################################################
### inconsistent behavior:
### While using 'start' and loop 'step' in file 'cmmds1', gdb breaks at line
7 twice.
### While setting breakpoint at 'small.c:7' in file 'cmmds2', gdb breaks at
line 7 once.
###
###############################################################################
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26317-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 03:28:56 2020
Return-Path: <gdb-prs-return-26317-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 50682 invoked by alias); 7 Feb 2020 03:28:56 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 50661 invoked by uid 48); 7 Feb 2020 03:28:56 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25515] inconsistency behavior for using loop step and
setting breakpoint
Date: Fri, 07 Feb 2020 03: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: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: <bug-25515-4717-d3lA2It33W@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25515-4717@http.sourceware.org/bugzilla/>
References: <bug-25515-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00232.txt
Content-length: 322
https://sourceware.org/bugzilla/show_bug.cgi?id=25515
--- Comment #2 from Yibiao Yang <yangyibiao at hust dot edu.cn> ---
Created attachment 12270
--> https://sourceware.org/bugzilla/attachment.cgi?id=12270&action=edit
file cmmds1
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26316-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 03:28:27 2020
Return-Path: <gdb-prs-return-26316-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 50115 invoked by alias); 7 Feb 2020 03:28:27 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 50080 invoked by uid 48); 7 Feb 2020 03:28:26 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25515] inconsistency behavior for using loop step and
setting breakpoint
Date: Fri, 07 Feb 2020 03: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: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: <bug-25515-4717-1XiAZ8jpUo@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25515-4717@http.sourceware.org/bugzilla/>
References: <bug-25515-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00231.txt
Content-length: 591
https://sourceware.org/bugzilla/show_bug.cgi?id=25515
Yibiao Yang <yangyibiao at hust dot edu.cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yangyibiao at hust dot edu.cn
--- Comment #1 from Yibiao Yang <yangyibiao at hust dot edu.cn> ---
Created attachment 12269
--> https://sourceware.org/bugzilla/attachment.cgi?id=12269&action=edit
file small.c
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26318-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 03:29:20 2020
Return-Path: <gdb-prs-return-26318-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 51701 invoked by alias); 7 Feb 2020 03:29:19 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 51683 invoked by uid 48); 7 Feb 2020 03:29:19 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25515] inconsistency behavior for using loop step and
setting breakpoint
Date: Fri, 07 Feb 2020 03: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: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: <bug-25515-4717-KsrAu0pRIl@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25515-4717@http.sourceware.org/bugzilla/>
References: <bug-25515-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00233.txt
Content-length: 322
https://sourceware.org/bugzilla/show_bug.cgi?id=25515
--- Comment #3 from Yibiao Yang <yangyibiao at hust dot edu.cn> ---
Created attachment 12271
--> https://sourceware.org/bugzilla/attachment.cgi?id=12271&action=edit
file cmmds2
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26319-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 09:58:16 2020
Return-Path: <gdb-prs-return-26319-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 121154 invoked by alias); 7 Feb 2020 09:58:15 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 119393 invoked by uid 48); 7 Feb 2020 09:58:14 -0000
From: "lucho at mbox dot contact.bg" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/25296] gdb8.3 tui source windows highlight cannot show
chinese word
Date: Fri, 07 Feb 2020 09: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: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: lucho at mbox dot contact.bg
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: <bug-25296-4717-a5W8CpSvsZ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25296-4717@http.sourceware.org/bugzilla/>
References: <bug-25296-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00234.txt
Content-length: 2351
https://sourceware.org/bugzilla/show_bug.cgi?id=25296
Лъчезар Георгиев <lucho at mbox dot contact.bg> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lucho at mbox dot contact.bg
--- Comment #1 from Лъчезар Георгиев <lucho at mbox dot contact.bg> ---
I can confirm the bug. The source code window doesn't show properly the UTF-8
characters (Chinese, Cyrillic, etc.) but shows correctly only the ASCII ones.
For example, the following source code
printf("Здравей, свят!\n");
appears in the source code window as
printf("^^P^ ^P^ ^Q^┗↑@^^P^ ^P^ ^P^ ^P^ ^^Q^┗↑╝^^P^ ^Q^ ^Q^ \n");
The command windows is not affected (when I type non-ASCII characters into it,
they appear OK).
Additionally, I found out the following:
(1) This bug was introduced in version 8.3;
(2) It affects only some CPU architectures.
In more detail, I tested version "Debian 8.3.1-1" on two 64-bit machines with
the same version of Debian (bullseye/sid), one with PowerPC, and the other with
SPARC. The bug shows up only on the SPARC machine, not the PowerPC one. I then
built the generic version 8.3.1 on a 64-bit ARM machine. The bug didn't show up
there. And then, I built it on a 64-bit MIPS (big endian) machine, where the
bug did show up. Repeated this with version 8.3. The bug showed up again. When
I built the generic version 8.2.1 on the same MIPS machine, the bug didn't show
up. A "diff -u gdb-8.2.1/gdb/tui gdb-8.3/gdb/tui" shows a lot of changes made
in the TUI code of version 8.3 to add some colourisation to the TUI, and the
bug was probably introduced during this process. Sorry that I can't help more
to isolate the bug. But it's quite strange that it manifests itself only on
x86-64 (as I had found out previously using Ubuntu 20-04), SPARC and MIPS, but
not on ARM and PowerPC. I suppose that because of this, it will be rather hard
to pinpoint.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26320-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 11:17:36 2020
Return-Path: <gdb-prs-return-26320-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 82824 invoked by alias); 7 Feb 2020 11:17:35 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 82806 invoked by uid 48); 7 Feb 2020 11:17:35 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25504] FAIL: gdb.threads/process-dies-while-detaching.exp:
single-process: continue: watchpoint: continue (Couldn't get registers: No
such process)
Date: Fri, 07 Feb 2020 11: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: vries 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: <bug-25504-4717-bHupFBH1Vb@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25504-4717@http.sourceware.org/bugzilla/>
References: <bug-25504-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00235.txt
Content-length: 2657
https://sourceware.org/bugzilla/show_bug.cgi?id=25504
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
I usually build gdb with -O0. I just did a build with -O2, and this FAIL (or, a
FAIL like this in the same test) becomes much more likely:
...
$ for n in $(seq 1 10); do ./test.sh 2>&1 | tee TESTLOG.$n; cp gdb.log
gdb.$n.log; cp gdb.sum gdb.$n.sum; done | grep "expected passes"
# of expected passes 65
# of expected passes 65
# of expected passes 64
# of expected passes 64
# of expected passes 63
# of expected passes 64
# of expected passes 65
# of expected passes 64
# of expected passes 65
# of expected passes 65
$ grep ^FAIL: gdb.[1-9].sum gdb.10.sum
gdb.1.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: killed outside: continue
gdb.2.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: detach: continue
gdb.3.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: detach: continue
gdb.3.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: killed outside: continue
gdb.4.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: watchpoint: continue
gdb.4.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: killed outside: continue
gdb.5.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: detach: continue
gdb.5.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: watchpoint: continue
gdb.5.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: killed outside: continue
gdb.6.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: detach: continue
gdb.6.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: watchpoint: continue
gdb.7.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: watchpoint: continue
gdb.8.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: watchpoint: continue
gdb.8.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: killed outside: continue
gdb.9.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: watchpoint: continue
gdb.10.sum:FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: watchpoint: continue
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26321-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 12:13:04 2020
Return-Path: <gdb-prs-return-26321-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 43210 invoked by alias); 7 Feb 2020 12:13:04 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 43186 invoked by uid 48); 7 Feb 2020 12:13:03 -0000
From: "carlo_bramini at users dot sourceforge.net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/25318] Aarch64-SIM: BLR opcode does not support XLR
register properly.
Date: Fri, 07 Feb 2020 12:13: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: carlo_bramini at users dot sourceforge.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: <bug-25318-4717-dx8uv0yiM1@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25318-4717@http.sourceware.org/bugzilla/>
References: <bug-25318-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00236.txt
Content-length: 610
https://sourceware.org/bugzilla/show_bug.cgi?id=25318
--- Comment #6 from Carlo Bramini <carlo_bramini at users dot sourceforge.net> ---
(In reply to cvs-commit@gcc.gnu.org from comment #5)
> The master branch has been updated by Andrew Burgess
> <aburgess@sourceware.org>:
>
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;
> h=69b1ffdb01106ed84a41a80f6ad2d9c26c4f45a9
The commit has fixed the issue.
So, this bug could be marked as resolved if you want.
Thank you very much for your support.
Sincerely.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26322-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 15:27:29 2020
Return-Path: <gdb-prs-return-26322-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 6326 invoked by alias); 7 Feb 2020 15:27:28 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 6304 invoked by uid 48); 7 Feb 2020 15:27:28 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/25318] Aarch64-SIM: BLR opcode does not support XLR
register properly.
Date: Fri, 07 Feb 2020 15:27: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: simark at simark dot ca
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: <bug-25318-4717-IoCMaDoWOG@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25318-4717@http.sourceware.org/bugzilla/>
References: <bug-25318-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00237.txt
Content-length: 970
https://sourceware.org/bugzilla/show_bug.cgi?id=25318
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Simon Marchi <simark at simark dot ca> ---
(In reply to Carlo Bramini from comment #6)
> (In reply to cvs-commit@gcc.gnu.org from comment #5)
> > The master branch has been updated by Andrew Burgess
> > <aburgess@sourceware.org>:
> >
> > https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;
> > h=69b1ffdb01106ed84a41a80f6ad2d9c26c4f45a9
>
> The commit has fixed the issue.
> So, this bug could be marked as resolved if you want.
> Thank you very much for your support.
>
> Sincerely.
Done, thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26323-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 19:46:49 2020
Return-Path: <gdb-prs-return-26323-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 7446 invoked by alias); 7 Feb 2020 19:46:49 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 7420 invoked by uid 55); 7 Feb 2020 19:46:48 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Fri, 07 Feb 2020 19: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
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: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-24915-4717-KgRv2C1ksn@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00238.txt
Content-length: 1140
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #20 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The gdb-9-branch branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=76f5096cd444948843f5bf65eee33c32881d6332
commit 76f5096cd444948843f5bf65eee33c32881d6332
Author: Tom Tromey <tromey@adacore.com>
Date: Wed Feb 5 10:53:44 2020 +0100
Revert basenames_may_differ patch
Commit a0c1ffedc regressed certain cases coming from Eclipse.
See PR breakpoints/24915.
This patch reverts the commit for the gdb 9 release.
gdb/ChangeLog
2020-02-07 Tom Tromey <tromey@adacore.com>
PR breakpoints/24915:
* source.c (find_and_open_source): Do not check basenames_may_differ.
gdb/testsuite/ChangeLog
2020-02-07 Tom Tromey <tromey@adacore.com>
PR breakpoints/24915:
* gdb.base/annotate-symlink.exp: Use setup_xfail.
Change-Id: Iadbf42f35eb40c95ad32b2108ae25d8f199998bd
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26324-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 20:27:20 2020
Return-Path: <gdb-prs-return-26324-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 70497 invoked by alias); 7 Feb 2020 20:27:20 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 70475 invoked by uid 55); 7 Feb 2020 20:27:20 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25190] annotations generated incorrectly unless "set
pagination off"
Date: Fri, 07 Feb 2020 20: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: 8.3.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: <bug-25190-4717-Faxmv511Yz@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25190-4717@http.sourceware.org/bugzilla/>
References: <bug-25190-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00239.txt
Content-length: 1700
https://sourceware.org/bugzilla/show_bug.cgi?id=25190
--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The gdb-9-branch branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f49692dff8efe149fe3087e2d3abdafca3d062eb
commit f49692dff8efe149fe3087e2d3abdafca3d062eb
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date: Wed Feb 5 12:45:13 2020 +0100
Make fputs_unfiltered use fputs_maybe_filtered
This patch redefines fputs_unfiltered in utils.c, with new behavior to
forward parameters to fputs_maybe_filtered. This makes
fputs_unfiltered identical to fputs_filtered, except filtering is
disabled.
Some callers of fputs_unfiltered have been updated to use ui_file_puts
where they were using other ui_file_* functions anyway for IO.
This fixes the problem I saw with \032\032post-prompt annotation being
flushed to stdout in the wrong order.
gdb/ChangeLog
2020-02-05 Iain Buclaw <ibuclaw@gdcproject.org>
PR gdb/25190:
* gdb/remote-sim.c (gdb_os_write_stderr): Update.
* gdb/remote.c (remote_console_output): Update.
* gdb/ui-file.c (fputs_unfiltered): Rename to...
(ui_file_puts): ...this.
* gdb/ui-file.h (ui_file_puts): Add declaration.
* gdb/utils.c (emit_style_escape): Update.
(flush_wrap_buffer): Update.
(fputs_maybe_filtered): Update.
(fputs_unfiltered): Add function.
Change-Id: I17ed5078f71208344f2f8ab634a6518b1af6e213
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26325-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 20:28:57 2020
Return-Path: <gdb-prs-return-26325-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 74135 invoked by alias); 7 Feb 2020 20:28:56 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 74115 invoked by uid 48); 7 Feb 2020 20:28:56 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25190] annotations generated incorrectly unless "set
pagination off"
Date: Fri, 07 Feb 2020 20: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: 8.3.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: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution target_milestone
Message-ID: <bug-25190-4717-ZbpRlLsPRT@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25190-4717@http.sourceware.org/bugzilla/>
References: <bug-25190-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00240.txt
Content-length: 649
https://sourceware.org/bugzilla/show_bug.cgi?id=25190
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |tromey at sourceware dot org
Resolution|--- |FIXED
Target Milestone|--- |9.1
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
Fixed for 9.1.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26326-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 21:10:46 2020
Return-Path: <gdb-prs-return-26326-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 30263 invoked by alias); 7 Feb 2020 21:10:45 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 30243 invoked by uid 48); 7 Feb 2020 21:10:45 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/25518] New: gdb annotations print real path
Date: Fri, 07 Feb 2020 21:10: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: <bug-25518-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00241.txt
Content-length: 899
https://sourceware.org/bugzilla/show_bug.cgi?id=25518
Bug ID: 25518
Summary: gdb annotations print real path
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: ---
gdb annotations and other file-name displays can show the real
path, not the path the user used to compile.
There was an attempt to fix this in commit a0c1ffedc, but
this had to be reverted due to bug#24915.
This bug is a reminder to re-investigate this and find a better fix.
Perhaps we can separate the concepts of the path used for
matching and the path used for display; and also maybe add some
caching.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26328-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 21:11:47 2020
Return-Path: <gdb-prs-return-26328-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 32185 invoked by alias); 7 Feb 2020 21:11:46 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 32162 invoked by uid 55); 7 Feb 2020 21:11:46 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25190] annotations generated incorrectly unless "set
pagination off"
Date: Fri, 07 Feb 2020 21: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.3.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: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25190-4717-m0kq2WMo5M@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25190-4717@http.sourceware.org/bugzilla/>
References: <bug-25190-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00243.txt
Content-length: 1674
https://sourceware.org/bugzilla/show_bug.cgi?id=25190
--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=dfcb27e41d37b8bff178697f5f33ec288387fb01
commit dfcb27e41d37b8bff178697f5f33ec288387fb01
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date: Wed Feb 5 12:45:13 2020 +0100
Make fputs_unfiltered use fputs_maybe_filtered
This patch redefines fputs_unfiltered in utils.c, with new behavior to
forward parameters to fputs_maybe_filtered. This makes
fputs_unfiltered identical to fputs_filtered, except filtering is
disabled.
Some callers of fputs_unfiltered have been updated to use ui_file_puts
where they were using other ui_file_* functions anyway for IO.
This fixes the problem I saw with \032\032post-prompt annotation being
flushed to stdout in the wrong order.
2020-02-05 Iain Buclaw <ibuclaw@gdcproject.org>
PR gdb/25190:
* gdb/remote-sim.c (gdb_os_write_stderr): Update.
* gdb/remote.c (remote_console_output): Update.
* gdb/ui-file.c (fputs_unfiltered): Rename to...
(ui_file_puts): ...this.
* gdb/ui-file.h (ui_file_puts): Add declaration.
* gdb/utils.c (emit_style_escape): Update.
(flush_wrap_buffer): Update.
(fputs_maybe_filtered): Update.
(fputs_unfiltered): Add function.
Change-Id: I17ed5078f71208344f2f8ab634a6518b1af6e213
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26327-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 21:11:34 2020
Return-Path: <gdb-prs-return-26327-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 31834 invoked by alias); 7 Feb 2020 21:11:34 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 31809 invoked by uid 55); 7 Feb 2020 21:11:33 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Fri, 07 Feb 2020 21:11: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: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-24915-4717-pbCDQpW3Fg@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00242.txt
Content-length: 1074
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
--- Comment #21 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5abbbe1d13e03496af5564b997f3c3a2e79b4d73
commit 5abbbe1d13e03496af5564b997f3c3a2e79b4d73
Author: Tom Tromey <tromey@adacore.com>
Date: Wed Feb 5 10:53:44 2020 +0100
Revert basenames_may_differ patch
Commit a0c1ffedc regressed certain cases coming from Eclipse.
See PR breakpoints/24915.
gdb/ChangeLog
2020-02-07 Tom Tromey <tromey@adacore.com>
PR breakpoints/24915:
* source.c (find_and_open_source): Do not check basenames_may_differ.
gdb/testsuite/ChangeLog
2020-02-07 Tom Tromey <tromey@adacore.com>
PR breakpoints/24915:
* gdb.base/annotate-symlink.exp: Use setup_xfail.
Change-Id: Iadbf42f35eb40c95ad32b2108ae25d8f199998bd
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26329-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 21:18:04 2020
Return-Path: <gdb-prs-return-26329-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 43213 invoked by alias); 7 Feb 2020 21:18:04 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 43193 invoked by uid 48); 7 Feb 2020 21:18:04 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/24915] paths for breakpoints are not resolved
Date: Fri, 07 Feb 2020 21: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: critical
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: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-24915-4717-wVwjgOezwf@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24915-4717@http.sourceware.org/bugzilla/>
References: <bug-24915-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00244.txt
Content-length: 630
https://sourceware.org/bugzilla/show_bug.cgi?id=24915
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |tromey at sourceware dot org
Resolution|--- |FIXED
--- Comment #22 from Tom Tromey <tromey at sourceware dot org> ---
Fixed. I filed a follow-up bug, see bug#25518.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26330-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 07 22:12:06 2020
Return-Path: <gdb-prs-return-26330-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 48222 invoked by alias); 7 Feb 2020 22:12:05 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 48203 invoked by uid 48); 7 Feb 2020 22:12:05 -0000
From: "atotic at chromium dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25190] annotations generated incorrectly unless "set
pagination off"
Date: Fri, 07 Feb 2020 22: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: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: atotic at chromium 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: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25190-4717-rcsgWIliEV@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25190-4717@http.sourceware.org/bugzilla/>
References: <bug-25190-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00245.txt
Content-length: 213
https://sourceware.org/bugzilla/show_bug.cgi?id=25190
--- Comment #4 from Aleks Totic <atotic at chromium dot org> ---
Thank you!
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26331-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 08 18:28:02 2020
Return-Path: <gdb-prs-return-26331-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 119900 invoked by alias); 8 Feb 2020 18:28:02 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 119844 invoked by uid 48); 8 Feb 2020 18:28:01 -0000
From: "b7.10110111 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/25520] New: Useless paging after emission of multiple New
Thread/Thread exited messages
Date: Sat, 08 Feb 2020 18:28: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: 9.1
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: <bug-25520-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00246.txt
Content-length: 5513
https://sourceware.org/bugzilla/show_bug.cgi?id=25520
Bug ID: 25520
Summary: Useless paging after emission of multiple New
Thread/Thread exited messages
Product: gdb
Version: 9.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cli
Assignee: unassigned at sourceware dot org
Reporter: b7.10110111 at gmail dot com
Target Milestone: ---
Consider the following test program:
```
#include <thread>
int main()
{
for(int i=0; i<100; ++i)
{
std::thread t([]{});
t.join();
}
}
```
If you run it in GDB 8.3.1 as `gdb -ex r ./test`, you'll get the following
output, which is fine:
```
Reading symbols from ./test...
Starting program: /tmp/test
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[New Thread 0xf7b00b40 (LWP 12044)]
[Thread 0xf7b00b40 (LWP 12044) exited]
[New Thread 0xf7b00b40 (LWP 12045)]
[Thread 0xf7b00b40 (LWP 12045) exited]
<...>
[New Thread 0xf7b00b40 (LWP 12144)]
[Thread 0xf7b00b40 (LWP 12144) exited]
[Inferior 1 (process 12039) exited normally]
```
But in GDB 9.1 the output ends in a paging request as follows (I pressed <RET>
here to proceed):
```
[Thread 0xf7b00b40 (LWP 16029) exited]
[Thread 0xf7b00b40 (LWP 16030) exited]
--Type <RET> for more, q to quit, c to continue without paging--
[Inferior 1 (process 15926) exited normally]
```
And this is after enough lines have been emitted that the first ones have
already scrolled away. Thus, not only is this paging request unexpected, but
it's also useless — doesn't page anything.
git-bisect gives the following result:
```
2a3c1174c3c0db1140180fb3fc56ac324d1c0a7c is the first bad commit
commit 2a3c1174c3c0db1140180fb3fc56ac324d1c0a7c
Author: Pedro Alves <palves@redhat.com>
Date: Wed Jun 5 09:17:16 2019 +0100
Introduce gdb-specific %p format suffixes
This introduces a few gdb-specific %p format suffixes. This is useful
for emitting gdb-specific output in an ergonomic way. It also yields
code that is more i18n-friendly.
The comment before ui_out::message explains the details.
Note that the tests had to change a little. When using one of the gdb
printf functions with styling, there can be spurious style changes
emitted to the output. This did not seem worthwhile to fix, as the
low-level output functions are rather spaghetti-ish already, and I
didn't want to make them even worse.
This change also necessitated adding support for "*" as precision and
width in format_pieces. These are used in various spots in gdb, and
it seemed better to me to implement them than to remove the uses.
gdb/ChangeLog
2019-10-01 Pedro Alves <palves@redhat.com>
Tom Tromey <tom@tromey.com>
* unittests/format_pieces-selftests.c: Add gdb_format parameter.
(test_gdb_formats): New function.
(run_tests): Call it.
(test_format_specifier): Update.
* utils.h (fputs_filtered): Update comment.
(vfprintf_styled, vfprintf_styled_no_gdbfmt)
(fputs_styled_unfiltered): Declare.
* utils.c (fputs_styled_unfiltered): New function.
(vfprintf_maybe_filtered): Add gdbfmt parameter.
(vfprintf_filtered): Update.
(vfprintf_unfiltered, vprintf_filtered): Update.
(vfprintf_styled, vfprintf_styled_no_gdbfmt): New functions.
* ui-out.h (enum ui_out_flag) <unfiltered_output,
disallow_ui_out_field>: New constants.
(enum class field_kind): New.
(struct base_field_s, struct signed_field_s): New.
(signed_field): New function.
(struct string_field_s): New.
(string_field): New function.
(struct styled_string_s): New.
(styled_string): New function.
(class ui_out) <message>: Add comment.
<vmessage, call_do_message>: New methods.
<do_message>: Add style parameter.
* ui-out.c (ui_out::call_do_message, ui_out::vmessage): New
methods.
(ui_out::message): Rewrite.
* mi/mi-out.h (class mi_ui_out) <do_message>: Add style
parameter.
* mi/mi-out.c (mi_ui_out::do_message): Add style parameter.
* gdbsupport/format.h (class format_pieces) <format_pieces>: Add
gdb_extensions parameter.
(class format_piece): Add parameter to constructor.
(n_int_args): New field.
* gdbsupport/format.c (format_pieces::format_pieces): Add
gdb_extensions parameter. Handle '*'.
* cli-out.h (class cli_ui_out) <do_message>: Add style parameter.
* cli-out.c (cli_ui_out::do_message): Add style parameter. Call
vfprintf_styled_no_gdbfmt.
(cli_ui_out::do_field_string, cli_ui_out::do_spaces)
(cli_ui_out::do_text, cli_ui_out::field_separator): Allow
unfiltered output.
* ui-style.h (struct ui_file_style) <ptr>: New method.
gdb/testsuite/ChangeLog
2019-10-01 Tom Tromey <tom@tromey.com>
* gdb.base/style.exp: Update tests.
:040000 040000 7787b903220259d836ede6df19cc72cb2c7bdd3d
ef36041a9f4c07654559dde028562157ab9a1d35 M gdb
```
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26332-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 08 18:29:20 2020
Return-Path: <gdb-prs-return-26332-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 120534 invoked by alias); 8 Feb 2020 18:29:19 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 120513 invoked by uid 48); 8 Feb 2020 18:29:19 -0000
From: "b7.10110111 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/25520] Useless paging after emission of multiple New
Thread/Thread exited messages
Date: Sat, 08 Feb 2020 18: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: 9.1
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: cc
Message-ID: <bug-25520-4717-1srqmkKh7M@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25520-4717@http.sourceware.org/bugzilla/>
References: <bug-25520-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00247.txt
Content-length: 391
https://sourceware.org/bugzilla/show_bug.cgi?id=25520
Ruslan <b7.10110111 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26333-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 10 16:18:42 2020
Return-Path: <gdb-prs-return-26333-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 45145 invoked by alias); 10 Feb 2020 16:18:42 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 45127 invoked by uid 48); 10 Feb 2020 16:18:41 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25528] New: incorrect trace for "asm volatile" statement
Date: Mon, 10 Feb 2020 16: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: critical
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25528-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00248.txt
Content-length: 2963
https://sourceware.org/bugzilla/show_bug.cgi?id=25528
Bug ID: 25528
Summary: incorrect trace for "asm volatile" statement
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
$ gdb -v
GNU gdb (GDB) 9.0.50.20191210-git
Copyright (C) 2019 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.
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d --enable-shared
--enable-threads=posix --with-system-zlib --with-isl --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch
--disable-libssp --enable-gnu-unique-object --enable-linker-build-id
--enable-lto --enable-plugin --enable-install-libiberty
--with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib
--disable-werror --enable-checking=release --enable-default-pie
--enable-default-ssp --enable-cet=auto gdc_include_dir=/usr/include/dlang/gdc
Thread model: posix
gcc version 9.2.0 (GCC)
$ cat small.c
const signed char NM[] = {-1, 0, 1};
__attribute__((noinline)) void f(short delta)
{
short p = 2, s;
for (s = 0; s < 2; s++)
{
p += delta;
if (NM[p] == 0)
asm volatile("");
}
}
void main(void) { f(-1); }
$ gcc -g small.c
$ gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) break small.c:9
Breakpoint 1 at 0x113f: file small.c, line 9.
(gdb) run
Starting program: /home/yibiao/cv-gcov/a.out
Breakpoint 1, f (delta=-1) at small.c:9
9 if (NM[p] == 0)
(gdb) step
10 asm volatile("");
(gdb) c
Continuing.
Breakpoint 1, f (delta=-1) at small.c:9
9 if (NM[p] == 0)
(gdb) step
10 asm volatile("");
(gdb) q
A debugging session is active.
Inferior 1 [process 4947] will be killed.
Quit anyway? (y or n) y
###############################################################################
### We can find that Line #10 @asm volatile("");@ is executed twice.
### However, it is obvious that Line #9 "if (NM[p] == 0)" is True in the second
for loop.
###############################################################################
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26334-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 11 06:09:16 2020
Return-Path: <gdb-prs-return-26334-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 42148 invoked by alias); 11 Feb 2020 06:09:15 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 42125 invoked by uid 55); 11 Feb 2020 06:09:14 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25488] UNRESOLVED: gdb.server/server-kill-python.exp:
ensure inferior is running
Date: Tue, 11 Feb 2020 06:09: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: 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: <bug-25488-4717-ytI2vLY52p@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25488-4717@http.sourceware.org/bugzilla/>
References: <bug-25488-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00249.txt
Content-length: 2469
https://sourceware.org/bugzilla/show_bug.cgi?id=25488
--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b2770d5e779088c62fd107a690dbfc94b4c89a88
commit b2770d5e779088c62fd107a690dbfc94b4c89a88
Author: Tom de Vries <tdevries@suse.de>
Date: Tue Feb 11 07:08:33 2020 +0100
[gdb/testsuite] Fix UNRESOLVED in gdb.server/server-kill-python.exp
The test-case gdb.server/server-kill-python.exp runs fine by itself:
...
Running src/gdb/testsuite/gdb.server/server-kill-python.exp ...
=== gdb Summary ===
nr of expected passes 3
...
But if we run f.i. gdb.server/file-transfer.exp before it, we get instead:
...
Running src/gdb/testsuite/gdb.server/server-kill-python.exp ...
ERROR: GDB process no longer exists
=== gdb Summary ===
nr of expected passes 13
nr of unresolved testcases 1
...
We can see the origin of the problem here:
...
spawn gdbserver --once localhost:2347 \
build/gdb/testsuite/outputs/gdb.server/file-transfer/file-transfer \
build/gdb/testsuite/outputs/gdb.server/server-kill-python/server-kill-python^M
Process build/gdb/testsuite/outputs/gdb.server/file-transfer/file-transfer
\ created; pid = 9464^M
Listening on port 2347^M
...
The spawn of the gdbserver for the server-kill-python test-case gets as
executable argument the file-transfer binary.
This is caused by proc gdbserver_spawn attempting to load the exec file in
$file_last_loaded. This is something that is meant to load the same exec
in
the gdbserver that was earlier loaded into gdb.
In this test-case however, nothing has been loaded into gdb by the
test-case,
and consequently we load the file that was loaded into gdb in the previous
test-case.
Fix this by unsetting $file_last_loaded in gdb_init.
Build and reg-tested on x86_64-linux.
gdb/testsuite/ChangeLog:
2020-02-11 Tom de Vries <tdevries@suse.de>
PR testsuite/25488
* lib/gdb.exp (gdb_init): Unset $file_last_loaded.
Change-Id: Ic385e08cbd34cbf85518720cf5695b4ff6619f4b
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26335-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 11 06:10:38 2020
Return-Path: <gdb-prs-return-26335-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 43027 invoked by alias); 11 Feb 2020 06:10:38 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 43003 invoked by uid 48); 11 Feb 2020 06:10:37 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25488] UNRESOLVED: gdb.server/server-kill-python.exp:
ensure inferior is running
Date: Tue, 11 Feb 2020 06:10: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: vries 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: <bug-25488-4717-WpdMCFaAB3@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25488-4717@http.sourceware.org/bugzilla/>
References: <bug-25488-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00250.txt
Content-length: 548
https://sourceware.org/bugzilla/show_bug.cgi?id=25488
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
Testsuite patch committed, marking resolved-fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26336-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 11 07:14:52 2020
Return-Path: <gdb-prs-return-26336-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 127620 invoked by alias); 11 Feb 2020 07:14:52 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 127597 invoked by uid 48); 11 Feb 2020 07:14:50 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25471] gdb hangs repeating "Couldn't get registers: No such
process" warning after external SIGKILL
Date: Tue, 11 Feb 2020 07: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: vries 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: <bug-25471-4717-M8u9ARQtTg@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25471-4717@http.sourceware.org/bugzilla/>
References: <bug-25471-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00251.txt
Content-length: 405
https://sourceware.org/bugzilla/show_bug.cgi?id=25471
--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
I reproduced the same problem on top of
https://github.com/barisaktemur/gdb/commits/thread-exit-in-stop-all-threads-v4
( submitted here: https://sourceware.org/ml/gdb-patches/2020-02/msg00152.html
).
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26337-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 11 16:37:10 2020
Return-Path: <gdb-prs-return-26337-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 92239 invoked by alias); 11 Feb 2020 16:37:10 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 92170 invoked by uid 55); 11 Feb 2020 16:37:09 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25126] GDB uses the staled (cached?) source file
Date: Tue, 11 Feb 2020 16:37: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: 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: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25126-4717-B4AMCUDzTf@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25126-4717@http.sourceware.org/bugzilla/>
References: <bug-25126-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00252.txt
Content-length: 1574
https://sourceware.org/bugzilla/show_bug.cgi?id=25126
--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Sergio Durigan Junior
<sergiodj@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f6be87130b5b327075a09c05e78532816f186995
commit f6be87130b5b327075a09c05e78532816f186995
Author: Sergio Durigan Junior <sergiodj@redhat.com>
Date: Thu Feb 6 17:52:54 2020 -0500
New testcase for PR tui/25126 (staled source cache)
I'm dealing with a Fedora GDB bug that is related to PR tui/25126, and
I thought I'd write a specific testcase for it because I couldn't find
one.
The idea is to get the simple reproducer from the bug and tweak the
testcase around it. This one was a bit hard because, since we need to
modify the source file and recompile it, it involved a bit of TCL-foo
to do things. Also for this reason, I'm only enabling the test for
native boards.
I tested this with an upstream GDB and made sure everything is
passing. I also tested with a faulty GDB and made sure the test
failed.
gdb/testsuite/ChangeLog:
2020-02-11 Sergio Durigan Junior <sergiodj@redhat.com>
PR tui/25126
https://bugzilla.redhat.com/show_bug.cgi?id=1784210
* gdb.base/cached-source-file.c: New file.
* gdb.base/cached-source-file.exp: New file.
Change-Id: Ib1b074342ebe8613c6d1dfde631691ebdf6d81c6
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26338-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 11 19:31:07 2020
Return-Path: <gdb-prs-return-26338-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 117990 invoked by alias); 11 Feb 2020 19:31:07 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 117968 invoked by uid 48); 11 Feb 2020 19:31:06 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25534] New: [cc-with-dwz] FAIL: gdb.cp/m-static.exp: static
const int initialized elsewhere
Date: Tue, 11 Feb 2020 19:31: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: vries 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: <bug-25534-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00253.txt
Content-length: 1167
https://sourceware.org/bugzilla/show_bug.cgi?id=25534
Bug ID: 25534
Summary: [cc-with-dwz] FAIL: gdb.cp/m-static.exp: static const
int initialized elsewhere
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
I see on master with board cc-with-dwz:
...
FAIL: gdb.cp/m-static.exp: static const int initialized elsewhere
FAIL: gdb.cp/m-static.exp: info variable everywhere
...
First FAIL in more detail:
...
(gdb) PASS: gdb.cp/m-static.exp: template object, static derived enum
print test4.elsewhere^M
$18 = <optimized out>^M
(gdb) FAIL: gdb.cp/m-static.exp: static const int initialized elsewhere
...
while normally we have instead:
...
(gdb) PASS: gdb.cp/m-static.exp: template object, static derived enum
print test4.elsewhere^M
$18 = 221^M
(gdb) PASS: gdb.cp/m-static.exp: static const int initialized elsewhere
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26339-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 11 19:32:49 2020
Return-Path: <gdb-prs-return-26339-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 119927 invoked by alias); 11 Feb 2020 19:32:48 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 119908 invoked by uid 48); 11 Feb 2020 19:32:48 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25534] [cc-with-dwz] FAIL: gdb.cp/m-static.exp: static
const int initialized elsewhere
Date: Tue, 11 Feb 2020 19: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: vries 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: <bug-25534-4717-EQNd8TbnLI@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25534-4717@http.sourceware.org/bugzilla/>
References: <bug-25534-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00254.txt
Content-length: 1664
https://sourceware.org/bugzilla/show_bug.cgi?id=25534
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Regression by commit 0494dbecdf "Consolidate partial symtab dependency
reading".
commit 0494dbecdfa0b0b9065393755a1ac64431997da1
Author: Tom Tromey <tom@tromey.com>
Date: Wed Oct 23 09:46:25 2019 -0600
Consolidate partial symtab dependency reading
Most of the symbol readers have code to iterate over a partial symtabs
dependencies, expanding each one and optionally printing a message.
Now that the "second-stage" psymtab expansion is available as a
method, these implementations can all be merged.
This patch also changes a couple more warnings into assertions.
gdb/ChangeLog
2020-01-26 Tom Tromey <tom@tromey.com>
* xcoffread.c (xcoff_psymtab_to_symtab_1): Call
read_dependencies. Add assert.
* psymtab.c (partial_symtab::read_dependencies): New method.
* psympriv.h (struct partial_symtab) <read_dependencies>: New
method.
* mdebugread.c (psymtab_to_symtab_1): Call read_dependencies.
* dwarf2read.c (dwarf2_psymtab::expand_psymtab): Call
read_dependencies.
* dbxread.c (dbx_psymtab_to_symtab_1): Call read_dependencies.
Add assert.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26340-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 12 00:35:13 2020
Return-Path: <gdb-prs-return-26340-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 10221 invoked by alias); 12 Feb 2020 00:35:12 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 10201 invoked by uid 48); 12 Feb 2020 00:35:12 -0000
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug rust/25535] New: Wrong field looked up for variant
discriminator
Date: Wed, 12 Feb 2020 00:35: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: 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: <bug-25535-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00255.txt
Content-length: 878
https://sourceware.org/bugzilla/show_bug.cgi?id=25535
Bug ID: 25535
Summary: Wrong field looked up for variant discriminator
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: rust
Assignee: unassigned at sourceware dot org
Reporter: dje at google dot com
Target Milestone: ---
Enums at non-zero offsets in a struct are printed wrong because the address of
the discriminator field is looked up wrong. Simple oversight of not applying
embedded_offset.
Patch to follow.
Testcase:
#[derive(Debug)]
struct S {
a: Option<u8>,
b: Option<u8>,
}
fn main() {
let s = S { a: Some(1), b: None };
println!("{:?}", s); // set breakpoint here
}
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26341-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 12 01:00:48 2020
Return-Path: <gdb-prs-return-26341-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 36483 invoked by alias); 12 Feb 2020 01:00:47 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 36380 invoked by uid 48); 12 Feb 2020 01:00:43 -0000
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug rust/25535] Wrong field looked up for variant discriminator
Date: Wed, 12 Feb 2020 01:00: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: dje at google dot com
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: assigned_to
Message-ID: <bug-25535-4717-130y9RTgf2@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25535-4717@http.sourceware.org/bugzilla/>
References: <bug-25535-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00256.txt
Content-length: 381
https://sourceware.org/bugzilla/show_bug.cgi?id=25535
dje at google dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at sourceware dot org |dje at google dot com
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26342-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 12 01:04:31 2020
Return-Path: <gdb-prs-return-26342-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 44289 invoked by alias); 12 Feb 2020 01:04:31 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 44267 invoked by uid 48); 12 Feb 2020 01:04:30 -0000
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug rust/25535] Wrong field looked up for variant discriminator
Date: Wed, 12 Feb 2020 01: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: 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: dje at google dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25535-4717-vifGD6zSky@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25535-4717@http.sourceware.org/bugzilla/>
References: <bug-25535-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00257.txt
Content-length: 398
https://sourceware.org/bugzilla/show_bug.cgi?id=25535
--- Comment #1 from dje at google dot com ---
... and incorrect gdb output ...
(gdb) p s
$1 = simple::EnumWithNonzeroOffset {a: core::option::Option<u8>::Some(1), b:
core::option::Option<u8>::Some(0)}
Note that the variant of "a" has been applied to "b".
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26343-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 12 04:43:16 2020
Return-Path: <gdb-prs-return-26343-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 71562 invoked by alias); 12 Feb 2020 04:43:15 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 71450 invoked by uid 48); 12 Feb 2020 04:43:15 -0000
From: "chrisj at rtems dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/25536] New: rtems-bfin fails to build the simulator on
FreeBSD
Date: Wed, 12 Feb 2020 04:43: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: 9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
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 cc target_milestone
Message-ID: <bug-25536-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00258.txt
Content-length: 4813
https://sourceware.org/bugzilla/show_bug.cgi?id=25536
Bug ID: 25536
Summary: rtems-bfin fails to build the simulator on FreeBSD
Product: gdb
Version: 9.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: sim
Assignee: unassigned at sourceware dot org
Reporter: chrisj at rtems dot org
CC: vapier at gentoo dot org
Target Milestone: ---
gdb-9.1 fails to build for bfin and gdb-8.3 did build A brief summary follows
and a more complete log can be found here ..
https://lists.rtems.org/pipermail/build/2020-February/010217.html
/usr/bin/cc -O2 -pipe -fbracket-depth=1024
-I/build/rtems/tools/rtems-source-builder.git/rtems/build/tmp/sb-500/5/rtems-bfin/build/rtems/tools/5/include
-DHAVE_CONFIG_H -DWITH_DEFAULT_MODEL='"bf537"'
-DWITH_DEFAULT_ALIGNMENT=STRICT_ALIGNMENT
-DWITH_TARGET_BYTE_ORDER=BFD_ENDIAN_LITTLE -DWITH_HW=1 -DDEFAULT_INLINE=0
-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 -I/usr/local/include/SDL -I/usr/local/include
-D_REENTRANT -D_THREAD_SAFE -DHAVE_SDL -I. -I../../../gdb-9.1/sim/bfin
-I../common -I../../../gdb-9.1/sim/bfin/../common -I../../include
-I../../../gdb-9.1/sim/bfin/../../include -I../../bfd
-I../../../gdb-9.1/sim/bfin/../../bfd -I../../opcodes
-I../../../gdb-9.1/sim/bfin/../../opcodes -c -o sim-reason.o -MT sim-re!
ason.o -MMD -MP -MF .deps/sim-reason.Tpo
../../../gdb-9.1/sim/bfin/../common/sim-reason.c
../../../gdb-9.1/sim/bfin/../common/sim-io.c:299:5: warning: implicitly
declaring library function 'abort' with type 'void (void)
__attribute__((noreturn))' [-Wimplicit-function-declaration]
abort ();
^
../../../gdb-9.1/sim/bfin/../common/sim-io.c:299:5: note: include the header
<stdlib.h> or explicitly provide a declaration for 'abort'
../../../gdb-9.1/sim/bfin/../common/sim-load.c:104:30: error: too few arguments
provided to function-like macro invocation
size = bfd_section_size (s);
^
/usr/local/include/bfd.h:317:9: note: macro 'bfd_section_size' defined here
warning#define bfd_section_size(bfd, ptr) ((ptr)->size)
^
: unknown warning option '-Wmissing-parameter-type' [-Wunknown-warning-option]
warning: unknown warning option '-Wmissing-parameter-type'
[-Wunknown-warning-option]
warning: unknown warning option '-Wold-style-declaration'; did you mean
'-Wout-of-line-declaration'? [-Wunknown-warning-option]
warning: unknown warning option '-Wold-style-declaration'; did you mean
'-Wout-of-line-declaration'? [-Wunknown-warning-option]
../../../gdb-9.1/sim/bfin/../common/sim-load.c:104:11: error: use of undeclared
identifier 'bfd_section_size'
size = bfd_section_size (s);
^
../../../gdb-9.1/sim/bfin/../common/sim-load.c:122:27: error: too few arguments
provided to function-like macro invocation
lma = bfd_section_lma (s);
^
/usr/local/include/bfd.h:320:9: note: macro 'bfd_section_lma' defined here
#define bfd_section_lma(bfd, ptr) ((ptr)->lma)
^
../../../gdb-9.1/sim/bfin/../common/sim-load.c:122:9: error: use of undeclared
identifier 'bfd_section_lma'
lma = bfd_section_lma (s);
^
../../../gdb-9.1/sim/bfin/../common/sim-load.c:124:27: error: too few arguments
provided to function-like macro invocation
lma = bfd_section_vma (s);
^
/usr/local/include/bfd.h:319:9: note: macro 'bfd_section_vma' defined here
#define bfd_section_vma(bfd, ptr) ((ptr)->vma)
^
../../../gdb-9.1/sim/bfin/../common/sim-load.c:124:9: error: use of undeclared
identifier 'bfd_section_vma'
lma = bfd_section_vma (s);
^
../../../gdb-9.1/sim/bfin/../common/sim-load.c:128:26: error: too few arguments
provided to function-like macro invocation
bfd_section_name (s),
^
/usr/local/include/bfd.h:316:9: note: macro 'bfd_section_name' defined here
#define bfd_section_name(bfd, ptr) ((ptr)->name)
^
2 warnings generated.
../../../gdb-9.1/sim/bfin/../common/sim-load.c:128:7: error: use of undeclared
identifier 'bfd_section_name'
bfd_section_name (s),
^
2 warnings generated.
2 warnings and 8 errors generated.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26344-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 12 05:02:54 2020
Return-Path: <gdb-prs-return-26344-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 60837 invoked by alias); 12 Feb 2020 05:02:53 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 60817 invoked by uid 48); 12 Feb 2020 05:02:53 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25534] [cc-with-dwz] FAIL: gdb.cp/m-static.exp: static
const int initialized elsewhere
Date: Wed, 12 Feb 2020 05: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc target_milestone
Message-ID: <bug-25534-4717-Q6AhQn24LR@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25534-4717@http.sourceware.org/bugzilla/>
References: <bug-25534-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00259.txt
Content-length: 704
https://sourceware.org/bugzilla/show_bug.cgi?id=25534
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simark at simark dot ca
Target Milestone|--- |10.1
--- Comment #2 from Simon Marchi <simark at simark dot ca> ---
If I understand correctly, this commit in not present in GDB 9, so it means the
bug is not in GDB 9? I will therefore put the target milestone to 10.1, we'll
want to fix that before GDB 10.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26345-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 12 07:14:21 2020
Return-Path: <gdb-prs-return-26345-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 15658 invoked by alias); 12 Feb 2020 07:14:21 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 15636 invoked by uid 48); 12 Feb 2020 07:14:20 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25534] [cc-with-dwz] FAIL: gdb.cp/m-static.exp: static
const int initialized elsewhere
Date: Wed, 12 Feb 2020 07: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: vries 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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25534-4717-q8sOfDYXCy@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25534-4717@http.sourceware.org/bugzilla/>
References: <bug-25534-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00260.txt
Content-length: 457
https://sourceware.org/bugzilla/show_bug.cgi?id=25534
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Simon Marchi from comment #2)
> If I understand correctly, this commit in not present in GDB 9, so it means
> the bug is not in GDB 9?
Yes.
> I will therefore put the target milestone to 10.1,
> we'll want to fix that before GDB 10.
Ack.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26346-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 12 08:58:50 2020
Return-Path: <gdb-prs-return-26346-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 62021 invoked by alias); 12 Feb 2020 08:58:50 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 62000 invoked by uid 48); 12 Feb 2020 08:58:49 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25534] [cc-with-dwz] FAIL: gdb.cp/m-static.exp: static
const int initialized elsewhere
Date: Wed, 12 Feb 2020 08: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: vries 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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25534-4717-jFDazqluZZ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25534-4717@http.sourceware.org/bugzilla/>
References: <bug-25534-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00261.txt
Content-length: 4552
https://sourceware.org/bugzilla/show_bug.cgi?id=25534
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
Difference before and after offending commit using cc-with-dwz board:
...
$ diff -U 0 ref-dwz/gdb.sum gdb.sum | grep -v @@
--- ref-dwz/gdb.sum 2020-02-12 08:43:21.261947714 +0100
+++ gdb.sum 2020-02-12 09:55:25.113550063 +0100
-PASS: gdb.ada/arr_acc_idx_w_gap.exp: print indexed_by_enum(lit2..lit4)
+FAIL: gdb.ada/arr_acc_idx_w_gap.exp: print indexed_by_enum(lit2..lit4)
-PASS: gdb.ada/array_char_idx.exp: Display my_table
+FAIL: gdb.ada/array_char_idx.exp: Display my_table
-PASS: gdb.ada/array_return.exp: value printed by finish of Create_Small
+FAIL: gdb.ada/array_return.exp: value printed by finish of Create_Small
-PASS: gdb.ada/array_return.exp: value printed by finish of Create_Large
+FAIL: gdb.ada/array_return.exp: value printed by finish of Create_Large
-PASS: gdb.ada/array_return.exp: value printed by finish of
Create_Small_Float_Vector
+FAIL: gdb.ada/array_return.exp: value printed by finish of
Create_Small_Float_Vector
-PASS: gdb.ada/funcall_char.exp: print f('A')
+FAIL: gdb.ada/funcall_char.exp: print f('A')
-PASS: gdb.ada/iwide.exp: print s_access.all
-PASS: gdb.ada/iwide.exp: print sp_access.all
+FAIL: gdb.ada/iwide.exp: print s_access.all
+FAIL: gdb.ada/iwide.exp: print sp_access.all
-PASS: gdb.ada/ptype_field.exp: ptype circle
-PASS: gdb.ada/ptype_field.exp: ptype circle.pos
-PASS: gdb.ada/ptype_field.exp: ptype circle.pos.x
+FAIL: gdb.ada/ptype_field.exp: ptype circle
+FAIL: gdb.ada/ptype_field.exp: ptype circle.pos
+FAIL: gdb.ada/ptype_field.exp: ptype circle.pos.x
-PASS: gdb.ada/rec_return.exp: print bar
+FAIL: gdb.ada/rec_return.exp: print bar
-PASS: gdb.ada/tagged_access.exp: ptype c.all
-PASS: gdb.ada/tagged_access.exp: ptype c.menu_name
+FAIL: gdb.ada/tagged_access.exp: ptype c.all
+FAIL: gdb.ada/tagged_access.exp: ptype c.menu_name
-PASS: gdb.ada/var_arr_typedef.exp: print va
-PASS: gdb.ada/var_arr_typedef.exp: print vb
-PASS: gdb.ada/var_arr_typedef.exp: print a
+FAIL: gdb.ada/var_arr_typedef.exp: print va
+FAIL: gdb.ada/var_arr_typedef.exp: print vb
+FAIL: gdb.ada/var_arr_typedef.exp: print a
-PASS: gdb.ada/var_rec_arr.exp: print a1
+FAIL: gdb.ada/var_rec_arr.exp: print a1
-PASS: gdb.ada/var_rec_arr.exp: print a1(2)
-PASS: gdb.ada/var_rec_arr.exp: print a1(3)
-PASS: gdb.ada/var_rec_arr.exp: print a2
-PASS: gdb.ada/var_rec_arr.exp: print a2(1)
-PASS: gdb.ada/var_rec_arr.exp: print a2(2)
+FAIL: gdb.ada/var_rec_arr.exp: print a1(2)
+FAIL: gdb.ada/var_rec_arr.exp: print a1(3)
+FAIL: gdb.ada/var_rec_arr.exp: print a2
+FAIL: gdb.ada/var_rec_arr.exp: print a2(1)
+FAIL: gdb.ada/var_rec_arr.exp: print a2(2)
-PASS: gdb.cp/m-static.exp: static const int initialized elsewhere
+FAIL: gdb.cp/m-static.exp: static const int initialized elsewhere
-PASS: gdb.cp/m-static.exp: info variable everywhere
+FAIL: gdb.cp/m-static.exp: info variable everywhere
-PASS: gdb.cp/ovsrch.exp: break A::outer::foo (char*) const if
(A::outer::func ())
-PASS: gdb.cp/ovsrch.exp: break 'A::outer::foo (char*) const' if
(A::outer::func ())
+FAIL: gdb.cp/ovsrch.exp: break A::outer::foo (char*) const if
(A::outer::func ())
+FAIL: gdb.cp/ovsrch.exp: break 'A::outer::foo (char*) const' if
(A::outer::func ())
-PASS: gdb.cp/ovsrch.exp: break A::outer::foo (int) const if (A::outer::func
())
-PASS: gdb.cp/ovsrch.exp: break 'A::outer::foo (int) const' if
(A::outer::func ())
+FAIL: gdb.cp/ovsrch.exp: break A::outer::foo (int) const if (A::outer::func
())
+FAIL: gdb.cp/ovsrch.exp: break 'A::outer::foo (int) const' if
(A::outer::func ())
-PASS: gdb.cp/ovsrch.exp: break A::B::inner::foo (char*) const if
(A::outer::func ())
-PASS: gdb.cp/ovsrch.exp: break 'A::B::inner::foo (char*) const' if
(A::outer::func ())
+FAIL: gdb.cp/ovsrch.exp: break A::B::inner::foo (char*) const if
(A::outer::func ())
+FAIL: gdb.cp/ovsrch.exp: break 'A::B::inner::foo (char*) const' if
(A::outer::func ())
-PASS: gdb.cp/ovsrch.exp: break A::B::inner::foo (int) const if
(A::outer::func ())
-PASS: gdb.cp/ovsrch.exp: break 'A::B::inner::foo (int) const' if
(A::outer::func ())
+FAIL: gdb.cp/ovsrch.exp: break A::B::inner::foo (int) const if
(A::outer::func ())
+FAIL: gdb.cp/ovsrch.exp: break 'A::B::inner::foo (int) const' if
(A::outer::func ())
-# of expected passes 77894
-# of unexpected failures 14
+# of expected passes 77861
+# of unexpected failures 47
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26347-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 12 09:28:27 2020
Return-Path: <gdb-prs-return-26347-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 90614 invoked by alias); 12 Feb 2020 09:28:26 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 90586 invoked by uid 48); 12 Feb 2020 09:28:26 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25534] [cc-with-dwz] FAIL: gdb.cp/m-static.exp: static
const int initialized elsewhere
Date: Wed, 12 Feb 2020 09: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: vries 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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25534-4717-8IeuOgWG2X@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25534-4717@http.sourceware.org/bugzilla/>
References: <bug-25534-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00262.txt
Content-length: 1152
https://sourceware.org/bugzilla/show_bug.cgi?id=25534
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #4)
> Difference before and after offending commit using cc-with-dwz board:
> ...
> $ diff -U 0 ref-dwz/gdb.sum gdb.sum | grep -v @@
> -# of expected passes 77894
> -# of unexpected failures 14
> +# of expected passes 77861
> +# of unexpected failures 47
> ...
Unexpected failures 14 -> 47.
Likewise, for cc-with-dwz-m board:
...
$ diff -U 0 ref-dwz-m/gdb.sum gdb.sum | grep -v @@
-# of expected passes 77389
-# of unexpected failures 31
-# of unexpected successes 3
-# of expected failures 128
-# of unknown successes 3
-# of known failures 71
-# of unresolved testcases 1
+# of expected passes 73779
+# of unexpected failures 2960
+# of unexpected successes 4
+# of expected failures 119
+# of known failures 74
+# of unresolved testcases 5
...
Unexpected failures 31 -> 2960.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26348-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 12 13:55:46 2020
Return-Path: <gdb-prs-return-26348-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 96898 invoked by alias); 12 Feb 2020 13:55:45 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 96876 invoked by uid 48); 12 Feb 2020 13:55:45 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25534] [cc-with-dwz] FAIL: gdb.cp/m-static.exp: static
const int initialized elsewhere
Date: Wed, 12 Feb 2020 13: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: vries 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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25534-4717-q1z5V19p3D@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25534-4717@http.sourceware.org/bugzilla/>
References: <bug-25534-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00263.txt
Content-length: 2484
https://sourceware.org/bugzilla/show_bug.cgi?id=25534
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
The difference in behaviour seems to come from dropping the
dependencies[i]->user == NULL test.
Using this patch, we reintroduce it and get the test passing again:
...
diff --git a/gdb/dwarf2read.c b/gdb/dwarf2read.c
index dafe01d94a..c90af761e7 100644
--- a/gdb/dwarf2read.c
+++ b/gdb/dwarf2read.c
@@ -9657,6 +9657,31 @@ process_queue (struct dwarf2_per_objfile
*dwarf2_per_objfile)
}
}
+void
+dwarf2_psymtab::read_dependencies (struct objfile *objfile)
+{
+ int i;
+
+ for (i = 0; i < number_of_dependencies; i++)
+ if (!dependencies[i]->readin
+ && dependencies[i]->user == NULL)
+ {
+ /* Inform about additional files that need to be read in. */
+ if (info_verbose)
+ {
+ /* FIXME: i18n: Need to make this a single string. */
+ fputs_filtered (" ", gdb_stdout);
+ wrap_here ("");
+ fputs_filtered ("and ", gdb_stdout);
+ wrap_here ("");
+ printf_filtered ("%s...", dependencies[i]->filename);
+ wrap_here (""); /* Flush output. */
+ gdb_flush (gdb_stdout);
+ }
+ dependencies[i]->expand_psymtab (objfile);
+ }
+}
+
/* Read in full symbols for PST, and anything it depends on. */
void
diff --git a/gdb/dwarf2read.h b/gdb/dwarf2read.h
index c5b69020d5..f06faf744c 100644
--- a/gdb/dwarf2read.h
+++ b/gdb/dwarf2read.h
@@ -286,6 +286,7 @@ struct dwarf2_psymtab : public partial_symtab
void read_symtab (struct objfile *) override;
void expand_psymtab (struct objfile *) override;
+ void read_dependencies (struct objfile *objfile) override;
struct dwarf2_per_cu_data *per_cu_data;
};
diff --git a/gdb/psympriv.h b/gdb/psympriv.h
index e4b23301e9..e9ed0d9df8 100644
--- a/gdb/psympriv.h
+++ b/gdb/psympriv.h
@@ -135,7 +135,7 @@ struct partial_symtab
virtual void expand_psymtab (struct objfile *) = 0;
/* Ensure that all the dependencies are read in. */
- void read_dependencies (struct objfile *);
+ virtual void read_dependencies (struct objfile *);
/* Return the raw low text address of this partial_symtab. */
CORE_ADDR raw_text_low () const
...
Tom, was the dropping of the dependencies[i]->user == NULL test intentional?
Is this patch the right way to fix this?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26349-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 12 15:57:11 2020
Return-Path: <gdb-prs-return-26349-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 20956 invoked by alias); 12 Feb 2020 15:57:11 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 20933 invoked by uid 48); 12 Feb 2020 15:57:10 -0000
From: "jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/25518] gdb annotations print real path
Date: Wed, 12 Feb 2020 15:57: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: jonah at kichwacoders 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: <bug-25518-4717-PIlG7Xe9eg@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25518-4717@http.sourceware.org/bugzilla/>
References: <bug-25518-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00264.txt
Content-length: 405
https://sourceware.org/bugzilla/show_bug.cgi?id=25518
Jonah Graham <jonah at kichwacoders dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jonah at kichwacoders dot com
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26350-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 12 16:12:29 2020
Return-Path: <gdb-prs-return-26350-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 79259 invoked by alias); 12 Feb 2020 16:12:29 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 79228 invoked by uid 48); 12 Feb 2020 16:12:28 -0000
From: "jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/25518] gdb annotations print real path
Date: Wed, 12 Feb 2020 16: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: normal
X-Bugzilla-Who: jonah at kichwacoders 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: <bug-25518-4717-cHqG4LmdLY@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25518-4717@http.sourceware.org/bugzilla/>
References: <bug-25518-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00265.txt
Content-length: 554
https://sourceware.org/bugzilla/show_bug.cgi?id=25518
--- Comment #1 from Jonah Graham <jonah at kichwacoders dot com> ---
Thank you Tom for resolving the issue in Bug#24915 before the 9.1 release.
When this problem is revisited, I created a testcase that reproduces the
regression in https://sourceware.org/ml/gdb-patches/2019-08/msg00421.html
However, that only handled case of a single file - there is another case that
could use a test Bug 24915 Comment 17.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26351-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 12 23:17:01 2020
Return-Path: <gdb-prs-return-26351-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 90748 invoked by alias); 12 Feb 2020 23:17:00 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 90727 invoked by uid 48); 12 Feb 2020 23:17:00 -0000
From: "cbiesinger at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/25538] New: armbsd_supply_fpregset is likely
incorrect (affects only OpenBSD)
Date: Wed, 12 Feb 2020 23:17: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger 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: <bug-25538-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00266.txt
Content-length: 1350
https://sourceware.org/bugzilla/show_bug.cgi?id=25538
Bug ID: 25538
Summary: armbsd_supply_fpregset is likely incorrect (affects
only OpenBSD)
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: corefiles
Assignee: unassigned at sourceware dot org
Reporter: cbiesinger at google dot com
Target Milestone: ---
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=gdb/arm-bsd-tdep.c;h=8cef77297bba2a28385b9647e44ac7f3768d60ca;hb=3d4560f707b077adfb54759df5efbd96301ca2d8
In practice, that file is only used for reading core files, and only OpenBSD
code uses it (see the call in arm-obsd-tdep.c to
set_gdbarch_iterate_over_regset_sections(gdbarch,
armbsd_iterate_over_regset_sections))
However, armbsd_supply_fpregset assumes a register layout that no longer
matches OpenBSD's arm/reg.h:
https://github.com/openbsd/src/blob/master/sys/arch/arm/include/reg.h
This was changed here:
https://github.com/openbsd/src/commit/43d76721fe6630a7386645f5ff3b6efa2499fa13
Apparently (?) OpenBSD ships with a very old GDB which they locally patched, so
it may not affect the GDB they ship.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26352-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 12 23:20:24 2020
Return-Path: <gdb-prs-return-26352-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 99556 invoked by alias); 12 Feb 2020 23:20:23 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 99538 invoked by uid 48); 12 Feb 2020 23:20:23 -0000
From: "cbiesinger at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/25538] armbsd_supply_fpregset is likely incorrect
(affects only OpenBSD)
Date: Wed, 12 Feb 2020 23:20: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger 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: <bug-25538-4717-vI1VPYeUQg@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25538-4717@http.sourceware.org/bugzilla/>
References: <bug-25538-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00267.txt
Content-length: 477
https://sourceware.org/bugzilla/show_bug.cgi?id=25538
--- Comment #1 from Christian Biesinger <cbiesinger at google dot com> ---
This code should probably also move to an OpenBSD file. FreeBSD has its own
code in arm-fbsd-tdep.c (using regcache_map_entry), and NetBSD has a different
struct layout from the other BSDs
(https://github.com/NetBSD/src/blob/trunk/sys/arch/arm/include/reg.h#L47)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26353-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 13 08:46:53 2020
Return-Path: <gdb-prs-return-26353-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 121208 invoked by alias); 13 Feb 2020 08:46:52 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 121190 invoked by uid 48); 13 Feb 2020 08:46:52 -0000
From: "marxin.liska at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25542] New: Crash in TUI mode
Date: Thu, 13 Feb 2020 08: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin.liska 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: <bug-25542-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00268.txt
Content-length: 4819
https://sourceware.org/bugzilla/show_bug.cgi?id=25542
Bug ID: 25542
Summary: Crash in TUI mode
Product: gdb
Version: 8.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tui
Assignee: unassigned at sourceware dot org
Reporter: marxin.liska at gmail dot com
Target Milestone: ---
Created attachment 12293
--> https://sourceware.org/bugzilla/attachment.cgi?id=12293&action=edit
gdb crash
I see the following crash:
$ gdb ./openblas_utest -x cmds.txt
...
malloc_consolidate(): invalid chunk size
Aborted (core dumped)
When I attach gdb to the crashing gdb I see the following backtrace:
Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 return ret;
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x00007ffff7dcb55d in __GI_abort () at abort.c:79
#2 0x00007ffff7e2533f in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x7ffff7f33f49 "%s\n")
at ../sysdeps/posix/libc_fatal.c:181
#3 0x00007ffff7e2c7dc in malloc_printerr (str=str@entry=0x7ffff7f35828
"malloc_consolidate(): invalid chunk size") at malloc.c:5332
#4 0x00007ffff7e2d1d8 in malloc_consolidate (av=av@entry=0x7ffff7f669e0
<main_arena>) at malloc.c:4477
#5 0x00007ffff7e2f323 in _int_malloc (av=av@entry=0x7ffff7f669e0 <main_arena>,
bytes=bytes@entry=4064) at malloc.c:3699
#6 0x00007ffff7e30e94 in __GI___libc_malloc (bytes=bytes@entry=4064) at
malloc.c:3058
#7 0x0000555555af8205 in xmalloc (size=4064) at
../../gdb/common/common-utils.c:44
#8 0x00005555556f6157 in _obstack_begin_worker (h=0x555556031cc0
<frame_cache_obstack>, size=<optimized out>,
alignment=<optimized out>) at ../../libiberty/obstack.c:141
#9 0x0000555555a6e517 in reinit_frame_cache () at ../../gdb/frame.c:1829
#10 0x000055555594a64b in registers_changed () at ../../gdb/regcache.c:456
#11 0x000055555589e4f0 in generic_mourn_inferior () at ../../gdb/target.c:3185
#12 0x0000555555a309cf in inf_child_target::mourn_inferior (this=0x555556007af8
<_ZL26the_amd64_linux_nat_target.lto_priv.0>)
at ../../gdb/inf-child.c:200
#13 inf_ptrace_target::mourn_inferior (this=0x555556007af8
<_ZL26the_amd64_linux_nat_target.lto_priv.0>) at ../../gdb/inf-ptrace.c:179
#14 0x00005555559ffd55 in linux_nat_target::mourn_inferior (this=0x555556007af8
<_ZL26the_amd64_linux_nat_target.lto_priv.0>)
at ../../gdb/linux-nat.c:3799
#15 0x000055555589e9c8 in target_mourn_inferior (ptid=...) at
../../gdb/target.h:1295
#16 target_mourn_inferior (ptid=...) at ../../gdb/target.c:2168
#17 0x0000555555a0007a in linux_nat_target::kill (this=<optimized out>) at
../../gdb/linux-nat.c:3787
#18 0x0000555555a33e0b in kill_if_already_running (from_tty=1) at
../../gdb/infcmd.c:521
#19 run_command_1 (args=0x0, from_tty=1, run_how=RUN_NORMAL) at
../../gdb/infcmd.c:572
#20 0x0000555555b0ff42 in cmd_func (cmd=<optimized out>, args=<optimized out>,
from_tty=<optimized out>)
at ../../gdb/cli/cli-decode.c:1892
#21 0x000055555587e898 in execute_command (p=<optimized out>, from_tty=1) at
../../gdb/top.c:626
#22 0x0000555555a7b46d in command_handler (command=0x555556059010 "") at
../../gdb/event-top.c:586
#23 0x0000555555a7b50d in command_line_handler (rl=...) at
../../gdb/event-top.c:773
#24 0x0000555555a74c76 in gdb_rl_callback_handler (rl=0x555556a614c0 "r") at
/usr/include/c++/9/bits/unique_ptr.h:153
#25 0x00007ffff7d791be in rl_callback_read_char () from /lib64/libreadline.so.8
#26 0x0000555555a74d5b in gdb_rl_callback_read_char_wrapper_noexcept () at
../../gdb/event-top.c:176
#27 0x0000555555a74e39 in gdb_rl_callback_read_char_wrapper
(client_data=<optimized out>) at ../../gdb/event-top.c:192
#28 0x0000555555a7b3c0 in stdin_event_handler (error=<optimized out>,
client_data=0x5555560601f0) at ../../gdb/event-top.c:514
#29 0x0000555555a75056 in gdb_wait_for_event (block=1) at
../../gdb/event-loop.c:859
#30 gdb_wait_for_event (block=block@entry=1) at ../../gdb/event-loop.c:746
#31 0x0000555555a778bc in gdb_do_one_event () at ../../gdb/event-loop.c:347
#32 0x0000555555a7b096 in gdb_do_one_event () at ../../gdb/event-loop.c:371
#33 start_event_loop () at ../../gdb/event-loop.c:371
#34 0x00005555559ef71b in captured_command_loop () at ../../gdb/main.c:332
#35 0x00005555556c6a48 in captured_main (data=0x7fffffffdb70) at
../../gdb/main.c:1274
#36 gdb_main (args=0x7fffffffdb70) at ../../gdb/main.c:1291
#37 main (argc=2, argv=0x7fffffffdd58) at ../../gdb/gdb.c:40
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26354-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 13 08:47:08 2020
Return-Path: <gdb-prs-return-26354-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 121538 invoked by alias); 13 Feb 2020 08:47:08 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 121510 invoked by uid 48); 13 Feb 2020 08:47:08 -0000
From: "marxin.liska at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25542] Crash in TUI mode
Date: Thu, 13 Feb 2020 08: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: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin.liska 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: <bug-25542-4717-iTuLpNVusZ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25542-4717@http.sourceware.org/bugzilla/>
References: <bug-25542-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00269.txt
Content-length: 403
https://sourceware.org/bugzilla/show_bug.cgi?id=25542
Martin Liška <marxin.liska at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vries at gcc dot gnu.org
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26355-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 13 08:56:08 2020
Return-Path: <gdb-prs-return-26355-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 130417 invoked by alias); 13 Feb 2020 08:56:08 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 130389 invoked by uid 48); 13 Feb 2020 08:56:07 -0000
From: "marxin.liska at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25542] Crash in TUI mode
Date: Thu, 13 Feb 2020 08: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin.liska 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: <bug-25542-4717-QuTUpW1zwF@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25542-4717@http.sourceware.org/bugzilla/>
References: <bug-25542-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00270.txt
Content-length: 254
https://sourceware.org/bugzilla/show_bug.cgi?id=25542
--- Comment #1 from Martin Liška <marxin.liska at gmail dot com> ---
Apparently, current git master works fine.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26356-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 13 14:17:34 2020
Return-Path: <gdb-prs-return-26356-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 21138 invoked by alias); 13 Feb 2020 14:17:33 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 21119 invoked by uid 48); 13 Feb 2020 14:17:33 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25545] New: [GDB] single step is not behave as expected for
atomic function
Date: Thu, 13 Feb 2020 14: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: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25545-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00271.txt
Content-length: 3194
https://sourceware.org/bugzilla/show_bug.cgi?id=25545
Bug ID: 25545
Summary: [GDB] single step is not behave as expected for atomic
function
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d --enable-shared
--enable-threads=posix --with-system-zlib --with-isl --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch
--disable-libssp --enable-gnu-unique-object --enable-linker-build-id
--enable-lto --enable-plugin --enable-install-libiberty
--with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib
--disable-werror --enable-checking=release --enable-default-pie
--enable-default-ssp --enable-cet=auto gdc_include_dir=/usr/include/dlang/gdc
Thread model: posix
gcc version 9.2.0 (GCC)
$ gdb -v
GNU gdb (GDB) 9.0.50.20191210-git
Copyright (C) 2019 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.
$ cat small.c
#include <stdatomic.h>
_Atomic char v = ATOMIC_VAR_INIT(0);
char expected = 0;
char max = ~0;
int main()
{
if (!atomic_compare_exchange_strong_explicit(&v, &expected, max,
memory_order_relaxed, memory_order_relaxed)) // Line 8
return 1;
return 0;
}
$ gcc -g small.c
$ gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) break small.c:9
Breakpoint 1 at 0x1150: small.c:9. (2 locations)
(gdb) run
Starting program: /home/yibiao/cv-gcov/a.out
Breakpoint 1, main () at small.c:9
9 if (!atomic_compare_exchange_strong_explicit(&v, &expected, max,
memory_order_relaxed, memory_order_relaxed))
(gdb) where
#0 main () at small.c:9
(gdb) step
Breakpoint 1, main () at small.c:9
9 if (!atomic_compare_exchange_strong_explicit(&v, &expected, max,
memory_order_relaxed, memory_order_relaxed))
(gdb) where
#0 main () at small.c:9
(gdb) step
11 return 0;
(gdb) q
A debugging session is active.
Inferior 1 [process 4166] will be killed.
Quit anyway? (y or n) y
################################################################################
We set breakpoint at Line #9.
We can find that gdb is wrongly stopped at Line #9 for two times.
That's to say, step is not really stepped this line of code.
################################################################################
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26357-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 13 14:17:43 2020
Return-Path: <gdb-prs-return-26357-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 21418 invoked by alias); 13 Feb 2020 14:17:42 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 21399 invoked by uid 48); 13 Feb 2020 14:17:42 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25545] [GDB] single step is not behave as expected for
atomic function
Date: Thu, 13 Feb 2020 14: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: critical
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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: <bug-25545-4717-XdYWz6sNMe@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25545-4717@http.sourceware.org/bugzilla/>
References: <bug-25545-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00272.txt
Content-length: 381
https://sourceware.org/bugzilla/show_bug.cgi?id=25545
Yibiao Yang <yangyibiao at hust dot edu.cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |critical
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26358-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 13 14:31:53 2020
Return-Path: <gdb-prs-return-26358-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 28622 invoked by alias); 13 Feb 2020 14:31:52 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 28064 invoked by uid 48); 13 Feb 2020 14:31:52 -0000
From: "rguenth at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25546] New: gdb interprets .debug_line programs multiple
times
Date: Thu, 13 Feb 2020 14:31: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: 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: <bug-25546-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00273.txt
Content-length: 2348
https://sourceware.org/bugzilla/show_bug.cgi?id=25546
Bug ID: 25546
Summary: gdb interprets .debug_line programs multiple times
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
When reworking how GCC produces DWARF CUs for LTO LTRANS units I run into gdb
startup being quite slow because it seems that when multiple CUs have the
same DW_AT_stmt_list attribute and thus share the same .debug_line line number
program gdb parses the same line number program multiple times. In my
case generating 8315 CUs instead of formerly 735 CUs (for which there was
a 1:1 correspondence of CU to line number program) gdb startup time regresses
by more than a factor of two with the top of the profile showing
Samples: 102K of event 'cycles:pu', Event count (approx.): 91710925103
Overhead Command Shared Object Symbol
15.21% gdb gdb [.]
lnp_state_machine::handle_special
9.16% gdb gdb [.] read_attribute_value
8.12% gdb gdb [.] dwarf_decode_lines
7.37% gdb gdb [.] partial_die_info::read
4.43% gdb gdb [.]
read_indirect_string_at_offset_fr
4.34% gdb gdb [.] load_partial_dies
4.09% gdb gdb [.] lnp_state_machine::record_line
3.50% gdb gdb [.] cpnameyyparse
3.20% gdb gdb [.]
cp_canonicalize_string[abi:cxx11]
3.14% gdb gdb [.] htab_find_with_hash
2.46% gdb gdb [.] get_objfile_arch
2.24% gdb gdb [.] peek_die_abbrev
2.14% gdb libc-2.26.so [.] _int_free
the solution must be to cache line number program evaluation somehow.
An example binary with the problem will show up at
http://www.suse.de/~rguenther/cc1.new.xz
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26359-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 13 14:33:13 2020
Return-Path: <gdb-prs-return-26359-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 42403 invoked by alias); 13 Feb 2020 14:33:12 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 42381 invoked by uid 48); 13 Feb 2020 14:33:12 -0000
From: "rguenth at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25546] gdb interprets .debug_line programs multiple times
Date: Thu, 13 Feb 2020 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: 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: cc
Message-ID: <bug-25546-4717-oFWaFWCAE2@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25546-4717@http.sourceware.org/bugzilla/>
References: <bug-25546-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00274.txt
Content-length: 397
https://sourceware.org/bugzilla/show_bug.cgi?id=25546
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vries at gcc dot gnu.org
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26360-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 13 14:52:37 2020
Return-Path: <gdb-prs-return-26360-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 29108 invoked by alias); 13 Feb 2020 14:52:35 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 29089 invoked by uid 48); 13 Feb 2020 14:52:34 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25547] New: GDB has different behaviors when breakpoint at
the first statement of a called function
Date: Thu, 13 Feb 2020 14:52: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: critical
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25547-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00275.txt
Content-length: 2187
https://sourceware.org/bugzilla/show_bug.cgi?id=25547
Bug ID: 25547
Summary: GDB has different behaviors when breakpoint at the
first statement of a called function
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
$ cat small.c
extern void abort(void);
static int expected;
static void handler(int *p)
{
if (*p != expected)
abort();
}
static void doit(int x, int y)
{
int r __attribute__((cleanup(handler)));
if (x < y) {
r = 0;
return;
}
}
int main()
{
doit(1, 2);
// doit(2, 1);
return 0;
}
$ gcc -g small.c; gdb -q -ex 'file ./a.out' -batch -ex 'break small.c:13' -ex
'run'
Breakpoint 1 at 0x11a1: file small.c, line 13.
[Inferior 1 (process 5714) exited normally]
$ cat small.c
extern void abort(void);
static int expected;
static void handler(int *p)
{
if (*p != expected)
abort();
}
static void doit(int x, int y)
{
int r __attribute__((cleanup(handler)));
if (x < y) {
r = 0;
return;
}
}
int main()
{
// doit(1, 2);
doit(2, 1);
return 0;
}
$ gcc -g small.c; gdb -q -ex 'file ./a.out' -batch -ex 'break small.c:13' -ex
'run'
Breakpoint 1 at 0x11a1: file small.c, line 13.
Breakpoint 1, doit (x=2, y=1) at small.c:13
13 int r __attribute__((cleanup(handler)));
###########################################################################
### We can find that, when replacing statement from "doit(1, 2)" to "doit(2,
1)" for the main function. Setting breakpoint for the first statement "int r
__attribute__((cleanup(handler)));" in the "doit" function have different
behaviors in gdb.
### doit(1, 2) lead gdb not stopped at small.c:13 (first statement in doit
function)
### doit(2, 1) lead gdb stopped at small.c:13 (first statement in doit
function)
###########################################################################
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26361-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 13 17:44:16 2020
Return-Path: <gdb-prs-return-26361-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 31240 invoked by alias); 13 Feb 2020 17:44:15 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 31213 invoked by uid 48); 13 Feb 2020 17:44:15 -0000
From: "kevinb at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/22214] Cannot view all variables in scope within OpenMP
parallel region
Date: Thu, 13 Feb 2020 17:44: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: ASSIGNED
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: bug_status
Message-ID: <bug-22214-4717-KzRKTZULtK@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22214-4717@http.sourceware.org/bugzilla/>
References: <bug-22214-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00276.txt
Content-length: 379
https://sourceware.org/bugzilla/show_bug.cgi?id=22214
Kevin Buettner <kevinb at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26362-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 13 17:46:45 2020
Return-Path: <gdb-prs-return-26362-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 33799 invoked by alias); 13 Feb 2020 17:46:45 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 33774 invoked by uid 48); 13 Feb 2020 17:46:44 -0000
From: "kevinb at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/22214] Cannot view all variables in scope within OpenMP
parallel region
Date: Thu, 13 Feb 2020 17: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kevinb at redhat dot com
X-Bugzilla-Status: ASSIGNED
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:
Message-ID: <bug-22214-4717-2U5pkrYocv@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22214-4717@http.sourceware.org/bugzilla/>
References: <bug-22214-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00277.txt
Content-length: 412
https://sourceware.org/bugzilla/show_bug.cgi?id=22214
--- Comment #1 from Kevin Buettner <kevinb at redhat dot com> ---
Proposed test case (or something very much like it) is now part of the GDB test
suite. Work continues on the problem of being able to access each in-scope
variable from threads other than the master thread.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26363-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 13 20:22:39 2020
Return-Path: <gdb-prs-return-26363-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 119496 invoked by alias); 13 Feb 2020 20:22:38 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 119472 invoked by uid 48); 13 Feb 2020 20:22:38 -0000
From: "marshall.ward at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug fortran/23051] internal-error for printing the contents of an
allocated pointer of a derived type that contains an allocated pointer array
Date: Thu, 13 Feb 2020 20:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marshall.ward 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: <bug-23051-4717-li0Tlv0I4S@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23051-4717@http.sourceware.org/bugzilla/>
References: <bug-23051-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00278.txt
Content-length: 852
https://sourceware.org/bugzilla/show_bug.cgi?id=23051
Marshall Ward <marshall.ward at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marshall.ward at gmail dot com
--- Comment #3 from Marshall Ward <marshall.ward at gmail dot com> ---
I am seeing this problem in GDB 9.1 build locally. Repeating the instruction
above.
(gdb) p buffer%alpha
../../gdb-9.1/gdb/value.c:2988: internal-error: value*
value_primitive_field(value*, LONGEST, int, type*): Assertion `PROP_CONST ==
TYPE_DATA_LOCATION_KIND (type)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26364-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 13 21:10:13 2020
Return-Path: <gdb-prs-return-26364-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 41215 invoked by alias); 13 Feb 2020 21:10:12 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 41189 invoked by uid 48); 13 Feb 2020 21:10:12 -0000
From: "marshall.ward at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug fortran/23051] internal-error for printing the contents of an
allocated pointer of a derived type that contains an allocated pointer array
Date: Thu, 13 Feb 2020 21:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marshall.ward 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: <bug-23051-4717-BWR9D6HpRK@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23051-4717@http.sourceware.org/bugzilla/>
References: <bug-23051-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00279.txt
Content-length: 525
https://sourceware.org/bugzilla/show_bug.cgi?id=23051
--- Comment #4 from Marshall Ward <marshall.ward at gmail dot com> ---
I ran gdb through gdb (there's a sentence I never thought I'd write) and it
appears that `buffer%alpha` is being treated as a PROP_LOCEXPR and not a
PROP_CONST:
(gdb) p *get_dyn_prop(DYN_PROP_DATA_LOCATION, type)
$9 = {kind = PROP_LOCEXPR, data = {const_val = 93937133865712, baton =
0x556f717ecaf0}}
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26365-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 14 01:39:40 2020
Return-Path: <gdb-prs-return-26365-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 108365 invoked by alias); 14 Feb 2020 01:39:40 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 108346 invoked by uid 48); 14 Feb 2020 01:39:40 -0000
From: "eblake at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/11839] gdb does not detect calls to dlmopen
Date: Fri, 14 Feb 2020 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: 7.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eblake 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: 7.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-11839-4717-Ru4BeRQp4L@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-11839-4717@http.sourceware.org/bugzilla/>
References: <bug-11839-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00280.txt
Content-length: 391
https://sourceware.org/bugzilla/show_bug.cgi?id=11839
Eric Blake <eblake at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |eblake at redhat dot com
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26366-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 14 02:40:57 2020
Return-Path: <gdb-prs-return-26366-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 112176 invoked by alias); 14 Feb 2020 02:40:57 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 112158 invoked by uid 48); 14 Feb 2020 02:40:56 -0000
From: "zhanghe9702 at 163 dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/25552] New: set a breakpoint cause gdb crash
Date: Fri, 14 Feb 2020 02:40: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.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zhanghe9702 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: <bug-25552-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00281.txt
Content-length: 1619
https://sourceware.org/bugzilla/show_bug.cgi?id=25552
Bug ID: 25552
Summary: set a breakpoint cause gdb crash
Product: gdb
Version: 8.2
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: breakpoints
Assignee: unassigned at sourceware dot org
Reporter: zhanghe9702 at 163 dot com
Target Milestone: ---
i have built an debug version mysql-server, when use gdb debug it, set a
breakpoint cause gdb crash, follows are my operations:
scrapy@scrapy:~/mysql$ gdb bin/mysqld
GNU gdb (Ubuntu 8.2.91.20190405-0ubuntu3) 8.2.91.20190405-git
......
Reading symbols from bin/mysqld...
SIGINT is used by the debugger.
Are you sure you want to change it? (y or n) [answered Y; input not from
terminal]
warning: Currently logging to gdb.txt. Turn the logging off and on to make the
new setting effective.
Already logging to gdb.txt.
(gdb) b JOIN::exec
段错误 (核心已转储)(segment fault)
NOTE: very strange, set a breakpoint like 'main' is OK
scrapy@scrapy:~/mysql$ gdb bin/mysqld
......
Reading symbols from bin/mysqld...
SIGINT is used by the debugger.
Are you sure you want to change it? (y or n) [answered Y; input not from
terminal]
warning: Currently logging to gdb.txt. Turn the logging off and on to make the
new setting effective.
Already logging to gdb.txt.
(gdb) b main
Breakpoint 1 at 0x2f72aa4: file /home/scrapy/mysql-server/sql/main.cc, line 25.
(gdb)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26367-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 14 03:33:34 2020
Return-Path: <gdb-prs-return-26367-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 72701 invoked by alias); 14 Feb 2020 03:33:34 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 72675 invoked by uid 48); 14 Feb 2020 03:33:33 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25553] New: wrongly stopped as expected on a breakpoint
when compiled with '-fsanitize=undefined' option
Date: Fri, 14 Feb 2020 03: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: critical
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25553-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00282.txt
Content-length: 2999
https://sourceware.org/bugzilla/show_bug.cgi?id=25553
Bug ID: 25553
Summary: wrongly stopped as expected on a breakpoint when
compiled with '-fsanitize=undefined' option
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d --enable-shared
--enable-threads=posix --with-system-zlib --with-isl --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch
--disable-libssp --enable-gnu-unique-object --enable-linker-build-id
--enable-lto --enable-plugin --enable-install-libiberty
--with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib
--disable-werror --enable-checking=release --enable-default-pie
--enable-default-ssp --enable-cet=auto gdc_include_dir=/usr/include/dlang/gdc
Thread model: posix
gcc version 9.2.0 (GCC)
$ gdb -v
GNU gdb (GDB) 9.0.50.20191210-git
Copyright (C) 2019 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.
$ cat small.c
int foo(signed char n8)
{
const int tw = 8;
int xq[tw];
int bj = 0, rk = 0;
while (bj < 1) {
int gs = n8 ^ 128;
++bj;
rk = xq[0];
}
return 0;
}
int main(void) { foo(1); }
$ gcc -g -fsanitize=undefined small.c; gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) break small.c:4
Breakpoint 1 at 0x11ab: small.c:4. (2 locations)
(gdb) run
Starting program: /home/yibiao/cv-gcov/a.out
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Breakpoint 1, foo (n8=1 '\001') at small.c:4
4 int xq[tw];
(gdb) continue
Continuing.
Breakpoint 1, foo (n8=1 '\001') at small.c:4
4 int xq[tw];
(gdb) q
A debugging session is active.
Inferior 1 [process 8634] will be killed.
Quit anyway? (y or n) y
##########################################
We expect that gdb only stopped once at breakpoint of "small.c:4"
However, it stopped at this breakpoint for two times.
When compiled without '-fsanitize=undefined' option, gdb stopped as expected.
##########################################
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26368-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 14 03:39:26 2020
Return-Path: <gdb-prs-return-26368-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 76095 invoked by alias); 14 Feb 2020 03:39:26 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 76076 invoked by uid 48); 14 Feb 2020 03:39:25 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25553] wrongly stopped at a breakpoint with array
declaration when compiled with '-fsanitize=undefined' option
Date: Fri, 14 Feb 2020 03: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: critical
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: <bug-25553-4717-WYoBxfh6NQ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25553-4717@http.sourceware.org/bugzilla/>
References: <bug-25553-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00283.txt
Content-length: 678
https://sourceware.org/bugzilla/show_bug.cgi?id=25553
Yibiao Yang <yangyibiao at hust dot edu.cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|wrongly stopped as expected |wrongly stopped at a
|on a breakpoint when |breakpoint with array
|compiled with |declaration when compiled
|'-fsanitize=undefined' |with '-fsanitize=undefined'
|option |option
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26369-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 14 04:11:42 2020
Return-Path: <gdb-prs-return-26369-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 104495 invoked by alias); 14 Feb 2020 04:11:42 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 104468 invoked by uid 48); 14 Feb 2020 04:11:41 -0000
From: "chrisj at rtems dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25554] New: rtems-lm32 does not build on darwin
Date: Fri, 14 Feb 2020 04: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: 9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
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: <bug-25554-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00284.txt
Content-length: 1693
https://sourceware.org/bugzilla/show_bug.cgi?id=25554
Bug ID: 25554
Summary: rtems-lm32 does not build on darwin
Product: gdb
Version: 9.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: chrisj at rtems dot org
Target Milestone: ---
gdb-9.1 fails to build for lm32. A brief summary follows and a more complete
log can be found here ..
https://lists.rtems.org/pipermail/build/2020-February/010238.html
/usr/bin/cc -O2 -pipe -fbracket-depth=1024
-I/opt/work/builds/tools/rtems-source-builder.git/rtems/build/tmp/sb-501/5/rtems-lm32/opt/work/builds/tools/5/include
-DHAVE_CONFIG_H -DWITH_DEFAULT_MODEL='"lm32"'
-DWITH_DEFAULT_ALIGNMENT=STRICT_ALIGNMENT
-DWITH_TARGET_BYTE_ORDER=BFD_ENDIAN_BIG -DWITH_HW=1 -DDEFAULT_INLINE=0
-DWITH_SCACHE=16384 -I. -I../../../gdb-9.1/sim/lm32 -I../common
-I../../../gdb-9.1/sim/lm32/../common -I../../include
-I../../../gdb-9.1/sim/lm32/../../include -I../../bfd
-I../../../gdb-9.1/sim/lm32/../../bfd -I../../opcodes
-I../../../gdb-9.1/sim/lm32/../../opcodes -g -O2 -c -o dv-lm32uart.o -MT
dv-lm32uart.o -MMD -MP -MF .deps/dv-lm32uart.Tpo
../../../gdb-9.1/sim/lm32/dv-lm32uart.c
../../../gdb-9.1/sim/lm32/dv-lm32uart.c:213:18: error: variable has incomplete
type 'struct timeval'
struct timeval tv;
^
../../../gdb-9.1/sim/lm32/dv-lm32uart.c:213:10: note: forward declaration of
'struct timeval'
struct timeval tv;
^
1 error generated.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26370-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 14 13:19:11 2020
Return-Path: <gdb-prs-return-26370-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 85930 invoked by alias); 14 Feb 2020 13:19:10 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 85838 invoked by uid 48); 14 Feb 2020 13:19:10 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/24956] backtrace in user-defined command not redirected
Date: Fri, 14 Feb 2020 13: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: vries 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: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-24956-4717-EKphcNFD8Q@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24956-4717@http.sourceware.org/bugzilla/>
References: <bug-24956-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00285.txt
Content-length: 588
https://sourceware.org/bugzilla/show_bug.cgi?id=24956
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.1
--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
$ git br --contains 65d1cd5f9cbcbb2df0b187cb7623949c1668728f -r \
| grep "origin/gdb-.*-branch"
origin/gdb-9-branch
Setting target milestone 9.1.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26371-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 15 01:23:52 2020
Return-Path: <gdb-prs-return-26371-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 97048 invoked by alias); 15 Feb 2020 01:23:52 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 96862 invoked by uid 48); 15 Feb 2020 01:23:52 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25556] New: falselybreak on a not executed statement when
compiled with "--coverage" option
Date: Sat, 15 Feb 2020 01: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: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25556-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00286.txt
Content-length: 3035
https://sourceware.org/bugzilla/show_bug.cgi?id=25556
Bug ID: 25556
Summary: falselybreak on a not executed statement when compiled
with "--coverage" option
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
$ gdb -v
GNU gdb (GDB) 9.0.50.20191210-git
Copyright (C) 2019 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.
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d --enable-shared
--enable-threads=posix --with-system-zlib --with-isl --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch
--disable-libssp --enable-gnu-unique-object --enable-linker-build-id
--enable-lto --enable-plugin --enable-install-libiberty
--with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib
--disable-werror --enable-checking=release --enable-default-pie
--enable-default-ssp --enable-cet=auto gdc_include_dir=/usr/include/dlang/gdc
Thread model: posix
gcc version 9.2.0 (GCC)
$ cat small.c
int foo(void) {}
asm(".text\n"
".globl main\n"
"\t.type main,@function\n"
"main:\n"
"\txorl %eax, %eax\n"
"\tret\n");
$ gcc -g --coverage ./small.c; gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) break small.c:1
Breakpoint 1 at 0x113f: file ./small.c, line 1.
(gdb) start
Temporary breakpoint 2 at 0x1142
Starting program: /tmp/tmpt87ognba/a.out
Temporary breakpoint 2, 0x0000555555555142 in main () at ./small.c:1
1 int foo(void) {}
(gdb) where
#0 0x0000555555555142 in main () at ./small.c:1
(gdb) q
A debugging session is active.
Inferior 1 [process 5503] will be killed.
Quit anyway? (y or n) y
##########################################################
We can find that gdb falsely break on "small.c:1"
However, this statement is not executed.
When compiling small.c without "--coverage" option, gdb behaves correctly as
follow:
$ gcc -g ./small.c; gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) break small.c:1
Breakpoint 1 at 0x111d: file ./small.c, line 1.
(gdb) start
Temporary breakpoint 2 at 0x1123
Starting program: /tmp/tmpt87ognba/a.out
[Inferior 1 (process 5465) exited normally]
(gdb) q
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26372-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 15 01:24:38 2020
Return-Path: <gdb-prs-return-26372-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 97636 invoked by alias); 15 Feb 2020 01:24:37 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 97610 invoked by uid 48); 15 Feb 2020 01:24:36 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25556] falsely break on a statement which is not executed
when compiled with "--coverage" option
Date: Sat, 15 Feb 2020 01: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: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: <bug-25556-4717-bw1d2YO6bC@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25556-4717@http.sourceware.org/bugzilla/>
References: <bug-25556-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00287.txt
Content-length: 609
https://sourceware.org/bugzilla/show_bug.cgi?id=25556
Yibiao Yang <yangyibiao at hust dot edu.cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|falselybreak on a not |falsely break on a
|executed statement when |statement which is not
|compiled with "--coverage" |executed when compiled with
|option |"--coverage" option
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26373-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 15 07:42:46 2020
Return-Path: <gdb-prs-return-26373-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 89737 invoked by alias); 15 Feb 2020 07:42:46 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 89719 invoked by uid 48); 15 Feb 2020 07:42:45 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25558] New: stop at a statement for unexpected times when
compiled with "--coverage" option
Date: Sat, 15 Feb 2020 07: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: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25558-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00288.txt
Content-length: 3261
https://sourceware.org/bugzilla/show_bug.cgi?id=25558
Bug ID: 25558
Summary: stop at a statement for unexpected times when compiled
with "--coverage" option
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
$ gdb -v
GNU gdb (GDB) 9.0.50.20191210-git
Copyright (C) 2019 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.
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d --enable-shared
--enable-threads=posix --with-system-zlib --with-isl --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch
--disable-libssp --enable-gnu-unique-object --enable-linker-build-id
--enable-lto --enable-plugin --enable-install-libiberty
--with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib
--disable-werror --enable-checking=release --enable-default-pie
--enable-default-ssp --enable-cet=auto gdc_include_dir=/usr/include/dlang/gdc
Thread model: posix
gcc version 9.2.0 (GCC)
$ cat small.c
void free(void *ptr)
{
return;
}
void *foo()
{
return 0;
}
void main()
{
void *p = foo();
free(p);
}
$ gcc -g --coverage small.c; gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) break small.c:3
Breakpoint 1 at 0x1143: file small.c, line 3.
(gdb) run
Starting program: /home/yibiao/cv-gcov/a.out
Breakpoint 1, free (ptr=0x0) at small.c:3
3 return;
(gdb) c
Continuing.
Breakpoint 1, free (ptr=0x0) at small.c:3
3 return;
(gdb) c
Continuing.
Breakpoint 1, free (ptr=0x55555555b2d0) at small.c:3
3 return;
(gdb) c
Continuing.
Breakpoint 1, free (ptr=0x55555555b2a0) at small.c:3
3 return;
(gdb) c
Continuing.
Breakpoint 1, free (ptr=0x0) at small.c:3
3 return;
(gdb) c
Continuing.
[Inferior 1 (process 2435) exited with code 01]
######################################################
We can find that gdb falsely break on "small.c:3" for 4 times.
However, "free" function is only called one time.
When compiling without "--coverage", gdb break on "small.c:3" for only one
time.
$ gcc -g small.c; gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) break small.c:3
Breakpoint 1 at 0x1121: file small.c, line 3.
(gdb) run
Starting program: /home/yibiao/cv-gcov/a.out
Breakpoint 1, free (ptr=0x0) at small.c:3
3 return;
(gdb) c
Continuing.
[Inferior 1 (process 2416) exited normally]
(gdb) q
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26374-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 15 08:04:13 2020
Return-Path: <gdb-prs-return-26374-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 125255 invoked by alias); 15 Feb 2020 08:04:12 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 125236 invoked by uid 48); 15 Feb 2020 08:04:12 -0000
From: "juraj5 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25559] New: QNX support does not even compile, severe bit
rot
Date: Sat, 15 Feb 2020 08: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.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juraj5 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: <bug-25559-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00289.txt
Content-length: 1677
https://sourceware.org/bugzilla/show_bug.cgi?id=25559
Bug ID: 25559
Summary: QNX support does not even compile, severe bit rot
Product: gdb
Version: 8.2
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: juraj5 at gmail dot com
Target Milestone: ---
QNX support is severely broken (does not even compile) as early as 8.2, up to
the current version at time of submission (9.1). For example, in
gdb/nto-procfs.c, an obvious blunder was commited in
6bd6f3b6569945700386847f624dc9e8b7f57450 (Simon Marchi
<simon.marchi@ericsson.com> 2018-01-19 17:47:24):
-procfs_detach (struct target_ops *ops, const char *args, int from_tty)
+procfs_detach (struct target_ops *ops, int from_tty)
{
- int siggnal = 0;
int pid;
target_announce_detach ();
- if (args)
- siggnal = atoi (args);
-
if (siggnal)
- SignalKill (nto_node (), ptid_get_pid (inferior_ptid), 0, siggnal, 0, 0);
+ SignalKill (nto_node (), ptid_get_pid (inferior_ptid), 0, 0, 0, 0);
This does not even compile, because the variable "siggnal" has been removed,
while remaining in the if condition. I tried fixing this, but there is A LOT of
other bit rot which I can not fix as easily. (For example,
"target_announce_detach" must now receive from_tty as an argument, and QNX has
been skipped while that API change was being made!)
How is it possible that a file which does not even compile has been shipped for
such a long time?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26376-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 15 08:26:50 2020
Return-Path: <gdb-prs-return-26376-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 35097 invoked by alias); 15 Feb 2020 08:26:50 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 35079 invoked by uid 48); 15 Feb 2020 08:26:50 -0000
From: "juraj5 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25559] QNX support does not even compile, severe bit rot
Date: Sat, 15 Feb 2020 08:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: 7.12
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juraj5 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: <bug-25559-4717-5scuMNunl9@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25559-4717@http.sourceware.org/bugzilla/>
References: <bug-25559-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00291.txt
Content-length: 357
https://sourceware.org/bugzilla/show_bug.cgi?id=25559
juraj5 at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|8.2 |7.12
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26375-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 15 08:26:07 2020
Return-Path: <gdb-prs-return-26375-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 34596 invoked by alias); 15 Feb 2020 08:26:06 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 34573 invoked by uid 48); 15 Feb 2020 08:26:06 -0000
From: "juraj5 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25559] QNX support does not even compile, severe bit rot
Date: Sat, 15 Feb 2020 08: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: 8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juraj5 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: <bug-25559-4717-U9ACOQyTyh@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25559-4717@http.sourceware.org/bugzilla/>
References: <bug-25559-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00290.txt
Content-length: 433
https://sourceware.org/bugzilla/show_bug.cgi?id=25559
--- Comment #1 from juraj5 at gmail dot com ---
The target_announce_detach() bit rot (from_tty not passed, therefore cannot be
compiled) dates to 0f48b7570 Pedro Alves <palves@redhat.com> 2016-07-01
12:16:32 and GDB 7.12. Is it possible that no one has tried compiling this file
since then?!
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26377-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 15 11:09:38 2020
Return-Path: <gdb-prs-return-26377-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 71349 invoked by alias); 15 Feb 2020 11:09:37 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 71330 invoked by uid 48); 15 Feb 2020 11:09:37 -0000
From: "cradesto at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25560] New: Assertion `pid != 0' failed
Date: Sat, 15 Feb 2020 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: 9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: cradesto 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: <bug-25560-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00292.txt
Content-length: 1247
https://sourceware.org/bugzilla/show_bug.cgi?id=25560
Bug ID: 25560
Summary: Assertion `pid != 0' failed
Product: gdb
Version: 9.1
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: cradesto at gmail dot com
Target Milestone: ---
On macOS Mojave 10.14.6
1)
cat 1.cpp
#include <stdio.h>
int
main (void)
{
printf("Hello world!\n");
return 1;
}
2) gcc -g -o a.out 1.cpp
3) gdb a.out
4) Then do command 'r' in gdb
You will get normal execetion
'
Hello world!
[Inferior 1 (process 41899) exited with code 01]
'
But
5) If you do
gdb
and then
6) file a.out
7) You will get
(gdb) file a.out
Reading symbols from a.out...
Reading symbols from ~/tmp/a.out.dSYM/Contents/Resources/DWARF/a.out...
../../gdb/inferior.c:283: internal-error: struct inferior
*find_inferior_pid(int): Assertion `pid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26378-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 16 02:32:06 2020
Return-Path: <gdb-prs-return-26378-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 122301 invoked by alias); 16 Feb 2020 02:31:52 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 121623 invoked by uid 48); 16 Feb 2020 02:31:17 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25562] New: falsely stops at a statement with macros
Date: Sun, 16 Feb 2020 02:31: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: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25562-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00293.txt
Content-length: 3240
https://sourceware.org/bugzilla/show_bug.cgi?id=25562
Bug ID: 25562
Summary: falsely stops at a statement with macros
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
$ gdb -v
GNU gdb (GDB) 9.0.50.20191210-git
Copyright (C) 2019 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.
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d --enable-shared
--enable-threads=posix --with-system-zlib --with-isl --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch
--disable-libssp --enable-gnu-unique-object --enable-linker-build-id
--enable-lto --enable-plugin --enable-install-libiberty
--with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib
--disable-werror --enable-checking=release --enable-default-pie
--enable-default-ssp --enable-cet=auto gdc_include_dir=/usr/include/dlang/gdc
Thread model: posix
gcc version 9.2.0 (GCC)
######### small.c ############
$ cat small.c
char g = 0;
#define FOO(x) (__extension__ ({ int __res; if (!g) { __res = (x); } else if
(sizeof(x) == 4) { __res = (x) + 1; } __res; }))
void __attribute__((noinline)) bar(char **p, char **d, int i)
{
*p = *d + FOO(i);
}
int main()
{
char *p;
char *d = (char *)0x8;
bar(&p, &d, 0x4);
}
########## debug with gdb #########
$ gcc -g small.c; gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) break small.c:7
Breakpoint 1 at 0x1148: small.c:7. (2 locations)
(gdb) run
Starting program: /home/yibiao/cv-gcov/a.out
Breakpoint 1, bar (p=0x7fffffffdeb8, d=0x7fffffffdec0, i=4) at small.c:7
7 *p = *d + FOO(i);
(gdb) where
#0 bar (p=0x7fffffffdeb8, d=0x7fffffffdec0, i=4) at small.c:7
#1 0x00005555555551b4 in main () at small.c:14
(gdb) continue
Continuing.
Breakpoint 1, bar (p=0x7fffffffdeb8, d=0x7fffffffdec0, i=4) at small.c:7
7 *p = *d + FOO(i);
(gdb) where
#0 bar (p=0x7fffffffdeb8, d=0x7fffffffdec0, i=4) at small.c:7
#1 0x00005555555551b4 in main () at small.c:14
(gdb) continue
Continuing.
[Inferior 1 (process 7468) exited normally]
(gdb) q
#######################################################
We can find that gdb stopped on "small.c:7" ( statement "*p = *d + FOO(i);" in
function "bar")for two times.
However, function bar is only called once. Thus, small.c:7 should be only
executed one time.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26379-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 16 03:51:40 2020
Return-Path: <gdb-prs-return-26379-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 108813 invoked by alias); 16 Feb 2020 03:51:39 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 108783 invoked by uid 48); 16 Feb 2020 03:51:39 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25559] QNX support does not even compile, severe bit rot
Date: Sun, 16 Feb 2020 03: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
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-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: <bug-25559-4717-EHwCC8Qj2x@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25559-4717@http.sourceware.org/bugzilla/>
References: <bug-25559-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00294.txt
Content-length: 971
https://sourceware.org/bugzilla/show_bug.cgi?id=25559
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-16
CC| |simark at simark dot ca
Ever confirmed|0 |1
--- Comment #2 from Simon Marchi <simark at simark dot ca> ---
Thanks for reporting, I haven't heard about anybody using this port in a long
time.
I would be happy to at least test-build this, but last time I checked, I
couldn't get my hand on a toolchain to build this, hence the bit rot. If you
know how to obtain a toolchain for this platform freely (both gratis and libre,
ideally), please let me know.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26380-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 16 03:54:07 2020
Return-Path: <gdb-prs-return-26380-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 109629 invoked by alias); 16 Feb 2020 03:54:06 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 109610 invoked by uid 48); 16 Feb 2020 03:54:06 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25559] QNX support does not even compile, severe bit rot
Date: Sun, 16 Feb 2020 03: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.12
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25559-4717-slJD8xProY@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25559-4717@http.sourceware.org/bugzilla/>
References: <bug-25559-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00295.txt
Content-length: 385
https://sourceware.org/bugzilla/show_bug.cgi?id=25559
--- Comment #3 from Simon Marchi <simark at simark dot ca> ---
Also, if you are interested in this GDB port and work on getting it in a better
shape, please consider sending patches [1].
[1] https://sourceware.org/gdb/wiki/ContributionChecklist
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26381-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 16 15:39:19 2020
Return-Path: <gdb-prs-return-26381-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 12389 invoked by alias); 16 Feb 2020 15:39:19 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 12371 invoked by uid 48); 16 Feb 2020 15:39:18 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25564] New: falsely set breakpoint for inline function call
statement
Date: Sun, 16 Feb 2020 15: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: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25564-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00296.txt
Content-length: 2324
https://sourceware.org/bugzilla/show_bug.cgi?id=25564
Bug ID: 25564
Summary: falsely set breakpoint for inline function call
statement
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
$ gdb -v
GNU gdb (GDB) 9.0.50.20191210-git
Copyright (C) 2019 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.
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d --enable-shared
--enable-threads=posix --with-system-zlib --with-isl --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch
--disable-libssp --enable-gnu-unique-object --enable-linker-build-id
--enable-lto --enable-plugin --enable-install-libiberty
--with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib
--disable-werror --enable-checking=release --enable-default-pie
--enable-default-ssp --enable-cet=auto gdc_include_dir=/usr/include/dlang/gdc
Thread model: posix
gcc version 9.2.0 (GCC)
$ cat small.c
__attribute__((always_inline)) inline void foo(int *x)
{
*x = 0;
}
int main()
{
int x;
foo(&x);
return x;
}
$ gcc -g small.c; gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) break small.c:9
Breakpoint 1 at 0x1163: file small.c, line 10.
(gdb) q
#############################################################
We can find that when typing "break small.c:9" [ foo(&x); ], it sets breakpoint
at "small.c:10".
However, Line #9 is actually executed.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26382-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 16 16:00:59 2020
Return-Path: <gdb-prs-return-26382-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 26306 invoked by alias); 16 Feb 2020 16:00:57 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 26141 invoked by uid 48); 16 Feb 2020 16:00:45 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25565] New: falsely not stopped for step an executed
statement when compiled with "--coverage" option
Date: Sun, 16 Feb 2020 16:00: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: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25565-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00297.txt
Content-length: 3023
https://sourceware.org/bugzilla/show_bug.cgi?id=25565
Bug ID: 25565
Summary: falsely not stopped for step an executed statement
when compiled with "--coverage" option
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
$ gdb -v
GNU gdb (GDB) 9.0.50.20191210-git
Copyright (C) 2019 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.
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d --enable-shared
--enable-threads=posix --with-system-zlib --with-isl --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch
--disable-libssp --enable-gnu-unique-object --enable-linker-build-id
--enable-lto --enable-plugin --enable-install-libiberty
--with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib
--disable-werror --enable-checking=release --enable-default-pie
--enable-default-ssp --enable-cet=auto gdc_include_dir=/usr/include/dlang/gdc
Thread model: posix
gcc version 9.2.0 (GCC)
$ cat small.c
void *memset (void *, int, __SIZE_TYPE__);
void *malloc (__SIZE_TYPE__);
void main()
{
char *x = (char*)malloc(10);
memset(x, 0, 10);
}
$ gcc -g --coverage small.c; gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) start
Temporary breakpoint 1 at 0x1173: file small.c, line 7.
Starting program: /home/yibiao/cv-gcov/a.out
Temporary breakpoint 1, main () at small.c:7
7 char *x = (char*)malloc(10);
(gdb) step
[Inferior 1 (process 2356) exited with code 0240]
(gdb) q
##############################################
We can find that, type "start" and follows "step" the program will exit
directly.
However, it behaves as expected when compiling small.c without "--coverage",
$ gcc -g small.c; gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) start
Temporary breakpoint 1 at 0x1151: file small.c, line 7.
Starting program: /home/yibiao/cv-gcov/a.out
Temporary breakpoint 1, main () at small.c:7
7 char *x = (char*)malloc(10);
(gdb) step
8 memset(x, 0, 10);
(gdb) q
A debugging session is active.
Inferior 1 [process 2376] will be killed.
Quit anyway? (y or n) y
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26383-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 16 16:02:42 2020
Return-Path: <gdb-prs-return-26383-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 27620 invoked by alias); 16 Feb 2020 16:02:41 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 27600 invoked by uid 48); 16 Feb 2020 16:02:41 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25565] falsely not stopped for stepping an executed
statement when compiled with "--coverage" option
Date: Sun, 16 Feb 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: <bug-25565-4717-jcDRXlZXHN@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25565-4717@http.sourceware.org/bugzilla/>
References: <bug-25565-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00298.txt
Content-length: 613
https://sourceware.org/bugzilla/show_bug.cgi?id=25565
Yibiao Yang <yangyibiao at hust dot edu.cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|falsely not stopped for |falsely not stopped for
|step an executed statement |stepping an executed
|when compiled with |statement when compiled
|"--coverage" option |with "--coverage" option
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26384-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 17 02:08:18 2020
Return-Path: <gdb-prs-return-26384-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 5433 invoked by alias); 17 Feb 2020 02:08:18 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 5414 invoked by uid 48); 17 Feb 2020 02:08:17 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25565] gdb step will falsely exit for malloc function call
statement when compiled with "--coverage" option
Date: Mon, 17 Feb 2020 02: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: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: <bug-25565-4717-l02eExGwkH@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25565-4717@http.sourceware.org/bugzilla/>
References: <bug-25565-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00299.txt
Content-length: 620
https://sourceware.org/bugzilla/show_bug.cgi?id=25565
Yibiao Yang <yangyibiao at hust dot edu.cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|falsely not stopped for |gdb step will falsely exit
|stepping an executed |for malloc function call
|statement when compiled |statement when compiled
|with "--coverage" option |with "--coverage" option
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26385-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 17 23:19:14 2020
Return-Path: <gdb-prs-return-26385-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 66893 invoked by alias); 17 Feb 2020 23:19:14 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 66868 invoked by uid 48); 17 Feb 2020 23:19:14 -0000
From: "starout at mail dot ru" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/9834] GDB choosing wrong process when multiple
processes have same name.
Date: Mon, 17 Feb 2020 23:19: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: 6.6
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: starout at mail dot ru
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: 6.8
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-9834-4717-FI4eHIAihW@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-9834-4717@http.sourceware.org/bugzilla/>
References: <bug-9834-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00300.txt
Content-length: 547
https://sourceware.org/bugzilla/show_bug.cgi?id=9834
doctor <starout at mail dot ru> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |starout at mail dot ru
--- Comment #2 from doctor <starout at mail dot ru> ---
Created attachment 12295
--> https://sourceware.org/bugzilla/attachment.cgi?id=12295&action=edit
dd
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26386-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 18 02:02:52 2020
Return-Path: <gdb-prs-return-26386-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 7536 invoked by alias); 18 Feb 2020 02:02:52 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 7459 invoked by uid 48); 18 Feb 2020 02:02:52 -0000
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/22214] Cannot view all variables in scope within OpenMP
parallel region
Date: Tue, 18 Feb 2020 02: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: woodard at redhat dot com
X-Bugzilla-Status: ASSIGNED
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: cc
Message-ID: <bug-22214-4717-RPGxTN6LON@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22214-4717@http.sourceware.org/bugzilla/>
References: <bug-22214-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00301.txt
Content-length: 394
https://sourceware.org/bugzilla/show_bug.cgi?id=22214
Ben Woodard <woodard at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |woodard at redhat dot com
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26387-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 18 08:17:54 2020
Return-Path: <gdb-prs-return-26387-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 90064 invoked by alias); 18 Feb 2020 08:17:54 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 90036 invoked by uid 48); 18 Feb 2020 08:17:53 -0000
From: "dinc.tarkan at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/25467] GDB cannot step over a function if the following
lines don't include and decision or branch
Date: Tue, 18 Feb 2020 08: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.9
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dinc.tarkan 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: <bug-25467-4717-il4qKxd0xv@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25467-4717@http.sourceware.org/bugzilla/>
References: <bug-25467-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00302.txt
Content-length: 816
https://sourceware.org/bugzilla/show_bug.cgi?id=25467
--- Comment #2 from Tarkan <dinc.tarkan at gmail dot com> ---
Problem solved, at least step over work fine now.
the error caused by rs6000_in_function_epilogue_frame_p() function.
as you can see the function scans forward until next blr for 52 instruction.
And scan backwards until adjustment to stack pointer.
These causees to put a breakpoint to be put on a previous code from the pc and
execution cannot be stopped.
The fuction modified just to retun 0.
I dont have a deep understanding in host side, maybe you'll find a better
solution.
I suspect there was a design change in previous versions in step functionality,
intel arhitecture code updated but powerpc forgetten.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26388-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 18 09:13:33 2020
Return-Path: <gdb-prs-return-26388-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 125212 invoked by alias); 18 Feb 2020 09:13:32 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 125194 invoked by uid 48); 18 Feb 2020 09:13:32 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25573] New: program received segmentation fault when
setting breakpoint for valid address in function _init
Date: Tue, 18 Feb 2020 09: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: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25573-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00303.txt
Content-length: 2955
https://sourceware.org/bugzilla/show_bug.cgi?id=25573
Bug ID: 25573
Summary: program received segmentation fault when setting
breakpoint for valid address in function _init
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yangyibiao at hust dot edu.cn
Target Milestone: ---
$ gdb -v
GNU gdb (GDB) 9.0.50.20191210-git
Copyright (C) 2019 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.
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d --enable-shared
--enable-threads=posix --with-system-zlib --with-isl --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch
--disable-libssp --enable-gnu-unique-object --enable-linker-build-id
--enable-lto --enable-plugin --enable-install-libiberty
--with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib
--disable-werror --enable-checking=release --enable-default-pie
--enable-default-ssp --enable-cet=auto gdc_include_dir=/usr/include/dlang/gdc
Thread model: posix
gcc version 9.2.0 (GCC)
$ cat small.c
int main()
{
return 0;
}
$ gcc -g small.c; gdb -q ./a.out
Reading symbols from ./a.out...
(gdb) disas _init
Dump of assembler code for function _init:
0x0000000000001000 <+0>: endbr64
0x0000000000001004 <+4>: sub $0x8,%rsp
0x0000000000001008 <+8>: mov 0x2fd9(%rip),%rax # 0x3fe8
0x000000000000100f <+15>: test %rax,%rax
0x0000000000001012 <+18>: je 0x1016 <_init+22>
0x0000000000001014 <+20>: callq *%rax
0x0000000000001016 <+22>: add $0x8,%rsp
0x000000000000101a <+26>: retq
End of assembler dump.
(gdb) break *_init+18
Breakpoint 1 at 0x1012
(gdb) run
Starting program: /home/yibiao/cv-gcov/a.out
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7df7fb2 in _init () from /usr/lib/libc.so.6
(gdb) q
A debugging session is active.
Inferior 1 [process 4286] will be killed.
Quit anyway? (y or n) y
#################################
We can find that when setting breakpoint for valid address "break *_init+18",
program exit with "Segmentation fault"
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26389-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 18 09:16:54 2020
Return-Path: <gdb-prs-return-26389-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 2507 invoked by alias); 18 Feb 2020 09:16:53 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 2485 invoked by uid 48); 18 Feb 2020 09:16:53 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25573] program received segmentation fault when setting
breakpoint for valid address in function _init
Date: Tue, 18 Feb 2020 09: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: critical
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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: <bug-25573-4717-hHECtz4xvJ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25573-4717@http.sourceware.org/bugzilla/>
References: <bug-25573-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00304.txt
Content-length: 381
https://sourceware.org/bugzilla/show_bug.cgi?id=25573
Yibiao Yang <yangyibiao at hust dot edu.cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |critical
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26390-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 18 09:17:59 2020
Return-Path: <gdb-prs-return-26390-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 26172 invoked by alias); 18 Feb 2020 09:17:59 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 25020 invoked by uid 48); 18 Feb 2020 09:17:58 -0000
From: "yangyibiao at hust dot edu.cn" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/25390] Segmentation fault when setting breakpoint
for valid address in function get_available_features due to optimization
Date: Tue, 18 Feb 2020 09: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: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: yangyibiao at hust dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: <bug-25390-4717-nwIGBTWkN9@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25390-4717@http.sourceware.org/bugzilla/>
References: <bug-25390-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00305.txt
Content-length: 684
https://sourceware.org/bugzilla/show_bug.cgi?id=25390
Yibiao Yang <yangyibiao at hust dot edu.cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Segmentation fault when |Segmentation fault when
|setting breakpoint on valid |setting breakpoint for
|address |valid address in function
| |get_available_features due
| |to optimization
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26391-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 18 18:09:57 2020
Return-Path: <gdb-prs-return-26391-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 97619 invoked by alias); 18 Feb 2020 18:09:56 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 97562 invoked by uid 48); 18 Feb 2020 18:09:54 -0000
From: "paul.naert at polymtl dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug compile/25575] New: Compile command crashes or fails with AVX
registers and -O2
Date: Tue, 18 Feb 2020 18:09: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: paul.naert at polymtl dot 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
attachments.created
Message-ID: <bug-25575-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00306.txt
Content-length: 1815
https://sourceware.org/bugzilla/show_bug.cgi?id=25575
Bug ID: 25575
Summary: Compile command crashes or fails with AVX registers
and -O2
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: compile
Assignee: unassigned at sourceware dot org
Reporter: paul.naert at polymtl dot ca
Target Milestone: ---
Created attachment 12300
--> https://sourceware.org/bugzilla/attachment.cgi?id=12300&action=edit
Test program
Calling the compile command in certain functions produces an error or crashes
gdb.
Attached is a small test program.
compile with
gcc -g -O2 -o bug bug-report.c
GDB commands:
start
break approx_sqrt
jump approx_sqrt
compile ;
Ubuntu version 18.04, x86_64 architecture.
gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
GNU gdb (GDB) 10.0.50.20200217-git
Also happens on older versions of gdb I tested with.
With this set of commands version of GDB, it produces the error below twice:
/tmp/gdbobj-eOWmD8/out1.c:17:59: error: ‘struct __gdb_regs’ has no member named
‘__ymm0’; did you mean ‘_dummy’?
__gdb_stack[__gdb_tos + 1] = (__gdb_uintptr) &__regs->__ymm0;
^~~~~~
_dummy
I think this may actually be coming from gcc.
With other versions of gdb and different commands, for instance accessing the
approx_sqrt function through main, I get different behaviors. I've had the
error printed once instead of twice, and gdb crashing with a Segfault and
Abort.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26392-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 19 12:49:11 2020
Return-Path: <gdb-prs-return-26392-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 106608 invoked by alias); 19 Feb 2020 12:49:08 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 106454 invoked by uid 48); 19 Feb 2020 12:48:55 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/14186] const volatile is ignored for TYPE_INSTANCE
Date: Wed, 19 Feb 2020 12: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: vries 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: <bug-14186-4717-p5JemEWvJ1@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-14186-4717@http.sourceware.org/bugzilla/>
References: <bug-14186-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00307.txt
Content-length: 722
https://sourceware.org/bugzilla/show_bug.cgi?id=14186
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vries at gcc dot gnu.org
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Pedro Alves from comment #5)
> I agree.
Removed kfail in commit d3308cfdec "[gdb/testsuite] Fix c++/14186 kpass in
cpexprs.exp" (
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=d3308cfdec5765e8667fa6f61f75bc36986cdcf9
).
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26393-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 19 13:28:04 2020
Return-Path: <gdb-prs-return-26393-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 105814 invoked by alias); 19 Feb 2020 13:28:04 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 105790 invoked by uid 48); 19 Feb 2020 13:28:03 -0000
From: "patrick at monnerat dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25577] New: Target synchronous mode is broken since Jan 10
Date: Wed, 19 Feb 2020 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: patrick at monnerat 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: <bug-25577-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00308.txt
Content-length: 1014
https://sourceware.org/bugzilla/show_bug.cgi?id=25577
Bug ID: 25577
Summary: Target synchronous mode is broken since Jan 10
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: patrick at monnerat dot net
Target Milestone: ---
Commit 5b6d1e4fa4fc6827c7b3f0e99ff120dfa14d65d2 (Multi-target support) broke
the target synchronous mode. When trying to run/start the program, gdb freezes.
To reproduce:
gdb a.out
maint set target-async off
start
This never finishes, Ctrl-C is inoperant anf gdb has to be killed.
As a hint, I suspect function fetch_inferior_event() to return too early when
do_target_wait() returns without having found a pending event. This has been
introduced in the above commit.
Thanks for investigating.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26394-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 19 14:03:39 2020
Return-Path: <gdb-prs-return-26394-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 15470 invoked by alias); 19 Feb 2020 14:03:38 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 15446 invoked by uid 48); 19 Feb 2020 14:03:38 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/14186] const volatile is ignored for TYPE_INSTANCE
Date: Wed, 19 Feb 2020 14: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: 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-14186-4717-hL9SSjfLxi@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-14186-4717@http.sourceware.org/bugzilla/>
References: <bug-14186-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00309.txt
Content-length: 533
https://sourceware.org/bugzilla/show_bug.cgi?id=14186
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Tom Tromey <tromey at sourceware dot org> ---
Sounds like this can be closed.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26395-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 19 16:49:59 2020
Return-Path: <gdb-prs-return-26395-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 95936 invoked by alias); 19 Feb 2020 16:49:59 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 95918 invoked by uid 48); 19 Feb 2020 16:49:58 -0000
From: "cbiesinger at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25577] Target synchronous mode is broken since Jan 10
Date: Wed, 19 Feb 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: <bug-25577-4717-RQkjapmMpJ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25577-4717@http.sourceware.org/bugzilla/>
References: <bug-25577-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00310.txt
Content-length: 404
https://sourceware.org/bugzilla/show_bug.cgi?id=25577
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26396-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 19 17:25:40 2020
Return-Path: <gdb-prs-return-26396-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 35900 invoked by alias); 19 Feb 2020 17:25:40 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 35873 invoked by uid 48); 19 Feb 2020 17:25:39 -0000
From: "juraj5 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25559] QNX support does not even compile, severe bit rot
Date: Wed, 19 Feb 2020 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.12
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juraj5 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: <bug-25559-4717-IqOrNcjIK5@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25559-4717@http.sourceware.org/bugzilla/>
References: <bug-25559-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00311.txt
Content-length: 968
https://sourceware.org/bugzilla/show_bug.cgi?id=25559
--- Comment #4 from juraj5 at gmail dot com ---
Hi Simon, thanks for your response.
Part of the toolchain for QNX 6.5 (GCC 4.8.3, both native and cross for Windows
and Linux) is available here (free registration is required):
http://community.qnx.com/sf/frs/do/viewRelease/projects.toolchain/frs.gcc.gcc_4_8
You still need some system headers and the C runtime to build something, which
are AFAIK non-free. I am not sure if they are redistributable. I could perhaps
provide SSH access to a QNX 6.5 VM with the native 4.8.3 toolchain.
I managed to build 8.1.1 using GCC 4.8.3 fixing some minor quirks. However, it
crashes after "break main; run" on a hello world debug executable with a failed
internal GDB assertion related to threads. My backlog is quite full currently
though to look into this in more detail.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26397-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 19 18:46:18 2020
Return-Path: <gdb-prs-return-26397-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 117229 invoked by alias); 19 Feb 2020 18:46:17 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 117151 invoked by uid 48); 19 Feb 2020 18:46:11 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25559] QNX support does not even compile, severe bit rot
Date: Wed, 19 Feb 2020 18: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
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25559-4717-RYKe2lmuLG@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25559-4717@http.sourceware.org/bugzilla/>
References: <bug-25559-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00312.txt
Content-length: 1751
https://sourceware.org/bugzilla/show_bug.cgi?id=25559
--- Comment #5 from Simon Marchi <simark at simark dot ca> ---
(In reply to juraj5 from comment #4)
> Hi Simon, thanks for your response.
>
> Part of the toolchain for QNX 6.5 (GCC 4.8.3, both native and cross for
> Windows and Linux) is available here (free registration is required):
>
> http://community.qnx.com/sf/frs/do/viewRelease/projects.toolchain/frs.gcc.
> gcc_4_8
>
> You still need some system headers and the C runtime to build something,
> which are AFAIK non-free.
Yeah, instead of "toolchain" I should have said "complete working build
environment".
> I am not sure if they are redistributable. I could
> perhaps provide SSH access to a QNX 6.5 VM with the native 4.8.3 toolchain.
>
> I managed to build 8.1.1 using GCC 4.8.3 fixing some minor quirks. However,
> it crashes after "break main; run" on a hello world debug executable with a
> failed internal GDB assertion related to threads. My backlog is quite full
> currently though to look into this in more detail.
Well, if you can send patches to at least get master to build, it would already
be a good first step. If you share the assertion message you hit when running
the program, perhaps somebody can give you pointers.
What we need for a GDB port to be alive is contributors who care about that
port, checking regularly that it builds and run fine. If nobody contributing
to GDB cares about QNX, then it is doomed to degrade like this. I'll gladly
review some patches that improve the support for QNX, but my backlog is also
too full (it's the same for everybody) to maintain a port I don't care about.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26398-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 19 19:20:21 2020
Return-Path: <gdb-prs-return-26398-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 26197 invoked by alias); 19 Feb 2020 19:20:21 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 26172 invoked by uid 55); 19 Feb 2020 19:20:20 -0000
From: "juraj5 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25559] QNX support does not even compile, severe bit rot
Date: Wed, 19 Feb 2020 19: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: 7.12
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juraj5 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: <bug-25559-4717-bNfJfrhiv9@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25559-4717@http.sourceware.org/bugzilla/>
References: <bug-25559-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00313.txt
Content-length: 2879
https://sourceware.org/bugzilla/show_bug.cgi?id=25559
--- Comment #6 from juraj5 at gmail dot com ---
Okay, thanks. I will share the build bringup patch and the thread
assertion when I catch some time. In the meantime I'll stick to GDB
7.6.1 and GCC 4.8.3 provided by QNX. However, it would be nice to be
able to use GCC 9 and GDB 9.
One thing I stumbled into with executables built with GCC 9 (I managed
to do a bringup of native three step bootstrap from 4.8.3) was that
GDB 7.6.1 cannot read the stack frames. E.g. backtrace errors out with
"cannot access memory at 0xfffffff1" after hitting the breakpoint on
main. Stopping on breakpoints works though, backtrace can sometimes
read the topmost frame, but locals are garbled in that case. Any idea
what might be going on? Did the stack frame format change sometime
from GCC 4.8.3 to GCC 9.2 so GDB 7.6.1 cannot read it?
Thanks, Juraj
On Wed, Feb 19, 2020 at 7:46 PM simark at simark dot ca
<sourceware-bugzilla@sourceware.org> wrote:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=25559
>
> --- Comment #5 from Simon Marchi <simark at simark dot ca> ---
> (In reply to juraj5 from comment #4)
> > Hi Simon, thanks for your response.
> >
> > Part of the toolchain for QNX 6.5 (GCC 4.8.3, both native and cross for
> > Windows and Linux) is available here (free registration is required):
> >
> > http://community.qnx.com/sf/frs/do/viewRelease/projects.toolchain/frs.gcc.
> > gcc_4_8
> >
> > You still need some system headers and the C runtime to build something,
> > which are AFAIK non-free.
>
> Yeah, instead of "toolchain" I should have said "complete working build
> environment".
>
> > I am not sure if they are redistributable. I could
> > perhaps provide SSH access to a QNX 6.5 VM with the native 4.8.3 toolchain.
> >
> > I managed to build 8.1.1 using GCC 4.8.3 fixing some minor quirks. However,
> > it crashes after "break main; run" on a hello world debug executable with a
> > failed internal GDB assertion related to threads. My backlog is quite full
> > currently though to look into this in more detail.
>
> Well, if you can send patches to at least get master to build, it would already
> be a good first step. If you share the assertion message you hit when running
> the program, perhaps somebody can give you pointers.
>
> What we need for a GDB port to be alive is contributors who care about that
> port, checking regularly that it builds and run fine. If nobody contributing
> to GDB cares about QNX, then it is doomed to degrade like this. I'll gladly
> review some patches that improve the support for QNX, but my backlog is also
> too full (it's the same for everybody) to maintain a port I don't care about.
>
> --
> You are receiving this mail because:
> You reported the bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26399-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 19 19:23:31 2020
Return-Path: <gdb-prs-return-26399-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 42997 invoked by alias); 19 Feb 2020 19:23:30 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 42977 invoked by uid 48); 19 Feb 2020 19:23:30 -0000
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25559] QNX support does not even compile, severe bit rot
Date: Wed, 19 Feb 2020 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: 7.12
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25559-4717-FjmTGG0MRV@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25559-4717@http.sourceware.org/bugzilla/>
References: <bug-25559-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00314.txt
Content-length: 1169
https://sourceware.org/bugzilla/show_bug.cgi?id=25559
--- Comment #7 from Simon Marchi <simark at simark dot ca> ---
(In reply to juraj5 from comment #6)
> Okay, thanks. I will share the build bringup patch and the thread
> assertion when I catch some time. In the meantime I'll stick to GDB
> 7.6.1 and GCC 4.8.3 provided by QNX. However, it would be nice to be
> able to use GCC 9 and GDB 9.
>
> One thing I stumbled into with executables built with GCC 9 (I managed
> to do a bringup of native three step bootstrap from 4.8.3) was that
> GDB 7.6.1 cannot read the stack frames. E.g. backtrace errors out with
> "cannot access memory at 0xfffffff1" after hitting the breakpoint on
> main. Stopping on breakpoints works though, backtrace can sometimes
> read the topmost frame, but locals are garbled in that case. Any idea
> what might be going on? Did the stack frame format change sometime
> from GCC 4.8.3 to GCC 9.2 so GDB 7.6.1 cannot read it?
The stack frame format, not likely, but the DWARF debug information may have
changed in ways that the old GDB does not understand.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26400-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 19 21:01:06 2020
Return-Path: <gdb-prs-return-26400-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 90997 invoked by alias); 19 Feb 2020 21:01:04 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 90778 invoked by uid 55); 19 Feb 2020 21:00:51 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug rust/25535] Wrong field looked up for variant discriminator
Date: Wed, 19 Feb 2020 21: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: 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: dje at google dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25535-4717-b2OYBaQvtw@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25535-4717@http.sourceware.org/bugzilla/>
References: <bug-25535-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00315.txt
Content-length: 1031
https://sourceware.org/bugzilla/show_bug.cgi?id=25535
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=084104828cba3e80b19a4bad9538d32991312d7a
commit 084104828cba3e80b19a4bad9538d32991312d7a
Author: Doug Evans <dje@google.com>
Date: Wed Feb 19 13:54:59 2020 -0700
rust/25535 Apply embedded offset to enum variant calculation
Hopefully straightforward (and I didn't miss anything ...).
gdb/ChangeLog
2020-02-19 Doug Evans <dje@google.com>
PR rust/25535
* rust-lang.c (rust_print_enum): Apply embedded_offset to
rust_enum_variant calculation.
gdb/testsuite/ChangeLog
2020-02-19 Doug Evans <dje@google.com>
PR rust/25535
* gdb.rust/simple.exp: Add test.
* gdb.rust/simple.rs: Add test.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26401-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 19 21:02:12 2020
Return-Path: <gdb-prs-return-26401-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 93445 invoked by alias); 19 Feb 2020 21:02:11 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 93419 invoked by uid 48); 19 Feb 2020 21:02:11 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug rust/25535] Wrong field looked up for variant discriminator
Date: Wed, 19 Feb 2020 21: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: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: dje at google dot com
X-Bugzilla-Target-Milestone: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution target_milestone
Message-ID: <bug-25535-4717-lIkElZwSRQ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25535-4717@http.sourceware.org/bugzilla/>
References: <bug-25535-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00316.txt
Content-length: 642
https://sourceware.org/bugzilla/show_bug.cgi?id=25535
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |tromey at sourceware dot org
Resolution|--- |FIXED
Target Milestone|--- |10.1
--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
Fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26402-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 20 11:15:00 2020
Return-Path: <gdb-prs-return-26402-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 7515 invoked by alias); 20 Feb 2020 11:14:59 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 7487 invoked by uid 48); 20 Feb 2020 11:14:59 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug go/17018] XFAIL: gdb.go/hello.exp: Starting string check
Date: Thu, 20 Feb 2020 11:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: go
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-17018-4717-vkCiabL1oS@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17018-4717@http.sourceware.org/bugzilla/>
References: <bug-17018-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00317.txt
Content-length: 2343
https://sourceware.org/bugzilla/show_bug.cgi?id=17018
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vries at gcc dot gnu.org
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
The test-case source is:
...
package main
import "fmt"
var myst = "Shall we?"
func main () {
fmt.Println ("Before assignment")
st := "Hello, world!" // this intentionally shadows the global "st"
fmt.Println (st) // set breakpoint 1 here
fmt.Println (myst)
}
...
The comment about shadowing is somewhat confusing given that there is no global
variable st.
I've made a variant renaming myst to st, which does contain shadowing:
...
package main
import "fmt"
var st = "Shall we?"
func main () {
fmt.Println (st)
fmt.Println ("Before assignment")
st := "Hello, world!"
fmt.Println (st)
}
...
Using this test-case, I ran into a gcc bug, filed as PR gcc/go/93844 (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93844 ).
[ Filed as go problem, but as richi mentioned, also happens for c++, and c99. ]
[ Same problem with go1.11.13 ].
The problem is as follows: the scope of local variable st start at the ':='
line, but the debug info fails to wrap the local variable in an appropriate
DW_TAG_lexical_block (or to emit an appropriate DW_AT_start_scope), and
consequently when accessing the value of st at the start main, we incorrectly
get the uninitialized local value, instead of the global value.
If you're lucky, the uninitialized local value is 0, and will be printed as:
...
(gdb) p st
$3 = 0x0 ""
...
And using a compiler without this bug, it should print:
...
(gdb) p st
$3 = 0x12345678 "Shall we?"
...
[ Just that I don't know if there's such a compiler. ]
This compiler bug matches the xfail comment:
...
# This used to print "", i.e., the local "st" initialized as "".
setup_xfail "*-*-*"
...
in the sense that printing "" indicates presence of the bug.
But then again it says "used to print", implying that there's a compiler where
this bug is fixed, and that doesn't match.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26403-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 20 11:28:22 2020
Return-Path: <gdb-prs-return-26403-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 102281 invoked by alias); 20 Feb 2020 11:28:22 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 102260 invoked by uid 48); 20 Feb 2020 11:28:22 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug go/17018] XFAIL: gdb.go/hello.exp: Starting string check
Date: Thu, 20 Feb 2020 11:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: go
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-17018-4717-5xU8xspyGM@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17018-4717@http.sourceware.org/bugzilla/>
References: <bug-17018-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00318.txt
Content-length: 761
https://sourceware.org/bugzilla/show_bug.cgi?id=17018
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> The test-case source is:
> ...
> package main
>
> import "fmt"
>
> var myst = "Shall we?"
>
> func main () {
> fmt.Println ("Before assignment")
> st := "Hello, world!" // this intentionally shadows the global "st"
> fmt.Println (st) // set breakpoint 1 here
> fmt.Println (myst)
> }
> ...
Anyway, looking at the actual test-case, the same gcc PR is triggered. It's
just that the valid behaviour for printing st at the start of main should be
'No symbol "st" in current context' or some such.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26404-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 20 11:29:18 2020
Return-Path: <gdb-prs-return-26404-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 103975 invoked by alias); 20 Feb 2020 11:29:18 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 103953 invoked by uid 48); 20 Feb 2020 11:29:17 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug go/17018] XFAIL: gdb.go/hello.exp: Starting string check
Date: Thu, 20 Feb 2020 11:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: go
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-17018-4717-4svv12aMlZ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17018-4717@http.sourceware.org/bugzilla/>
References: <bug-17018-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00319.txt
Content-length: 791
https://sourceware.org/bugzilla/show_bug.cgi?id=17018
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Pedro Alves from comment #0)
> On Fedora 20, I noticed this:
>
> print st
> $1 = 0xc200016210 "\000\000\000\000\000\000\000\000\200c\000\000\302",
> '\000' <repeats 11 times>,
> "d\000\000\000\000\000\000\000P$\322\367\377\177\000\000\000\000\000\000\0
> 00\000\000\000pb\001\000\302", '\000' <repeats 43 times>,
> "\240b\001\000\302", '\000' <repeats 43 times>, "\320b\001\000\302", '\000'
> <repeats 44 times>, "c\001\000\302\000
> \000\000"...
> (gdb) XFAIL: gdb.go/hello.exp: Starting string check
>
I can reproduce this with the google go compiler (go1.11.13).
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26405-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 20 11:44:53 2020
Return-Path: <gdb-prs-return-26405-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 23096 invoked by alias); 20 Feb 2020 11:44:53 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 23074 invoked by uid 48); 20 Feb 2020 11:44:53 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug go/17018] XFAIL: gdb.go/hello.exp: Starting string check
Date: Thu, 20 Feb 2020 11:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: go
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-17018-4717-6pvkZbGbEG@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17018-4717@http.sourceware.org/bugzilla/>
References: <bug-17018-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00320.txt
Content-length: 1700
https://sourceware.org/bugzilla/show_bug.cgi?id=17018
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Pedro Alves from comment #0)
> The comment in the test says this is XFAIL for a different reason:
>
> # This used to print "", i.e., the local "st" initialized as "".
> setup_xfail "*-*-*"
>
> gdb_test "print st" \
> ".* = $hex \"\"" \
> "Starting string check"
>
> So I wonder if this is really expected.
I'd say a more accurate formulation of the xfail would be:
...
diff --git a/gdb/testsuite/gdb.go/hello.exp b/gdb/testsuite/gdb.go/hello.exp
index 1096f6475b..d857a69dee 100644
--- a/gdb/testsuite/gdb.go/hello.exp
+++ b/gdb/testsuite/gdb.go/hello.exp
@@ -34,12 +34,17 @@ if { [go_runto_main] < 0 } {
return -1
}
-# This used to print "", i.e., the local "st" initialized as "".
-setup_xfail "*-*-*"
-
-gdb_test "print st" \
- ".* = $hex \"\"" \
- "starting string check"
+gdb_test_multiple "print st" "starting string check" {
+ -re -wrap "No symbol \"st\" in current context" {
+ pass $gdb_test_name
+ }
+ -re -wrap ".*" {
+ # GCC PR 93844 (Same problem with google go compiler go1.11.13).
+ # Due to the PR, gdb prints an uninitialized value, which can manifest
+ # as '$3 = 0x0 ""', but also as printing a wild pointer.
+ xfail $gdb_test_name
+ }
+}
if { [gdb_breakpoint ${srcfile}:${bp_location1}] } {
pass "setting breakpoint 1"
...
I wonder though if that's all a bit too complicated for what should be "basic
tests". We could also just remove the print of the out-of-scope variable.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26406-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 20 12:41:44 2020
Return-Path: <gdb-prs-return-26406-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 103563 invoked by alias); 20 Feb 2020 12:41:43 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 103545 invoked by uid 48); 20 Feb 2020 12:41:43 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug go/17018] XFAIL: gdb.go/hello.exp: Starting string check
Date: Thu, 20 Feb 2020 12:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: go
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-17018-4717-4o7MYCp0bK@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17018-4717@http.sourceware.org/bugzilla/>
References: <bug-17018-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00321.txt
Content-length: 548
https://sourceware.org/bugzilla/show_bug.cgi?id=17018
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #4)
> I wonder though if that's all a bit too complicated for what should be
> "basic tests". We could also just remove the print of the out-of-scope
> variable.
After some more consideration, I went for a two-testcase solution. Submitted
here: https://sourceware.org/ml/gdb-patches/2020-02/msg00818.html .
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26407-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 20 14:26:35 2020
Return-Path: <gdb-prs-return-26407-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 80822 invoked by alias); 20 Feb 2020 14:26:34 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 80798 invoked by uid 48); 20 Feb 2020 14:26:34 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25534] [cc-with-dwz] FAIL: gdb.cp/m-static.exp: static
const int initialized elsewhere
Date: Thu, 20 Feb 2020 14: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: vries 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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25534-4717-7XicRoU859@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25534-4717@http.sourceware.org/bugzilla/>
References: <bug-25534-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00322.txt
Content-length: 500
https://sourceware.org/bugzilla/show_bug.cgi?id=25534
--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #6)
> The difference in behaviour seems to come from dropping the
> dependencies[i]->user == NULL test.
>
> Using this patch, we reintroduce it and get the test passing again:
Submitted as https://sourceware.org/ml/gdb-patches/2020-02/msg00820.html .
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26408-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 20 16:47:13 2020
Return-Path: <gdb-prs-return-26408-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 80907 invoked by alias); 20 Feb 2020 16:47:12 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 80878 invoked by uid 55); 20 Feb 2020 16:47:11 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug go/17018] XFAIL: gdb.go/hello.exp: Starting string check
Date: Thu, 20 Feb 2020 16:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: go
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: <bug-17018-4717-i4Gb49Kym2@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17018-4717@http.sourceware.org/bugzilla/>
References: <bug-17018-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00323.txt
Content-length: 2758
https://sourceware.org/bugzilla/show_bug.cgi?id=17018
--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a9c798035de33ccc3bc3e494449bbe931e900372
commit a9c798035de33ccc3bc3e494449bbe931e900372
Author: Tom de Vries <tdevries@suse.de>
Date: Thu Feb 20 17:46:17 2020 +0100
[gdb/testsuite] Fix hello.go xpass
With gdb.go/hello.go, we run into an xpass:
...
Thread 1 "hello" hit Breakpoint 1, main.main () at hello.go:7^M
7 func main () {^M
(gdb) print st^M
$1 = 0x0 ""^M
(gdb) XPASS: gdb.go/hello.exp: starting string check
...
The xfail is setup as follows:
...
\# This used to print "", i.e., the local "st" initialized as "".
setup_xfail "*-*-*"
gdb_test "print st" \
".* = $hex \"\"" \
"starting string check"
...
It's not clear what gccgo/gc PR this xfail refers to.
It's also not clear why the empty string is both:
- listed as reason for xfail, and
- used in the pass pattern.
Furthermore, there's a comment in the hello.go testcase:
...
st := "Hello, world!" // this intentionally shadows the global "st"
...
while there's no global st variable present, only a variable myst:
...
var myst = "Shall we?"
...
Fix this by splitting up the test-case in two test-cases, hello.{go,exp}
and
global-local-var-shadow.{go,exp}.
In hello.exp we no longer attempt to print st before its declaration. In
hello.go we remove the myst variable as well the comment related to
shadowing.
In global-local-var-shadow.go, we rename myst to st, such that the comment
related to shadowing is correct. In global-local-var-shadow.exp we attempt
to
print the value of st before the local definition, which should print the
value of the global definition, and xfail this with reference to GCC
PR93844.
Tested on x86_64-linux, with gccgo 10.
gdb/testsuite/ChangeLog:
2020-02-20 Tom de Vries <tdevries@suse.de>
PR go/17018
* gdb.go/hello.exp: Copy ...
* gdb.go/global-local-var-shadow.exp: ... here. New file. Expect
print of st to print value of global definition. Add xfail for GCC
PR93844.
* gdb.go/hello.exp: Remove printing of st before definition.
* gdb.go/hello.go: Copy ...
* gdb.go/global-local-var-shadow.go: ... here. New test. Rename myst
to st.
* gdb.go/hello.go: Remove myst. Remove comment about shadowing.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26409-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 20 16:57:11 2020
Return-Path: <gdb-prs-return-26409-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 2460 invoked by alias); 20 Feb 2020 16:57:10 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 2437 invoked by uid 48); 20 Feb 2020 16:57:10 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug go/17018] XFAIL: gdb.go/hello.exp: Starting string check
Date: Thu, 20 Feb 2020 16:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: go
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-17018-4717-xMeTKsZiBN@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17018-4717@http.sourceware.org/bugzilla/>
References: <bug-17018-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00324.txt
Content-length: 540
https://sourceware.org/bugzilla/show_bug.cgi?id=17018
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
Test-case updated, marking resolved-fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26410-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 21 15:37:31 2020
Return-Path: <gdb-prs-return-26410-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 59150 invoked by alias); 21 Feb 2020 15:37:30 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 59127 invoked by uid 55); 21 Feb 2020 15:37:29 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25534] [cc-with-dwz] FAIL: gdb.cp/m-static.exp: static
const int initialized elsewhere
Date: Fri, 21 Feb 2020 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: 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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25534-4717-YsiFz29Enm@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25534-4717@http.sourceware.org/bugzilla/>
References: <bug-25534-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00325.txt
Content-length: 1686
https://sourceware.org/bugzilla/show_bug.cgi?id=25534
--- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1eb731795357d77ac1f6200edd04f86d210bec79
commit 1eb731795357d77ac1f6200edd04f86d210bec79
Author: Tom de Vries <tdevries@suse.de>
Date: Fri Feb 21 16:36:48 2020 +0100
[gdb] Fix cc-with-dwz regression
I noticed a regression with board cc-with-dwz:
...
FAIL: gdb.cp/m-static.exp: static const int initialized elsewhere
FAIL: gdb.cp/m-static.exp: info variable everywhere
...
The problem started with commit 0494dbecdf "Consolidate partial symtab
dependency reading".
The commit replaces the dwarf2_psymtab::expand_psymtab specific reading of
dependencies, which contains a "dependencies[i]->user == NULL" test, with a
generic partial_symtab::read_dependencies call, which does not test the
user
field.
This patch fixes the regression by adding back the test, in the generic
partial_symtab::read_dependencies.
Build and reg-tested on x86_64-linux.
Tested natively, as well as with boards cc-with-dwz and cc-with-dwz-m.
The patch fixes all 33 regressions with cc-with-dwz, and all 2929
regression
with cc-with-dwz-m.
gdb/ChangeLog:
2020-02-21 Tom de Vries <tdevries@suse.de>
PR gdb/25534
* psymtab.c (partial_symtab::read_dependencies): Don't read dependency
if dependencies[i]->user != NULL.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26411-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 21 15:37:58 2020
Return-Path: <gdb-prs-return-26411-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 59679 invoked by alias); 21 Feb 2020 15:37:57 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 59659 invoked by uid 48); 21 Feb 2020 15:37:57 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25534] [cc-with-dwz] FAIL: gdb.cp/m-static.exp: static
const int initialized elsewhere
Date: Fri, 21 Feb 2020 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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-25534-4717-bQIwkvX8iz@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25534-4717@http.sourceware.org/bugzilla/>
References: <bug-25534-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00326.txt
Content-length: 538
https://sourceware.org/bugzilla/show_bug.cgi?id=25534
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Tom de Vries <vries at gcc dot gnu.org> ---
Patch committed, marking resolved-fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26412-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 21 19:48:16 2020
Return-Path: <gdb-prs-return-26412-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 121104 invoked by alias); 21 Feb 2020 19:48:15 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 121076 invoked by uid 55); 21 Feb 2020 19:48:14 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug go/18926] FAIL: gdb.go/methods.exp: setting breakpoint at
main.T.Foo
Date: Fri, 21 Feb 2020 19:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: go
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: <bug-18926-4717-jW6Jw1S99j@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-18926-4717@http.sourceware.org/bugzilla/>
References: <bug-18926-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00327.txt
Content-length: 4523
https://sourceware.org/bugzilla/show_bug.cgi?id=18926
--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=755251522afd2f33de7e64f8a30ddd732f30b2de
commit 755251522afd2f33de7e64f8a30ddd732f30b2de
Author: Tom de Vries <tdevries@suse.de>
Date: Fri Feb 21 20:47:28 2020 +0100
[gdb/testsuite] Fix gdb.go/methods.exp
With gccgo-6/7, we have:
...
FAIL: gdb.go/methods.exp: setting breakpoint at main.T.Foo
XFAIL: gdb.go/methods.exp: going to first breakpoint \
(the program exited)
FAIL: gdb.go/methods.exp: setting breakpoint at (*main.T).Bar
XFAIL: gdb.go/methods.exp: going to second breakpoint \
(the program is no longer running)
...
And with gccgo-8/9/10, we have:
...
PASS: gdb.go/methods.exp: setting breakpoint 1
XFAIL: gdb.go/methods.exp: going to first breakpoint
FAIL: gdb.go/methods.exp: setting breakpoint at (*main.T).Bar
XFAIL: gdb.go/methods.exp: going to second breakpoint \
(the program exited)
...
The first test passes and fails with different messages:
...
FAIL: gdb.go/methods.exp: setting breakpoint at main.T.Foo
...
or:
...
PASS: gdb.go/methods.exp: setting breakpoint 1
...
Fix this by removing the explicit pass call and using the message argument
for
gdb_breakpoint, for both breakpoint locations.
The setup of the xfails is non-specific:
...
setup_xfail "*-*-*" ;# mangling issues IIRC
...
so let's start with removing these.
The first FAIL with gccgo-6:
...
FAIL: gdb.go/methods.exp: setting breakpoint at main.T.Foo
...
is due an incorrect DW_AT_name attribute:
...
# <554> DW_AT_name : main.Foo.N6_main.T
...
Fix this by recognizing the incorrect attribute, and xfailing the test.
Furthermore, if setting the breakpoint fails, there's not much point in
trying
to continue to the breakpoint:
...
FAIL: gdb.go/methods.exp: setting breakpoint at main.T.Foo
FAIL: gdb.go/methods.exp: going to first breakpoint (the program exited)
...
Fix this by skipping the second test if the first one fails, also for the
second breakpoint.
With gccgo-10, we manage to set the first breakpoint, but continuing to
breakpoint test fails:
...
PASS: gdb.go/methods.exp: setting breakpoint 1
FAIL: gdb.go/methods.exp: going to first breakpoint
...
This is due to an incorrect regexp, requiring a colon in front of the
breakpoint location. Fix this for both breakpoints.
Setting the second breakpoint fails:
...
FAIL: gdb.go/methods.exp: setting breakpoint at (*main.T).Bar
...
presumably because the breakpoint location "(*main.T).Bar" does not follow
the
naming convention explained at https://golang.org/doc/gdb#Naming. Fix this
by
updating the breakpoint location to "main.(*T).Bar".
Still this test fails, for gccgo-6/7 because of an incorrect DW_AT_name
attribute:
...
# <529> DW_AT_name : main.Bar.pN6_main.T
...
and for gccgo-8/9/10 because of incorrect DW_AT_name/DW_AT_linkage_name
attributes (filed as gcc PR93866):
...
# <6e5> DW_AT_name : main.Bar..1main.T
# <6ec> DW_AT_linkage_name: main.T.Bar
..
Add xfails for both of these.
All in all, now we have with gccgo-6/7:
...
XFAIL: gdb.go/methods.exp: setting breakpoint at main.T.Foo
XFAIL: gdb.go/methods.exp: setting breakpoint at main.(*T).Bar
...
and with gccgo-8/9/10, we have:
...
PASS: gdb.go/methods.exp: setting breakpoint at main.T.Foo
PASS: gdb.go/methods.exp: going to first breakpoint
XFAIL: gdb.go/methods.exp: setting breakpoint at main.(*T).Bar
...
Tested on x86_64-linux with gccgo-6/7/8/9/10.
gdb/testsuite/ChangeLog:
2020-02-21 Tom de Vries <tdevries@suse.de>
PR go/18926
* lib/gdb.exp (bp_location2/bp_location2_regexp): Fix.
Remove blanket xfails. Use message argument for gdb_breakpoint.
Make continuing to breakpoint test conditional on setting breakpoint.
Fix continuing to breakpoint regexp. Add xfails for gccgo-6/7
DW_AT_name attribute. Add xfail for GCC PR93866.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26413-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 22 17:43:55 2020
Return-Path: <gdb-prs-return-26413-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 64889 invoked by alias); 22 Feb 2020 17:43:54 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 64856 invoked by uid 48); 22 Feb 2020 17:43:54 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25542] Crash in TUI mode
Date: Sat, 22 Feb 2020 17:43: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.3.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: <bug-25542-4717-5UV5CeHQD7@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25542-4717@http.sourceware.org/bugzilla/>
References: <bug-25542-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00328.txt
Content-length: 574
https://sourceware.org/bugzilla/show_bug.cgi?id=25542
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
Could you try gdb 9?
We probably won't try to fix 8.3 but there may be another release
from the 9 branch.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26414-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 22 19:56:51 2020
Return-Path: <gdb-prs-return-26414-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 22156 invoked by alias); 22 Feb 2020 19:56:50 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 22137 invoked by uid 48); 22 Feb 2020 19:56:50 -0000
From: "eliz at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25586] New: Resizing the source/disassembly or commend
window produces corrupted display
Date: Sat, 22 Feb 2020 19:56: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: 9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eliz 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
Message-ID: <bug-25586-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00329.txt
Content-length: 765
https://sourceware.org/bugzilla/show_bug.cgi?id=25586
Bug ID: 25586
Summary: Resizing the source/disassembly or commend window
produces corrupted display
Product: gdb
Version: 9.1
Status: NEW
Severity: normal
Priority: P2
Component: tui
Assignee: unassigned at sourceware dot org
Reporter: eliz at gnu dot org
Target Milestone: ---
This was reported by Aleksey Midenkov <midenok@gmail.com> on the gdb mailing
list.
After starting GDB 9.1, the command "winheight src +8" produces corrupted
display because the command window overlaps the source window.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26415-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 22 20:02:32 2020
Return-Path: <gdb-prs-return-26415-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 31208 invoked by alias); 22 Feb 2020 20:02:31 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 31190 invoked by uid 48); 22 Feb 2020 20:02:31 -0000
From: "eliz at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25586] Resizing the source/disassembly or commend window
produces corrupted display
Date: Sat, 22 Feb 2020 20:02: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: 9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eliz 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: attachments.created
Message-ID: <bug-25586-4717-TLYLBRLuhV@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25586-4717@http.sourceware.org/bugzilla/>
References: <bug-25586-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00330.txt
Content-length: 359
https://sourceware.org/bugzilla/show_bug.cgi?id=25586
--- Comment #1 from Eli Zaretskii <eliz at gnu dot org> ---
Created attachment 12312
--> https://sourceware.org/bugzilla/attachment.cgi?id=12312&action=edit
Proposed patch to fix problems with resizing TUI windows
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26416-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 22 20:14:04 2020
Return-Path: <gdb-prs-return-26416-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 22094 invoked by alias); 22 Feb 2020 20:14:03 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 22071 invoked by uid 48); 22 Feb 2020 20:14:03 -0000
From: "eliz at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25586] Resizing the source/disassembly or commend window
produces corrupted display
Date: Sat, 22 Feb 2020 20:14: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: 9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eliz 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: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-25586-4717-0jxbJ8oRgS@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25586-4717@http.sourceware.org/bugzilla/>
References: <bug-25586-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00331.txt
Content-length: 368
https://sourceware.org/bugzilla/show_bug.cgi?id=25586
Eli Zaretskii <eliz at gnu dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.1
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26417-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 22 20:16:34 2020
Return-Path: <gdb-prs-return-26417-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 23917 invoked by alias); 22 Feb 2020 20:16:33 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 23893 invoked by uid 48); 22 Feb 2020 20:16:32 -0000
From: "eliz at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25586] Resizing the source/disassembly or commend window
produces corrupted display
Date: Sat, 22 Feb 2020 20:16: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: 9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eliz at gnu 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: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-25586-4717-OwFACDHFDX@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25586-4717@http.sourceware.org/bugzilla/>
References: <bug-25586-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00332.txt
Content-length: 523
https://sourceware.org/bugzilla/show_bug.cgi?id=25586
Eli Zaretskii <eliz at gnu dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Eli Zaretskii <eliz at gnu dot org> ---
Fixed on the gdb-9-branch branch.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26418-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 22 22:25:58 2020
Return-Path: <gdb-prs-return-26418-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 93919 invoked by alias); 22 Feb 2020 22:25:58 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 93901 invoked by uid 48); 22 Feb 2020 22:25:57 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25587] New: tui testcase wrapping issue
Date: Sat, 22 Feb 2020 22:25: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: vries 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: <bug-25587-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00333.txt
Content-length: 5687
https://sourceware.org/bugzilla/show_bug.cgi?id=25587
Bug ID: 25587
Summary: tui testcase wrapping issue
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Running gdb.tui/*.exp, and tracking execution time:
...
$ tail -F gdb.sum -n +1 | ./prefix-time.sh 2>&1 | tee LOG
...
there is just one long running test (10 seconds):
...
$ egrep -v "^(0|1):" LOG
10: PASS: gdb.tui/main.exp: show main after file
...
Using a bit more verbosity in the log:
...
diff --git a/gdb/testsuite/lib/tuiterm.exp b/gdb/testsuite/lib/tuiterm.exp
index da5580324a..116dde048d 100644
--- a/gdb/testsuite/lib/tuiterm.exp
+++ b/gdb/testsuite/lib/tuiterm.exp
@@ -424,6 +424,9 @@ namespace eval Term {
}
timeout {
+ verbose -log "\nwait_for: TIMEOUT: regexp: $wait_for"
+ verbose -log "wait_for: TIMEOUT: last line ($_cur_y):
$prev"
+ dump_screen
# Assume a timeout means we somehow missed the
# expected result, and carry on.
return 0
@@ -443,6 +446,10 @@ namespace eval Term {
break
}
set wait_for $prompt_wait_for
+ } {
+ verbose -log "\nwait_for: MATCH FAILED: regexp: $wait_for"
+ verbose -log "wait_for: MATCH FAILED: last line ($_cur_y):
$prev"
+ dump_screen
}
}
...
we find:
...
wait_for: MATCH FAILED: regexp: file
/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb\.tui/main/main
wait_for: MATCH FAILED: last line (18): n
...
Screen Dump (80 x 24):
0
+------------------------------------------------------------------------------+
1 |
|
2 |
|
3 |
|
4 |
|
5 |
|
6 |
|
7 | [ No Source Available ]
|
8 |
|
9 |
|
10 |
|
11 |
|
12 |
|
13 |
|
14
+------------------------------------------------------------------------------+
15 None No process In: L??
PC: ??
16 (gdb)
17 (gdb) file
/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.tui/main/mai
18 n
...
So, what happens is:
1.
in proc command, we do send_gdb "file
/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.tui/main/main\n"
2.
the tui adds that string after the prompt on line 17, and wraps it to the next
line
3.
we try to match the full command string, but we do that using the last line,
which at that point is "n", and the match fails, making wait_for time out.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26419-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 22 22:26:37 2020
Return-Path: <gdb-prs-return-26419-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 94323 invoked by alias); 22 Feb 2020 22:26:37 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 94301 invoked by uid 48); 22 Feb 2020 22:26:36 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25587] tui testcase wrapping issue
Date: Sat, 22 Feb 2020 22:26: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: vries 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: <bug-25587-4717-vrsJbhaf6p@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25587-4717@http.sourceware.org/bugzilla/>
References: <bug-25587-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00334.txt
Content-length: 399
https://sourceware.org/bugzilla/show_bug.cgi?id=25587
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26420-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 22 22:36:57 2020
Return-Path: <gdb-prs-return-26420-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 16996 invoked by alias); 22 Feb 2020 22:36:56 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 16975 invoked by uid 48); 22 Feb 2020 22:36:56 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25587] tui testcase wrapping issue
Date: Sat, 22 Feb 2020 22: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: vries 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: <bug-25587-4717-lbkNKWE07q@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25587-4717@http.sourceware.org/bugzilla/>
References: <bug-25587-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00335.txt
Content-length: 1877
https://sourceware.org/bugzilla/show_bug.cgi?id=25587
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
FWIW, it's a bit odd that this timeout does not cause a FAIL.
Using something link this:
...
diff --git a/gdb/testsuite/gdb.tui/main.exp b/gdb/testsuite/gdb.tui/main.exp
index ae2393e6e9..3c488adbf0 100644
--- a/gdb/testsuite/gdb.tui/main.exp
+++ b/gdb/testsuite/gdb.tui/main.exp
@@ -33,7 +33,7 @@ if {![Term::enter_tui]} {
unsupported "TUI not supported"
}
-Term::command "file [standard_output_file $testfile]"
+Term::command "file [standard_output_file $testfile]" "load file"
Term::check_contents "show main after file" "\\|.*21 *return 0"
# Ensure that "file" clears the source window.
diff --git a/gdb/testsuite/lib/tuiterm.exp b/gdb/testsuite/lib/tuiterm.exp
index da5580324a..1adff34d60 100644
--- a/gdb/testsuite/lib/tuiterm.exp
+++ b/gdb/testsuite/lib/tuiterm.exp
@@ -492,9 +492,16 @@ namespace eval Term {
# Send the command CMD to gdb, then wait for a gdb prompt to be
# seen in the TUI. CMD should not end with a newline -- that will
# be supplied by this function.
- proc command {cmd} {
+ proc command {cmd {name ""}} {
+ if { $name == ""} {
+ set name $cmd
+ }
send_gdb "$cmd\n"
- wait_for [string_to_regexp $cmd]
+ if { [wait_for [string_to_regexp $cmd]] } {
+ pass "Term::command: $name"
+ } else {
+ fail "Term::command: $name"
+ }
}
# Return the text of screen line N, without attributes. Lines are
...
we get:
...
Running src/gdb/testsuite/gdb.tui/main.exp ...
FAIL: gdb.tui/main.exp: Term::command: load file
=== gdb Summary ===
# of expected passes 7
# of unexpected failures 1
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26421-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat Feb 22 22:56:16 2020
Return-Path: <gdb-prs-return-26421-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 32826 invoked by alias); 22 Feb 2020 22:56:15 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 32802 invoked by uid 48); 22 Feb 2020 22:56:15 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25542] Crash in TUI mode
Date: Sat, 22 Feb 2020 22: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25542-4717-jIkIsz21dn@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25542-4717@http.sourceware.org/bugzilla/>
References: <bug-25542-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00336.txt
Content-length: 417
https://sourceware.org/bugzilla/show_bug.cgi?id=25542
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #2)
> Could you try gdb 9?
> We probably won't try to fix 8.3 but there may be another release
> from the 9 branch.
Reproduced at 8.3 branch point, works fine with gdb-9-branch.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26422-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 23 07:17:33 2020
Return-Path: <gdb-prs-return-26422-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 123154 invoked by alias); 23 Feb 2020 07:17:33 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 123126 invoked by uid 48); 23 Feb 2020 07:17:32 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25542] Crash in TUI mode
Date: Sun, 23 Feb 2020 07:17: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25542-4717-gu7yKKtbbO@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25542-4717@http.sourceware.org/bugzilla/>
References: <bug-25542-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00337.txt
Content-length: 1007
https://sourceware.org/bugzilla/show_bug.cgi?id=25542
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #3)
> (In reply to Tom Tromey from comment #2)
> > Could you try gdb 9?
> > We probably won't try to fix 8.3 but there may be another release
> > from the 9 branch.
>
> Reproduced at 8.3 branch point, works fine with gdb-9-branch.
In more detail, first passing commit:
...
commit 53e7cdbaa1d8c0c53038226de07d8160d7f66d82
Author: Tom Tromey <tom@tromey.com>
Date: Sun Jun 23 14:27:04 2019 -0600
Remove union tui_which_element
This removes union tui_which_element, instead moving the content
directly into tui_source_window_base. This allows for the deletion of
a fair amount of code. Now the TUI window hierarchy is more
type-safe. In particular, there is never any confusion now about
which members are in use by which subtype.
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26423-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 23 08:51:39 2020
Return-Path: <gdb-prs-return-26423-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 7095 invoked by alias); 23 Feb 2020 08:51:39 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 7072 invoked by uid 48); 23 Feb 2020 08:51:39 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25542] Crash in TUI mode
Date: Sun, 23 Feb 2020 08:51: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25542-4717-x5i22dBc1t@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25542-4717@http.sourceware.org/bugzilla/>
References: <bug-25542-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00338.txt
Content-length: 2251
https://sourceware.org/bugzilla/show_bug.cgi?id=25542
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #4)
> (In reply to Tom de Vries from comment #3)
> > (In reply to Tom Tromey from comment #2)
> > > Could you try gdb 9?
> > > We probably won't try to fix 8.3 but there may be another release
> > > from the 9 branch.
> >
> > Reproduced at 8.3 branch point, works fine with gdb-9-branch.
>
> In more detail, first passing commit:
> ...
> commit 53e7cdbaa1d8c0c53038226de07d8160d7f66d82
> Author: Tom Tromey <tom@tromey.com>
> Date: Sun Jun 23 14:27:04 2019 -0600
>
> Remove union tui_which_element
>
> This removes union tui_which_element, instead moving the content
> directly into tui_source_window_base. This allows for the deletion of
> a fair amount of code. Now the TUI window hierarchy is more
> type-safe. In particular, there is never any confusion now about
> which members are in use by which subtype.
> ...
And first failing commit:
...
commit 0c820d679358aa1ec7cd9e33c4bc23a7db964ea1
Author: Tom Tromey <tom@tromey.com>
Date: Mon Jan 28 13:21:35 2019 -0700
Fix some valgrind errors in the TUI
The styling series introduced some new errors in the TUI -- the series
changed how source lines are allocated, without updating
tui_set_source_content_nil.
There are several failures but a typical one looks like:
==6274== Use of uninitialised value of size 8
==6274== at 0x4E4A095: wclrtoeol (in /usr/lib64/libncursesw.so.6.1)
==6274== by 0x4E47617: waddch (in /usr/lib64/libncursesw.so.6.1)
==6274== by 0x8325CB: tui_puts_internal(_win_st*, char const*, int*)
(tui-io.c:393)
==6274== by 0x82E89D: tui_file::puts(char const*) (tui-file.c:39)
==6274== by 0x84BF5F: vfprintf_unfiltered(ui_file*, char const*,
__va_list_tag*) (utils.c:2026)
This patch rewrites tui_set_source_content_nil, fixing the bug.
This was also reported as PR tui/24197.
Verified by running valgrind before and after on x86-64 Fedora 29.
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26424-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 23 08:59:40 2020
Return-Path: <gdb-prs-return-26424-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 11131 invoked by alias); 23 Feb 2020 08:59:40 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 11109 invoked by uid 48); 23 Feb 2020 08:59:39 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25542] Crash in TUI mode
Date: Sun, 23 Feb 2020 08: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25542-4717-w61bDdJOd2@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25542-4717@http.sourceware.org/bugzilla/>
References: <bug-25542-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00339.txt
Content-length: 259
https://sourceware.org/bugzilla/show_bug.cgi?id=25542
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
Propose to mark resolved-fixed with target milestone 9.1.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26425-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Feb 23 17:29:47 2020
Return-Path: <gdb-prs-return-26425-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 1692 invoked by alias); 23 Feb 2020 17:29:46 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 1667 invoked by uid 48); 23 Feb 2020 17:29:45 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25542] Crash in TUI mode
Date: Sun, 23 Feb 2020 17: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: 8.3.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: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-25542-4717-cblioiV95M@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25542-4717@http.sourceware.org/bugzilla/>
References: <bug-25542-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00340.txt
Content-length: 594
https://sourceware.org/bugzilla/show_bug.cgi?id=25542
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.1
--- Comment #7 from Tom Tromey <tromey at sourceware dot org> ---
Agreed. Thanks for tracking this down.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26426-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 24 08:31:11 2020
Return-Path: <gdb-prs-return-26426-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 56145 invoked by alias); 24 Feb 2020 08:31:10 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 56043 invoked by uid 48); 24 Feb 2020 08:31:00 -0000
From: "tim@mr-dog.net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/10079] Commands attached to a breakpoint do not
execute without an interactive prompt
Date: Mon, 24 Feb 2020 08: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tim@mr-dog.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: 6.8
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-10079-4717-plOkhii2hC@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-10079-4717@http.sourceware.org/bugzilla/>
References: <bug-10079-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00341.txt
Content-length: 748
https://sourceware.org/bugzilla/show_bug.cgi?id=10079
Tim Jones <tim@mr-dog.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tim@mr-dog.net
--- Comment #10 from Tim Jones <tim@mr-dog.net> ---
Just hit this with GNU gdb (GDB) 9.1.90.20200224-git.
Took a while before I assumed this could have been a bug in gdb and found this
bug report. Had been searching for a bug in our testing scripts!
Is there a gdb command which may trigger this to work which can be -ex'd after
sourcing a script and running the target?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26427-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 24 10:44:13 2020
Return-Path: <gdb-prs-return-26427-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 73262 invoked by alias); 24 Feb 2020 10:44:12 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 73188 invoked by uid 48); 24 Feb 2020 10:44:12 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25592] New: info locals does not print static var with
DW_AT_const_value
Date: Mon, 24 Feb 2020 10: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25592-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00342.txt
Content-length: 2187
https://sourceware.org/bugzilla/show_bug.cgi?id=25592
Bug ID: 25592
Summary: info locals does not print static var with
DW_AT_const_value
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Consider test-case test.c:
...
int c = 1;
static int d = 2;
int
main (void)
{
int a = 1;
static int b = 2;
return b;
}
...
Compiled with debug info:
...
$ gcc -g test.c
...
When printing info locals, we get both vars a and b:
...
$ gdb a.out -batch -ex start -ex "info locals"
Temporary breakpoint 1 at 0x40049b: file test.c, line 7.
Temporary breakpoint 1, main () at test.c:7
7 int a = 1;
a = 0
b = 2
...
Now modify the example in the following way:
...
- return b;
+ return 0;
...
and recompile.
Now we have only var a:
...
$ gdb a.out -batch -ex start -ex "info locals"
Temporary breakpoint 1 at 0x40049b: file test.c, line 7.
Temporary breakpoint 1, main () at test.c:7
7 int a = 1;
a = 0
...
In the dwarf, we can see what is different: b doesn't have a DW_AT_location,
but a DW_AT_const_value instead:
...
<2><13e>: Abbrev Number: 4 (DW_TAG_variable)
<13f> DW_AT_name : a
<141> DW_AT_decl_file : 1
<142> DW_AT_decl_line : 7
<143> DW_AT_type : <0x107>
<147> DW_AT_location : 2 byte block: 91 6c (DW_OP_fbreg: -20)
<2><14a>: Abbrev Number: 6 (DW_TAG_variable)
<14b> DW_AT_name : b
<14d> DW_AT_decl_file : 1
<14e> DW_AT_decl_line : 8
<14f> DW_AT_type : <0x107>
<153> DW_AT_const_value : 2
...
The info locals documentation states:
...
Print the local variables of the selected frame, each on a separate line. These
are all variables (declared either static or automatic) accessible at the point
of execution of the selected frame.
...
So, it's a bug that info locals does not print b.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26428-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 24 10:47:50 2020
Return-Path: <gdb-prs-return-26428-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 78347 invoked by alias); 24 Feb 2020 10:47:50 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 78329 invoked by uid 48); 24 Feb 2020 10:47:49 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25592] info locals does not print static var with
DW_AT_const_value
Date: Mon, 24 Feb 2020 10: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: vries 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: <bug-25592-4717-dDihEXZnR6@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25592-4717@http.sourceware.org/bugzilla/>
References: <bug-25592-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00343.txt
Content-length: 774
https://sourceware.org/bugzilla/show_bug.cgi?id=25592
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Using this tentative fix:
...
diff --git a/gdb/stack.c b/gdb/stack.c
index af30405f29..266d771e35 100644
--- a/gdb/stack.c
+++ b/gdb/stack.c
@@ -2237,6 +2237,7 @@ iterate_over_block_locals (const struct block *b,
{
switch (SYMBOL_CLASS (sym))
{
+ case LOC_CONST:
case LOC_LOCAL:
case LOC_REGISTER:
case LOC_STATIC:
...
we get:
...
$ gdb a.out -batch -ex start -ex "info locals"
Temporary breakpoint 1 at 0x40049b: file test.c, line 7.
Temporary breakpoint 1, main () at test.c:7
7 int a = 1;
a = 0
b = 2
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26429-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 24 11:59:05 2020
Return-Path: <gdb-prs-return-26429-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 120498 invoked by alias); 24 Feb 2020 11:59:05 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 120172 invoked by uid 48); 24 Feb 2020 11:59:05 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25592] info locals does not print static var with
DW_AT_const_value
Date: Mon, 24 Feb 2020 11: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: vries 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: <bug-25592-4717-jtu2Dj3Ml6@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25592-4717@http.sourceware.org/bugzilla/>
References: <bug-25592-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00344.txt
Content-length: 286
https://sourceware.org/bugzilla/show_bug.cgi?id=25592
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Patch submitted at https://sourceware.org/ml/gdb-patches/2020-02/msg00919.html
.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26430-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 24 14:33:19 2020
Return-Path: <gdb-prs-return-26430-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 38356 invoked by alias); 24 Feb 2020 14:33:19 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 38337 invoked by uid 55); 24 Feb 2020 14:33:18 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25592] info locals does not print static var with
DW_AT_const_value
Date: Mon, 24 Feb 2020 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: 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: <bug-25592-4717-8ocuOx7Fel@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25592-4717@http.sourceware.org/bugzilla/>
References: <bug-25592-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00345.txt
Content-length: 2018
https://sourceware.org/bugzilla/show_bug.cgi?id=25592
--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a88ef40d0f21342bb5ce01ce677846995ca0d133
commit a88ef40d0f21342bb5ce01ce677846995ca0d133
Author: Tom de Vries <tdevries@suse.de>
Date: Mon Feb 24 15:32:36 2020 +0100
[gdb] Ensure listing of unused static var in info locals
Consider a test-case compiled with -g:
...
int main (void) {
static int b = 2;
return 0;
}
...
When running info locals in main, we get:
...
(gdb) info locals
No locals.
...
The info locals documentation states:
...
Print the local variables of the selected frame, each on a separate line.
These are all variables (declared either static or automatic) accessible at
the point of execution of the selected frame.
...
So, "info locals" should have printed static variable b.
The variable is present in dwarf info:
...
<2><14a>: Abbrev Number: 6 (DW_TAG_variable)
<14b> DW_AT_name : b
<153> DW_AT_const_value : 2
...
but instead of a location attribute, it has a const_value attribute, which
causes the corresponding symbol to have LOC_CONST, which causes info locals
to
skip it.
Fix this by handling LOC_CONST in iterate_over_block_locals.
Build and reg-tested on x86_64-linux.
gdb/ChangeLog:
2020-02-24 Tom de Vries <tdevries@suse.de>
PR gdb/25592
* stack.c (iterate_over_block_locals): Handle LOC_CONST.
gdb/testsuite/ChangeLog:
2020-02-24 Tom de Vries <tdevries@suse.de>
PR gdb/25592
* gdb.base/info-locals-unused-static-var.c: New test.
* gdb.base/info-locals-unused-static-var.exp: New file.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26431-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 24 14:34:24 2020
Return-Path: <gdb-prs-return-26431-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 40706 invoked by alias); 24 Feb 2020 14:34:24 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 40644 invoked by uid 48); 24 Feb 2020 14:34:23 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25592] info locals does not print static var with
DW_AT_const_value
Date: Mon, 24 Feb 2020 14: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: vries 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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-25592-4717-k0cwSRzTSR@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25592-4717@http.sourceware.org/bugzilla/>
References: <bug-25592-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00346.txt
Content-length: 607
https://sourceware.org/bugzilla/show_bug.cgi?id=25592
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.1
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
Patch with test-case committed, marking resolved-fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26432-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 24 15:17:43 2020
Return-Path: <gdb-prs-return-26432-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 60310 invoked by alias); 24 Feb 2020 15:17:43 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 60286 invoked by uid 48); 24 Feb 2020 15:17:43 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug d/22480] `ptype` returns `struct` for D classes
Date: Mon, 24 Feb 2020 15:17: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: 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: cc
Message-ID: <bug-22480-4717-03YCaxtBtJ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22480-4717@http.sourceware.org/bugzilla/>
References: <bug-22480-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00347.txt
Content-length: 887
https://sourceware.org/bugzilla/show_bug.cgi?id=22480
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I think the trailing '*' is probably the hint.
The D language implementation is somewhat incomplete in gdb.
It just uses the C type-printing code -- so what you get is what the
C language code in gdb thinks the type is.
Here it is a pointer to a structure, hence the trailing "*".
Enhancing the D language code is completely possible if you are
interested. Right now it doesn't seem to be under active development.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26433-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 24 17:50:31 2020
Return-Path: <gdb-prs-return-26433-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 55252 invoked by alias); 24 Feb 2020 17:50:30 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 55224 invoked by uid 48); 24 Feb 2020 17:50:30 -0000
From: "joelkevinjones at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/25597] New: Missing ncurses.h causes miscompilation of
python/py-tui.c
Date: Mon, 24 Feb 2020 17:50: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: joelkevinjones 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: <bug-25597-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00348.txt
Content-length: 1682
https://sourceware.org/bugzilla/show_bug.cgi?id=25597
Bug ID: 25597
Summary: Missing ncurses.h causes miscompilation of
python/py-tui.c
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tui
Assignee: unassigned at sourceware dot org
Reporter: joelkevinjones at gmail dot com
Target Milestone: ---
Using commit a98c743fdf721a2333220209ca15e147badb55d1 on a system that doesn't
have ncurses installed, the following results:
In file included from ../../binutils-gdb/gdb/python/py-tui.c:24:0:
../../binutils-gdb/gdb/gdb_curses.h:47:21: fatal error: ncurses.h: No such file
or directory
compilation terminated.
Makefile:1600: recipe for target 'python/py-tui.o' failed
make[2]: *** [python/py-tui.o] Error 1
I can fix it by moving the guard for TUI, but I don't think that is the right
fix,as, at least as I read it, gdb_curses.h has the pre-processor macro
HAVE_NCURSES_H defined, which it shouldn't.
$ git diff
diff --git a/gdb/python/py-tui.c b/gdb/python/py-tui.c
index 4cb86ae..ba44ffb 100644
--- a/gdb/python/py-tui.c
+++ b/gdb/python/py-tui.c
@@ -21,9 +21,9 @@
#include "defs.h"
#include "arch-utils.h"
#include "python-internal.h"
+#ifdef TUI
#include "gdb_curses.h"
-#ifdef TUI
#include "tui/tui-data.h"
#include "tui/tui-io.h"
This is on Ubuntu 16.04.4 LTS with the following:
$ uname -a
Linux gbt2s-8 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:49:43 UTC
2018 aarch64 aarch64 aarch64 GNU/Linux
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26434-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Feb 24 20:14:39 2020
Return-Path: <gdb-prs-return-26434-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 103073 invoked by alias); 24 Feb 2020 20:14:39 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 101351 invoked by uid 48); 24 Feb 2020 20:14:38 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25471] gdb hangs repeating "Couldn't get registers: No such
process" warning after external SIGKILL
Date: Mon, 24 Feb 2020 20: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: vries 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: <bug-25471-4717-gBBLzqJKpZ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25471-4717@http.sourceware.org/bugzilla/>
References: <bug-25471-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00349.txt
Content-length: 278
https://sourceware.org/bugzilla/show_bug.cgi?id=25471
--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
submitted patch: https://sourceware.org/ml/gdb-patches/2020-02/msg00930.html
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26435-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Feb 25 07:15:25 2020
Return-Path: <gdb-prs-return-26435-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 59748 invoked by alias); 25 Feb 2020 07:15:24 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 59714 invoked by uid 55); 25 Feb 2020 07:15:23 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug go/18926] FAIL: gdb.go/methods.exp: setting breakpoint at
main.T.Foo
Date: Tue, 25 Feb 2020 07:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: go
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: <bug-18926-4717-cgbwnGO7xD@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-18926-4717@http.sourceware.org/bugzilla/>
References: <bug-18926-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00350.txt
Content-length: 1069
https://sourceware.org/bugzilla/show_bug.cgi?id=18926
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=70d497007d097a68cbd5e78104619f4f88a09838
commit 70d497007d097a68cbd5e78104619f4f88a09838
Author: Tom de Vries <tdevries@suse.de>
Date: Tue Feb 25 08:14:41 2020 +0100
[gdb/testsuite] Remove gcc/93866 xfail in methods.exp
The test-case gdb.go/methods.exp contains an xfail for PR gcc/93866.
However, that PR has been marked resolved-wontfix, with clarification that
the
gccgo symbol names for methods are correct, even if they're not the same as
for gc.
Remove the xfail.
Tested on x86_64-linux with gccgo-10.
gdb/testsuite/ChangeLog:
2020-02-25 Tom de Vries <tdevries@suse.de>
PR go/18926
* gdb.go/methods.exp: Remove gcc/93866 xfail.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26436-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 26 00:09:31 2020
Return-Path: <gdb-prs-return-26436-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 65912 invoked by alias); 26 Feb 2020 00:09:31 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 65887 invoked by uid 48); 26 Feb 2020 00:09:31 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/14903] incorrect handling of unicode filenames by gdb-mi
Date: Wed, 26 Feb 2020 00:09: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.3
X-Bugzilla-Keywords: mi3
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: <bug-14903-4717-FajOxn94HC@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-14903-4717@http.sourceware.org/bugzilla/>
References: <bug-14903-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00351.txt
Content-length: 1315
https://sourceware.org/bugzilla/show_bug.cgi?id=14903
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
MI is weird here.
It does:
if (c < 0x20 || /* Low control chars */
(c >= 0x7F && c < 0xA0) || /* DEL, High controls */
(sevenbit_strings && c >= 0x80))
.. when deciding whether to quote a character.
Maybe you're disabling sevenbit_strings ... but unfortunately
that 0x80 still falls into the quoting trap.
So, you get a literal "\200" in the output.
200 octal = 0x80.
Some kind of quoting in MI string values seems needed.
But perhaps in MI 3 we could make it so that it only
messes with the few (I guess newline, quote, and backslash)
that actually require quoting.
It's unclear to me that you could really rely on this being
UTF-8 though, even if you made sure to run gdb in a UTF-8
locale. There may be some code path that prints a file name
coming from the filesystem, and those are just bytes.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26437-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 26 07:54:25 2020
Return-Path: <gdb-prs-return-26437-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 34777 invoked by alias); 26 Feb 2020 07:54:25 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 34758 invoked by uid 48); 26 Feb 2020 07:54:24 -0000
From: "noelgrandin at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/25601] New: console output unordered when using breakpoint
commands
Date: Wed, 26 Feb 2020 07:54: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.3
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: noelgrandin 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: <bug-25601-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00352.txt
Content-length: 1062
https://sourceware.org/bugzilla/show_bug.cgi?id=25601
Bug ID: 25601
Summary: console output unordered when using breakpoint
commands
Product: gdb
Version: 8.3
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cli
Assignee: unassigned at sourceware dot org
Reporter: noelgrandin at gmail dot com
Target Milestone: ---
Created attachment 12323
--> https://sourceware.org/bugzilla/attachment.cgi?id=12323&action=edit
log of my console
This is version:
GNU gdb (GDB) Fedora 8.3.50.20190824-30.fc31
If I do something like:
br MyFunc
comm
info args
bt 21
cont
The output is ordered rather strangely. The backtrace seems to come out first,
followed by message of hitting the breakpoint, and then the args.
Also the output from the "bt 21" action seems to be hitting the console more
than once? Very weird.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26438-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 26 08:01:14 2020
Return-Path: <gdb-prs-return-26438-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 85531 invoked by alias); 26 Feb 2020 08:00:51 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 85306 invoked by uid 48); 26 Feb 2020 08:00:25 -0000
From: "noelgrandin at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/25601] console output unordered when using breakpoint
commands
Date: Wed, 26 Feb 2020 08: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: 8.3
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: noelgrandin 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: <bug-25601-4717-ildTzr2nrP@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25601-4717@http.sourceware.org/bugzilla/>
References: <bug-25601-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00353.txt
Content-length: 1218
https://sourceware.org/bugzilla/show_bug.cgi?id=25601
--- Comment #1 from Noel Grandin <noelgrandin at gmail dot com> ---
Hmmm, this breakpoint looks odd:
gdb) info br
Num Type Disp Enb Address What
1 breakpoint keep y <MULTIPLE>
breakpoint already hit 20 times
info args
bt 21
c
1.1 y 0x00007fffd1665048 in (anonymous
namespace)::SwDrawModellListener_Impl::addShapeEventListener(com::sun::star::uno::Reference<com::sun::star::drawing::XShape>
const&,
com::sun::star::uno::Reference<com::sun::star::document::XShapeEventListener>
const&) at sw/source/core/access/accmap.cxx:183
1.2 y 0x00007fffd1665444 <non-virtual thunk to
(anonymous
namespace)::SwDrawModellListener_Impl::addShapeEventListener(com::sun::star::uno::Reference<com::sun::star::drawing::XShape>
const&,
com::sun::star::uno::Reference<com::sun::star::document::XShapeEventListener>
const&)+4>
Some kind of linking issue that means it gets hit twice in quick succession?
And then output is asynchronous somehow?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26439-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 26 11:56:53 2020
Return-Path: <gdb-prs-return-26439-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 14878 invoked by alias); 26 Feb 2020 11:56:53 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 14859 invoked by uid 48); 26 Feb 2020 11:56:53 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25603] New: If language set manually, then loading file
sets language partially
Date: Wed, 26 Feb 2020 11: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-25603-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00354.txt
Content-length: 1484
https://sourceware.org/bugzilla/show_bug.cgi?id=25603
Bug ID: 25603
Summary: If language set manually, then loading file sets
language partially
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Initially, gdb sets the language to auto/c:
...
$ gdb -q
(gdb) show language
The current source language is "auto; currently c".
...
And after loading a c++ executable, that changes to auto/c++:
...
(gdb) file a.out
Reading symbols from a.out...
(gdb) show language
The current source language is "auto; currently c++".
...
Now consider setting the language manually to c:
...
$ gdb -q
(gdb) show language
The current source language is "auto; currently c".
(gdb) set language c
(gdb) show language
The current source language is "c".
...
The resulting language is manual/c.
Surprisingly, a subsequent load of the c++ executable:
...
(gdb) file a.out
Reading symbols from a.out...
(gdb) show language
The current source language is "c++".
...
gets us language manual/c++.
Loading the file should get us either:
- auto/c++, or
- manual/c.
That is, either the manual setting should be reset by loading, or the manual
setting should persist.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26440-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 26 12:51:00 2020
Return-Path: <gdb-prs-return-26440-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 33609 invoked by alias); 26 Feb 2020 12:50:59 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 33560 invoked by uid 48); 26 Feb 2020 12:50:58 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25603] If language set manually, then loading file sets
language partially
Date: Wed, 26 Feb 2020 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: vries 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: <bug-25603-4717-RtcODwtsfx@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25603-4717@http.sourceware.org/bugzilla/>
References: <bug-25603-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00355.txt
Content-length: 278
https://sourceware.org/bugzilla/show_bug.cgi?id=25603
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Patch submitted: https://sourceware.org/ml/gdb-patches/2020-02/msg00974.html
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26441-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 26 12:54:44 2020
Return-Path: <gdb-prs-return-26441-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 59759 invoked by alias); 26 Feb 2020 12:54:43 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 59736 invoked by uid 48); 26 Feb 2020 12:54:43 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/23710] gdb is slow and memory hungry consuming debug
generated with LTO by GCC
Date: Wed, 26 Feb 2020 12: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.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-23710-4717-ZGebUJHpNR@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23710-4717@http.sourceware.org/bugzilla/>
References: <bug-23710-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00356.txt
Content-length: 859
https://sourceware.org/bugzilla/show_bug.cgi?id=23710
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #0)
> "Mirror" of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87432 where we try
> to improve the GCC side. Input from gdb folks is needed here.
>
> gdb takes ~10s to process a LTO bootstrapped cc1 binary and another two
> seconds
> when setting the first breakpoint. It also has allocated 1.6GB memory at
> that point (compared to ~200MB for a non-LTO binary).
The proposed patch at
https://sourceware.org/ml/gdb-patches/2020-02/msg00974.html allows a speedup
when manually specifying the source language before loading, which takes 17%
off the execution time of loading and setting the first breakpoint.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26442-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 26 13:14:05 2020
Return-Path: <gdb-prs-return-26442-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 73037 invoked by alias); 26 Feb 2020 13:14:04 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 73018 invoked by uid 48); 26 Feb 2020 13:14:04 -0000
From: "simon.brass at desy dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug fortran/22424] gdb.lookup_type fails for Fortran
Date: Wed, 26 Feb 2020 13:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
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: simon.brass at desy 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 attachments.created
Message-ID: <bug-22424-4717-DhMTJ88BMB@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22424-4717@http.sourceware.org/bugzilla/>
References: <bug-22424-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00357.txt
Content-length: 1348
https://sourceware.org/bugzilla/show_bug.cgi?id=22424
Simon Braß <simon.brass at desy dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simon.brass at desy dot de
--- Comment #2 from Simon Braß <simon.brass at desy dot de> ---
Created attachment 12325
--> https://sourceware.org/bugzilla/attachment.cgi?id=12325&action=edit
Include Fortran veto on symbol_matches_domain
I've bumped into this problem today.
I tried looking up the solution from bug 21763:
In symtab.c's symbol_matches_domain, it seems that symbol_domain and domain do
not match (d'uh) for the derived type lookup.
I've then looked up the definition of my derived type in the dwarf output of
gfortran, and found that the derived is tagged as DW_TAG_structure_type (would
go into STRUCT_DOMAIN), not as DW_TAG_typedef (would go into VAR_DOMAIN), as
one could maybe expect?
The information about the type should then be searched in STRUCT_DOMAIN and not
in VAR_DOMAIN, or not?
Adding an exception for language_fortran in symtab.c's symbol_matches_domain
seems to resolve the problem (however, I did not run the testsuite).
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26443-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 26 13:38:26 2020
Return-Path: <gdb-prs-return-26443-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 76677 invoked by alias); 26 Feb 2020 13:38:26 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 76658 invoked by uid 48); 26 Feb 2020 13:38:26 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/23710] gdb is slow and memory hungry consuming debug
generated with LTO by GCC
Date: Wed, 26 Feb 2020 13: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: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-23710-4717-pGjmu1hD00@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23710-4717@http.sourceware.org/bugzilla/>
References: <bug-23710-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00358.txt
Content-length: 915
https://sourceware.org/bugzilla/show_bug.cgi?id=23710
--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
Measuring the two speed workarounds mentioned in comment 5 and 6, it seems
they're complementary:
With loading main full symtab and default max-cache-age:
...
$ ../measure/time.sh ../gdb.sh cc1 -batch -ex "b do_rpo_vn" -iex "maint set
dwarf max-cache-age 5"
Breakpoint 1 at 0xd40e30: do_rpo_vn. (2 locations)
maxmem: 1463412
real: 8.92
user: 8.52
system: 0.46
...
With skipping main full symtab and increased max-cache-age:
...
$ ../measure/time.sh ../gdb.sh -iex "set language c++" cc1 -batch -ex "b
do_rpo_vn" -iex "maint set dwarf max-cache-age 316"
Breakpoint 1 at 0xd40e30: do_rpo_vn. (2 locations)
maxmem: 1066220
real: 6.34
user: 6.09
system: 0.31
...
That is: reduction of user execution time by 28,5%.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26444-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 26 13:52:52 2020
Return-Path: <gdb-prs-return-26444-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 112236 invoked by alias); 26 Feb 2020 13:52:52 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 112206 invoked by uid 55); 26 Feb 2020 13:52:52 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25603] If language set manually, then loading file sets
language partially
Date: Wed, 26 Feb 2020 13: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: 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: <bug-25603-4717-fGnCk9d3ab@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25603-4717@http.sourceware.org/bugzilla/>
References: <bug-25603-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00359.txt
Content-length: 2958
https://sourceware.org/bugzilla/show_bug.cgi?id=25603
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0dce428051fd2cf07f9d38e9efe2dbb5d8f7fbef
commit 0dce428051fd2cf07f9d38e9efe2dbb5d8f7fbef
Author: Tom de Vries <tdevries@suse.de>
Date: Wed Feb 26 14:52:00 2020 +0100
[gdb] Don't set initial language if set manually
Initially, gdb sets the language to auto/c:
...
$ gdb -q
(gdb) show language
The current source language is "auto; currently c".
...
And after loading a c++ executable, that changes to auto/c++:
...
(gdb) file a.out
Reading symbols from a.out...
(gdb) show language
The current source language is "auto; currently c++".
...
Now consider setting the language manually to c:
...
$ gdb -q
(gdb) show language
The current source language is "auto; currently c".
(gdb) set language c
(gdb) show language
The current source language is "c".
...
The resulting language is manual/c.
Surprisingly, a subsequent load of the c++ executable:
...
(gdb) file a.out
Reading symbols from a.out...
(gdb) show language
The current source language is "c++".
...
gets us language manual/c++.
Loading the file should get us either:
- auto/c++, or
- manual/c.
That is, either the manual setting should be reset by loading, or the
manual
setting should persist.
Fix this in the manual/c fashion. [ Though we could make some gdb setting
to
choose one or the other. ]
Build and reg-tested on x86_64-linux.
[ Note: In PR23710 comment 1 a cc1 binary is attached for which gdb is slow
when
loading and settting a breakpoint on do_rpo_vn:
...
$ time.sh gdb cc1 -batch -ex "b do_rpo_vn"
Breakpoint 1 at 0xd40e30: do_rpo_vn. (2 locations)
maxmem: 1463496
real: 8.88
user: 8.59
system: 0.35
...
This fix enables a speedup by manually setting the language before
loading, reducing executing time with ~17%, due to not having to load the
full
symtab containing main:
...
$ time.sh gdb -iex "set language c++" cc1 -batch -ex "b do_rpo_vn"
Breakpoint 1 at 0xd40e30: do_rpo_vn. (2 locations)
maxmem: 1067308
real: 7.36
user: 7.14
system: 0.28
... ]
gdb/ChangeLog:
2020-02-26 Tom de Vries <tdevries@suse.de>
PR gdb/25603
* symfile.c (set_initial_language): Exit-early if
language_mode == language_mode_manual.
gdb/testsuite/ChangeLog:
2020-02-26 Tom de Vries <tdevries@suse.de>
PR gdb/25603
* gdb.base/persistent-lang.cc: New test.
* gdb.base/persistent-lang.exp: New file.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26445-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 26 13:54:28 2020
Return-Path: <gdb-prs-return-26445-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 114943 invoked by alias); 26 Feb 2020 13:54:27 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 114915 invoked by uid 48); 26 Feb 2020 13:54:27 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25603] If language set manually, then loading file sets
language partially
Date: Wed, 26 Feb 2020 13: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: vries 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: 10.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-25603-4717-kb80JHgooa@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25603-4717@http.sourceware.org/bugzilla/>
References: <bug-25603-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00360.txt
Content-length: 607
https://sourceware.org/bugzilla/show_bug.cgi?id=25603
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.1
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Patch with test-case committed, marking resolved-fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26446-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 26 17:51:22 2020
Return-Path: <gdb-prs-return-26446-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 27446 invoked by alias); 26 Feb 2020 17:51:22 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 27424 invoked by uid 48); 26 Feb 2020 17:51:22 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/23439] backtrace not logging to file from inside breakpoint
command
Date: Wed, 26 Feb 2020 17: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.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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 resolution
Message-ID: <bug-23439-4717-udd6tSE0H2@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23439-4717@http.sourceware.org/bugzilla/>
References: <bug-23439-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00361.txt
Content-length: 717
https://sourceware.org/bugzilla/show_bug.cgi?id=23439
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
I've tested once more with release branches 8.0, 8.1, 8.2 and 8.3, release tag
8.1 and master, all work.
Since I cannot reproduce this with a build from plain gdb sources, marking it
resolved-worksforme.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26447-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 26 21:34:38 2020
Return-Path: <gdb-prs-return-26447-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 130839 invoked by alias); 26 Feb 2020 21:34:38 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 130817 invoked by uid 48); 26 Feb 2020 21:34:37 -0000
From: "nojhan at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/23439] backtrace not logging to file from inside breakpoint
command
Date: Wed, 26 Feb 2020 21: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: 8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nojhan at gmail 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: <bug-23439-4717-X1d7Y2HbFM@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23439-4717@http.sourceware.org/bugzilla/>
References: <bug-23439-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00362.txt
Content-length: 383
https://sourceware.org/bugzilla/show_bug.cgi?id=23439
--- Comment #4 from nojhan <nojhan at gmail dot com> ---
I've tried with 8.3 and 9.1 with the previous minimal example (without the
prompt) and I confirm it works.
Version 8.1-0ubuntu3.2 is still impacted, but I guess it's an ubuntu specific.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26448-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Feb 26 22:21:43 2020
Return-Path: <gdb-prs-return-26448-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 83108 invoked by alias); 26 Feb 2020 22:21:42 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 83089 invoked by uid 48); 26 Feb 2020 22:21:42 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug rust/22251] &str type should be built in
Date: Wed, 26 Feb 2020 22: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: 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: <bug-22251-4717-n6XRQ4vmP0@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22251-4717@http.sourceware.org/bugzilla/>
References: <bug-22251-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00363.txt
Content-length: 572
https://sourceware.org/bugzilla/show_bug.cgi?id=22251
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
Note that this still doesn't work even if &str appears in the DWARF.
You can see this with the "simple.rs" test case in the test suite.
In that case, the type appears in DWARF as "&str" but, probably,
the parser here is being smart and looking up "str", which indeed
does not exist. Maybe a special case is needed.
See https://github.com/rust-lang/rust/issues/65272
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26449-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Feb 27 23:08:26 2020
Return-Path: <gdb-prs-return-26449-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 54362 invoked by alias); 27 Feb 2020 23:08:25 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 54335 invoked by uid 48); 27 Feb 2020 23:08:25 -0000
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/22399] No support for DW_OP_GNU_variable_value
Date: Thu, 27 Feb 2020 23: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: 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: <bug-22399-4717-WuTp2dL8cN@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22399-4717@http.sourceware.org/bugzilla/>
References: <bug-22399-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00364.txt
Content-length: 676
https://sourceware.org/bugzilla/show_bug.cgi?id=22399
Sergio Durigan Junior <sergiodj at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |sergiodj at redhat dot com
Resolution|--- |FIXED
--- Comment #3 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
I think this can be marked as FIXED, since the series was accepted and pushed.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26450-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 28 13:43:38 2020
Return-Path: <gdb-prs-return-26450-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 91975 invoked by alias); 28 Feb 2020 13:43:38 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 91956 invoked by uid 48); 28 Feb 2020 13:43:38 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25609] New: [runtest -v] FAIL:
gdb.base/jit-reader.exp: jit-reader-load
Date: Fri, 28 Feb 2020 13:43: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: vries 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: <bug-25609-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00365.txt
Content-length: 2487
https://sourceware.org/bugzilla/show_bug.cgi?id=25609
Bug ID: 25609
Summary: [runtest -v] FAIL: gdb.base/jit-reader.exp:
jit-reader-load
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
When running test-case gdb.base/jit-reader.exp, we have:
...
Running src/gdb/testsuite/gdb.base/jit-reader.exp ...
=== gdb Summary ===
# of expected passes 24
...
But when running runtest with -v, we run into:
...
FAIL: gdb.base/jit-reader.exp: jit-reader-load
FAIL: gdb.base/jit-reader.exp: with jit-reader: before mangling: bt works
FAIL: gdb.base/jit-reader.exp: with jit-reader: after mangling: bt works
FAIL: gdb.base/jit-reader.exp: with jit-reader again: jit-reader-load
FAIL: gdb.base/jit-reader.exp: with jit-reader again: bt
=== gdb Summary ===
# of expected passes 20
# of unexpected failures 5
...
The first failure in more detail:
...
(gdb) PASS: gdb.base/jit-reader.exp: set debug jit 1
jit-reader-load
/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/jit-reader/jitreader.so^M
Opening shared object
/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/jit-reader/jitreader.so.^M
jit_inferior_init^M
jit_breakpoint_re_set_internal, breakpoint_addr = 0x4005a7^M
jit_read_descriptor, descriptor_addr = 0x601040^M
(gdb) FAIL: gdb.base/jit-reader.exp: jit-reader-load
...
So what happens is that using runtest -v causes "set debug jit 1", which causes
some extra output, that the gdb_test regexp is not prepared for.
This is easy enough to fix, but the second FAIL looks more complicated:
...
(gdb) PASS: gdb.base/jit-reader.exp: expect SIGTRAP
bt^M
Could not unwind frame using JIT reader.^M
#0 0x00007ffff7ff4001 in jit_function_stack_mangle ()^M
#1 0x00000000004006ec in main (Could not unwind frame using JIT reader.^M
argc=1, argv=0x7fffffffd3b8) at
/data/gdb_versions/devel/src/gdb/testsuite/gdb.base/jithost.c:94^M
(gdb) FAIL: gdb.base/jit-reader.exp: with jit-reader: before mangling: bt works
...
It's not clear for me whether the "could not unwind frame using JIT reader" is
expected or not.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26451-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 28 13:51:43 2020
Return-Path: <gdb-prs-return-26451-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 118351 invoked by alias); 28 Feb 2020 13:51:43 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 118331 invoked by uid 48); 28 Feb 2020 13:51:43 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/25609] [runtest -v] FAIL: gdb.base/jit-reader.exp:
jit-reader-load
Date: Fri, 28 Feb 2020 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: vries 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: <bug-25609-4717-SzfXrJY9W8@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25609-4717@http.sourceware.org/bugzilla/>
References: <bug-25609-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00366.txt
Content-length: 610
https://sourceware.org/bugzilla/show_bug.cgi?id=25609
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com,
| |sanjoy@playingwithpointers.
| |com
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
CC-ing test authors.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26452-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 28 15:12:19 2020
Return-Path: <gdb-prs-return-26452-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 24527 invoked by alias); 28 Feb 2020 15:12:19 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 24507 invoked by uid 48); 28 Feb 2020 15:12:19 -0000
From: "eyalroz at technion dot ac.il" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25610] New: NULL print_value in
varobj.c:1425:install_new_value
Date: Fri, 28 Feb 2020 15: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
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eyalroz at technion dot 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: <bug-25610-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00367.txt
Content-length: 1196
https://sourceware.org/bugzilla/show_bug.cgi?id=25610
Bug ID: 25610
Summary: NULL print_value in varobj.c:1425:install_new_value
Product: gdb
Version: 7.12
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: eyalroz at technion dot ac.il
Target Milestone: ---
Filing this bug because gdb told me to do so...
I was using cuda-gdb from CUDA 10.1, within NVIDIA nSight (a modified Eclipse
CDT), to debug some program (not the GPU-side part of it actually), but the
debugger stopped/crashed with the following message:
------
cuda-gdb/7.12/gdb/varobj.c:1425: internal-error: install_new_value: Assertion
`var->print_value != NULL && print_value != NULL' 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:
<http://www.gnu.org/software/gdb/bugs/>.
------
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26453-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Feb 28 22:25:53 2020
Return-Path: <gdb-prs-return-26453-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 29054 invoked by alias); 28 Feb 2020 22:25:53 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 29024 invoked by uid 48); 28 Feb 2020 22:25:53 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25613] New: [gdb] verbose message appear not at start of
line during backtrace
Date: Fri, 28 Feb 2020 22:25: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: vries 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: <bug-25613-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00368.txt
Content-length: 2449
https://sourceware.org/bugzilla/show_bug.cgi?id=25613
Bug ID: 25613
Summary: [gdb] verbose message appear not at start of line
during backtrace
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Consider the following test-case:
...
$ gcc -g src/gdb/testsuite/gdb.base/break-interp-*.c
...
When using "set language c" to avoid loading the full symbol table for
break-interb-main.c, and using "set verbose" to be verbose about symbol table
expansion:
...
$ gdb -batch \
-iex "set verbose" \
-iex "set language c" \
-ex r \
-ex bt \
--args ./a.out segv
Reading symbols from ./a.out...
Reading symbols from /lib64/ld-linux-x86-64.so.2...
(No debugging symbols found in /lib64/ld-linux-x86-64.so.2)
Reading symbols from system-supplied DSO at 0x7ffff7ffa000...
(No debugging symbols found in system-supplied DSO at 0x7ffff7ffa000)
Reading symbols from /lib64/libc.so.6...
(No debugging symbols found in /lib64/libc.so.6)
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7a53160 in raise () from /lib64/libc.so.6
Reading in symbols for src/gdb/testsuite/gdb.base/break-interp-lib.c...done.
#0 0x00007ffff7a53160 in raise () from /lib64/libc.so.6
#1 0x0000000000400712 in libfunc (Reading in symbols for
src/gdb/testsuite/gdb.base/break-interp-main.c...done.
action=0x7fffffffe0d6 "segv") at
src/gdb/testsuite/gdb.base/break-interp-lib.c:34
#2 0x00000000004007a4 in main (argc=2, argv=0x7fffffffdbd8) at
src/gdb/testsuite/gdb.base/break-interp-main.c:27
...
we get the "Reading in symbols for
src/gdb/testsuite/gdb.base/break-interp-main.c...done" message in the middle of
the libfunc entry.
It would be better if we didn't split up lines midway, so this would be better:
...
#0 0x00007ffff7a53160 in raise () from /lib64/libc.so.6
Reading in symbols for src/gdb/testsuite/gdb.base/break-interp-main.c...done.
#1 0x0000000000400712 in libfunc (action=0x7fffffffe0d6 "segv") at
src/gdb/testsuite/gdb.base/break-interp-lib.c:34
#2 0x00000000004007a4 in main (argc=2, argv=0x7fffffffdbd8) at
src/gdb/testsuite/gdb.base/break-interp-main.c:27
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26454-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Mar 01 15:07:57 2020
Return-Path: <gdb-prs-return-26454-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 126295 invoked by alias); 1 Mar 2020 15:07:57 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 126273 invoked by uid 48); 1 Mar 2020 15:07:56 -0000
From: "sedepbanget007 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/21395] thread.c:1010 internal-error: int
is_executing(ptid_t): Assertion `tp' failed.
Date: Sun, 01 Mar 2020 15:07: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: sedepbanget007 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: cc attachments.created
Message-ID: <bug-21395-4717-v0EdwV5nLw@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-21395-4717@http.sourceware.org/bugzilla/>
References: <bug-21395-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00369.txt
Content-length: 586
https://sourceware.org/bugzilla/show_bug.cgi?id=21395
Fitriadi <sedepbanget007 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sedepbanget007 at gmail dot com
--- Comment #4 from Fitriadi <sedepbanget007 at gmail dot com> ---
Created attachment 12328
--> https://sourceware.org/bugzilla/attachment.cgi?id=12328&action=edit
Bugpath
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26455-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Mar 01 17:18:41 2020
Return-Path: <gdb-prs-return-26455-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 73229 invoked by alias); 1 Mar 2020 17:18:41 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 73209 invoked by uid 48); 1 Mar 2020 17:18:41 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25613] [gdb] verbose message appears not at start of line
during backtrace
Date: Sun, 01 Mar 2020 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: vries 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: short_desc
Message-ID: <bug-25613-4717-ls9kWNBDSs@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25613-4717@http.sourceware.org/bugzilla/>
References: <bug-25613-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00370.txt
Content-length: 534
https://sourceware.org/bugzilla/show_bug.cgi?id=25613
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[gdb] verbose message |[gdb] verbose message
|appear not at start of line |appears not at start of
|during backtrace |line during backtrace
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26456-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Mar 01 19:48:43 2020
Return-Path: <gdb-prs-return-26456-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 2262 invoked by alias); 1 Mar 2020 19:48:43 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 2196 invoked by uid 48); 1 Mar 2020 19:48:38 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25613] [gdb] verbose message appears not at start of line
during backtrace
Date: Sun, 01 Mar 2020 19: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: vries 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: <bug-25613-4717-7KSehBuZ8p@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25613-4717@http.sourceware.org/bugzilla/>
References: <bug-25613-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00371.txt
Content-length: 631
https://sourceware.org/bugzilla/show_bug.cgi?id=25613
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 12330
--> https://sourceware.org/bugzilla/attachment.cgi?id=12330&action=edit
Tentative patch with test-case
Tentative patch, with the following regressions:
....
FAIL: gdb.base/style-logging.exp: frame
FAIL: gdb.base/style.exp: frame
FAIL: gdb.base/style.exp: frame when width=20
FAIL: gdb.base/style.exp: frame when width=30
FAIL: gdb.opt/inline-cmds.exp: mi: step into inline call (timeout)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26457-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Mar 01 20:15:02 2020
Return-Path: <gdb-prs-return-26457-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 58431 invoked by alias); 1 Mar 2020 20:15:01 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 58403 invoked by uid 48); 1 Mar 2020 20:15:01 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25613] [gdb] verbose message appears not at start of line
during backtrace
Date: Sun, 01 Mar 2020 20: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: vries 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: <bug-25613-4717-OLUgGPuG7P@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25613-4717@http.sourceware.org/bugzilla/>
References: <bug-25613-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00372.txt
Content-length: 275
https://sourceware.org/bugzilla/show_bug.cgi?id=25613
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Sent out RFC: https://sourceware.org/ml/gdb-patches/2020-03/msg00008.html
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26458-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 02 07:03:13 2020
Return-Path: <gdb-prs-return-26458-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 16619 invoked by alias); 2 Mar 2020 07:03:13 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 16599 invoked by uid 48); 2 Mar 2020 07:03:13 -0000
From: "sedepbanget007 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/7292] cp error in sid/component/lcd/testsuite
Date: Mon, 02 Mar 2020 07: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sedepbanget007 at gmail dot com
X-Bugzilla-Status: CLOSED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: cagney at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-7292-4717-gil9oiu6fV@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-7292-4717@http.sourceware.org/bugzilla/>
References: <bug-7292-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00373.txt
Content-length: 404
https://sourceware.org/bugzilla/show_bug.cgi?id=7292
Fitriadi <sedepbanget007 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sedepbanget007 at gmail dot com
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26459-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 02 08:31:46 2020
Return-Path: <gdb-prs-return-26459-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 89402 invoked by alias); 2 Mar 2020 08:31:46 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 89376 invoked by uid 48); 2 Mar 2020 08:31:46 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/23710] gdb is slow and memory hungry consuming debug
generated with LTO by GCC
Date: Mon, 02 Mar 2020 08: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: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-23710-4717-58KZlyoCdm@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23710-4717@http.sourceware.org/bugzilla/>
References: <bug-23710-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00374.txt
Content-length: 1089
https://sourceware.org/bugzilla/show_bug.cgi?id=23710
--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #6)
> (In reply to Richard Biener from comment #0)
> > "Mirror" of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87432 where we try
> > to improve the GCC side. Input from gdb folks is needed here.
> >
> > gdb takes ~10s to process a LTO bootstrapped cc1 binary and another two
> > seconds
> > when setting the first breakpoint. It also has allocated 1.6GB memory at
> > that point (compared to ~200MB for a non-LTO binary).
>
> The proposed patch at
> https://sourceware.org/ml/gdb-patches/2020-02/msg00974.html allows a speedup
> when manually specifying the source language before loading, which takes 17%
> off the execution time of loading and setting the first breakpoint.
That patch has been accepted.
I've submitted a RFC patch that automates this workaround:
https://sourceware.org/ml/gdb-patches/2020-03/msg00009.html .
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26460-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 02 11:26:24 2020
Return-Path: <gdb-prs-return-26460-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 59134 invoked by alias); 2 Mar 2020 11:26:24 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 59110 invoked by uid 48); 2 Mar 2020 11:26:23 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/23710] gdb is slow and memory hungry consuming debug
generated with LTO by GCC
Date: Mon, 02 Mar 2020 11: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: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-23710-4717-dMn2zDCGh4@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23710-4717@http.sourceware.org/bugzilla/>
References: <bug-23710-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00375.txt
Content-length: 1956
https://sourceware.org/bugzilla/show_bug.cgi?id=23710
--- Comment #9 from Tom de Vries <vries at gcc dot gnu.org> ---
The cc1 executable contains CUs importing other CUs (as opposed to PUs). By
treating these imports as hints and ignoring them during during symtab
expansion, we can shave off another 8.3%.
Cumulatively, that gets us to user time reduction of 33.5%.
Tentative patch:
...
diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c
index 07cee58c1f..a2a6889f73 100644
--- a/gdb/dwarf2/read.c
+++ b/gdb/dwarf2/read.c
@@ -7425,6 +7425,18 @@ process_psymtab_comp_unit (struct dwarf2_per_cu_data
*this_cu,
cutu_reader reader (this_cu, NULL, 0, false);
+ switch (reader.comp_unit_die->tag)
+ {
+ case DW_TAG_compile_unit:
+ this_cu->unit_type = DW_UT_compile;
+ break;
+ case DW_TAG_partial_unit:
+ this_cu->unit_type = DW_UT_partial;
+ break;
+ default:
+ abort ();
+ }
+
if (reader.dummy_p)
{
/* Nothing. */
@@ -9760,6 +9772,9 @@ process_imported_unit_die (struct die_info *die, struct
dwarf2_cu *cu)
= dwarf2_find_containing_comp_unit (sect_off, is_dwz,
cu->per_cu->dwarf2_per_objfile);
+ if (per_cu->unit_type == DW_UT_compile)
+ return;
+
/* If necessary, add it to the queue and load its DIEs. */
if (maybe_queue_comp_unit (cu, per_cu, cu->language))
load_full_comp_unit (per_cu, false, cu->language);
diff --git a/gdb/dwarf2/read.h b/gdb/dwarf2/read.h
index 00652c2b45..58b80d4821 100644
--- a/gdb/dwarf2/read.h
+++ b/gdb/dwarf2/read.h
@@ -323,6 +323,8 @@ struct dwarf2_per_cu_data
dummy CUs (a CU header, but nothing else). */
struct dwarf2_cu *cu;
+ enum dwarf_unit_type unit_type;
+
/* The corresponding dwarf2_per_objfile. */
struct dwarf2_per_objfile *dwarf2_per_objfile;
...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26461-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 02 15:08:35 2020
Return-Path: <gdb-prs-return-26461-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 90022 invoked by alias); 2 Mar 2020 15:08:34 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 89964 invoked by uid 55); 2 Mar 2020 15:08:32 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/22597] Regression: backwards compatibility with old
GDBservers broken
Date: Mon, 02 Mar 2020 15:08: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: 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: <bug-22597-4717-b0dBCW19rp@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22597-4717@http.sourceware.org/bugzilla/>
References: <bug-22597-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00376.txt
Content-length: 7239
https://sourceware.org/bugzilla/show_bug.cgi?id=22597
--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=24ed6739b699f329c2c45aedee5f8c7d2f54e493
commit 24ed6739b699f329c2c45aedee5f8c7d2f54e493
Author: Andrew Burgess <andrew.burgess@embecosm.com>
Date: Thu Jan 30 14:35:40 2020 +0000
gdb/remote: Restore support for 'S' stop reply packet
With this commit:
commit 5b6d1e4fa4fc6827c7b3f0e99ff120dfa14d65d2
Date: Fri Jan 10 20:06:08 2020 +0000
Multi-target support
There was a regression in GDB's support for older aspects of the
remote protocol. Specifically, when a target sends the 'S' stop reply
packet (which doesn't include a thread-id) then GDB has to figure out
which thread actually stopped.
Before the above commit GDB figured this out by using inferior_ptid in
process_stop_reply, which contained the ptid of the current
process/thread. This would be fine for single threaded
targets (which is the only place using an S packet makes sense), but
in the general case, relying on inferior_ptid for processing a stop is
wrong - there's no reason to believe that what was GDB's current
thread will be the same thread that just stopped in the target.
With the above commit the inferior_ptid now has the value null_ptid
inside process_stop_reply, this can be seen in do_target_wait, where
we call switch_to_inferior_no_thread before calling do_target_wait_1.
The problem this causes can be seen in the new test that runs
gdbserver using the flag --disable-packet=T, and causes GDB to throw
this assertion:
inferior.c:279: internal-error: inferior*
find_inferior_pid(process_stratum_target*, int): Assertion `pid != 0' failed.
A similar problem was fixed in this commit:
commit 3cada74087687907311b52781354ff551e10a0ed
Date: Thu Jan 11 00:23:04 2018 +0000
Fix backwards compatibility with old GDBservers (PR remote/22597)
However, this commit deals with the case where the T packet doesn't
include a thread-id, not the S packet case. This commit solves the
problem providing a thread-id at the GDB side if the remote target
doesn't provide one. The thread-id provided comes from
remote_state::general_thread, however, though this does work, I don't
think it is the ideal solution.
The remote_state tracks two threads, the continue_thread and the
general_thread, these are updated when GDB asks the remote target to
switch threads. The general_thread is set before performing things
like register or memory accesses, and the continue_thread is set
before things like continue or step commands. Further, the
general_thread is updated after a target stops to reference the thread
that stopped.
The first thing to note from the above description is that we have a
cycle of dependency, when a T packet arrives without a thread-id we
fill in the thread-id from the general_thread data. The thread-id
from the stop event is then used to set the general_thread. This in
itself feels a little weird.
The second question is why use the general_thread at all? You'd think
given how they are originally set that the continue thread would be a
better choice. The problem with this is that the continue_thread, if
the user just does "continue", will be set to the minus_one_ptid, in
the remote protocol this means all threads. When the stop arrives
with no thread-id and we use continue_thread we end up with a very
similar assertion to before because we now end up trying to lookup a
thread using the minus_one_ptid. By contrast, once GDB has connected
to a remote target the general_thread will be set to a valid
thread-id, after which, if the target is single threaded, and stop
events arrive without a thread-id, everything works fine.
There is one slight weirdness with the above behaviour though. When
GDB first connects to the remote target inferior_ptid is null_ptid,
however, upon connecting we query the remote for its threads. As the
thread information arrives GDB adds the threads to its internal
database, and this process involves setting inferior_ptid to the id of
each new thread in turn. Once we know about all the threads we wait
for a stop event from the remote target to indicate that GDB is now in
control of the target.
The problem is that after adding the new threads we don't reset
inferior_ptid, and the code path we use to wait for a stop event from
the target also doesn't reset inferior_ptid, so it turns out that
during the initial connection inferior_ptid is not null_ptid. This is
lucky, because during the initial connection the general_thread
variable _is_ set to null_ptid.
So, during the initial connection, if the first stop event is missing
a thread-id then we "provide" a thead-id from general_thread. This
turns out to be null_ptid meaning no thread-id is known, and then
during process_stop_reply we fill in the missing thread-id using
inferior_ptid.
This was all discussed on the mailing list here:
https://sourceware.org/ml/gdb-patches/2020-02/msg01011.html
My proposal for a fix then is:
1. Move the call to switch_to_inferior_no_thread into
do_target_wait_1, this means that in all cases where we are waiting
for an inferior the inferior_ptid will be set to null_ptid. This is
good as no wait code should rely on inferior_ptid.
2. Remove the use of general_thread from the 'T' packet processing.
The general_thread read here was only ever correct by chance, and we
shouldn't be using it this way.
3. Remove use of inferior_ptid from process_stop_event as this is
wrong, and will always be null_ptid now anyway.
4. When a stop_event has null_ptid due to a lack of thread-id (either
from a T packet or an S packet) then pick the first non exited thread
in the target and use that. This will be fine for single threaded
targets. A multi-thread or multi-inferior aware remote target
should be using T packets with a thread-id, so we give a warning if
the target is multi-threaded, and we are still missing a thread-id.
5. Extend the existing test that covered the T packet with missing
thread-id to also cover the S packet.
gdb/ChangeLog:
* remote.c (remote_target::remote_parse_stop_reply): Don't use the
general_thread if the stop reply is missing a thread-id.
(remote_target::process_stop_reply): Use the first non-exited
thread if the target didn't pass a thread-id.
* infrun.c (do_target_wait): Move call to
switch_to_inferior_no_thread to ....
(do_target_wait_1): ... here.
gdb/testsuite/ChangeLog:
* gdb.server/stop-reply-no-thread.exp: Add test where T packet is
disabled.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26462-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Mar 02 16:16:28 2020
Return-Path: <gdb-prs-return-26462-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 2919 invoked by alias); 2 Mar 2020 16:16:27 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 2896 invoked by uid 48); 2 Mar 2020 16:16:27 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/23710] gdb is slow and memory hungry consuming debug
generated with LTO by GCC
Date: Mon, 02 Mar 2020 16: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.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-23710-4717-aWjavdwvdq@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23710-4717@http.sourceware.org/bugzilla/>
References: <bug-23710-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00377.txt
Content-length: 607
https://sourceware.org/bugzilla/show_bug.cgi?id=23710
--- Comment #10 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #9)
> The cc1 executable contains CUs importing other CUs (as opposed to PUs). By
> treating these imports as hints and ignoring them during during symtab
> expansion, we can shave off another 8.3%.
>
> Cumulatively, that gets us to user time reduction of 33.5%.
>
> Tentative patch:
Submitted: https://sourceware.org/ml/gdb-patches/2020-03/msg00026.html .
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26463-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Mar 04 15:32:04 2020
Return-Path: <gdb-prs-return-26463-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 118505 invoked by alias); 4 Mar 2020 15:32:03 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 118466 invoked by uid 48); 4 Mar 2020 15:32:03 -0000
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/24917] [check-read1] FAIL: gdb.tui/basic.exp: list
main
Date: Wed, 04 Mar 2020 15: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: 9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-24917-4717-jAsiKwGJgF@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24917-4717@http.sourceware.org/bugzilla/>
References: <bug-24917-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00378.txt
Content-length: 616
https://sourceware.org/bugzilla/show_bug.cgi?id=24917
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.1
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
Fixed in commit 45e4216376 "Make TUI resizing tests more robust".
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26464-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 05 00:18:45 2020
Return-Path: <gdb-prs-return-26464-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 68953 invoked by alias); 5 Mar 2020 00:18:45 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 68935 invoked by uid 48); 5 Mar 2020 00:18:45 -0000
From: "kevinb at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/25631] New: GDB cannot access unwritten-to mmap'd
buffer from core file
Date: Thu, 05 Mar 2020 00:18: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: 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: <bug-25631-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00379.txt
Content-length: 2241
https://sourceware.org/bugzilla/show_bug.cgi?id=25631
Bug ID: 25631
Summary: GDB cannot access unwritten-to mmap'd buffer from core
file
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: corefiles
Assignee: unassigned at sourceware dot org
Reporter: kevinb at redhat dot com
Target Milestone: ---
Created attachment 12347
--> https://sourceware.org/bugzilla/attachment.cgi?id=12347&action=edit
Test case demonstrating mmap core file bug
Compile the test case as follows:
gcc -g -o mkmmapcore mkmmapcore.c
Next, make sure that your system can create core files in a local directory.
This might require executing the following command as root or using sudo:
echo core > /proc/sys/kernel/core_pattern
Also, it may be necessary to do "ulimit -c unlimited".
Now, run the program using GDB...
(gdb) b 11
Breakpoint 1 at 0x401171: file mkmmapcore.c, line 11.
(gdb) run
Starting program: /tmp/mkmmapcore
Breakpoint 1, main (argc=1, argv=0x7fffffffd678) at mkmmapcore.c:11
11 abort ();
(gdb) x/x buf
0x7ffff7fcb000: 0x00000000
(gdb) c
Continuing.
Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 return ret;
(gdb) q
A debugging session is active.
Inferior 1 [process 304383] will be killed.
Quit anyway? (y or n) y
In the above, note that GDB is able to access the contents of the buffer
created using mmap().
Now, debug the program again, this time using the core file:
[kev@f31-1 tmp]$ gdb -q ./mkmmapcore core.304767
Reading symbols from ./mkmmapcore...
[New LWP 304767]
Core was generated by `/tmp/mkmmapcore'.
Program terminated with signal SIGABRT, Aborted.
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 return ret;
(gdb) x/x buf
0x7ffff7fcb000: Cannot access memory at address 0x7ffff7fcb000
(gdb) q
This demonstrates the bug; using the core file, GDB should be able to access
the same memory region as when the process was live.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26465-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 05 00:19:37 2020
Return-Path: <gdb-prs-return-26465-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 70240 invoked by alias); 5 Mar 2020 00:19:37 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 70222 invoked by uid 48); 5 Mar 2020 00:19:37 -0000
From: "kevinb at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/25631] GDB cannot access unwritten-to mmap'd buffer
from core file
Date: Thu, 05 Mar 2020 00: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kevinb at redhat dot com
X-Bugzilla-Status: ASSIGNED
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: bug_status assigned_to
Message-ID: <bug-25631-4717-mZXlLKqLLl@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25631-4717@http.sourceware.org/bugzilla/>
References: <bug-25631-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00380.txt
Content-length: 590
https://sourceware.org/bugzilla/show_bug.cgi?id=25631
Kevin Buettner <kevinb at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at sourceware dot org |kevinb at redhat dot com
--- Comment #1 from Kevin Buettner <kevinb at redhat dot com> ---
I have a fix for this bug; I'll be posting a patch set soon.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26466-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 05 00:45:39 2020
Return-Path: <gdb-prs-return-26466-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 100595 invoked by alias); 5 Mar 2020 00:45:38 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 95268 invoked by uid 48); 5 Mar 2020 00:45:26 -0000
From: "kevinb at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/25631] GDB cannot access unwritten-to mmap'd buffer
from core file
Date: Thu, 05 Mar 2020 00:45: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kevinb at redhat dot com
X-Bugzilla-Status: ASSIGNED
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:
Message-ID: <bug-25631-4717-m9HxyJcgJm@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25631-4717@http.sourceware.org/bugzilla/>
References: <bug-25631-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00381.txt
Content-length: 296
https://sourceware.org/bugzilla/show_bug.cgi?id=25631
--- Comment #2 from Kevin Buettner <kevinb at redhat dot com> ---
Patch series can be found here:
https://sourceware.org/ml/gdb-patches/2020-03/msg00106.html
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26467-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 05 12:55:35 2020
Return-Path: <gdb-prs-return-26467-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 96332 invoked by alias); 5 Mar 2020 12:55:35 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 96308 invoked by uid 48); 5 Mar 2020 12:55:35 -0000
From: "vincent-srcware at vinc17 dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug web/25634] New: Please update the mpfr.org URL to https
Date: Thu, 05 Mar 2020 12:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: web
X-Bugzilla-Version: 9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: vincent-srcware at vinc17 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: <bug-25634-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00382.txt
Content-length: 910
https://sourceware.org/bugzilla/show_bug.cgi?id=25634
Bug ID: 25634
Summary: Please update the mpfr.org URL to https
Product: gdb
Version: 9.1
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: web
Assignee: unassigned at sourceware dot org
Reporter: vincent-srcware at vinc17 dot net
Target Milestone: ---
On https://sourceware.org/gdb/current/onlinedocs/gdb/Requirements.html the MPFR
URL http://www.mpfr.org should be changed to the https version:
https://www.mpfr.org
I can see in Debian that gdb.pdf also has the http URL. I suppose that this is
related to the GDB documentation in general (I haven't seen a doc or manual
component for the bug report).
You may also want to check the other URLs...
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26468-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Mar 05 23:46:15 2020
Return-Path: <gdb-prs-return-26468-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 64493 invoked by alias); 5 Mar 2020 23:46:15 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 64466 invoked by uid 48); 5 Mar 2020 23:46:14 -0000
From: "cbiesinger at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/25638] New: GDB detects NetBSD/ARM core file as
Symbian
Date: Thu, 05 Mar 2020 23:46: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger 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
attachments.created
Message-ID: <bug-25638-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00383.txt
Content-length: 1312
https://sourceware.org/bugzilla/show_bug.cgi?id=25638
Bug ID: 25638
Summary: GDB detects NetBSD/ARM core file as Symbian
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: corefiles
Assignee: unassigned at sourceware dot org
Reporter: cbiesinger at google dot com
Target Milestone: ---
Created attachment 12351
--> https://sourceware.org/bugzilla/attachment.cgi?id=12351&action=edit
Sample core file
The attached core file was generated on ARM/NetBSD 9.0 RC1.
When trying to load it into GDB, it gets detected as an OSABI of Symbian, if
you have a GDB with --enable-targets=all.
That's incorrect. Here is the reason:
The generic ELF sniffer (via generic_elf_osabi_sniff_abi_tag_sections) does
correctly detect this as NetBSD.
However, later the Symbian OSABI sniffer runs (arm_symbian_osabi_sniffer) and
returns Symbian.
Because the Symbian sniffer is a "specific" sniffer (has an arch of ARM), it
gets used instead, by gdbarch_lookup_osabi.
So, we end up using the wrong gdbarch to try to process this core file.
I don't know yet how we avoid this situation for Linux/ARM.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26469-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 06 00:59:32 2020
Return-Path: <gdb-prs-return-26469-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 1025 invoked by alias); 6 Mar 2020 00:59:32 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 1000 invoked by uid 48); 6 Mar 2020 00:59:32 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug exp/25299] complex numbers not fully supported in expressions
Date: Fri, 06 Mar 2020 00:59: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: assigned_to
Message-ID: <bug-25299-4717-T9yOVvYOw4@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25299-4717@http.sourceware.org/bugzilla/>
References: <bug-25299-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00384.txt
Content-length: 505
https://sourceware.org/bugzilla/show_bug.cgi?id=25299
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at sourceware dot org |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I have some patches for this.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-26470-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Mar 06 01:00:41 2020
Return-Path: <gdb-prs-return-26470-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 2227 invoked by alias); 6 Mar 2020 01:00:39 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 2173 invoked by uid 48); 6 Mar 2020 01:00:38 -0000
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug fortran/18373] Array of double precision complex numbers
Date: Fri, 06 Mar 2020 01:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.11
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 resolution
Message-ID: <bug-18373-4717-MDt6ZhkIDA@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-18373-4717@http.sourceware.org/bugzilla/>
References: <bug-18373-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-q1/txt/msg00385.txt
Content-length: 721
https://sourceware.org/bugzilla/show_bug.cgi?id=18373
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |tromey at sourceware dot org
Resolution|--- |FIXED
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
It sounds like perhaps this was fixed.
If it is still a problem with a newer gdb, please reopen.
A simple reproducer would be very helpful.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug gdb/24865] gdb crashes while debugging due to invalid pointer exception in value.c:416.
[not found] <bug-24865-4717@http.sourceware.org/bugzilla/>
2020-01-02 14:49 ` [Bug gdb/24865] gdb crashes while debugging due to invalid pointer exception in value.c:416 josephschuchart at gmail dot com
@ 2020-03-24 15:49 ` tromey at sourceware dot org
2020-03-24 16:05 ` tromey at sourceware dot org
2020-04-08 12:16 ` ssbssa at sourceware dot org
3 siblings, 0 replies; 4+ messages in thread
From: tromey at sourceware dot org @ 2020-03-24 15:49 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=24865
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
Ever confirmed|0 |1
Last reconfirmed| |2020-03-24
Status|UNCONFIRMED |NEW
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug gdb/24865] gdb crashes while debugging due to invalid pointer exception in value.c:416.
[not found] <bug-24865-4717@http.sourceware.org/bugzilla/>
2020-01-02 14:49 ` [Bug gdb/24865] gdb crashes while debugging due to invalid pointer exception in value.c:416 josephschuchart at gmail dot com
2020-03-24 15:49 ` tromey at sourceware dot org
@ 2020-03-24 16:05 ` tromey at sourceware dot org
2020-04-08 12:16 ` ssbssa at sourceware dot org
3 siblings, 0 replies; 4+ messages in thread
From: tromey at sourceware dot org @ 2020-03-24 16:05 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=24865
--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
With git master I get:
(gdb) p X
$1 = {static ndims = <error reading variable: Missing ELF symbol "X<long, 1,
Y<1, int, 1> >::ndims".>, _a = {static ndims = <error reading variable: Missing
ELF symbol "Y<1, int, 1>::ndims".>,
static bases = <error reading variable: Missing ELF symbol "Y<1, int,
1>::bases".>, _size = 0, _offsets = {_M_elems = {0}}}}
... which is at least not a crash.
This seems familiar, I think it's some known bug with C++17 DWARF?
I forget, we'll have to dig a little to find it.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug gdb/24865] gdb crashes while debugging due to invalid pointer exception in value.c:416.
[not found] <bug-24865-4717@http.sourceware.org/bugzilla/>
` (2 preceding siblings ...)
2020-03-24 16:05 ` tromey at sourceware dot org
@ 2020-04-08 12:16 ` ssbssa at sourceware dot org
3 siblings, 0 replies; 4+ messages in thread
From: ssbssa at sourceware dot org @ 2020-04-08 12:16 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=24865
Hannes Domani <ssbssa at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|NEW |RESOLVED
CC| |ssbssa at sourceware dot org
--- Comment #4 from Hannes Domani <ssbssa at sourceware dot org> ---
Dup.
*** This bug has been marked as a duplicate of bug 20020 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-04-08 12:16 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-24865-4717@http.sourceware.org/bugzilla/>
2020-01-02 14:49 ` [Bug gdb/24865] gdb crashes while debugging due to invalid pointer exception in value.c:416 josephschuchart at gmail dot com
2020-03-24 15:49 ` tromey at sourceware dot org
2020-03-24 16:05 ` tromey at sourceware dot org
2020-04-08 12:16 ` ssbssa at sourceware dot org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).