Am 26.11.2015 um 20:08 schrieb Peter Bex:
> On Thu, Nov 26, 2015 at 06:01:13PM +0100, Jörg F. Wittenberger wrote:
>> Am 26.11.2015 um 11:34 schrieb Peter Bex:
Error: (assq) bad argument type: #
>>> Do you also get this when compiling said code with the 4.10.1 snapshot?
>>
>> I get the same
Something is definitely wrong at master and it is non-deterministic.
I may be able to help narrowing this down, since I get these segfaults
within minutes. But I lack any idea what to look for by now.
Most of the time I get a segfault, that is. (NB: No matter whether or
not I run with -:S the
On Thu, Nov 26, 2015 at 11:29:20AM +0100, Jörg F. Wittenberger wrote:
> Something is definitely wrong at master and it is non-deterministic.
>
> I may be able to help narrowing this down, since I get these segfaults
> within minutes. But I lack any idea what to look for by now.
>
> Most of the
Am 26.11.2015 um 11:34 schrieb Peter Bex:
> On Thu, Nov 26, 2015 at 11:29:20AM +0100, Jörg F. Wittenberger wrote:
>> Something is definitely wrong at master and it is non-deterministic.
>>
>> I may be able to help narrowing this down, since I get these segfaults
>> within minutes. But I lack any
Am 26.11.2015 um 13:56 schrieb Jörg F. Wittenberger:
> Am 26.11.2015 um 11:34 schrieb Peter Bex:
>> On Thu, Nov 26, 2015 at 11:29:20AM +0100, Jörg F. Wittenberger wrote:
>>> Something is definitely wrong at master and it is non-deterministic.
...
>>> (if (let ((g10816 key))
Am 26.11.2015 um 11:34 schrieb Peter Bex:
>> Error: (assq) bad argument type: #
> Do you also get this when compiling said code with the 4.10.1 snapshot?
I get the same strange segfaults from 4.10.1 snapshot (plus both the
mutex-related fixes I posted these days as they are essential to work
long
On Thu, Nov 26, 2015 at 06:01:13PM +0100, Jörg F. Wittenberger wrote:
> Am 26.11.2015 um 11:34 schrieb Peter Bex:
> >> Error: (assq) bad argument type: #
> > Do you also get this when compiling said code with the 4.10.1 snapshot?
>
> I get the same strange segfaults from 4.10.1 snapshot (plus
