[Liblas-devel] lasinfo, las2las, las2txt with no argument bombs

[Peder Axensten]

Howard,

I had Boost 1.45.0, but now that I checked it I found that older Boost files were still around, presumably files from an earlier version.
In any case, I removed everything Boost and installed version 1.46.0.
It now works well.

Sorry for bothering you with my self-inflicted problems.
Thank you for making me aware of a latent problem!

/Peder


Regards,
Peder

On 24 feb 2011, at 16.26, Howard Butler wrote:

> 
> On Feb 20, 2011, at 4:10 PM, Peder Axensten wrote:
> 
>> I've just installed liblas 1.6 with tools. When I use libinfo with no arguments (I wanted to get the version info) it got a memory issue:
>> 
>> $ lasinfo
>> Input LAS file not specified!
>> --------------------------------------------------------------------
>>  lasinfo (libLAS 1.6.0 with GeoTIFF 1.3.0 GDAL 1.8.0 LASzip 1.0.1)
>> --------------------------------------------------------------------
>> 
>> lasinfo options:
>> lasinfo(21384) malloc: *** error for object 0x7fff70717500: pointer being freed was not allocated
>> *** set a breakpoint in malloc_error_break to debug
>> -h [ --help ]         produce help messageAbort trap
>> 
>> This does not happen if I give it a file. Same thing with las2las, las2txt, but not with the -old variants.
>> 
>> Is this a known issue?
> 
> Peder,
> 
> Which version of Boost are you using?  If I recall correctly, there was a bug in older versions of program_options, which is what libLAS is using in lasinfo to output help information and parse commandline arguments.  
> 
> Howard
> 
> PS, Please join the list at your slu.se address, as you are not able to post by default with this email and I manually allowed this message to come through.