From: Philip Blundell <pb@nexus.co.uk>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@cygnus.com
Subject: Re: support for ARM GNU/Linux
Date: Wed, 14 Apr 1999 02:21:00 -0000 [thread overview]
Message-ID: <E10XLr3-0001eA-00@fountain.nexus.co.uk> (raw)
In-Reply-To: <37142B16.B43B5200@cygnus.com>
>I'm slightly curious about what is going on with all these different
>breakpoints (I should hasten to point out that I'm _not_ the ARM
>expert/maintainer :-). Stan Shebs recently commited the change:
Under Linux/ARM (and I think RISC iX, which is probably where the original
breakpoint definitions came from) the traditional way to perform a breakpoint
is to execute a particular SWI. The kernel will then stop the inferior
process with SIGTRAP and wake the debugger. For systems where there is no
explicit OS support for breakpoints, the set of opcodes that Stan put in
will provoke a CPU "undefined instruction" exception which again stops the
process. Plus of course there's an equivalent set for Thumb.
I think all of these are needed for their respective target systems. The RISC
iX support probably wants splitting out into its own file anyway; at the
moment it's hiding away in various files that are named as if they contain
only ARM generic code.
>Could I suggest including a comment explaining where your breakpoint
>instructions come from. If it is part of the LINUX/ARM environment then
>make a reference to that.
OK.
p.
next prev parent reply other threads:[~1999-04-14 2:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-12 12:26 Philip Blundell
1999-04-12 13:19 ` Scott Bambrough
1999-04-12 14:12 ` Scott Bambrough
1999-04-12 14:27 ` Philip Blundell
1999-04-12 20:18 ` Jim Blandy
1999-04-13 6:45 ` Philip Blundell
[not found] ` <E10X3Uv-0003Kd-00.cygnus.patches.gdb@fountain.nexus.co.uk>
1999-04-13 22:44 ` Andrew Cagney
1999-04-14 2:21 ` Philip Blundell [this message]
1999-04-14 3:36 ` Richard Earnshaw
1999-04-14 2:52 ` Richard Earnshaw
1999-04-14 11:34 ` Stan Shebs
1999-04-14 12:18 ` Richard Earnshaw
[not found] ` <37142B16.B43B5200.cygnus.patches.gdb@cygnus.com>
1999-04-13 23:56 ` Andrew Cagney
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=E10XLr3-0001eA-00@fountain.nexus.co.uk \
--to=pb@nexus.co.uk \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@cygnus.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