Re: [PATCH] gdb/testsuite: capture GDB tty name in default_gdb_spawn

[Bernd Edlinger <bernd.edlinger@hotmail.de>]

On 7/19/21 8:53 PM, Simon Marchi wrote:
>> every time I do "make check-gdb" since this patch,
>> I see a SIGSEGV in /usr/bin/expect at the end:
>>
>> The symptoms are:
>>
>> 		=== gdb Summary ===
>>
>> # of expected passes		80145
>> # of unexpected failures	867
>> # of expected failures		72
>> # of unknown successes		3
>> # of known failures		121
>> # of unresolved testcases	5
>> # of untested testcases		41
>> # of unsupported tests		257
>> # of duplicate test names	100
>> /home/ed/gnu/gdb-build-2/gdb/testsuite/../../gdb/gdb version  11.0.50.20210610-git -nw -nx -data-directory /home/ed/gnu/gdb-build-2/gdb/testsuite/../data-directory -iex "set height 0" -iex "set width 0" 
>>
>> /bin/bash: line 1:  8471 Segmentation fault      (core dumped) runtest --status
>> make[3]: *** [check-single] Error 139
>> make[3]: Leaving directory `/home/ed/gnu/gdb-build-2/gdb/testsuite'
>> make[2]: *** [check] Error 2
>> make[2]: Leaving directory `/home/ed/gnu/gdb-build-2/gdb/testsuite'
>> make[1]: *** [check] Error 2
>> make[1]: Leaving directory `/home/ed/gnu/gdb-build-2/gdb'
>> make: *** [check-gdb] Error 2
>>
>>
>> the crash is always:
>>
>> "expect -- /usr/share/dejagnu/runtest.exp --status"
>>
>> crashed with SIGSEGV in Tcl_GetChannelName()
>>
>> Do you have any idea what is wrong here, and how to fix it?
> 
> I don't know, probably an Expect bug?  Does it happen when running any
> test or when running a specific test?
> 
> What version do you have?  For reference, I have:
> 
>  - expect 5.45.4
>  - tcl 8.6.11
>  - dejagnu 1.6.2
> 
> And I don't see that.
> 

Hmm,

I see the same effect with

expect                                      5.45-5ubuntu1 
tcl                                         8.6.0+6ubuntu3
dejagnu                                     1.5-3ubuntu1

and 

expect                                        5.45.4-2build1
tcl                                           8.6.9+1
dejagnu                                       1.6.2-1


not sure what I made wrong, does anybody else have similar issues?

Bernd.