Page 1 of 1

Minor bug with frequency_map, but causes segmentation fault

Posted: 03 Nov 2020, 18:16
by GPenn
Hi,

I have noticed an issue where if I run frequency_map on a lattice that starts with a CHARGE element, it quickly generates a segmentation fault (message is: Terminated by SIGSEGV). Attached is a simple example based on the example given in PAR/frequencyMap
It's very easy to just not have the CHARGE element, but since segmentation faults can cause other problems I thought it was worth pointing out.

To trigger the fault it is necessary both to add a CHARGE element, and either remove the RECIRC element (there just happens to be one in this example) or arrange things so the CHARGE element comes after the RECIRC element. So the issue seems to be caused by seeing the CHARGE element multiple times.

I haven't seen this with any other elegant commands

-Gregg

Re: Minor bug with frequency_map, but causes segmentation fault

Posted: 09 Nov 2020, 11:23
by michael_borland
Gregg,

Thanks for reporting this. The fix will appear in the next release.

--Michael