2009/3/14 Neil Jerram
> Stanislav Ievlev writes:
>
> > It's very strange but I see an only one thread. full Backtrace in attach.
>
> That is indeed odd. Are you using GDB, and the "info threads"
> command, and it lists only one thread?
Yes, "info threads" shows me only one thread.
2009/3/14 Neil Jerram
> Stanislav Ievlev writes:
>
> > It's very strange but I see an only one thread. full Backtrace in attach.
>
> That is indeed odd. Are you using GDB, and the "info threads"
> command, and it lists only one thread?
>
> > > #0 0x2b4ba31b4004 in __lll_lock_wait () fr
Stanislav Ievlev writes:
> It's very strange but I see an only one thread. full Backtrace in attach.
That is indeed odd. Are you using GDB, and the "info threads"
command, and it lists only one thread?
> > #0 0x2b4ba31b4004 in __lll_lock_wait () from /lib64/libpthread.so.0
> > #1
Hi,
Stanislav Ievlev writes:
> #6 0x2b98cf981eaf in scm_list_1 () from /usr/lib64/libguile.so.17
> #7 0x2b98cf964099 in gdb_maybe_valid_type_p () from
> /usr/lib64/libguile.so.17
All theses `gdb_*' calls are strange. They refer to Guile's GDB
interface, which never got to the point
It's very strange but I see an only one thread. full Backtrace in attach.
2009/3/12 Neil Jerram
> Stanislav Ievlev writes:
>
> > Greetings!
> >
> > On my 2.6.18 kernel guile (latest snapshot from git, branch-release-1.8
> head)
> > in some situations (unfortunately I can't made a testcase) sto
Stanislav Ievlev writes:
> Greetings!
>
> On my 2.6.18 kernel guile (latest snapshot from git, branch-release-1.8 head)
> in some situations (unfortunately I can't made a testcase) stops forever.
> Guile
> with 2.6.27 kernel works well.
>
> Strace:
> futex(0xc571890, FUTEX_WAIT, 2, NULL...
>
>
