[Bug 701059] New: wget / libproxy1 segfault.
https://bugzilla.novell.com/show_bug.cgi?id=701059 https://bugzilla.novell.com/show_bug.cgi?id=701059#c0 Summary: wget / libproxy1 segfault. Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 (gdb) run http://pypi.python.org/packages/source/p/psycopg2/psycopg2-2.4.2.tar.gz The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /usr/bin/wget http://pypi.python.org/packages/source/p/psycopg2/psycopg2-2.4.2.tar.gz [Thread debugging using libthread_db enabled] asking libproxy about url 'http://pypi.python.org/packages/source/p/psycopg2/psycopg2-2.4.2.tar.gz' [New Thread 0x7fffe8a46700 (LWP 629)] Program received signal SIGSEGV, Segmentation fault. 0x00007ffff30bd145 in WTF::OSAllocator::reserveAndCommit (bytes=<value optimized out>, usage=<value optimized out>, writable=<value optimized out>, executable=<value optimized out>) at Source/JavaScriptCore/wtf/OSAllocatorPosix.cpp:85 85 Source/JavaScriptCore/wtf/OSAllocatorPosix.cpp: No such file or directory. in Source/JavaScriptCore/wtf/OSAllocatorPosix.cpp (gdb) (gdb) It's possible that the fix is in the new libproxy (0.4.7). Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c
zj jia
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c1
Dominique Leuenberger
From the current presented information, it appears you are using either wpad or a proxy auto configuration URL for your proxy settings.
Also, the used javascript parser seems to be the webkit one in your case. There are several thins I would like to test with you to make sure we're on the right path finding a solution: First, please install the libproxy-tools package (if you don't have it already). It contains a 'test' application, called proxy, which queries libproxy based on your configuration, hoping to get the same behavior (it's a very simple test case app). Then, please execute: _PX_DEBUG=1 proxy http://www.google.com => Does that crash also? Maybe try: _PX_DEBUG=1 _MM_DEBUG=1 proxy http://pypi.python.org/packages/source/p/psycopg2/psycopg2-2.4.2.tar.gz (let's query the same address you used) I assume this crashes the same way? It might be worthy to test if only the webkit pacrunner is affected; the mozjs might work just fine: remove libproxy1-pacrunner-webkit and install libproxy1-pacrunner-mozjs Perform the same tests again. Please, if possible, also attach your .pac/wpad.dat -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c2
Jon Nelson
Jon,
thank you very much for your bug report. From the current presented information, it appears you are using either wpad or a proxy auto configuration URL for your proxy settings.
Also, the used javascript parser seems to be the webkit one in your case.
There are several thins I would like to test with you to make sure we're on the right path finding a solution:
First, please install the libproxy-tools package (if you don't have it already). It contains a 'test' application, called proxy, which queries libproxy based on your configuration, hoping to get the same behavior (it's a very simple test case app).
Then, please execute: _PX_DEBUG=1 proxy http://www.google.com
=> Does that crash also?
It did not crash when I tried it last night. It does crash today. [jnelson~] _PX_DEBUG=1 proxy http://www.google.com Using config: 20kde_config_extension Using ignore: Config is: pac+http://192.168.1.2/~jnelson/proxy.pac PAC received! Using pacrunner: 26webkit_pacrunner_extension Segmentation fault (core dumped) [jnelson~]
Maybe try: _PX_DEBUG=1 _MM_DEBUG=1 proxy http://pypi.python.org/packages/source/p/psycopg2/psycopg2-2.4.2.tar.gz (let's query the same address you used)
I assume this crashes the same way?
Yes.
It might be worthy to test if only the webkit pacrunner is affected; the mozjs might work just fine: remove libproxy1-pacrunner-webkit and install libproxy1-pacrunner-mozjs
[jnelson~] _PX_DEBUG=1 proxy http://www.google.com Using config: 20kde_config_extension Using ignore: Config is: pac+http://192.168.1.2/~jnelson/proxy.pac PAC received! Unable to find a required pacrunner! direct:// [jnelson~] rpm -q libproxy1-pacrunner-mozjs libproxy1-pacrunner-mozjs-0.4.6-3.9.1.x86_64 [jnelson~]
Perform the same tests again.
Please, if possible, also attach your .pac/wpad.dat
[jnelson~] curl -o - http://192.168.1.2/~jnelson/proxy.pac function FindProxyForURL(url, host) { if (isPlainHostName(host) || dnsDomainIs(host, '.wplc.info') || dnsDomainIs(host, '.contentserve.com') || dnsDomainIs(host, '.local') || dnsDomainIs(host, '.site') || isInNet(host, "192.168.0.0", "255.255.0.0") ) { return 'DIRECT'; } else { return 'PROXY 192.168.1.2:3128'; } } [jnelson~] -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c3
--- Comment #3 from Dominique Leuenberger
=> Does that crash also?
It did not crash when I tried it last night. It does crash today.
Any idea what changed in between? (Was the .pac file available for example?)
[jnelson~] _PX_DEBUG=1 proxy http://www.google.com Using config: 20kde_config_extension Using ignore: Config is: pac+http://192.168.1.2/~jnelson/proxy.pac PAC received! Using pacrunner: 26webkit_pacrunner_extension Segmentation fault (core dumped) [jnelson~]
Ok... that is not nice. But at least it's consistently crashing. Which gices us something to work on.
[jnelson~] _PX_DEBUG=1 proxy http://www.google.com Using config: 20kde_config_extension Using ignore: Config is: pac+http://192.168.1.2/~jnelson/proxy.pac PAC received! Unable to find a required pacrunner! direct:// [jnelson~] rpm -q libproxy1-pacrunner-mozjs libproxy1-pacrunner-mozjs-0.4.6-3.9.1.x86_64 [jnelson~]
Hmm.. mozjs pacrunner seems not to work at all... that's really bad. Which is a different issue all-together (possibly easier to fix though). Very likely, the output of "ldd /usr/lib64/libproxy-0.4.7/modules/pacrunner_mozjs.so" will show "libmozjs.so => Not found" Something that can probably easily be 'worked around' with a symlink.
[jnelson~] curl -o - http://192.168.1.2/~jnelson/proxy.pac function FindProxyForURL(url, host) { if (isPlainHostName(host) || dnsDomainIs(host, '.wplc.info') || dnsDomainIs(host, '.contentserve.com') || dnsDomainIs(host, '.local') || dnsDomainIs(host, '.site') || isInNet(host, "192.168.0.0", "255.255.0.0") ) { return 'DIRECT'; } else { return 'PROXY 192.168.1.2:3128'; } }
Thanks.. the pac does look simple enough and should not cause too much trouble. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c4
--- Comment #4 from Dominique Leuenberger
It's possible that the fix is in the new libproxy (0.4.7).
Would you be willing to test this if I provide some 0.4.7 packages? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c5
--- Comment #5 from Jon Nelson
(In reply to comment #2)
=> Does that crash also?
It did not crash when I tried it last night. It does crash today.
Any idea what changed in between? (Was the .pac file available for example?)
I believe that simply time and use are sufficient. The .pac file did not change. Last night I tested after logging out and back in again for other reasons. .
Hmm.. mozjs pacrunner seems not to work at all... that's really bad.
Which is a different issue all-together (possibly easier to fix though). Very likely, the output of "ldd /usr/lib64/libproxy-0.4.7/modules/pacrunner_mozjs.so" will show "libmozjs.so => Not found"
Correct! Why can't it find it?
Something that can probably easily be 'worked around' with a symlink.
I added the appropriate directory to /etc/ld.so.conf and re-ran ldconfig (as a temporary measure) and re-ran the test app: Using config: 20kde_config_extension Using ignore: Config is: pac+http://192.168.1.2/~jnelson/proxy.pac PAC received! Using pacrunner: 25mozjs_pacrunner_extension Segmentation fault (core dumped) ..
Thanks.. the pac does look simple enough and should not cause too much trouble.
regarding:
Would you be willing to test this if I provide some 0.4.7 packages?
Yes. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c6
--- Comment #6 from Dominique Leuenberger
Correct! Why can't it find it?
Probably an issue from a xulrunner 2.0 update. Xul is in a versioned folder and the update might have moved it to a new folder. pacrunner_mozjs has an rapth pointing to the folder used during the build
Using config: 20kde_config_extension Using ignore: Config is: pac+http://192.168.1.2/~jnelson/proxy.pac PAC received! Using pacrunner: 25mozjs_pacrunner_extension Segmentation fault (core dumped)
Now THAT is unexpected. It should be a completely different code path. on this pacrunner. Can you please do: gdb proxy run http://www.google.com (wait for the segfault) bt full
Would you be willing to test this if I provide some 0.4.7 packages?
Yes.
Packages are building. Once completed I will enable publishing tomorrow. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c7
--- Comment #7 from Jon Nelson
(In reply to comment #5)
Correct! Why can't it find it?
Probably an issue from a xulrunner 2.0 update. Xul is in a versioned folder and the update might have moved it to a new folder. pacrunner_mozjs has an rapth pointing to the folder used during the build
Using config: 20kde_config_extension Using ignore: Config is: pac+http://192.168.1.2/~jnelson/proxy.pac PAC received! Using pacrunner: 25mozjs_pacrunner_extension Segmentation fault (core dumped)
Now THAT is unexpected. It should be a completely different code path. on this pacrunner.
It's not unexpected if the problem is /before/ the pacrunner stuff is used.
Can you please do: gdb proxy run http://www.google.com (wait for the segfault) bt full
#0 0x00007ffff395453d in getReservedSlot (this=<value optimized out>) at
/usr/src/debug/mozilla/js/src/jsobjinlines.h:248
#1 extractFrom (this=<value optimized out>) at
/usr/src/debug/mozilla/js/src/jsregexpinlines.h:594
#2 JSContext::regExpStatics (this=<value optimized out>) at
/usr/src/debug/mozilla/js/src/jscntxtinlines.h:115
#3 0x00007ffff399d063 in str_search (cx=0x6bd500, argc=1, vp=0x7ffff27cd120)
at /usr/src/debug/mozilla/js/src/jsstr.cpp:1910
#4 0x00007ffff38ec019 in CallJSNative (cx=<value optimized out>,
entryFrame=0x7ffff27cd058, inlineCallCount=1, interpMode=JSINTERP_NORMAL)
at /usr/src/debug/mozilla/js/src/jscntxtinlines.h:701
#5 js::Interpret (cx=<value optimized out>, entryFrame=0x7ffff27cd058,
inlineCallCount=1, interpMode=JSINTERP_NORMAL)
at /usr/src/debug/mozilla/js/src/jsinterp.cpp:4799
#6 0x00007ffff38f8965 in js::RunScript (cx=0x6bd500, script=0x72c230,
fp=0x7ffff27cd058) at /usr/src/debug/mozilla/js/src/jsinterp.cpp:653
#7 0x00007ffff38fa832 in js::Invoke (cx=0x6bd500, argsRef=<value optimized
out>, flags=<value optimized out>)
at /usr/src/debug/mozilla/js/src/jsinterp.cpp:740
#8 0x00007ffff38fad1b in js::ExternalInvoke (cx=0x6bd500, thisv=..., fval=...,
argc=2, argv=0x7ffffffe45a0, rval=0x7ffffffe45b8)
at /usr/src/debug/mozilla/js/src/jsinterp.cpp:863
#9 0x00007ffff3869904 in JS_CallFunctionName (cx=0x6bd500, obj=0x7ffff2603048,
name=<value optimized out>, argc=2, argv=0x7ffffffe45a0, rval=0x7ffffffe45b8)
at /usr/src/debug/mozilla/js/src/jsapi.cpp:5159
#10 0x00007ffff3da5438 in mozjs_pacrunner::run (this=0x62c3f0, url_=<value
optimized out>)
at /usr/src/debug/libproxy-0.4.6/libproxy/modules/pacrunner_mozjs.cpp:165
#11 0x00007ffff7bc986e in libproxy::proxy_factory::_get_proxies (this=0x603010,
realurl=0x60b770, response=...)
at /usr/src/debug/libproxy-0.4.6/libproxy/proxy.cpp:372
#12 0x00007ffff7bcad6e in libproxy::proxy_factory::get_proxies (this=0x603010,
url_=...) at /usr/src/debug/libproxy-0.4.6/libproxy/proxy.cpp:194
#13 0x00007ffff7bcaf0c in px_proxy_factory_get_proxies (self=0x603010,
url=<value optimized out>) at
/usr/src/debug/libproxy-0.4.6/libproxy/proxy.cpp:420
#14 0x0000000000400d2c in main ()
(gdb)
(gdb) frame 11
#11 0x00007ffff7bc986e in libproxy::proxy_factory::_get_proxies (this=0x603010,
realurl=0x60b770, response=...)
at /usr/src/debug/libproxy-0.4.6/libproxy/proxy.cpp:372
372 /usr/src/debug/libproxy-0.4.6/libproxy/proxy.cpp: No such file or
directory.
in /usr/src/debug/libproxy-0.4.6/libproxy/proxy.cpp
(gdb) print realurl
$1 = (libproxy::url *) 0x60b770
(gdb) print *realurl
$2 = {m_orig = {static npos = 18446744073709551615, _M_dataplus =
{
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c8
--- Comment #8 from Jon Nelson
Packages are building. Once completed I will enable publishing tomorrow.
have packages built properly? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c9
Dominique Leuenberger
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c10
Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c11
--- Comment #11 from Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c12
Dominique Leuenberger
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c13
Christian Dengler
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c14
--- Comment #14 from Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c15
--- Comment #15 from Dominique Leuenberger
I should note that the packages provided (4.7) have debugging enabled, so one always gets:
asking libproxy about url .... libproxy suggest to use ... and so on.
This output ia by wget, not by libproxy. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c16
--- Comment #16 from Marcus Meissner
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c17
--- Comment #17 from Dominique Leuenberger
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c18
--- Comment #18 from Marcus Meissner
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c19
--- Comment #19 from Dominique Leuenberger
please also tell upstream that they mistyped google.com in one of the testcases (they used googe.com) Thanks.. that typo has been fixed in upstream svn.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c20
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c21
Christian Dengler
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c22
--- Comment #22 from Christian Dengler
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c23
Benjamin Brunner
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c24
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=701059
https://bugzilla.novell.com/show_bug.cgi?id=701059#c
Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com