Your message dated Sun, 03 Aug 2025 17:20:04 -0400
with message-id <[email protected]>
and subject line Closing bug
has caused the Debian Bug report #898048,
regarding gdb: Couldn't write extended state status: Bad address
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
898048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898048
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdb
Version: 7.12-6
Severity: normal
Dear Héctor,
When using the print command to evaluate C code, gdb output
"Couldn't write extended state status: Bad address" and get
in a confused state.
The attached script should allow to reproduce the bug.
Breakpoint 1, doadd (a=2, b=4) at main.c:2
2 int doadd(int a, int b) { return add(a,b);}
(gdb) $1 = 2
(gdb) Couldn't write extended state status: Mauvaise adresse.
(gdb) No symbol "a" in current context.
(gdb) Couldn't write extended state status: Mauvaise adresse.
on jessie I get:
Breakpoint 1, doadd (a=2, b=4) at main.c:2
2 int doadd(int a, int b) { return add(a,b);}
(gdb) $1 = 2
(gdb) $2 = 11
(gdb) $3 = 2
(gdb) $4 = 11
I can reproduce it on a recently installed stretch system
and also in a sid chroot, but not with gdb 8 in experimental.
However there is no problem on a jessie system and also
in a sid chroot.
So maybe it is related to the kernel.
google do not report anything for 'Couldn't write extended state status:'.
The gdb code is
if (ptrace (PTRACE_SETREGSET, tid,
(unsigned int) NT_X86_XSTATE, (long) &iov) < 0)
perror_with_name (_("Couldn't write extended state status"));
I would be very grateful if you could tell me if you can reproduce it.
Thanks for maintaining gdb,
Bill.
-- System Information:
Debian Release: 9.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-6-amd64 (SMP w/32 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gdb depends on:
ii libbabeltrace-ctf1 1.5.1-1
ii libbabeltrace1 1.5.1-1
ii libc6 2.24-11+deb9u3
ii libexpat1 2.2.0-2+deb9u1
ii liblzma5 5.2.2-1.2+b1
ii libncurses5 6.0+20161126-1+deb9u2
ii libpython3.5 3.5.3-1
ii libreadline7 7.0-3
ii libtinfo5 6.0+20161126-1+deb9u2
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages gdb recommends:
ii libc6-dbg [libc-dbg] 2.24-11+deb9u3
Versions of packages gdb suggests:
pn gdb-doc <none>
ii gdbserver 7.12-6
-- no debconf information
dotest.sh
Description: Bourne shell script
--- End Message ---
--- Begin Message ---
Control: fixed -1 gdb/8.0-1
Thanks both for the detailed bug report.
I can't reproduce the problem with GDB 16.3 anymore. I'm closing the
bug. Feel free to reopen if it's still applicable.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/
signature.asc
Description: PGP signature
--- End Message ---
