[GRASS-user] r.in.lidar segfaulting

[Micha Silver]

On 09/23/2013 05:07 PM, Markus Metz wrote:
> Micha Silver wrote:
>> Markus Metz wrote:
>>
>>
>> Both r.in.lidar and v.in.lidar say that none of the 7651 points in
>> that file is valid. I am using libLAS 1.7.0 with GeoTIFF 1.4.0 GDAL
>> 1.10.0 LASzip 2.1.0. I remember that [r|v].in.lidar require a recent
>> version of libLAS and other users experienced problems with older
>> versions of libLAS. Which version are you using?
>>
>>
>> GRASS 7.0.svn (ITM):~ > lasinfo -h
>> --------------------------------------------------------------------
>>      lasinfo (libLAS 1.7.0 with GeoTIFF 1.3.0 GDAL 1.9.0 LASzip 2.2.0)
>> --------------------------------------------------------------------
>>
> Looks good to me. Now it seems it's time to use gdb.

Here's what I get:

GRASS 7.0.svn (ITM):~ > gdb --args r.in.lidar 
in=/media/cdrom0/pt000005.las out=rast_05 meth=mean
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/local/grass-7.0.svn/bin/r.in.lidar...done.
(gdb) r
Starting program: /usr/local/grass-7.0.svn/bin/r.in.lidar 
in=/media/cdrom0/pt000005.las out=rast_05 meth=mean
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) generate-core-file
Saved corefile core.1905
(gdb) quit
A debugging session is active.

     Inferior 1 [process 1905] will be killed.

Quit anyway? (y or n) y
GRASS 7.0.svn (ITM):~ >

The core dump is here:
http://surfaces.co.il/dl/core.1905.gz

Thanks,
Micha