Re: [log4j] NUL in log event message

Good stuff! (Shameless plug) Every java main() method deserves http://picocli.info > On Feb 10, 2018, at 2:47, Gary Gregory wrote: > > I fixed this in the one spot where we initialize Jansi and replace NULs > with SPACEs when we log the exception's message. That's the

Re: [log4j] NUL in log event message

I fixed this in the one spot where we initialize Jansi and replace NULs with SPACEs when we log the exception's message. That's the simplest thing to do and leaves room for someone to investigate why JAnsi returns such a string since at least you can see it. Gary On Thu, Feb 8, 2018 at 5:40 PM,

Re: [log4j] NUL in log event message

Could that be UTF-16 or something similar? On 8 February 2018 at 16:52, Remko Popma wrote: > How about stripping nulls out of any error messages coming from Jansi? > > (Shameless plug) Every java main() method deserves http://picocli.info > > > On Feb 9, 2018, at 5:03,

Re: [log4j] NUL in log event message

It might be a bug in JAnsi's WindowsSupport.getLastErrorMessage() Gary On Thu, Feb 8, 2018 at 12:42 PM, Ralph Goers wrote: > Maybe this is a silly question, but in what world is it rational to have > NULL chars in the middle of a String? > > Ralph > > > On Feb 8,