Date: Sat, 02 Jun 2001 08:28:00 +0300 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: Nate Eldredge Message-Id: <3405-Sat02Jun2001082759+0300-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9 CC: djgpp AT delorie DOT com In-reply-to: <83y9rcc8hc.fsf@mercury.bitbucket> (message from Nate Eldredge on 01 Jun 2001 12:20:47 -0700) Subject: Re: GDB and FSDB - getting x86 specific info (page tables, ldt, gdt) References: <000b01c0ea24$55501dd0$e70610ac AT speakeasy DOT net> <2593-Fri01Jun2001085054+0300-eliz AT is DOT elta DOT co DOT il> <831yp4wusv DOT fsf AT mercury DOT bitbucket> <3405-Fri01Jun2001112310+0300-eliz AT is DOT elta DOT co DOT il> <83y9rcc8hc DOT fsf AT mercury DOT bitbucket> 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 > From: Nate Eldredge > Newsgroups: comp.os.msdos.djgpp > Date: 01 Jun 2001 12:20:47 -0700 > > > > > > > > Please define ``dump memory''. GDB generally displays memory > > > > addresses as variables; if you mean ``dump memory'' the DEBUG.COM > > > > style, then it cannot do that, even for memory that is part of the > > > > normal DS selector addressable range. > > > > > > What about the `x' command? That certainly can dump memory in a > > > format rather like debug's. > > > > Not without some tricky use of GDB advanced features, such as > > ``artifical arrays''. > > Huh? A command like > > x/32x 0xaddress > > doesn't seem especially tricky or advanced to me. This is not ``dumping memory'' in my book. That's why I said (see above) that GDB displays memory addresses as variables, meaning that you can easily display the contents of an address interpreted as a single int, or short, or double. But ``dumping memory'' normally means displaying a relatively large portion of memory between two addresses.