[PATCH 2/2] gdb.threads/attach-into-signal.exp: don't rely on linux native target's internal debug output

[Jan Kratochvil]

On Mon, 20 Feb 2012 13:25:32 +0100, Pedro Alves wrote:
> On 02/20/2012 08:57 AM, Jan Kratochvil wrote:
> > On Fri, 17 Feb 2012 20:37:50 +0100, Pedro Alves wrote:
> >> > +		    set test2 "pull thread list"
> >> > +		    gdb_test_multiple "info threads" $test2 {
> >> > +			-re "\r\n$gdb_prompt $" {
> >> > +			}
> >> > +		    }
> > This can be just:
> > 		    gdb_test "info threads" ".*" "pull thread list"
> 
> I avoided that on purpose, because that'd generate a PASS for every
> attempt/iteration at trying to catch the signal.

OK, I agree now.


> > Still this is a bug of extended gdbserver mode.
> 
> Yeah, it could be considered a bug.  Not only of extended gdbserver
> tough.  It happens with all remote targets, and we have similar things
> in other tests.  One thing at a time though, otherwise, I'll never be
> done.  :-)

Yes; but it should be somehow marked/filed, unless you track this issue
already.


Thanks,
Jan