gdb.threads/threxit-hop-specific.exp failure

[Ulrich Weigand]

FAIL: gdb.threads/threxit-hop-specific.exp: get past the thread specific breakpoint

warning: Breakpoint address adjusted from 0x4002d29d to 0x4002d29c.^M
start_thread (arg=<value optimized out>) at pthread_create.c:285^M
285 pthread_create.c: No such file or directory.^M
        in pthread_create.c^M

Originally tracked as part of Bug #616006.

This is actually combination of two separate issues:

- The warning "Breakpoint address adjusted" is caused by arm_get_longjmp_target not removing the Thumb bit from the longjmp target address; the rest of the code doesn't cope well with breakpoint addresses with Thumb bit set.

- The stop in start_thread happens because I've installed the libc-dbg debug info packages, so that GDB actually considers the pthread implementation to be routines it ought to stop in. This is really a bug in the test case as-is. On the other hand, this doesn't show up elsewhere because usually libc debuginfo is not installed during GDB test suite runs; we only have to do it on Arm because of missing prologue parsing support for Thumb-2 code ...

[Ulrich Weigand (uweigand)]

For the breakpoint address adjusted issue, see the discussion on gdb-patches started at:
http://sourceware.org/ml/gdb-patches/2010-08/msg00271.html

For the start_thread debug info problem, see the discussion on gdb-patches started at:
http://sourceware.org/ml/gdb-patches/2010-08/msg00224.html

[Ulrich Weigand (uweigand)]

Fix checked into mainline:
http://sourceware.org/ml/gdb-patches/2010-09/msg00179.html
http://sourceware.org/ml/gdb-cvs/2010-09/msg00057.html