Hi,
using i.smap, I get a segfault:
i.smap group=22_1684 subgroup=22_1684 output=22_1684_classificate
signaturefile=sig_22_1684
Processing rows 1-128 (of 215)...
Processing rows 129-215 (of 215)...
Writing raster map <22_1684_classificate>...
D3/3: class: [0] row/col: [0][0]
Segmentation fault
b
Markus Neteler wrote:
> using i.smap, I get a segfault:
> #0 0x0040295d in write_img (img=0x75e950, ncols=210,
> nrows=215, S=0x7fff87ab2a60, parms=0x7fff87ab2ba0,
> files=0x7fff87ab2a80) at write_img.c:23
> class = 0
> row = 0
> col = 0
> I don't see the problem i
On Tue, Jun 29, 2010 at 4:38 PM, Glynn Clements
wrote:
>
> Markus Neteler wrote:
>
>> using i.smap, I get a segfault:
>
>> #0 0x0040295d in write_img (img=0x75e950, ncols=210,
>> nrows=215, S=0x7fff87ab2a60, parms=0x7fff87ab2ba0,
>> files=0x7fff87ab2a80) at write_img.c:23
>> class
Markus Neteler wrote:
> The "only" thing to do seems to catch such error of "emtpy"
> signature file without crashing.
Given that write_img() will always be called, I suggest making
read_signatures() generate an error if the ClassSig field is NULL
after I_ReadSigSet() returns.
AFAICT, the same
On Wed, Jun 30, 2010 at 5:26 AM, Glynn Clements
wrote:
>
> Markus Neteler wrote:
>
>> The "only" thing to do seems to catch such error of "emtpy"
>> signature file without crashing.
>
> Given that write_img() will always be called, I suggest making
> read_signatures() generate an error if the Clas
