r.los crashes

[iomeneandrei]

Hi all,
I'm usign WinGRASS-6.3.0-4, and I have some difficult with visibility (r.los) analysis.

When I run r.los using location of mine, r.los crashes.
I use this command:
r.los input=dem@debug output=visibilita coordinate=303778,4210733 obs_elev=1.75 max_dist=10000

If I set max_dist to a lower value (i.e. 1000) I have no crash.

This is my location:
castdecimale.zip

This is the error I have:


What about this crash? What am I doing wrong?

Thank you,

a

[Markus Neteler]

On Wed, Nov 12, 2008 at 11:23 AM, iomeneandrei <[hidden email]> wrote:
>
> Hi all,
> I'm usign WinGRASS-6.3.0-4, and I have some difficult with visibility
> (r.los) analysis.
>
> When I run r.los using location of mine, r.los crashes.
> I use this command:
> r.los input=dem@debug output=visibilita coordinate=303778,4210733
> obs_elev=1.75 max_dist=10000

I tried this on Linux, no problem.
Can anyone replicate this on Windows (I don't have it)?

Markus

> If I set max_dist to a lower value (i.e. 1000) I have no crash.
>
> This is my location:
> http://www.nabble.com/file/p20457630/castdecimale.zip castdecimale.zip
>
> This is the error I have:
> http://www.nabble.com/file/p20457630/r.los.jpg
>
> What about this crash? What am I doing wrong?
>
> Thank you,
>
> a
>
> -----
> Andrea Borruso
>
> ----------------------------------------------------
> email: [hidden email]
> blog: http://blog.spaziogis.it
> ----------------------------------------------------
> --
> View this message in context: http://www.nabble.com/r.los-crashes-tp20457630p20457630.html
> Sent from the Grass - Win mailing list archive at Nabble.com.
>
> _______________________________________________
> grass-windows mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/grass-windows
>

--
Open Source Geospatial Foundation
http://www.osgeo.org/
http://www.grassbook.org/
_______________________________________________
grass-windows mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-windows

[iomeneandrei]

Hi Markus,
thank you.

Markus Neteler OSGeo wrote:

I tried this on Linux, no problem.

I have made this test too with the same data, and I have no problem in Linux.

I'll wait for some windows user  ;-)

ciao,

a

[Markus Neteler]

On Wed, Nov 12, 2008 at 10:16 PM, iomeneandrei <[hidden email]> wrote:
> I have made this test too with the same data, and I have no problem in
> Linux.
>
> I'll wait for some windows user  ;-)

Another, better option is to generate a "backtrace" with a debugger,
see
 http://grass.osgeo.org/wiki/GRASS_Debugging

Maybe you could try?

Best
Markus
_______________________________________________
grass-windows mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-windows

[iomeneandrei]

Ciao Markus,

Markus Neteler OSGeo wrote:

Another, better option is to generate a "backtrace" with a debugger,
see
 http://grass.osgeo.org/wiki/GRASS_Debugging

I'm not your man ;-)
I have tried to read "GRASS Debugging" webpage, I have installed gdb for windows using ming, but I'm not able to use it to debug the processes of wingrass (as r.los.exe).

Some tips for me?

Thank you,

a

[Moritz Lennert]

On 13/11/08 10:16, iomeneandrei wrote:

> Ciao Markus,
>
> Markus Neteler OSGeo wrote:
>> Another, better option is to generate a "backtrace" with a debugger,
>> see
>>  http://grass.osgeo.org/wiki/GRASS_Debugging
>>
>
> I'm not your man ;-)
> I have tried to read "GRASS Debugging" webpage, I have installed gdb for
> windows using ming, but I'm not able to use it to debug the processes of
> wingrass (as r.los.exe).
>
> Some tips for me?

ISTR that gdb debugging does not work with WinGRASS. Can't remember why,
though.

So, the best bet is to work with a series of fprintf statements in the
code to identify where exactly it crashes.

I've been away from WinGRASS for quite a while, though, so maybe there
are other debugging options now.

Moritz
_______________________________________________
grass-windows mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-windows

[iomeneandrei]

Hi all,
I have made a test also with QGIS 1.0.0 Preview 2 for windows and its GRASS plugin, and I have the same problem. I think it's normal.

That's all,

a

[Marco Pasetti]

Hi all,

> I have made a test also with QGIS 1.0.0 Preview 2 for windows and its
> GRASS
> plugin, and I have the same problem. I think it's normal.

as it should be! ;-) because GRASS binaries bundled in QGIS are the same
distributed within the official WinGRASS release.

by the way, it's a known bug: http://trac.osgeo.org/grass/ticket/111
on latest tests, it seems to be fixed on Vista, but not on XP.

Regards,

Marco

_______________________________________________
grass-windows mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-windows

[iomeneandrei]

Ciao Marco,
thank you for your reply.

Marco Pasetti wrote:

by the way, it's a known bug: http://trac.osgeo.org/grass/ticket/111
on latest tests, it seems to be fixed on Vista, but not on XP.

A stupid question. Do you think that also the xp version will be patched/fixed?

Best regards,

Andrea

[iomeneandrei]

Ciao Marco,

Marco Pasetti wrote:

on latest tests, it seems to be fixed on Vista, but not on XP.

I have tested it in Vista. I have no error with my original command:
r.los input=dem@debug output=visibilita coordinate=303778,4210733 obs_elev=1.75 max_dist=10000

But I have error if I modify it a little (max_dist parameter):
r.los input=dem@debug output=visibilita coordinate=303778,4210733 obs_elev=1.75 max_dist=17000


That's all,

a