[GRASS-dev] seemingly random errors in r.mapcalc

[Sören Gebbert]

Hi,
you can set the environment variable GRASS_SIGSEGV_ON_ERROR to raise a
segmentation fault signal that can be catched by gdb. Then you can
make backtrace and send it to the list.

I hope we will be able to help you then ... but i am not sure.

I assume you use bash or equivalent:
{{{
export GRASS_SIGSEGV_ON_ERROR=1

gdb r.mapcalc

(gdb) r expr="test = 1 + 1"
...
(gdb) bt
... stack
}}}

Best regards
Soeren

2013/8/2 Paulo van Breugel <p.vanbreugel at gmail.com>:
> Sorry, pushed the short cut sending the email off too early.. What I wanted
> to ask is, is there any way I can find out what kind of error I am getting?
> Now, the only message is "Error".
>
>
>
> On Fri, Aug 2, 2013 at 12:38 PM, Paulo van Breugel <p.vanbreugel at gmail.com>
> wrote:
>>
>> One reason I did not think about problem to be related to hard drive
>> issues is that I would expect other GRASS functions to fail, at least
>> occasionally, as well as other programs.
>>
>>
>>
>> On Fri, Aug 2, 2013 at 4:32 AM, Glynn Clements <glynn at gclements.plus.com>
>> wrote:
>>>
>>>
>>> Paulo van Breugel wrote:
>>>
>>> > I am really puzzled as to what is going on here. Any idea what I am
>>> > doing
>>> > wrong here or what could be the cause?
>>>
>>> My first suspicion would be hardware issues, e.g. a failing disk
>>> drive.
>>>
>>> While there are certain types of programming error which can cause
>>> non-deterministic behaviour (e.g. reading uninitialised memory),
>>> neither r.mapcalc nor lib/raster have had any significant changes
>>> recently.
>>>
>>> --
>>> Glynn Clements <glynn at gclements.plus.com>
>>
>>
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev