Dear all,
I was now able to test my hypothesis that this is/was a bug in Linux
that has been fixed since. Here's what I tried:
0. Under the old system, the test failed with the previously mentioned
error message. To make sure it wasn't caused by some weird system state,
I rebooted the
Dear Bill, dear Héctor,
I am also experiencing this issue, and I may be able to narrow it down a
bit further.
Specifically, I have two different stretch machines, only one of which
has this issue.
The two machines are very similar in terms of software: one was last
upgraded in early
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
3 matches
Mail list logo
