Re: [commit+7.5] [patchv2] Write bpt at the ON_STACK bpt address

[Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>]

On 08/03/2012 12:07 PM, Jan Kratochvil wrote:
> On Fri, 03 Aug 2012 17:01:56 +0200, Edjunior Barbosa Machado wrote:
>> the patch below aborts the testcase if vgdb remote connection is closed,
>> avoiding the testsuite to get stuck in the `continue' loop that happens when
>> occurs the internal-error. It also considers the leading `.' for _start(),
>> which is expected in ppc64.
> 
> OK with the change below, so that the same testcase name appears during diffs
> of various testsuite results.
> 
> 
>> --- a/gdb/testsuite/gdb.base/valgrind-infcall.exp
>> +++ b/gdb/testsuite/gdb.base/valgrind-infcall.exp
> [...]
>> @@ -97,6 +97,10 @@ while 1 {
>>  	    pass $test
>>  	    break
>>  	}
>> +	-re "Remote connection closed.*\r\n$gdb_prompt $" {
>> +	    fail "Remote connection closed. Testcase aborted"
> 
> fail "$test (remote connection closed)"
> 
>> +	    return -1
>> +	}
>>  	-re "\r\n$gdb_prompt $" {
>>  	    pass "$test (false warning)"
>>  	}
> 
> 
> Thanks,
> Jan
> 

Thanks!
Checked in with the aforementioned change:
	http://sourceware.org/ml/gdb-cvs/2012-08/msg00036.html

Btw, is it OK for 7.5 branch too?

-- 
Edjunior