Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: GDB patches <gdb-patches@sourceware.org>
Subject: Re: New ARI warning Wed Dec 13 01:56:09 UTC 2017
Date: Wed, 13 Dec 2017 03:02:00 -0000	[thread overview]
Message-ID: <CAAfxs77O4X_+fmYh8NzfyLQKPDSuP0NUQtgz9h_3Cma9Ginx8Q@mail.gmail.com> (raw)
In-Reply-To: <9452aa8f742176ecf3bce3044dd74854@polymtl.ca>

On 13 Dec 2017 11:53 a.m., "Simon Marchi" <simon.marchi@polymtl.ca> wrote:

On 2017-12-12 20:56, GDB Administrator wrote:

> 394a395,403
>
>> gdb/or1k-tdep.c:135: gettext: _ markup: All messages should be marked up
>> with _.
>>
> gdb/or1k-tdep.c:135:        error ("bitstring \"%s\" at offset %d has no
> length field.\n",
>
>> gdb/or1k-tdep.c:144: gettext: _ markup: All messages should be marked up
>> with _.
>>
> gdb/or1k-tdep.c:144:        error ("bitstring \"%s\" at offset %d has no
> terminating 'b'.\n",
>
>> gdb/or1k-tdep.c:161: gettext: _ markup: All messages should be marked up
>> with _.
>>
> gdb/or1k-tdep.c:161:      error ("invalid character in bitstring \"%s\"
> at offset %d.\n",
>
>> gdb/or1k-tdep.c:544: code: %p: Do not use printf(%p), instead use
>> printf(%s,paddr()) to dump a target address, or host_address_to_string()
>> for a host address
>>
> gdb/or1k-tdep.c:544:    fprintf_unfiltered (gdb_stdlog,
> "or1k_unwind_pc, pc=0x%p\n",
>
>> gdb/or1k-tdep.c:564: code: %p: Do not use printf(%p), instead use
>> printf(%s,paddr()) to dump a target address, or host_address_to_string()
>> for a host address
>>
> gdb/or1k-tdep.c:564:    fprintf_unfiltered (gdb_stdlog,
> "or1k_unwind_sp, sp=0x%p\n",
>
>> gdb/or1k-tdep.c:885: code: %p: Do not use printf(%p), instead use
>> printf(%s,paddr()) to dump a target address, or host_address_to_string()
>> for a host address
>>
> gdb/or1k-tdep.c:885:                    "or1k_frame_cache, prologue_cache
> = 0x%p\n",
>
>> gdb/or1k-tdep.c:945: gettext: _ markup: All messages should be marked up
>> with _.
>>
> gdb/or1k-tdep.c:945:    error ("end addr 0x%08x is less than start
> addr 0x%08x\n",
>
>> gdb/or1k-tdep.c:1071: code: %p: Do not use printf(%p), instead use
>> printf(%s,paddr()) to dump a target address, or host_address_to_string()
>> for a host address
>>
> gdb/or1k-tdep.c:1071:      fprintf_unfiltered (gdb_stdlog, "
> this_sp_for_id = 0x%p\n",
>
>> gdb/or1k-tdep.c:1073: code: %p: Do not use printf(%p), instead use
>> printf(%s,paddr()) to dump a target address, or host_address_to_string()
>> for a host address
>>
> gdb/or1k-tdep.c:1073:      fprintf_unfiltered (gdb_stdlog, "
> start_addr     = 0x%p\n",
>

Hi Stafford,

Could you address the warnings mentioned above?  They should be pretty
straightforward, I think it will be an obvious patch.

Simon


Hi Simon,

Yes I just saw this. I'm out until the end of the day. I should be able to
have patches ready after I get home.

(Also replying on my phone so the multipart message might not make it to
the list.)

- Stafford


      reply	other threads:[~2017-12-13  3:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13  1:56 GDB Administrator
2017-12-13  2:53 ` Simon Marchi
2017-12-13  3:02   ` Stafford Horne [this message]

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=CAAfxs77O4X_+fmYh8NzfyLQKPDSuP0NUQtgz9h_3Cma9Ginx8Q@mail.gmail.com \
    --to=shorne@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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