[ ijbswa-Bugs-3507301 ] null pointer in log message

Bugs item #3507301, was opened at 2012-03-17 16:13
Message generated for change (Comment added) made by fabiankeil
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=111118&aid=3507301&group_id=11118

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: version 3.0.19
>Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Matthew Fischer (futhark)
Assigned to: Fabian Keil (fabiankeil)
Summary: null pointer in log message

Initial Comment:
an error message in get_last_url() uses new_url when it is NULL

----------------------------------------------------------------------

>Comment By: Fabian Keil (fabiankeil)
Date: 2012-03-19 05:05

Message:
Thanks for the confirmation.

----------------------------------------------------------------------

Comment By: Matthew Fischer (futhark)
Date: 2012-03-18 15:09

Message:
Yes, I noticed it from looking at the code, not from actually running into
it.

----------------------------------------------------------------------

Comment By: Fabian Keil (fabiankeil)
Date: 2012-03-18 06:53

Message:
Thanks for the report. Fixed in CVS.

I take it you discovered the issue through code review/analysis and not by
reaching the message while running Privoxy?

While log_error() should deal with NULL pointers gracefully, the error
message in question isn't supposed to be reached in practice. If it is, it
would indicate another bug.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=111118&aid=3507301&group_id=11118

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure