Re: Help debugging glibc pthread_join freezing on sarge using PD/pdp/Gem software
Well, you can try http://people.redhat.com/drepper/assumekernel.html
LD_ASSUME_KERNEL=2.4.19
That will avoid NPTL and should use the libc in /lib instead of /lib/tls
See how that works. It could be that pd/gem tries to do multiple
thread_joins which will fail except in old pthreads.
On Tue, 20 Sep 2005, B. Bogart wrote:
> Hello,
>
> Ok well what happens is I try and set the v4l channel, then the
> application freezes (pd/gem). I manually kill the application and look
> at the trace and its sitting in pthread_join() just before the syscall.
> pthread_join is all I have to go on, how do I check what threads are
> running? How do I see what thread in what code is actually causing the
> freeze?
>
> I've asked on many lists so far and no one is suggesting how to get more
> information on what is actually happening (even the authors of the
> software).
>
> So if pthread_join is not the issue then please let me know how I can
> figure out what is the issue.
>
> Thanks!
>
> b.
>
> Daniel Jacobowitz wrote:
> > On Tue, Sep 20, 2005 at 01:23:12PM -0400, B. Bogart wrote:
> >
> >>Hello all,
> >>
> >>I tried on debian-user without any luck, perhaps someone on here will
> >>have an idea how I can further debug this issue. Sorry for anyone who
> >>got tired of seeing this on debian-user.
> >>
> >>I'm running a stock sarge machine with the 32bit 2.6.8 kernel on a AMD64
> >>3200+ machine. I'm using some unstable and demudi packages for media
> >>applications, in particular pure-data (PD).
> >>
> >>Problem I'm having is that PD crashes when I try and use v4l2. Actually
> >>there is no fault, but PD hangs. I traced it down to the use of
> >>pthread_join() which is where the code hangs. (I've been doing a
> >>backtrace after manually killing the application)
> >
> >
> > Why do you think it's pthread_join's fault? pthread_join will wait for
> > a thread to complete. Is the thread being joined still running?
> >
> >
>
Reply to: