This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi Samuel! On Tue, 16 Sep 2014 01:09:50 +0200, Samuel Thibault <samuel.thibault@gnu.org> wrote: > Thomas Schwinge, le Tue 16 Sep 2014 00:08:01 +0200, a Ãcrit : > > Do you agree that thread_get_state(i386_DEBUG_STATE) should be > > returning the actual DR6, > > Indeed. > > > and where in GNU Mach would we need to copy the DR6 > > register into the PCB? > > it would be user_trap(), probably, in the T_DEBUG case. Thanks for the pointer. Something like the following does accomplish its task w.r.t. GDB, but there are some TODO items. It might help to compare what the Linux kernel is doing; Âgit grep --cached -i dr6 -- arch/x86/Â or similar. diff -ru gnumach-1.4.orig/i386/i386/trap.c gnumach-1.4/i386/i386/trap.c --- gnumach-1.4.orig/i386/i386/trap.c 2013-09-27 08:05:57.000000000 +0200 +++ gnumach-1.4/i386/i386/trap.c 2014-09-16 10:45:58.000000000 +0200 @@ -404,6 +404,17 @@ return 0; } #endif + + /* Make the content of the debug status register (DR6) + available to user space. */ + /* TODO: Do we have to sanitize its content? (Mask out + reserved bits?) */ + /* TODO: Where should its content be reset (zeroed)? From user + space? */ + /* TODO: Anything to take care about w.r.t interaction with + KDB? */ + thread->pcb->ims.ids.dr[6] = get_dr6(); + exc = EXC_BREAKPOINT; code = EXC_I386_SGL; break; GrÃÃe, Thomas
Attachment:
pgpn1yDk1HNL1.pgp
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |