## Andriy Gapon (a...@freebsd.org):
> It did not make sense to me that libcrypto would have such a bug and then I
> noticed that libcrypto.so.7 was involved.
Now that you mention libcrypto... There was a similar (the same?) issue
about a year ago in VirtualBox, which ended up being linked against
On 19/01/2016 15:16, Andriy Gapon wrote:
> So, it's "QT_IM_MODULE=xim" with 4 bytes (corresponding to "DULE") replaced
> with
> zeroes. This is 100% reproducible in my current environment, so it could be a
> deterministic write to a wrong offset.
Okay, I've debugged and fixed the problem, but I
On 05/01/2016 21:36, Ryan Stone wrote:
> On Tue, Jan 5, 2016 at 3:54 AM, Andriy Gapon wrote:
>
>> Is there a limit on the environment's size?
>>
>
> If memory serves, this is bounded by ARG_MAX in sys/syslimits.h. The value
> is not tunable as far as I know, so if you want to experiment with ch
On 05/01/2016 10:54, Andriy Gapon wrote:
> On 05/01/2016 10:45, Andriy Gapon wrote:
>>
>> Very weird, this suddenly started happening to me but with libreoffice. I
>> can
>> not correlate the problem with any actions / events.
>>
>> stderr:
>> soffic
On Tue, Jan 5, 2016 at 3:54 AM, Andriy Gapon wrote:
> Is there a limit on the environment's size?
>
If memory serves, this is bounded by ARG_MAX in sys/syslimits.h. The value
is not tunable as far as I know, so if you want to experiment with changing
it you will have to change syslimits.h and r
On 05/01/2016 10:45, Andriy Gapon wrote:
>
> Very weird, this suddenly started happening to me but with libreoffice. I can
> not correlate the problem with any actions / events.
>
> stderr:
> soffice.bin: environment corrupt; missing value for QT_IM_MO
>
> gdb:
Very weird, this suddenly started happening to me but with libreoffice. I can
not correlate the problem with any actions / events.
stderr:
soffice.bin: environment corrupt; missing value for QT_IM_MO
gdb:
Core was generated by `soffice.bin'.
Program terminated with signal SIGABRT, Aborte
