Minor bug with frequency_map, but causes segmentation fault

Moderators: michael_borland, soliday

Post Reply
GPenn
Posts: 38
Joined: 28 Aug 2018, 09:46

Minor bug with frequency_map, but causes segmentation fault

Post by GPenn » 03 Nov 2020, 18:16

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
Attachments
FMAwithCHARGE.zip
(4.27 KiB) Downloaded 181 times

michael_borland
Posts: 1796
Joined: 19 May 2008, 09:33
Location: Argonne National Laboratory
Contact:

Re: Minor bug with frequency_map, but causes segmentation fault

Post by michael_borland » 09 Nov 2020, 11:23

Gregg,

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

--Michael

Post Reply