When using the graph operator in r.mapcalc and when using many points (+500) to define the graph, I am getting a ‘Segmentation fault (core dumped)’. This is shown after the calculation has (apparently) finished.
It is difficult to really check whether the whole calculation has been carried out correctly, but the new layer looks OK. I did notice that in the meta data (r.info) of the new layer, only the statement ‘generated by r.mapcalc’ is given, while normally the whole r.mapcalc statement would be shown. Could that be related to the segmentation fault message?
When using the graph operator in r.mapcalc and when using many points
(+500) to define the graph, I am getting a 'Segmentation fault (core
dumped)'. This is shown after the calculation has (apparently) finished.
It is difficult to really check whether the whole calculation has been
carried out correctly, but the new layer looks OK. I did notice that in the
meta data (r.info) of the new layer, only the statement 'generated by
r.mapcalc' is given, while normally the whole r.mapcalc statement would be
shown. Could that be related to the segmentation fault message?
The expression is added to the history as a comment. The code which
formats the expression had a fixed-sized buffer of 1024 arguments, so
512 or more x,y pairs would overflow it.
On Sat, Aug 18, 2012 at 8:03 PM, Glynn Clements
<glynn@gclements.plus.com> wrote:
Paulo van Breugel wrote:
When using the graph operator in r.mapcalc and when using many points
(+500) to define the graph, I am getting a 'Segmentation fault (core
dumped)'. This is shown after the calculation has (apparently) finished.
It is difficult to really check whether the whole calculation has been
carried out correctly, but the new layer looks OK. I did notice that in the
meta data (r.info) of the new layer, only the statement 'generated by
r.mapcalc' is given, while normally the whole r.mapcalc statement would be
shown. Could that be related to the segmentation fault message?
The expression is added to the history as a comment. The code which
formats the expression had a fixed-sized buffer of 1024 arguments, so
512 or more x,y pairs would overflow it.
This should be fixed in r52725.
Paulo sent me the formula, I have tried it, fix confirmed, working now.
I can also confirm it works in the in GRASS 7.0 r52727
Thanks a lot for this quick fix!
Paulo
On 08/19/2012 10:03 AM, Markus Neteler wrote:
On Sat, Aug 18, 2012 at 8:03 PM, Glynn Clements
<glynn@gclements.plus.com> wrote:
Paulo van Breugel wrote:
When using the graph operator in r.mapcalc and when using many points
(+500) to define the graph, I am getting a 'Segmentation fault (core
dumped)'. This is shown after the calculation has (apparently) finished.
It is difficult to really check whether the whole calculation has been
carried out correctly, but the new layer looks OK. I did notice that in the
meta data (r.info) of the new layer, only the statement 'generated by
r.mapcalc' is given, while normally the whole r.mapcalc statement would be
shown. Could that be related to the segmentation fault message?
The expression is added to the history as a comment. The code which
formats the expression had a fixed-sized buffer of 1024 arguments, so
512 or more x,y pairs would overflow it.
This should be fixed in r52725.
Paulo sent me the formula, I have tried it, fix confirmed, working now.