|Message: GPS segmentation fault at end of program||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
I have a very strange segmentation fault occurring directly at the end of my program once everything is finished.
The very last line of code is executed in the main which prints "Finished" which it does but then does Segmentation fault (core dumped).
I've narrowed down the problem to using these GPS commands. Specificity whenever I use any biasing commands such as:
/gps/hist/point 0.00 1.00
/gps/hist/point 0.10 1.02
/gps/hist/point 0.20 1.04
/gps/hist/point 0.30 1.06
/gps/hist/point 0.40 1.08
/gps/hist/point 0.50 1.10
/gps/hist/point 0.60 1.08
/gps/hist/point 0.70 1.06
/gps/hist/point 0.80 1.04
/gps/hist/point 0.90 1.02
/gps/hist/point 1.00 1.00
What's stranger is that it wont lead to a segmentation fault if I apply the commands but don't run the simulation. It's only once when I run the simulation that once the program goes to exit that it leads to a segmentation fault once it has literally done everything. If I don't use these commands at all then I don't have this issue.
This isn't a massive issue as I've said it happens once the program has finished but could be a problem when wrapping this program and shouldn't happen to begin with.
Does anyone have any suggestions on how to fix or solve this or is this a bug?