public inbox for
 help / color / mirror / Atom feed
From: Nick Clifton <>
Subject: Re: small patch for objdump
Date: Tue, 27 Oct 1998 14:42:00 -0000	[thread overview]
Message-ID: <> (raw)

: Date: Tue, 27 Oct 1998 16:46:12 +0100
: From: Philip Blundell <>
: I just found this change in my tree.  I made it some months ago to fix a 
: problem with addresses above 0x80000000 being reported incorrectly when 
: disassembling code.  Although I haven't tested versions later than the 2.9.1
: release it looks like the problem is still there; would someone like to 
: take a look?  Thanks.
: p.
: 1998-10-27  Philip Blundell  <>
: 	* objdump.c (disassemble_bytes): Make address variables unsigned
: 	to avoid problems when disassembling code at high-bit-set
: 	addresses.

I checked, and you are right, the code was still using signed
addresses.  (Of course some processors do have signed address spaces,
but they are in the minority).  So, I have applied your patch.


             reply	other threads:[~1998-10-27 14:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-27 14:42 Nick Clifton [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-10-27  8:47 Philip Blundell

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).