From: Antoine Tremblay <antoine.tremblay@ericsson.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] Fix inconsistent breakpoint kinds between breakpoints and tracepoints in GDBServer.
Date: Thu, 22 Oct 2015 19:58:00 -0000 [thread overview]
Message-ID: <56290999.9070103@ericsson.com> (raw)
In-Reply-To: <56290915.9060608@redhat.com>
On 10/22/2015 12:04 PM, Pedro Alves wrote:
> On 10/22/2015 05:03 PM, Antoine Tremblay wrote:
>>
>>
>> On 10/22/2015 11:58 AM, Pedro Alves wrote:
>>> On 10/22/2015 04:56 PM, Antoine Tremblay wrote:
>>>> This patch fixes a regression introduced by :
>>>> https://sourceware.org/ml/gdb-patches/2015-10/msg00369.html
>>>>
>>>> Tests : gdb.trace/trace-break.exp and gdb.trace/trace-mt.exp would fail on x86
>>>> with gdbserver-{native,extended}.
>>>>
>>>> Before this patch, the breakpoint kind set by GDB with a Z packet and the one
>>>> set in the case of a tracepoint would be inconsistent on targets that did not
>>>> implement breakpoint_kind_from_pc. On x86 for example a breakpoint set by GDB
>>>> would have a kind of 1 but a breakpoint set by a tracepoint would have a kind of
>>>> 0.
>>>>
>>>> This created a missmatch when trying to insert a tracepoint and a breakpoint at
>>>> the same location. One of the two breakpoints would be removed with debug
>>>> message : "Inconsistent breakpoint kind".
>>>>
>>>> This patch fixes the issue by changing the default 0 breakpoint kind to be
>>>> the size of the breakpoint according to sw_breakpoint_from_kind.
>>>>
>>>> The default breakpoint kind must be the breakpoint length to keep consistency
>>>> between breakpoints set via GDB and the ones set internally by GDBServer.
>>>>
>>>> No regression on Ubuntu 14.04 x86-64 with gdbserver-{native-extended}
>>>>
>>>> gdb/gdbserver/ChangeLog:
>>>>
>>>> * linux-low.c (default_breakpoint_kind_from_pc): New function.
>>>> (linux_breakpoint_kind_from_pc): Use default_breakpoint_kind_from_pc for
>>>> the default breakpoint kind.
>>>
>>> OK.
>>>
>>
>> I forgot to set the function default_breakpoint_kind_from_pc static, ok
>> with that change ?
>
> Sure.
>
> (I think you'll need to move the function to target.c to
> fix !Linux ports, but I'm OK with doing that as a separate step.)
>
I don't think so since I fix !linux ports like so :
/* Implementation of the target_ops method "breakpoint_kind_from_pc". */
static int
win32_breakpoint_kind_from_pc (CORE_ADDR *pcptr)
{
return the_low_target.breakpoint_len;
}
/* Implementation of the target_ops method "sw_breakpoint_from_kind". */
static const gdb_byte *
win32_sw_breakpoint_from_kind (int kind, int *size)
{
*size = the_low_target.breakpoint_len;
return the_low_target.breakpoint;
}
?
next prev parent reply other threads:[~2015-10-22 16:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 16:04 [PATCH] " Antoine Tremblay
2015-10-22 16:11 ` Pedro Alves
2015-10-22 16:14 ` Antoine Tremblay
2015-10-22 16:23 ` [PATCH v2] " Antoine Tremblay
2015-10-22 16:26 ` Pedro Alves
2015-10-22 17:42 ` Antoine Tremblay
2015-10-22 19:58 ` Pedro Alves
2015-10-22 19:58 ` Antoine Tremblay [this message]
2015-10-22 19:58 ` Pedro Alves
2015-10-23 1:42 ` Antoine Tremblay
2015-10-23 8:18 ` Antoine Tremblay
2015-10-23 8:52 ` Pedro Alves
2015-10-23 15:05 ` Antoine Tremblay
2015-10-23 16:48 ` Antoine Tremblay
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=56290999.9070103@ericsson.com \
--to=antoine.tremblay@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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