public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Nicholas Sherlock <n.sherlock@gmail.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb@sourceware.org
Subject: Re: ARM EABI Linux, breakpoints cause SIGILL and target dies
Date: Tue, 24 Jan 2012 02:44:00 -0000	[thread overview]
Message-ID: <CADwwazavZ-qwsG3Jm15ZL6-fx0r0JK41qWO9_YTEtOkztjsYnQ@mail.gmail.com> (raw)
In-Reply-To: <201201231329.q0NDTGAR004332@d06av02.portsmouth.uk.ibm.com>

On 24 January 2012 02:29, Ulrich Weigand <uweigand@de.ibm.com> wrote:
> If this does not work correctly for some reason, this would explain
> both why GDB doesn't recognize the situation *and* also why the
> kernel doesn't recognize the breakpoint instruction to convert the
> signal into a SIGTRAP.

Yeah, that sounds likely.

> Do you see any differences either here in traps.c, or in one of the
> entry-*.S assembler files, between your two kernels?

Thanks for the pointer! I found the commit that fixed this bug in the
ARM kernel entry routine:

https://github.com/cyanogen/cm-kernel-exp/commit/d12aee22b3e025a4b76d4078f76542ea8cbd0315#diff-0

I'll port that patch over to my kernel and see if it fixes GDB.

Cheers,
Nicholas Sherlock

  reply	other threads:[~2012-01-24  2:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADwwazYuWuicgqL=4JyxbdoN+6MmVg354bD6UTzC=Ew-po8JzA@mail.gmail.com>
2012-01-20  2:45 ` Nicholas Sherlock
2012-01-20 10:45   ` Ulrich Weigand
2012-01-22 23:34     ` Nicholas Sherlock
2012-01-23  1:29       ` Nicholas Sherlock
2012-01-23 13:29         ` Ulrich Weigand
2012-01-24  2:44           ` Nicholas Sherlock [this message]
2012-01-24  3:02             ` Nicholas Sherlock
2012-01-24 13:37               ` Ulrich Weigand

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=CADwwazavZ-qwsG3Jm15ZL6-fx0r0JK41qWO9_YTEtOkztjsYnQ@mail.gmail.com \
    --to=n.sherlock@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=uweigand@de.ibm.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).