libproxy segfaults when fed a pac file with syntax errors

[GoogleCodeExporter]

Steps to reproduce:
- Configure proxy settings to use a pac file
- Add a syntax error in the pac file (like missing ; or anything)
- use proxy test binary to verify the settings.

Result: proxy segfaults.

Expected: the error in the script is 'skipped' and direct:// returned in
any case due to fallback mechanism.

i'll try to reproduce it and get a backtrace.

Original issue reported on code.google.com by dominiqu...@gmail.com on 21 Aug 2009 at 10:19

[GoogleCodeExporter]

Original comment by dominiqu...@gmail.com on 21 Aug 2009 at 10:20

• Added labels: Milestone-Release0.3.x

[GoogleCodeExporter]

I actually can not reproduce it with libproxy 0.3.0, neither with webkit not 
mozjs
script engine.

Original comment by dominiqu...@gmail.com on 18 Sep 2009 at 8:47

• Changed state: Invalid

[GoogleCodeExporter]

Finally found a case where I can reproduce it.
Wrote a test, submitted to svn. 

It's the webkit pacrunner crashing on this test. mozjs seems to pass it.

Original comment by dominiqu...@gmail.com on 24 Sep 2009 at 4:17

• Changed state: Accepted

[GoogleCodeExporter]

I ran the test againts 0.4.2 and found that is hangs instead of crash.

Original comment by nicolas.dufresne@gmail.com on 2 Jun 2010 at 7:45

[GoogleCodeExporter]

Works on latest SVN now, do we still want this in the 0.3.X ?

Original comment by nicolas.dufresne@gmail.com on 4 Jun 2010 at 4:19

[GoogleCodeExporter]

This bug won't be fixed in 0.3.X, we recommend upgrading to 0.4.3 when time 
comes.

Original comment by nicolas.dufresne@gmail.com on 4 Jun 2010 at 7:12

• Changed state: WontFix