Re: [capnproto] Re: Segfault during JSON encode() in v0.6.1

2018-03-07 Thread Marc Sune
t; > Is it at all possible that your generated code was created with a > different version of Cap'n Proto compiler vs. the runtime library and/or > headers you are compiling against? > > -Kenton > > On Mon, Mar 5, 2018 at 2:34 PM, Marc Sune <ma...@voltanet.io > > wrote

Re: [capnproto] Re: Segfault during JSON encode() in v0.6.1

2018-03-05 Thread Marc Sune
a copy or not. Marc On Monday, March 5, 2018 at 10:43:11 PM UTC+1, Marc Sune wrote: > > Thanks Kenton, > > An update on this. I am leaning to think it is an stack overflow, although > I couldn't confirm 100%. The truth is that, calling the same code from the > main(), with the

[capnproto] Re: Segfault during JSON encode() in v0.6.1

2018-03-02 Thread Marc Sune
> That's about all that I can get, even though capnproto is compiled with DEBUG. Or shall I say, it should :/ On Friday, March 2, 2018 at 7:17:02 PM UTC+1, Marc Sune wrote: > > Hi guys, > > I am experiencing a _very_ strange segfault during JSON encoding of > message:

Re: [capnproto] Re: Segfault during JSON encode() in v0.6.1

2018-03-02 Thread Marc Sune
would complain before the SEGFAULT if something would be out of the stack, and the only thing I get is the direct SEGFAULT. Any thoughts? I will keep trying to isolate the problem marc -Kenton > > On Fri, Mar 2, 2018 at 10:18 AM, Marc Sune <ma...@voltanet.io > > wrote: > >&g