From: Simon Marchi <simon.marchi@polymtl.ca>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>,
gdb-patches@sourceware.org,
Tobias Klausmann <klausman@schwarzvogel.de>,
rth@twiddle.net
Subject: Re: [PATCH]: Fix PR19061, gdb hangs/spins-on-cpu when debugging any program on Alpha
Date: Thu, 31 May 2018 14:55:00 -0000 [thread overview]
Message-ID: <4a93db59737d2b7ebbea5982180f16d2@polymtl.ca> (raw)
In-Reply-To: <CAFULd4aFah-xkSoCQNQOHA5i1R21D24Qmkr0iJ4Rf64R4rYd_w@mail.gmail.com>
On 2018-05-31 05:23, Uros Bizjak wrote:
> On Wed, May 30, 2018 at 4:53 PM, Simon Marchi
> <simon.marchi@ericsson.com> wrote:
>> Does Alpha even have hardware breakpoints? If not, I would suggest
>> defining GDB_ARCH_IS_TRAP_HWBKPT to 0 for __alpha__. It would get
>> rid of the error, and be more exact (no si_code can mean "hardware
>> breakpoint" on alpha).
>
> I didn't find any mentions of hardware breakpoint support in Alpha
> Architecture Handbook v.4.
>
> Please note that save_stop_reason from linux-nat.c has some code to
> detect ambigous si_code, where si_code is both TRAP_BRKPT and
> TRAP_HWBKPT, and returns TARGET_STOPPED_BY_SW_BREAKPOINT in this case.
> So, if we don't define anything for __alpha__ in nat/linux-ptrace.h,
> we get the same result.
TRAP_BKPT and TRAP_HWBKPT are different, so this will never happen with
the default definitions of
GDB_ARCH_IS_TRAP_BRKPT/GDB_ARCH_IS_TRAP_HWBKPT. Since the kernel for
alpha never sets si_code to TRAP_HWBKPT, it means we'll never get in to
the HW breakpoint branch, which is fine.
In short, the patch LGTM.
> I have tested the attached patch, and resulting gdb works OK for me.
Thanks!
Simon
next prev parent reply other threads:[~2018-05-31 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 12:11 Uros Bizjak
2017-12-15 18:21 ` Pedro Alves
2017-12-17 18:11 ` Uros Bizjak
2017-12-17 19:14 ` Uros Bizjak
2018-01-03 16:02 ` Pedro Alves
2018-05-30 18:07 ` Simon Marchi
2018-05-30 18:49 ` Uros Bizjak
2018-05-30 19:04 ` Simon Marchi
2018-05-31 11:10 ` Uros Bizjak
2018-05-31 14:55 ` Simon Marchi [this message]
2018-05-31 16:18 ` Simon Marchi
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=4a93db59737d2b7ebbea5982180f16d2@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=klausman@schwarzvogel.de \
--cc=rth@twiddle.net \
--cc=simon.marchi@ericsson.com \
--cc=ubizjak@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).