diff options
| author | Lancelot SIX <lancelot.six@amd.com> | 2025-02-07 11:09:09 +0000 |
|---|---|---|
| committer | Lancelot SIX <lancelot.six@amd.com> | 2025-02-07 20:05:33 +0000 |
| commit | ae84e36caf44936ee94d9dcbfe427ff0bd9434df (patch) | |
| tree | 59ae5a5a87849ca82ae9be0951d5e96413944a51 /gprof/po/ja.po | |
| parent | 9dd3d66b79a2907726f407039234ad8677e9df16 (diff) | |
| download | fsf-binutils-gdb-master.zip fsf-binutils-gdb-master.tar.gz fsf-binutils-gdb-master.tar.bz2 | |
On ubuntu systems with libc debug info available (libc6-dbg), I see the
following failures for the gdb.base/corefile-exec-context.exp testcase:
show args
Argument list to give program being debugged when it is started is "aaaaa bbbbb ccccc ddddd e\ e\ e\ e\ e".
(gdb) PASS: gdb.base/corefile-exec-context.exp: show args
up
#1 __pthread_kill_internal (signo=6, threadid=133859295332160) at ./nptl/pthread_kill.c:78
78 in ./nptl/pthread_kill.c
(gdb) FAIL: gdb.base/corefile-exec-context.exp: move up to main
This failures is because the pattern used to parse the output of `up`
is not expecting what is seen when debugging information is present for
those frames.
This patch adjusts the pattern to allow both possible outputs.
Tested on ubuntu-22.04 and ubuntu24.04 with libc6-dbg installed for gdb
build with --with-separate-debug-dir=/usr/lib/debug.
Change-Id: I217d4b20006d0ecdb4b7a71eeb8d01597ec5ac63
Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gprof/po/ja.po')
0 files changed, 0 insertions, 0 deletions