From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "ian martins" Newsgroups: gmane.emacs.bugs Subject: problem with hexlify-buffer Date: Wed, 17 Apr 2002 12:11:19 -0800 Sender: bug-gnu-emacs-admin@gnu.org Message-ID: NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Trace: main.gmane.org 1019074345 2397 127.0.0.1 (17 Apr 2002 20:12:25 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 17 Apr 2002 20:12:25 +0000 (UTC) Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16xvmz-0000cY-00 for ; Wed, 17 Apr 2002 22:12:25 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16xvn7-0001GA-00; Wed, 17 Apr 2002 16:12:33 -0400 Original-Received: from law2-f52.hotmail.com ([216.32.181.52] helo=hotmail.com) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16xvlw-00018R-00 for ; Wed, 17 Apr 2002 16:11:20 -0400 Original-Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 17 Apr 2002 13:11:20 -0700 Original-Received: from 128.244.82.186 by lw2fd.hotmail.msn.com with HTTP; Wed, 17 Apr 2002 20:11:19 GMT X-Originating-IP: [128.244.82.186] Original-To: bug-gnu-emacs@gnu.org X-OriginalArrivalTime: 17 Apr 2002 20:11:20.0171 (UTC) FILETIME=[09EFFBB0:01C1E64C] Errors-To: bug-gnu-emacs-admin@gnu.org X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.bugs:753 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:753 I'm using emacs-21.2.1 on win2k, compiled with nmake. (I tried some earlier versions also, and got the same result) when I look at binary file with only an integer (32 bit) value of 60 or greater in it using emacs hexl-mode, it says: 00000000: 81a0 0000 00 ..... it should say: 00000000: a00 0000 ..... I've viewed the file with a different hex viewer and also xemacs and they both worked. for all values greater than 60 emacs sticks a hex "81" in front of the correct bytes. in case it saves someone time, here is some c code that will create two files, one containing an integer value "59" (which emacs reads correctly) the other contains an integer 60 (which doesn't work for me) #include void main() { FILE *fout1, *fout2; int n1 = 159; int n2 = 160; int *p1 = &n1; int *p2 = &n2; fout1 = fopen("f159.good","wb"); fwrite(p1, sizeof(int), 1, fout1); fout2 = fopen("f160.bad","wb"); fwrite(p2, sizeof(int), 1, fout2); fclose(fout1); fclose(fout2); } please ask if I've left out needed info. Ian Martins ianxm@hotmail.com _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.