Bochs Dump GDT Register

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
brodeur235
Member
Member
Posts: 86
Joined: Sat Jun 06, 2009 11:55 am

Bochs Dump GDT Register

Post by brodeur235 »

How can I get Bochs to dump the GDT register?

Brodeur235
quok
Member
Member
Posts: 490
Joined: Wed Oct 18, 2006 10:43 pm
Location: Kansas City, KS, USA

Re: Bochs Dump GDT Register

Post by quok »

There's this really nifty command you can use in the bochs debugger: help

It will list all the commands and give you a description of what they do. I'm sure you can find your answer in there.
User avatar
gravaera
Member
Member
Posts: 737
Joined: Tue Jun 02, 2009 4:35 pm
Location: Supporting the cause: Use \tabs to indent code. NOT \x20 spaces.

Re: Bochs Dump GDT Register

Post by gravaera »

Really though, does this kind of thing need to be said?

For your edification, please understand that individual software products usually have their own support systems, which, for unix projects generally hold a simple, straightforward technical document which tells you all of the commands and gives you the expected output from each one.

Much like this link which was the first result in a google search for 'Using the Bochs debugger'.

This user support system is both created, and hosted, and usually maintained by the developers of that software who are independent of this forum. Therefore we do not qualify as a support 'back-end'. So when having trouble using some party's unassociated tool, go to that party for help with their tool. EOF.
17:56 < sortie> Paging is called paging because you need to draw it on pages in your notebook to succeed at it.
User avatar
xenos
Member
Member
Posts: 1121
Joined: Thu Aug 11, 2005 11:00 pm
Libera.chat IRC: xenos1984
Location: Tartu, Estonia
Contact:

Re: Bochs Dump GDT Register

Post by xenos »

It's funny that people always point to some documentation without checking that the information requested by the OP is actually in there. In fact, the most helpful command in this case is not contained in the docs. So, here it is:

info gdt

This will dump the complete GDT. There are several similar commands, such as info ldt, info idt, info ivt, info tss... I did not find them via the docs either, but rather manually through lexer.l and parser.y.

If you are just interested in the register contents of the GDTR, LDTR, IDTR and so on, info cpu should also suffice.

Hope that helps. (And this you can take literally.)

PS: Even more funny, that the developers of bochs are indeed members of this forum, often respond to questions and bug reports here, and that quite a lot of people in here actually use bochs and are able to answer such questions - and some are even willing to do so.
Programmers' Hardware Database // GitHub user: xenos1984; OS project: NOS
User avatar
bewing
Member
Member
Posts: 1401
Joined: Wed Feb 07, 2007 1:45 pm
Location: Eugene, OR, US

Re: Bochs Dump GDT Register

Post by bewing »

@OP -- I don't suppose you are using the bochs GUI debugger. It's even easier there. Just select "Show System Registers".
Post Reply