From: Pedro Alves <palves@redhat.com>
To: Luis Machado <lgustavo@codesourcery.com>, gdb-patches@sourceware.org
Cc: macro@linux-mips.org
Subject: Re: [PATCH, v3] Expect SI_KERNEL or TRAP_BRKPT si_code values for MIPS breakpoint traps
Date: Wed, 24 Feb 2016 16:46:00 -0000 [thread overview]
Message-ID: <56CDDE42.8060903@redhat.com> (raw)
In-Reply-To: <56CDC1C6.9040400@redhat.com>
On 02/24/2016 02:44 PM, Pedro Alves wrote:
> On 02/24/2016 01:21 PM, Luis Machado wrote:
>
>> Yes. We need to check the MIPS debug registers unconditionally and not
>> just when a meaningful si_code of TRAP_HWBKPT shows up.
>
> Yeah, though we won't be able to do that unconditionally, due
> to the s390 quirk.
>
>> Did you want that in the same patch or in a separate one? I was
>> attempting to address the software breakpoint issue for now, but it
>> seems i ended up with 2 problems now. :-)
>
> I see this as a single problem of a regression caused by the
> rely-on-si_code change. So I think we should fix it with a single patch.
> Give me a bit while I try an approach here.
Posted here:
https://sourceware.org/ml/gdb-patches/2016-02/msg00734.html
Could you give it a try?
Thanks,
Pedro Alves
prev parent reply other threads:[~2016-02-24 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 22:20 Luis Machado
2016-02-22 22:41 ` Pedro Alves
2016-02-22 22:48 ` Luis Machado
2016-02-23 0:01 ` Maciej W. Rozycki
2016-02-23 2:00 ` Luis Machado
2016-02-23 21:09 ` Maciej W. Rozycki
2016-02-24 12:55 ` Pedro Alves
2016-02-24 13:21 ` Luis Machado
2016-02-24 14:44 ` Pedro Alves
2016-02-24 16:46 ` Pedro Alves [this message]
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=56CDDE42.8060903@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=macro@linux-mips.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