From: Luis Gustavo <luis_gustavo@mentor.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Regressions in gdbserver mode #2 [Re: General regressions in gdbserver mode]
Date: Sun, 26 Feb 2012 23:09:00 -0000 [thread overview]
Message-ID: <4F4AB8BA.8050708@mentor.com> (raw)
In-Reply-To: <20120226215423.GA9147@host2.jankratochvil.net>
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
next prev parent reply other threads:[~2012-02-26 22:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 20:33 [rfc target-side break conditions 0/5 v2] General info Luis Gustavo
2012-02-06 13:33 ` [ping] " Luis Gustavo
2012-02-07 21:32 ` Stan Shebs
2012-02-08 23:05 ` Luis Gustavo
2012-02-24 15:28 ` Luis Gustavo
2012-02-25 15:40 ` General regressions in gdbserver mode [Re: [rfc target-side break conditions 0/5 v2] General info] Jan Kratochvil
2012-02-25 15:57 ` Luis Gustavo
2012-02-25 17:19 ` Jan Kratochvil
2012-02-25 18:25 ` Luis Gustavo
2012-02-25 19:40 ` Luis Gustavo
2012-02-25 19:41 ` Jan Kratochvil
2012-02-25 20:08 ` Luis Gustavo
2012-02-26 22:57 ` Regressions in gdbserver mode #2 [Re: General regressions in gdbserver mode] Jan Kratochvil
2012-02-26 23:09 ` Luis Gustavo [this message]
2012-02-28 16:19 ` Jan Kratochvil
2012-02-27 4:46 ` Luis Gustavo
2012-02-27 5:55 ` Jan Kratochvil
2012-02-27 16:23 ` Luis Gustavo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F4AB8BA.8050708@mentor.com \
--to=luis_gustavo@mentor.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox