Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: frederic.riss@st.com
Cc: jimb@red-bean.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC] DW_CFA_restore handling causes memory fault
Date: Fri, 18 Nov 2005 14:21:00 -0000	[thread overview]
Message-ID: <200511181345.jAIDjZNc026609@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <1132317183.8685.101.camel@crx549.cro.st.com> (message from Frederic RISS on Fri, 18 Nov 2005 13:33:03 +0100)

> X-From_: gdb-patches-return-41536-m.m.kettenis=alumnus.utwente.nl@sourceware.org  Fri Nov 18 13:38:27 2005
> From: Frederic RISS <frederic.riss@st.com>
> Date: Fri, 18 Nov 2005 13:33:03 +0100
> 
> On Fri, 2005-11-18 at 00:35 -0800, Jim Blandy wrote:
> > Yes!  But --- I apologize for not noticing this from the beginning ---
> > as I see your comment, it occurs to me that probably a call to
> > 'complaint' would be better than just a comment.  Mark or Daniel can
> > string me up if they feel this will yield another 'incomplete CFI
> > data; unspecified blah blah blah' annoyance, but I think it's probably
> > the right thing.

On the highest tree!  Seriously though, if it turns out to be a major
annoyance, we can always do something about it later.  So this is fine
to me ;-).

> OK, third try attached. I mimiced the formatting of other complaints of
> the file. I didn't put the complaint in the 'else' clause, but added a
> check after the whole 'if', because an allocated register state isn't
> necessarily set to a correct value.

That could possibly lead to two complaints about the same
"unspecified" register, but let's see what happens with this patch.

> Just a question: why are the i18n'ified strings formatted this way ?

Formatted in what way?  Starting in column 0?  Well, that's because
it's easier to see whether the string will be longer than 80
characters, which your string will be once the %s is filled in.  So
could you split the string over two lines?  You're going to have to do
that anyway, because I'm going to ask you to make a little change: can
you also print the register number for the register that the complaint
is about?

Thanks,

Mark


  reply	other threads:[~2005-11-18 13:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17 18:58 Frederic RISS
2005-11-17 19:46 ` Jim Blandy
2005-11-18 12:12   ` Frederic RISS
2005-11-18 12:32     ` Jim Blandy
2005-11-18 13:30       ` Frederic RISS
2005-11-18 14:21         ` Mark Kettenis [this message]
2005-11-18 15:55           ` Frederic RISS
2005-11-23 16:51           ` Frederic RISS
2005-11-25 10:32             ` Mark Kettenis
2005-11-25 14:31               ` Frederic RISS
2005-11-25 18:35                 ` Daniel Jacobowitz
2005-11-25 23:00                 ` Mark Kettenis
2005-11-25 23:21                   ` Joel Brobecker
2005-11-28 19:30                     ` Frederic RISS
2005-11-18 14:43         ` Eli Zaretskii
2005-11-18 15:08           ` Frederic RISS

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=200511181345.jAIDjZNc026609@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=frederic.riss@st.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@red-bean.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