bug#19676: madvise bug in guile-git

2015-01-24 Thread Linas Vepstas
Hi, I've got a test where hit guile with maybe a dozen threads doing assorted things. Doing this, I then see handful of these messages: "madvise failed: Cannot allocate memory" every 5 or 10 seconds. Except for the printing, everything seems stable. I've aptured a stack trace for this, below, b

bug#18592: FFI should have portable access to ‘errno’

2015-01-24 Thread Ludovic Courtès
Mark H Weaver skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> Chaos Eternal skribis: >> >>> Proposals to solve this bug: >>> >>> Proposal 1. >>> >>> Adding a keyword argument to pointer->procedure, if set to true, the >>> generated wrapper will check 'errno' immediately after ffi_call and

bug#18592: FFI should have portable access to ‘errno’

2015-01-24 Thread Mark H Weaver
Mark H Weaver writes: > l...@gnu.org (Ludovic Courtès) writes: > >> Chaos Eternal skribis: >> >>> Proposal 2. >>> >>> let pointer->procedure check return_type, if it is a list: >>> (func_return_type, 'errno) >>> then return multiple values, as errno be second value. >> >> That’s my favorite beca

bug#18592: FFI should have portable access to ‘errno’

2015-01-24 Thread Mark H Weaver
l...@gnu.org (Ludovic Courtès) writes: > Chaos Eternal skribis: > >> Proposals to solve this bug: >> >> Proposal 1. >> >> Adding a keyword argument to pointer->procedure, if set to true, the >> generated wrapper will check 'errno' immediately after ffi_call and >> return the errno as second value