Re: one week to go until GDB 7.11 branch creation...

[Yao Qi <qiyaoltc@gmail.com>]

Joel Brobecker <brobecker@adacore.com> writes:

>>  - some fails in test cases added by fort_dyn_array patch on some OS and
>>    targets.  I reported them here
>>    https://sourceware.org/ml/gdb-patches/2016-01/msg00467.html
>>    and the original patch is
>>    https://sourceware.org/ml/gdb-patches/2015-10/msg00085.html
>
> For those, do they only affect Fortran, by any chance? If it is
> not a regression, then let's make this a non-blocking known issue.
> (communication between the author and myself has been infrequent,
> mostly my fault, but we may not get an answer in the near future).

As far as I can see, they only affect Fortran.  If the author or someone
else can't fix them before release, why do we still ship them in the
release?  Can't we revert the patch?  Since they were added three months
ago, it shouldn't be hard to remove them.

>
>>  - PR 19491, fail in gdb.base/multi-forks.exp
>
> Looks like an issue with the test itself, rather than a regression?

No ideas without further analysis.

>
>>  - GDB sets breakpoint on the wrong place, if the file basename is
>>    identical to the current file basename.  PR 19474.
>>    I posted a patch
>>    https://www.sourceware.org/ml/gdb-patches/2015-12/msg00321.html
>>    but it causes a regression.
>
> This one is indeed annoying. What's the status? Looks like you are
> saying the patch you suggested introduces a regression too?

Correct.

>
> Let's put it on the "blocking for branching" list for now.
> The idea would be: either we fix it before branching, or alternatively
> we branch, but only after knowing that the fix will likely be
> reasonable for backporting.

OK.

>>  - A fail in gdb.threads/interrupted-hand-call.exp
>> 
>>   $ make check
>> RUNTESTFLAGS='--target_board=remote-gdbserver-on-localhost
>> interrupted-hand-call.exp'
>> 
>>   (gdb) PASS: gdb.threads/interrupted-hand-call.exp: dummy frame popped
>>   continue^M
>>   Continuing.^M
>>   FAIL: gdb.threads/interrupted-hand-call.exp: continue until exit (timeout)
>>   Remote debugging from host 127.0.0.1^M
>>   ptrace(regsets_fetch_inferior_registers) PID=9710: No such process^M
>>   ptrace(regsets_fetch_inferior_registers) PID=9710: No such process^
>> 
>>   I suspect it is about a GDB PR about disappeared inferior, but I can't
>>   find the PR in bugzilla.  I'll look into it.
>
> A little confusing, at the very least, but if the program did terminate,
> I would say this issue is not blocking for the release. WDYT?

I am afraid not, the program didn't terminate, at least there is one
thread, as far as I can tell.  Again, nothing useful to say here without
further analysis.  PR 19508 is opened to track it.

I set the target milestone of PR 19491, PR 19474, and 19508 to "GDB
7.11", so I don't write them down in the wikipage again.

-- 
Yao (齐尧)