I don't know if this is worth filing a bug report for, so I'll check here first.
r.report seg faults if the page width parameter is set to values 27 and less; a page width of 28 seems to invoke an infinite loop.
I can't think of any use for having page widths that narrow, but shouldn't the module trap out of bounds values? I can file this on trac if anyone thinks it's worth the trouble.
I don't know if this is worth filing
a bug report for, so I'll check here first.
r.report seg faults
sure that's bug worthy, a segfault is a segfault. they shouldn't happen
under normal circumstances.
if the page width parameter is set to values 27 and less; a page
width of 28 seems to invoke an infinite loop.
seems to be map dependent. for spearfish fields the min seems to be
pw=7,8.
I can't think of any use for having page widths that
narrow, but shouldn't the module trap out of bounds values?
I can file this on trac if anyone thinks it's worth the
trouble.
I don't know if this is worth filing a bug report for, so I'll check here first.
r.report seg faults if the page width parameter is set to values 27
and less; a page width of 28 seems to invoke an infinite loop.
Sounds like a word-wrapping algorithm which fails if a "word" is wider
than the page.
I can't think of any use for having page widths that narrow, but
shouldn't the module trap out of bounds values? I can file this on
trac if anyone thinks it's worth the trouble.
I can't think of any use for having page widths that narrow, but
shouldn't the module trap out of bounds values? I can file this on
trac if anyone thinks it's worth the trouble.