On Wed, 2013-11-06 at 01:07 +0100, Benoît Minisini wrote: > What is the exact definition of 'uuid_t' ? > From http://linux.die.net/man/3/uuid_unparse
The uuid_unparse function converts the supplied UUID uu from the binary representation into a 36-byte string (plus tailing '\0') of the form 1b4e28ba-2fa1-11d2-883f-0016d3cca427 and stores this value in the character string pointed to by out. The case of the hex digits returned by uuid_unparse may be upper or lower case, and is dependent on the system-dependent local default. i.e. it is the 16byte UUID returned by uuid_generate From http://linux.die.net/man/3/uuid_generate The UUID is 16 bytes (128 bits) long, which gives approximately 3.4x10^38 unique values (there are approximately 10^80 elementary particles in the universe according to Carl Sagan's Cosmos). > Also, you can use valgrind to know when exactly the faulty memory access > occurs. This will give better clues. Could, if I knew how to... :-) The thing is, the extern calls work, it is only when the module exits that the Segfault occurs. So it even looks (to me) like the Free()s work. I have tried using the routine as a function and it works, the problem only happens when the Main() method exits. rgds Bruce ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
