Eli Zaretskii writes:
> Also, since the only way I could get a functional MinGW Guile was to
> configure it without threads, I would suggest that this be the default
> for MinGW, but that isn't a big deal.
FWIW, the situation seems to have improved since you last looked. In
the last couple of we
I realize the _i_ will have to be replaced, and the name
scm_c_with_continuation_barrier is already taken, however,
I found in writing gdb/guile/scm-safe-call.c that
scm_i_with_continuation_barrier is exactly what I need. Since it's
not available I had to do two levels of calls where one should
su
On Tue, Feb 18, 2014 at 3:06 PM, Ludovic Courtès wrote:
> Doug Evans skribis:
>
>> I see (at least) two high level problems.
>>
>> 1) Some apps need ability to use their own signal handlers.
>
> You mean the "real" signal handler, right?
Right.
>> 2) Remove need for a separate thread.
>>
>> I'm
Eli Zaretskii skribis:
>> From: l...@gnu.org (Ludovic Courtès)
>> Cc: xdj...@gmail.com, gdb-patc...@sourceware.org, guile-devel@gnu.org
>> Date: Tue, 18 Feb 2014 18:45:53 +0100
>>
>> > Sorry, I meant why that code couldn't be used when Guile was built
>> > without pthreads.
>>
>> Because with
Doug Evans skribis:
> I see (at least) two high level problems.
>
> 1) Some apps need ability to use their own signal handlers.
You mean the “real” signal handler, right?
> 2) Remove need for a separate thread.
>
> I'm not addressing (2) in this patch, though I am allowing for the day
> when th
Hi,
A question come up at ##prolog of guile-log supporting servers that keeps
on tail calling and as a consequence any logical variables not referencable
needs to be gc:ed.
Currently there is a call ideom that will basically do a call and then
transfer a few
variable to results and then backtrack
> From: l...@gnu.org (Ludovic Courtès)
> Cc: guile-devel@gnu.org
> Date: Tue, 18 Feb 2014 18:32:34 +0100
>
> > I don't know if they were, though. One thing I do know is that the
> > request to gnulib maintainers to include hstrerror, which I posted, at
> > your request, here
> >
> > http://list
> From: l...@gnu.org (Ludovic Courtès)
> Cc: xdj...@gmail.com, gdb-patc...@sourceware.org, guile-devel@gnu.org
> Date: Tue, 18 Feb 2014 18:45:53 +0100
>
> > Sorry, I meant why that code couldn't be used when Guile was built
> > without pthreads.
>
> Because with the patch Doug posted, both the
On Tue, Feb 18, 2014 at 9:42 AM, Ludovic Courtès wrote:
> (Dropping GDB.)
>
> Doug Evans skribis:
>
>> On Tue, Feb 18, 2014 at 3:20 AM, Ludovic Courtès wrote:
>
> [...]
>
>>> (I think we should aim to get rid of the signal-delivery thread
>>> eventually, and I remember Mark mentioned it before t
(Dropping GDB.)
Doug Evans skribis:
> On Tue, Feb 18, 2014 at 3:20 AM, Ludovic Courtès wrote:
[...]
>> (I think we should aim to get rid of the signal-delivery thread
>> eventually, and I remember Mark mentioned it before too.)
>
> Note that Python queues the asyncs directly from the signal h
Eli Zaretskii skribis:
>> From: l...@gnu.org (Ludovic Courtès)
>> Cc: xdj...@gmail.com, gdb-patc...@sourceware.org, guile-devel@gnu.org
>> Date: Tue, 18 Feb 2014 17:45:27 +0100
[...]
>> >> The non-pthread code is used when Guile is built without pthread
>> >> support. In that case, the async
Eli Zaretskii skribis:
>> From: l...@gnu.org (Ludovic Courtès)
>> Cc: Eli Zaretskii , gdb-patc...@sourceware.org,
>> guile-devel@gnu.org
>> Date: Tue, 18 Feb 2014 12:20:39 +0100
>>
>> Doug Evans skribis:
>>
>> I don’t remember, Eli: do you have patches pending review for these
>> issues and o
On Tue, Feb 18, 2014 at 3:20 AM, Ludovic Courtès wrote:
> Right, when Guile is built with pthread support, it has a signal
> delivery thread. The actual SIGINT handler ('take_signal' in scmsigs.c)
> just write one byte to a pipe; the signal delivery thread reads from
> that pipe, and queues an as
> From: l...@gnu.org (Ludovic Courtès)
> Cc: xdj...@gmail.com, gdb-patc...@sourceware.org, guile-devel@gnu.org
> Date: Tue, 18 Feb 2014 17:45:27 +0100
>
> >> I don’t remember, Eli: do you have patches pending review for these
> >> issues and other MinGW issues in Guile?
> >
> > I don't know, you
Eli Zaretskii skribis:
>> From: l...@gnu.org (Ludovic Courtès)
>> Cc: Eli Zaretskii , gdb-patc...@sourceware.org,
>> guile-devel@gnu.org
>> Date: Tue, 18 Feb 2014 12:20:39 +0100
>>
>> Doug Evans skribis:
>>
>> I don’t remember, Eli: do you have patches pending review for these
>> issues and o
> From: l...@gnu.org (Ludovic Courtès)
> Cc: Eli Zaretskii , gdb-patc...@sourceware.org,
> guile-devel@gnu.org
> Date: Tue, 18 Feb 2014 12:20:39 +0100
>
> Doug Evans skribis:
>
> I don’t remember, Eli: do you have patches pending review for these
> issues and other MinGW issues in Guile?
I don
Doug Evans skribis:
> On Mon, Feb 17, 2014 at 1:13 PM, Eli Zaretskii wrote:
>>> Date: Mon, 17 Feb 2014 12:59:22 -0800
>>> From: Doug Evans
>>> Cc: "gdb-patc...@sourceware.org" ,
>>> guile-devel@gnu.org
>>>
>>> >> +void
>>> >> +gdbscm_initialize_sigint (void)
>>> >> +{
>>> >> + siscm_sigint_pi
17 matches
Mail list logo
