Re: Regressions in gdbserver mode #2 [Re: General regressions in gdbserver mode]

Luis Gustavo
2012-02-26T22:57:01Z

Hi Jan,

On 02/26/2012 06:54 PM, Jan Kratochvil wrote:
> On Sat, 25 Feb 2012 20:58:53 +0100, Luis Gustavo wrote:
>> I've checked the following in.
>
> Still getting now these regressions in gdbserver non-extended mode:
>
> -PASS: gdb.base/save-bp.exp: info break
> +FAIL: gdb.base/save-bp.exp: info break
> +FAIL: gdb.cp/mb-templates.exp: initial condition: run to breakpoint (timeout)
> +FAIL: gdb.cp/mb-templates.exp: initial condition: run to breakpoint 2 (GDB internal error)
> +FAIL: gdb.cp/mb-templates.exp: ...

Yes. I am aware of those.

I've mentioned the mb-templates.exp one in the first mail about the
series. It seems to be a problem that i uncovered when dealing with the
agent expressions machinery on GDB's side. I'll debug this next.

The save-bp.exp one is due to the additional information that is output
by info break. I'll have a patch for that soon (to make it accept
additional info after the condition expression).

Luis

>
> info break
> Num Type Disp Enb Address What
> 2 breakpoint keep y 0x0000000000400540 in break_me at ./gdb.base/save-bp.c:21
> 3 breakpoint keep y 0x000000000040054a in main at ./gdb.base/save-bp.c:27
> 4 breakpoint keep y 0x000000000040054f in main at ./gdb.base/save-bp.c:28 thread 1
> stop only in thread 1
> 5 breakpoint keep y 0x000000000040055d in main at ./gdb.base/save-bp.c:31
> stop only if i == 1 (host evals)
> 6 breakpoint keep y 0x000000000040056c in main at ./gdb.base/save-bp.c:33
> silent
> (gdb) FAIL: gdb.base/save-bp.exp: info break
>
> (I did not check now what is expeted.)
>
> (gdb) continue
> Continuing.
> ax-gdb.c:560: internal-error: gen_fetch: bad type code
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> Quit this debugging session? (y or n) Found breakpoint condition.
> FAIL: gdb.cp/mb-templates.exp: initial condition: run to breakpoint (timeout)
>
>
> Regards,
> Jan