Front page | perl.perl5.porters |
Postings from November 2022
Hi, On Sun, 13 Nov 2022, Dave Mitchell wrote: > On Sun, Nov 13, 2022 at 07:09:12PM +0100, Uwe Düffert wrote: >> What kind of debugging symbols are you interested in? Last time, one >> suggestion was to build perl with -DDEBBUGGING, but that completely >> concealed the problem, > [...] > So > ./Configure -DEBUGGING=-g > is probably the one to try first; I can confirm that this (with one more D) already adds line numbers to valgrind output. > Another important option is > ./Configure -Duseithreads > which controls whether threads is enabled or not, and can make big changes > to certain type of code (such as globally initialising locate state). Full configure line used now is in https://uwe-dueffert.de/code/perl5.37.5/texinfo-7.0_doc_problem.sh And produces this updated valgrind output: https://uwe-dueffert.de/code/perl5.37.5/texinfo-7.0_valgrind.log > Well if you can get valgrind to complain about the double free with line > numbers (along with an indication of the args you passed to Configure) > it would be a good place to start. We (or Karl, anyway) can take it from > there. Good luck, then ;-) Regards UweThread Previous | Thread Next