Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: zhigang gong <zhigang.gong@gmail.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Wrong data type in function unpack_varlen_hex()
Date: Thu, 13 Jul 2006 04:07:00 -0000	[thread overview]
Message-ID: <20060713040658.GZ24622@nevyn.them.org> (raw)
In-Reply-To: <40c9f5b20606160558v277bb813r9d5a497c9899432@mail.gmail.com>

On Fri, Jun 16, 2006 at 08:58:33PM +0800, zhigang gong wrote:
> Hi,
> 
>        I am working on an mips4k platform. When I added hw watchpoint
> support for my target board and debug it with gdb. The write
> watchpoint works fine, but rwatch and awatch doesn't work. After trace
> the source code of the gdb, I found there is a bug in
> unpack_varlen_hex. The local variable retval is a signed integer. For
> my case, the ULONGEST is a 64bit integer type. So when the
> watchpoint's address is 0x8XXXXXXX, the "retval" will be 0x8XXXXXXX,
> and pass its value to variable "result", the "result"'s value will be
> sign extended to 0xFFFFFFFF8XXXXXXX. Then when i set a rwatch point,
> the address matching will fail when the read watchpoint ocurred.
>     The patch is as belows. And I test it,

Thank you for the patch.  This is definitely an improvement, so I have
committed it.

There may be more problems here: addresses on MIPS are generally
considered to be signed, so it might be a bug somewhere else in GDB
that you're getting 0x000000008xxxxxxx.  But, we'll worry about that
only if it causes a problem for someone else.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-07-13  4:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16 12:58 zhigang gong
2006-07-13  4:07 ` Daniel Jacobowitz [this message]
2006-07-13 15:19   ` zhigang gong
2006-07-13 15:23     ` Daniel Jacobowitz
2006-07-13 15:36       ` Daniel Jacobowitz
2006-07-15 10:34         ` zhigang gong
2006-07-17  0:10           ` Daniel Jacobowitz

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=20060713040658.GZ24622@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=zhigang.gong@gmail.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