From: Juha Aaltonen <turbopultti@gmail.com>
To: gdb-mailing list <gdb@sourceware.org>
Subject: Re: remote supporting 'swbreak' and 'hwbreak' ?
Date: Wed, 11 Nov 2015 22:39:00 -0000 [thread overview]
Message-ID: <CAHR0xd4r0de6HXkQqZErYgSV=KEyA5t=B=eER+XAofpewTvuaw@mail.gmail.com> (raw)
In-Reply-To: <CAHR0xd5T2T7AAUa2iDP-pc4hHNY+=Or42LA1GDW9s62=P6mmcg@mail.gmail.com>
Found it in the gdb server sources: ';' was missing from the end.
I thought it was a separator, that shouldn't be there after last item.
On Wed, Nov 11, 2015 at 6:49 PM, Juha Aaltonen <turbopultti@gmail.com> wrote:
> If a remote 'agent' supports 'swbreak' and 'hwbreak', what's the
> correct "syntax" for T05-packet?
>
> And is 'hwbreak+' needed in qSupported response if only SW breakpoints
> and HW watchpoints are supported (not actual HW breakpoints)?
>
> I've tried 'T05swbreak" with and without single quotes around swbreak,
> and with and without colon, but gdb always complains about malformed
> packet.
>
>
> I'm using "GNU gdb (Debian 7.10-1) 7.10".
next prev parent reply other threads:[~2015-11-11 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 16:49 Juha Aaltonen
2015-11-11 22:39 ` Juha Aaltonen [this message]
2015-11-11 22:41 ` Juha Aaltonen
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='CAHR0xd4r0de6HXkQqZErYgSV=KEyA5t=B=eER+XAofpewTvuaw@mail.gmail.com' \
--to=turbopultti@gmail.com \
--cc=gdb@sourceware.org \
/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