Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 May 1999 06:16:46 -0400 (EDT)
From:      Daniel Eischen <eischen@vigrid.com>
To:        dfr@nlsystems.com, jb@cimlogic.com.au
Cc:        current@FreeBSD.ORG
Subject:   Re: Debugging uthreads
Message-ID:  <199905121016.GAA08837@pcnet1.pcnet.com>

next in thread | raw e-mail | index | archive | help
John Birrell wrote:
> Doug Rabson wrote:
> > Other gdb thread debugging systems tend to export a set of variables from
> > the thread library which describe the important offsets in the thread
> > structure e.g. _debug_pthread_status_offset, _debug_pthread_foo_offset
> > etc.
>
> > If you think there will be a real problem, I could do this I guess.
>
> Maybe we should just isolate the things that gdb is allowed to look at
> and document them as "cast in stone".

Why don't we make a libc_r_db and provide the necessary interfaces to
gdb from that instead of having gdb know about uthread internals?

Dan Eischen
eischen@vigrid.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905121016.GAA08837>