Thanks, I figured as much. I just thought I remember being told at one
point that gdb's thread support on FreeBSD had improved. Given a choice
between adding thread support to GDB myself and developing my application
on NT, which by the way has very good thread debugging support on MSVC6.0.
I think I would rather just spend a weekend adding support to GDB.
-Kip
On Wed, 15 Sep 1999, f.johan.beisser wrote:
>
> sorry folks, i passed this on to someone who should know..
>
> jan
>
> ---------- Forwarded message ----------
> Date: Wed, 15 Sep 1999 17:07:33 -0400 (EDT)
> From: Chris Doherty <cdohe...@wopr.skidmore.edu>
> To: f.johan.beisser <j...@caustic.org>
> Subject: Re: does gdb on 3.3RC have thread support? (fwd)
>
> Kip--
>
> I'm not actually on the lists; your message was forwarded to me.
>
> the first place to check is the documentation at www.gnu.org; that
> will tell you that thread support in gdb is sketchy--"present on some
> platforms" is what I think it says. I wrote an application this past
> summer using pthreads and had no debugging support; I know nothing
> about uthreads but wouldn't be surprised if the same thing was true.
>
> things you *can* do:
>
> 1. printf() is, as always, your friend.
> 2. gdb will happily set breakpoints at arbitrary lines in arbitrary
> files, or simply at the beginning of a function. since each of my
> threads ran a separate function, I could set a breakpoint at that
> function and there gdb would stop. inefficient and somewhat painful,
> but it worked. although I didn't go into it, you may be able to set a
> breakpoint in another thread while the program is running.
>
> this was all on 3.2 and 3.1, but afaik the versions of gdb are roughly
> the same.
>
> HTH, sorry I didn't have better news...
>
> Chris
>
>
> > Date: Wed, 15 Sep 1999 12:20:49 -0700 (PDT)
> > From: Kip Macy <k...@lyris.com>
> > To: freebsd-sta...@freebsd.org, freebsd-hackers@FreeBSD.ORG
> > Subject: does gdb on 3.3RC have thread support?
> >
> > When I run my program under ddd, press Ctrl-C to return control to gdb and
> > then type info threads at the gdb prompt it returns nothing.
> >
> > When I run it under gdb on the command line and do the same as above, gdb
> > dumps core.
> >
> > How should I proceed? Should I grab the source for uthreads from current?
> >
> >
> > -Kip
> >
> >
>
> --------------------------------------
> Only this, THIS!
> Soen
> --------------------------------------
> Chris cdohe...@skidmore.edu
> a.k.a. Fuzzy Logic
> --------------------------------------
>
>
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-hackers" in the body of the message
>
>
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
