picca

Nothing, more, did you red the Debian thread ? I think that it would be nice o discuss with the guy who does the real job.

Here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889878

here the valgrind output on the arm64 porter box from debian ``` (sid_arm64-dchroot)picca@amdahl:~/hkl/Documentation/figures$ ../../libtool --mode=execute valgrind --leak-check=full --show-leak-kinds=all --main-stacksize=1000000 sirius ==7368== Memcheck, a memory error detector ==7368== Copyright (C) 2002-2017,...

here my generator ``` struct Trajectory { enum trajectory_e tag; union { struct {double h0; double k0; double l0; double h1; double k1; double l1; uint n; struct Mode mode;}...

And indeed te code which call the generator ``` HklGeometryList *Trajectory_solve(struct Trajectory tconfig, struct Geometry gconfig, struct Sample sconfig, uint move) { const struct Engine *econfig; HklGeometryList *solutions = hkl_geometry_list_new();...

Thanks a lot for your reply, I can confirm that using 4 times the current stack_size (8192*4), make the problem vanish for my use case. Now it is time to...

It vanish on the arm64 architecture, but even if I increase a lot the stack size, on amd64 it still faill

the stack trace is a bit different ``` #0 0x000055555559311f in trajectory_gen_generator__ (ret=0x557be730) at hkl2.c:246 #1 0x00007ffff6aefd70 in () at /lib/x86_64-linux-gnu/libc.so.6 #2 0x0000000000000000 in () ```

the sefgault arise when I define the generator. ```c generator_def(trajectory_gen, struct Engine, struct Trajectory, tconfig) { switch(tconfig.tag){ case TRAJECTORY_HKL_FROM_TO: { uint i; double dh = (tconfig.hklfromto.h1 - tconfig.hklfromto.h0) / (tconfig.hklfromto.n);...

Here the valgrind output on amd64 ```valgrind (sid_amd64-dchroot)picca@barriere:~/hkl$ ./libtool --mode=execute valgrind --track-origins=yes Documentation/figures/sirius ==21449== Memcheck, a memory error detector ==21449== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et...