> Hmm, in that case errnum must be set to 0. What about the attached
> patch, which prints the existing message if errnum == 0, and the new
> and improved only for errnum > 0?
OK. Thanks for the patch.
FX
On Tue, Sep 1, 2015 at 1:04 AM, FX wrote:
>> the attached patch improves the error handling for backtrace failing,
>> by printing the error number or the error string in addition to the
>> message. It also fixes a potential null pointer crash in gf_strerror.
>>
>> Regtested on x86_64-pc-linux-gnu,
> the attached patch improves the error handling for backtrace failing,
> by printing the error number or the error string in addition to the
> message. It also fixes a potential null pointer crash in gf_strerror.
>
> Regtested on x86_64-pc-linux-gnu, Ok for trunk?
Mostly OK. I have one question,
Hi,
the attached patch improves the error handling for backtrace failing,
by printing the error number or the error string in addition to the
message. It also fixes a potential null pointer crash in gf_strerror.
Regtested on x86_64-pc-linux-gnu, Ok for trunk?
2015-09-01 Janne Blomqvist
P
