Summary: | net-dialup/wvdial-1.60 segfaulting when initiating connection | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lubos Kolouch <kolcon> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | net-dialup, r.c.g, sghebuz, y3dips |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Lubos Kolouch
2008-01-18 21:11:11 UTC
Please follow http://www.gentoo.org/doc/en/bugzilla-howto.xml and post here the backtrace. (gdb) run Starting program: /usr/bin/wvdial --conf /home/kolcon/wvdial.conf GPRS --> WvDial: Internet dialer version 1.60 --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 OK --> Sending: AT+CGDCONT=1,"IP","internet","",0,0 AT+CGDCONT=1,"IP","internet","",0,0 OK --> Modem initialized. Program received signal SIGSEGV, Segmentation fault. 0xb7c2110f in makecontext () from /lib/libc.so.6 (gdb) (gdb) bt #0 0xb7c2110f in makecontext () from /lib/libc.so.6 #1 0xb7d644f3 in WvTaskMan::do_task () from /usr/lib/libwvbase.so.4.4 #2 0x00000001 in ?? () #3 0x0806dc10 in ?? () #4 0xb7d33768 in ?? () from /usr/lib/libwvbase.so.4.4 #5 0xb7da5ff4 in ?? () from /usr/lib/libwvbase.so.4.4 #6 0x00000080 in ?? () #7 0x0806dd94 in ?? () #8 0x0806dc10 in ?? () #9 0xb7ff36a0 in ?? () from /lib/ld-linux.so.2 #10 0xb7d6472e in WvTaskMan::_stackmaster () from /usr/lib/libwvbase.so.4.4 #11 0xb7d647fa in WvTaskMan::stackmaster () from /usr/lib/libwvbase.so.4.4 #12 0xb7d64140 in ?? () from /usr/lib/libwvbase.so.4.4 #13 0x0806dc10 in ?? () #14 0x00000000 in ?? () (gdb) Build wvstreams with debug USE flag and with FEATURES=nostrip and post the backtrace. (gdb) bt #0 0xb7b2d10f in makecontext () from /lib/libc.so.6 #1 0xb7c704df in WvTaskMan::do_task () at utils/wvtask.cc:513 #2 0xb7c70708 in WvTaskMan::_stackmaster () at utils/wvtask.cc:429 #3 0xb7c707ca in WvTaskMan::stackmaster () at utils/wvtask.cc:386 #4 0xb7c70120 in ?? () from /usr/lib/libwvbase.so.4.4 #5 0x0806dc10 in ?? () #6 0x00000000 in ?? () Should I try something like emerge -e system, emerge -u world etc.? No. I tried to bump wvstreams version to 4.4.1 but the included gnulib is utterly broken and I didn't had time to fix it. Thank you for your great efforts. I will wait, though it is currently stopping me completely from using gentoo :(( This is not a bug in wvdial or wvstreams, but a bug in gentoo's glibc package. On archlinux the same bug was reported by one of our users, and after looking at valgrind outputs, we found out that glibc was reading invalid memory in the make/getcontext functions. The cause of this problem is 0060_all_glibc-2.7-i386- makecontext-align-BZ5435.patch. It should be removed, or fixed using an additional patch from upstream CVS. On archlinux we apply the additional patch, which can be found here: http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/base/glibc/fix-makecontext.patch?rev=1.1&content-type=text/vnd.viewcvs-markup toolchain guys, please, review comment #8. (In reply to comment #8) > This is not a bug in wvdial or wvstreams, but a bug in gentoo's glibc package. > > On archlinux the same bug was reported by one of our users, and after looking > at valgrind outputs, we found out that glibc was reading invalid memory in the > make/getcontext functions. > > The cause of this problem is 0060_all_glibc-2.7-i386- > makecontext-align-BZ5435.patch. It should be removed, or fixed using an > additional patch from upstream CVS. On archlinux we apply the additional patch, > which can be found here: > http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/base/glibc/fix-makecontext.patch?rev=1.1&content-type=text/vnd.viewcvs-markup > patch not found ? anyway, ive already tried another patch but not working et all, somebody with working help ? correct link: http://repos.archlinux.org/viewvc.cgi/glibc/trunk/fix-makecontext.patch?revision=1 but doesn't solve for me (glibc 2.7 on x86) Manually applying the changes from the patch to sysdeps/unix/sysv/linux/i386/makecontext.S solved the problem at least here. glibc-2.7-r2 on x86 Reassigned to toolchain team. is it already in glibc patchset, right now ? Updated to sys-libs/glibc-2.8_p20080602 today. Problem doesn't occur anymore with this glibc version. Fixed in the newer versions of glibc, thanks for reporting. |