From: Pedro Alves <palves@redhat.com>
To: Kaushik Phatak <Kaushik.Phatak@kpitcummins.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Yao Qi <yao@codesourcery.com>,
Pedro Alves <palves@redhat.com>
Subject: Re: [RFC] New GDB Port CR16
Date: Fri, 07 Sep 2012 17:47:00 -0000 [thread overview]
Message-ID: <504A331F.2090204@redhat.com> (raw)
In-Reply-To: <C6CA53A2A46BA7469348BDBD663AB65845B296C5@KCHJEXMB03.kpit.com>
On 09/04/2012 07:49 AM, Kaushik Phatak wrote:
> Hi Pedro,
>> Is this dependency on host signal defines what is done on other sims?
> This was probably added when breakpoint support was being added to this
> sim port with reference of the SH port I believe.
>
>> there is cruft like this in other sims. it probably would be desirable to clean it up.
> Yes Mike, I agree. I have tested it without this hunk and breakpoints seem to
> work as expected. Please see below the patch that reverts this in sim.
> I am rearranging some code to create cr16-linux-tdep.c file as suggested by Yao
> and will post the gdb related patches soon.
> Thanks!
>
>
> 2012-09-03 Kaushik Phatak<kaushik.phatak@kpitcummins.com>
>
> sim/cr16/ChangeLog:
> * interp.c: Clean SIGBUS related macro.
>
> --- gdb_src.orig/sim/cr16/interp.c 2012-09-04 12:08:34.000000000 +0530
> +++ gdb_src/src/sim/cr16/interp.c 2012-06-18 05:04:17.000000000 +0530
> @@ -1192,11 +1192,7 @@ sim_resume (SIM_DESC sd, int step, int s
> iaddr = imem_addr ((uint32)PC);
> if (iaddr == State.mem.fault)
> {
> -#ifdef SIGBUS
> State.exception = SIGBUS;
> -#else
> - State.exception = SIGSEGV;
> -#endif
> break;
> }
Looks obvious enough to me.
Though, we should really get away with using host signals for this stuff,
using sim/gdb's own signal numbers instead. For a rainy day, perhaps...
--
Pedro Alves
next prev parent reply other threads:[~2012-09-07 17:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 6:37 Kaushik Phatak
2012-08-27 16:21 ` Yao Qi
2012-08-28 14:47 ` Kaushik Phatak
2012-08-29 22:14 ` Mike Frysinger
2012-08-30 5:23 ` Kaushik Phatak
2012-08-30 6:10 ` Mike Frysinger
2012-09-03 9:31 ` Pedro Alves
2012-09-04 3:52 ` Mike Frysinger
2012-09-04 6:50 ` Kaushik Phatak
2012-09-07 17:47 ` Pedro Alves [this message]
2012-09-11 13:16 ` Kaushik Phatak
2012-09-11 19:02 ` Mike Frysinger
2012-09-24 12:55 ` Kaushik Phatak
2012-09-11 19:00 ` Mike Frysinger
2012-08-27 21:10 ` Mike Frysinger
2012-08-28 16:24 ` Pedro Alves
2012-08-30 4:49 ` Kaushik Phatak
2012-08-30 5:14 ` Yao Qi
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=504A331F.2090204@redhat.com \
--to=palves@redhat.com \
--cc=Kaushik.Phatak@kpitcummins.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.org \
--cc=yao@codesourcery.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