Re: segfault in errx

2016-09-28 Thread Florian Weimer
* Florian Weimer: >> I can reproduce something like this with 2.24-3 on amd64. valgrind >> isn't very helpful. > > And it needs a UTF-8 locale (C.UTF-8 will do). Another multi-byte > locale may work as well. Bisecting this with the attached script leads to: commit

Re: segfault in errx

2016-09-28 Thread Michael Meskes
On Wed, Sep 28, 2016 at 02:36:49PM +0200, Florian Weimer wrote: > What's the glibc version and architecture? Oops, sorry, up-to-date unstable on amd64. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Meskes at (Debian|Postgresql) dot Org Jabber:

Re: segfault in errx

2016-09-28 Thread Florian Weimer
* Florian Weimer: > * Michael Meskes: > >> I recently learned that ul (from bsdmainutils) segfaults when run >> against the attached file. Some debugging shows that the segfault >> happens when cleaning up in errx(): >> >> michael@feivel:~$ ul ul.segf >> ul: unknown escape sequence in input: 33,

Re: segfault in errx

2016-09-28 Thread Florian Weimer
* Michael Meskes: > I recently learned that ul (from bsdmainutils) segfaults when run > against the attached file. Some debugging shows that the segfault > happens when cleaning up in errx(): > > michael@feivel:~$ ul ul.segf > ul: unknown escape sequence in input: 33, 135 >

segfault in errx

2016-09-28 Thread Michael Meskes
Hi, I recently learned that ul (from bsdmainutils) segfaults when run against the attached file. Some debugging shows that the segfault happens when cleaning up in errx(): michael@feivel:~$ ul ul.segf ul: unknown escape sequence in input: 33, 135 Speicherzugriffsfehler "Speicherzugriffsfehler"