[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: segfault in errx



* 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
> Speicherzugriffsfehler

What's the glibc version and architecture?

I can reproduce something like this with 2.24-3 on amd64.  valgrind
isn't very helpful.

ul: unknown escape sequence in input: 33, 135
==16450== Conditional jump or move depends on uninitialised value(s)
==16450==    at 0x52A9A63: utf8_internal_loop (loop.c:298)
==16450==    by 0x52A9A63: __gconv_transform_utf8_internal (skeleton.c:609)
==16450==    by 0x52F26CD: do_length (iofwide.c:463)
==16450== 
==16450== Jump to the invalid address stated on the next line
==16450==    at 0x0: ???
==16450==    by 0x4224167: ???
==16450==    by 0x4024537: ???
==16450==    by 0x5833A3F: ???
==16450==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==16450== 
==16450== 
==16450== Process terminating with default action of signal 11 (SIGSEGV)
==16450==  Bad permissions for mapped region at address 0x0
==16450==    at 0x0: ???
==16450==    by 0x4224167: ???
==16450==    by 0x4024537: ???
==16450==    by 0x5833A3F: ???
==16450== Jump to the invalid address stated on the next line
==16450==    at 0x0: ???
==16450==    by 0x42239D7: ??? (in /lib/x86_64-linux-gnu/ld-2.24.so)
==16450==    by 0x4025477: ???
==16450==    by 0x5833A3F: ???
==16450==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==16450== 
==16450== 
==16450== Process terminating with default action of signal 11 (SIGSEGV)
==16450==  Bad permissions for mapped region at address 0x0
==16450==    at 0x0: ???
==16450==    by 0x42239D7: ??? (in /lib/x86_64-linux-gnu/ld-2.24.so)
==16450==    by 0x4025477: ???
==16450==    by 0x5833A3F: ???

I'll have to try this on a distribution with better debugging
information.


Reply to: