In msg103780 Martin v. Löwis wrote:
> Ah, ok. That was the problem indeed. The patch actually works fine.
Good to hear.  Thanks for tracking this down and clarifying it.

As I understand it, the current status of this bug is that file17000 fixes the reported issue, but hasn't yet been applied to trunk.

In msg103781 Nick Coghlan wrote:
> I still get one failure after that, even after a "make clean", "make", 
> "./python -m test.regrtest -v test_gdb". Given the "unable to read 
> Python frame information" embedded in the result on my machine (64-bit 
> Kubuntu 9.10), it is probably related to the current issue.
I believe this is a different issue; please can you open a separate bug about this.  Reading the frame information seems to be highly sensitive to the optimization level and the exact version of gcc for the build, and the exact version of gdb, alas.  I've been tracking a failure like the one you describe, seen on 64-bit with Fedora in our downstream tracker here:
https://bugzilla.redhat.com/show_bug.cgi?id=556975