Hey everyone, it appears after a lot of well-placed (format
t)(force-output) statements, the problem isn't in the callback mechanism,
but instead in tcp-connect function itself (or rather,
cl-async-util::ip-str-to-sockaddr which seems to be overwriting its own
return address somehow). This is anoth
Right you are, I edited the example. And as you suspected, the issue still
happens =]. Any pointers on where I would start look for something like
adding :stdcall convention support to the compiler/CFFI? Thanks!
Andrew
On Fri, Jun 20, 2014 at 11:50 AM, Matthew Mondor
wrote:
> On Fri, 20 Jun 20
On Fri, 20 Jun 2014 11:19:00 -0700
Andrew Lyon wrote:
> Hello all. I'm the author of cl-async (
> https://github.com/orthecreedence/cl-async) and I'm getting segfaults when
> using it in Windows with ECL (Windows 7 x64, ECL git (52bbd351500), libffi
> 3.0.11, libevent 2.0.21, all compiled via 32b
Hello all. I'm the author of cl-async (
https://github.com/orthecreedence/cl-async) and I'm getting segfaults when
using it in Windows with ECL (Windows 7 x64, ECL git (52bbd351500), libffi
3.0.11, libevent 2.0.21, all compiled via 32bit MinGW gcc 4.8.1. I'm using
ECL's c compiler for everything (s
