lnstat

2 messages, 2 authors, 2018-03-04 · open the first message on its own page

lnstat

From: David Kaufmann <hidden>
Date: 2018-03-03 22:04:03

Hi!

`lnstat` segfaults (tested on Debian 9, CentOS 6+7, Fedora 27) if it is
started as `lnstat -w 1`

according to gdb the crash is in `build_hdr_string` at lnstat.c:212

as it seems to be an useless value for the option anyway it might make
sense to just handle a single "1" the same as if "0" was specified.
`-w 0,1`, `-w 1,0`, `-w 1,1` and other variations do work.

All the best,
Astra

PS: I did not find any other place to report this, if this is the wrong
place please tell we where to post.

Re: lnstat

From: Stephen Hemminger <stephen@networkplumber.org>
Date: 2018-03-04 16:58:48

On Sat, 3 Mar 2018 22:56:02 +0100
David Kaufmann [off-list ref] wrote:
Hi!

`lnstat` segfaults (tested on Debian 9, CentOS 6+7, Fedora 27) if it is
started as `lnstat -w 1`

according to gdb the crash is in `build_hdr_string` at lnstat.c:212

as it seems to be an useless value for the option anyway it might make
sense to just handle a single "1" the same as if "0" was specified.
`-w 0,1`, `-w 1,0`, `-w 1,1` and other variations do work.
Right having one character width is breaking the header building code.
Probably should just catch it in the option parsing.
All the best,
Astra

PS: I did not find any other place to report this, if this is the wrong
place please tell we where to post.
This the right place.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help