Re: GDB bug or something else?

[Valery Ushakov <uwe%stderr.spb.ru@localhost>]

On Thu, Oct 22, 2026 at 09:29:04 +0100, Sad Clouds wrote:

> The test program is attached. Can anyone think of reasons why single
> stepping through the program with GDB results in incorrect value read
> from the stack, instead of 0x12345? Using GDB x/xg command to examine
> the value at the specified address also gives the same incorrect value.

Register window flushed?  Print $i6 after writing to the stack.  You
are probably getting _taht_ value back when you read and print it.

-uwe