Message-Id: <3.0.1.32.20010423135434.006ce910@wingate>
X-Sender: n_abing#ns DOT roxas-online DOT net DOT ph AT wingate
X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
Date: Mon, 23 Apr 2001 13:54:34 +0800
To: djgpp AT delorie DOT com
From: "Nimrod A. Abing" <n_abing AT ns DOT roxas-online DOT net DOT ph>
Subject: Re: can gdb display the processor registers?
Cc: dennis51 AT jps DOT net
In-Reply-To: <3.0.1.32.20010423130443.006ce944@wingate>
References: <3AE3A817 DOT 565DD680 AT jps DOT net>
 <3 DOT 0 DOT 1 DOT 32 DOT 20010423104500 DOT 006cdd44 AT wingate>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

At 01:04 PM 04/23/2001 +0800, you wrote:
>At 08:57 PM 04/22/2001 -0700, you wrote:
>>> Whilst running your program under gdb, type info ``all-registers''
(without
>>> the quotes) on the gdb command line.
>>
>>It doesn't work, this is what I get:
>>
>>(gdb) all-registers
>>Undefined command: "all-registers".  Try "help".
>>(gdb) registers
>>Undefined command: "registers".  Try "help".
>
>Oops! Made a little booboo there ;-) From the gdb command prompt, type
>``info all-registers''. Although I would suggest to read the GDB docs
>first, at least you'd know most of the basic and commonly used gdb commands.

Also be sure that the program is being debugged currently <*running*>, i.e.
place a breakpoint on an instruction or function in your program. When you
run it and you hit the breakpoint, you can then use the ``info'' command to
display your program's status. Type ``help info'' on the gdb command line
to see other information that you can view with the ``info'' command.

nimrod_a_abing
--------------

+========================================+
|  Home page: www.geocities.com/n_abing  |
+========================================+

"Tinimbang ka ngunit kulang."
If you understand that phrase, i-email mo'ko. ;-)