src/gnu/usr.bin/gdb/libgdb/fbsd-threads.c, branch release/7.0.0_cvs FreeBSD source tree This commit was manufactured by cvs2svn to create tag 2008-02-24T05:45:17+00:00 cvs2svn cvs2svn@FreeBSD.org 2008-02-24T05:45:17+00:00 a9c219fa3cec18ef9f30edec6fa106bf0e2d423d 'RELENG_7_0_0_RELEASE'. This commit was manufactured to restore the state of the 7.0-RELEASE image. 
'RELENG_7_0_0_RELEASE'.

This commit was manufactured to restore the state of the 7.0-RELEASE image.
Avoid writing uninitialized stack data into a thread's MMX/SSE state by 2007-02-20T18:10:13+00:00 Ed Maste emaste@FreeBSD.org 2007-02-20T18:10:13+00:00 5a16cfaeb6a845fff113b9d8e1027a033abb50a6 first getting the current state with td_thr_getxmmregs_p. Without this, debugging a threaded app that uses libthr resulted in kernel panics or spurious SIGFPEs for me. (As of revision 1.6, sys/i386/i386/ptrace_machdep.c masks off the reserved bits in the mxcsr register, which prevents the kernel panics.) Architectures without PT_GETXMMREGS are not affected. MFC after: 1 week 
first getting the current state with td_thr_getxmmregs_p.  Without this,
debugging a threaded app that uses libthr resulted in kernel panics or
spurious SIGFPEs for me.

(As of revision 1.6, sys/i386/i386/ptrace_machdep.c masks off the
reserved bits in the mxcsr register, which prevents the kernel panics.)

Architectures without PT_GETXMMREGS are not affected.

MFC after:      1 week
Introduce a new proc service routine ps_linfo() to get LWP info. 2006-02-07T02:29:55+00:00 David Xu davidxu@FreeBSD.org 2006-02-07T02:29:55+00:00 d56a014b6e3794e617dc3f2405227fe4727afb9f 






1. Eliminate compile warnings.
2006-02-06T06:07:56+00:00

David Xu
davidxu@FreeBSD.org

2006-02-06T06:07:56+00:00

9224f6b811bd52b6c073eb0e164eba5c269648ce

2. Add command 'thread signal' to print out current thread's signal mask
   and pending signals.





2. Add command 'thread signal' to print out current thread's signal mask
   and pending signals.







Add support for XMM registers in GDB for x86 processors that support
2005-05-31T09:43:04+00:00

Doug Rabson
dfr@FreeBSD.org

2005-05-31T09:43:04+00:00

8d7681bb7fc40b6681f759c2f6051e84cfc6d087

SSE (or its successors).

Reviewed by: marcel, davidxu
MFC After: 2 weeks





SSE (or its successors).

Reviewed by: marcel, davidxu
MFC After: 2 weeks







Don't try to enable event reporting for core file, it is not writable.
2005-05-06T11:01:15+00:00

David Xu
davidxu@FreeBSD.org

2005-05-06T11:01:15+00:00

e8595f94cd98433cc0cc0dde48d39d4fed233064












Report events from thread library.
2005-04-12T03:04:04+00:00

David Xu
davidxu@FreeBSD.org

2005-04-12T03:04:04+00:00

e6e653cd66818e7d2f7531c51ac49908482c6e92












Print thread address.
2005-04-05T11:40:58+00:00

David Xu
davidxu@FreeBSD.org

2005-04-05T11:40:58+00:00

0d6c666e742f75381d1036f73c09b7062121312a

PR: threads/76821





PR: threads/76821







When grabbing registers for an lwp, fake the inferior's pid using the
2005-01-11T14:53:16+00:00

Peter Edwards
peadar@FreeBSD.org

2005-01-11T14:53:16+00:00

ad93bc4a369f5d4b4283ab437a71ddcc6d5484cb

lwp ID before invoking the underlying target operation.

For corefiles, we rely on gdb internals to do this, and it uses the
pid as an index, rather than the lwpid, so previously, backtraces
for multithreaded core files wasn't working correctly. For processes,
we currently use ptrace directly, so fixup that code to also use
the pid directly.

Discussed With: marcel, davidxu
MFC After: 4 days





lwp ID before invoking the underlying target operation.

For corefiles, we rely on gdb internals to do this, and it uses the
pid as an index, rather than the lwpid, so previously, backtraces
for multithreaded core files wasn't working correctly. For processes,
we currently use ptrace directly, so fixup that code to also use
the pid directly.

Discussed With: marcel, davidxu
MFC After: 4 days







Always set current thread when activating thread debugger,
2004-11-15T13:06:01+00:00

David Xu
davidxu@FreeBSD.org

2004-11-15T13:06:01+00:00

ba4030c7addd9e8e62a547ad85db6ec690996f2b

the current thread may already be added by fbsd_find_new_threads,
this can result that current thread is not set correctly.





the current thread may already be added by fbsd_find_new_threads,
this can result that current thread is not set correctly.