Nicolas Cannasse

PS: if you're doing concurrent access to objects, this is not allowed in Neko

@Horsetopus it's hard to tell when multi-thread gets involved, it comes down to whatever CPU instruction gets instructed in which order, etc. For gdb, if I remember correctly you would...

Should we should check if val_db(r->database) == NULL since the database might have been closed in the meanwhile

This is some issue related to lime and should be handled at lime level. It seems weird that there is a 256MB limit to resources as I think some projects...

@ppenzin yes, this is somewhat lime specific. Maybe recompiling and running the build tool with HashLink would prevent this error from occurring.

Well you don't have the 256MB limit. On Sat, Jan 5, 2019 at 7:18 AM Petr Penzin wrote: > Are strings allocated differently in HashLink? I haven't gotten to >...

Your __UThrowsCast is not multi-thread-safe ;)

I guess some alloc_int needs to be replaced by alloc_best_int in sqlite.c support On Wed, Jun 21, 2017 at 2:47 PM, avl93 wrote: > Sqlite in neko can only read...

Anybody else having this issue?

Uhm, it should be supported, are you sure you're not trying to read an old version of the bytecode?