From: Richard Earnshaw <rearnsha@arm.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: jules@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [ARI regression] in arm-tdep.c
Date: Thu, 03 Sep 2009 16:01:00 -0000 [thread overview]
Message-ID: <1251993692.12941.0.camel@e200601-lin.cambridge.arm.com> (raw)
In-Reply-To: <001001ca2c6e$294c4750$7be4d5f0$@u-strasbg.fr>
On Thu, 2009-09-03 at 10:11 +0200, Pierre Muller wrote:
> Hi Jules,
>
> your patch from august 31
> add a new regression about use of abort() function
> See
> http://sourceware.org/gdb/current/ari/
>
> As stated:
> Do not use abort, instead use internal_error; GDB should never abort
>
> Below is a proposition of patch,
> but as I have no precise idea of what
> displaced_write_reg function does,
> it might be better if you commit a
> patch with a more adequate description of
> the problem, maybe something like
> "wrong write_pc argument value in displaced_write_reg fuinction"?
>
> Could you please take care of this?
>
> Pierre Muller
> GDB ARI maintainer.
>
>
> Index: arm-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/arm-tdep.c,v
> retrieving revision 1.286
> diff -u -p -r1.286 arm-tdep.c
> --- arm-tdep.c 14 Aug 2009 00:32:31 -0000 1.286
> +++ arm-tdep.c 3 Sep 2009 08:01:10 -0000
> @@ -2769,7 +2769,8 @@ displaced_write_reg (struct regcache *re
> break;
>
> default:
> - abort ();
> + internal_error (__FILE__, __LINE__,
> + _("Error inside displaced_write_reg function"));
> }
>
> dsc->wrote_to_pc = 1;
OK, though I think "Invalid argument to displaced_write_reg" might be a
better error.
R.
next prev parent reply other threads:[~2009-09-03 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090730230505.22710.qmail@sourceware.org>
2009-09-03 8:11 ` Pierre Muller
2009-09-03 16:01 ` Richard Earnshaw [this message]
2009-09-03 18:53 ` Joel Brobecker
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=1251993692.12941.0.camel@e200601-lin.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=jules@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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