From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16809 invoked by alias); 27 Jun 2004 04:20:48 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 16792 invoked from network); 27 Jun 2004 04:20:47 -0000 Received: from unknown (HELO blount.mail.mindspring.net) (207.69.200.226) by sourceware.org with SMTP; 27 Jun 2004 04:20:47 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by blount.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1BeR9p-0002oD-00; Sun, 27 Jun 2004 00:20:45 -0400 Received: by berman.michael-chastain.com (Postfix, from userid 502) id CABC44B104; Sun, 27 Jun 2004 00:20:52 -0400 (EDT) To: cagney@gnu.org, mec.gnu@mindspring.com Subject: Re: native hppa2.0w-hp-hpux11.00, 32-bit versus 64-bit Cc: gdb@sources.redhat.com, tausq@debian.org Message-Id: <20040627042052.CABC44B104@berman.michael-chastain.com> Date: Sun, 27 Jun 2004 04:20:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-06/txt/msg00263.txt.bz2 ac> What's the ABI wordsize - the size of a register pushed onto the stack? ac> "info registers" should be using that register size and looking at the ac> HP/PA code, that appears to be the case. It's 4 bytes, all right. ac> It might also pay to check out `file gdb`, `file test-program`, "(gdb) ac> show architecture" and "(gdb) maint print registers" to see what's been ac> compbined. At least for other architectures only a 64-bit native /home/mec/bin/gdb-611: PA-RISC1.1 shared executable dynamically linked -not stripped a.out: PA-RISC2.0 shared executable dynamically linked -not stripped (gdb-611) show architecture The target architecture is set automatically (currently hppa1.0) The funny thing is, gdb 6.1.1 "maint print registers" says that r19 is 4 bytes long, but "info reg r19" has special code to print all 8 bytes of it. I'm still kinda dubious, but if it's okay with randolph that the debugger quietly operates in 32-bit mode, it's okay with me. I would do something like this: gdb_test_multiple "info reg r19" "$name" { -re "r19 deadbeefbadcadee ..." { pass "$name (64 bit)" } -re "r19 "badcadee ..." { pass "$name (32 bit)" } } Michael C