Re: [Gc] GNU Guile 2.0.10 released

Panicz Maciej Godek <[email protected]>
Newsgroups gmane.comp.programming.garbage-collection.boehmgc,gmane.lisp.guile.user
Message-ID <CAMFYt2b4DgFNtvA=nEiuZWuJEKCgCE6FQWfL1xSZoBKDiLJGAg@mail.gmail.com>
2014-03-26 19:24 GMT+01:00 Eli Zaretskii <eliz-mXXj517/[email protected]>:
>> I had a "process hacker" tool installed, and it allows me to do some
>> introspection (although I understand very little). [...]
>
> Isn't this the same problem I reported last year, starting here:
>
>   http://lists.gnu.org/archive/html/guile-user/2013-06/msg00022.html
>
> I suggest to configure Guile --without-threads, and see if that
> resolves the issue.

I suspect that it is. But I wanted to rebuild my SLAYER framework for
Windows and make a new release with Guile 2.0.10 and threads enabled
-- because then it would make more sense to distribute it.

I wish I knew a way to find out whether the problem is on Guile's or
GC's or mingw's or pthreads-win32's side.

Some guys who had similar problem (i.e. their process also stopped at
"ntdll!KiUserApcDispatcher+0x7") suggest that it is a busy resource:
http://stackoverflow.com/questions/2214465/debugging-the-dreaded-application-has-failed-to-initialize-error

So now, instead of just compiling --without-threads, I'd like to
somehow get the threaded version working, even it takes much more time
and more digging.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.