the changes you (Allin) made to gretl in git seem not to work. If I
don't set the environment variable up, I continue to obtain the crash.
This is the output of valgrind (I assume you only need the last part)
==2059846== by 0x1F321B: gui_exec_line (library.c:10759)
==2059846== Address 0x1ffefd93ab is on thread 1's stack
==2059846== in frame #3, created by buffered_vfprintf
resolved to 'R/lib/libR.soB+�'
cannot find system Renviron
Fatal error: unable to open the base package
==2059846== HEAP SUMMARY:
==2059846== in use at exit: 13,857,526 bytes in 102,329 blocks
==2059846== total heap usage: 896,320 allocs, 793,991 frees,
84,031,037 bytes allocated
==2059846== LEAK SUMMARY:
==2059846== definitely lost: 30,776 bytes in 41 blocks
==2059846== indirectly lost: 50,779 bytes in 2,182 blocks
==2059846== possibly lost: 7,244 bytes in 67 blocks
==2059846== still reachable: 12,239,855 bytes in 89,702 blocks
==2059846== of which reachable via heuristic:
==2059846== length64 : 10,008 bytes in
==2059846== newarray : 2,288 bytes in
==2059846== suppressed: 0 bytes in 0 blocks
==2059846== Rerun with --leak-check=full to see details of leaked memory
==2059846== Use --track-origins=yes to see where uninitialised values
==2059846== For lists of detected and suppressed errors, rerun with: -s
==2059846== ERROR SUMMARY: 1111 errors from 31 contexts (suppressed: 0
El 12/3/22 a las 14:43, Allin Cottrell escribió:
On Sat, 12 Mar 2022, Riccardo (Jack) Lucchetti wrote:
> On Fri, 11 Mar 2022, Allin Cottrell wrote:
>>> If someone could give me the exact steps to run gretl with "gdb" I
>>> can try to do it.
>> Thanks, Ignacio. Here are the steps:
> valgrind can be another option for tracing the problem. Just install
> valgrind and issue the command
> valgrind /usr/bin/gretl_x11 your_script.inp
> Execution will be _very_ slow, but if you get a crash you should
> receive a list of the internal functions that led to it.
Valgrind can be very helpful in general, but this case is special.
I'm pretty sure it's not a "true" crash -- I believe that the libR
code is calling abort() when it can't find Renviron (because it
doesn't know the value of R_HOME). And when abort is called by a
library, the program that loaded the library is automatically
terminated. This is consistent with the fact that Ignacio couldn't get
a backtrace from gdb: gretl didn't segfault, it just exited.
Gretl-devel mailing list -- gretl-devel(a)gretlml.univpm.it
To unsubscribe send an email to gretl-devel-leave(a)gretlml.univpm.it