Re: Fix PR breakpoints/16101: gdb.base/dprintf.exp agent-printf, failures with non-Z0-supporting gdbservers

[Hui Zhu <hui_zhu at mentor dot com>]

Hi Pedro,

Thanks for your patch.

On 03/25/14 03:39, Pedro Alves wrote:
> AFAICT, this is actually PR16101, not PR16494.  Adjusting subject.
>
> On 03/23/2014 11:35 AM, Hui Zhu wrote:
> > On 03/21/14 21:11, Pedro Alves wrote:
>
>
> Similarly for the MI test.
>
> This patch makes the tests handle this scenario.
>
> Tested with native, and native gdbserver on x86_64 Fedora 17.
>
> Also tested with the native-gdbserver.exp board hacked with:
>
>   set GDBFLAGS "${GDBFLAGS} -ex \"set remote breakpoint-commands off\""
>
> (actually, "set remote breakpoint-commands off" is presently broken,
> so this was on top of a fix for that command.)

Do you have plan to fix it?

> which results in:
>   (gdb) PASS: gdb.base/dprintf.exp: 2nd dprintf, gdb
>   set dprintf-style agent
>   warning: Target cannot run dprintf commands, falling back to GDB printf
>   warning: Target cannot run dprintf commands, falling back to GDB printf
>   (gdb) UNSUPPORTED: gdb.base/dprintf.exp: set dprintf style to agent
>
> gdb.sum:


> (One of the new comments mentions breakpoint always-inserted mode.
> Actually testing with breakpoint always-inserted mode fails these
> dprintf tests, due to the way they are written.  But that'll take a
> more substancial rewrite of the tests, so I'm leaving that for another
> day.)

I tried "set breakpoint always-inserted on", "set breakpoint always-inserted off" and
"set breakpoint always-inserted auto".  But I didn't get fail.
Do you mind let me take a look on the log?

Best,
Hui