Your message dated Fri, 08 Nov 2013 11:11:09 +0100
with message-id <[email protected]>
and subject line Bug#728697: wget: segfault with SSL and --read-timeout
has caused the Debian Bug report #728697,
regarding wget: segfault with SSL and --read-timeout
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
728697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728697
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wget
Version: 1.13.4-3
Severity: normal
File: /usr/bin/wget

Dear Maintainer,

After upgrading from squeeze to wheezy, the following invokation of wget
segfaults:

  wget --read-timeout=0.0 -O - https://www.google.de

This is the corresponding terminal output:

  --2013-11-04 09:10:04--  https://www.google.de/
  Resolving www.google.de (www.google.de)... 173.194.69.94,
  2a00:1450:4008:c01::5e
  Connecting to www.google.de
  (www.google.de)|173.194.69.94|:443... connected.
  HTTP request sent, awaiting response... Segmentation fault

GDB is incapable of supplying a corresponding backtrace:

  [..]
  Program received signal SIGSEGV, Segmentation fault.
  0x00424e98 in ?? ()
  (gdb) bt
  #0  0x00424e98 in ?? ()
  warning: GDB can't find the start of the function at 0x424e98.

This is the disassambly around the error location:

  (gdb) disas $pc-16,$pc+16
  Dump of assembler code from 0x424e88 to 0x424ea8:
     0x00424e88:  sw      ra,36(sp)
     0x00424e8c:  jal     0x403330 <clock_gettime@plt>
     0x00424e90:  addiu   a1,sp,24
     0x00424e94:  lw      v0,28(sp)
  => 0x00424e98:  lw      v1,4(s0)
     0x00424e9c:  lw      a0,0(s0)
     0x00424ea0:  subu    v1,v0,v1
     0x00424ea4:  mtc1    v1,$f0
  End of assembler dump.

Register dump:

 (gdb) info regist
           zero       at       v0       v1       a0       a1       a2
           a3
  R0   00000000 cfffffff 1740e769 00488098 00000001 7fff2620 00000000
  00000000 
             t0       t1       t2       t3       t4       t5       t6
             t7
  R8   00000004 00000002 00000000 00424e94 00000000 80000008 80277ea0
  00470000 
             s0       s1       s2       s3       s4       s5       s6
             s7
  R16  00000000 00000000 00488098 00000000 00000008 ffffffcc 00000000
  00000080 
             t8       t9       k0       k1       gp       sp       s8
             ra
  R24  00000000 2acf8620 00487e88 00000000 2ad14040 7fff2608 00000000
  00424e94 
         status       lo       hi badvaddr    cause       pc
       000044f3 0953fd71 00000001 00000004 10008008 00424e98 
           fcsr      fir  restart
       00800004 00000501 00000000 

Looks like a 0-pointer dereference.  Accordingo to /proc/<pid>/maps, the
location of the faulting instruction is part of wget's code segment
(i.e. it's not a shared library that causes the crash):

   00400000-00458000 r-xp 00000000 fe:02 131578 /usr/bin/wget


-- System Information:
Debian Release: 7.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: mipsel (mips64)

Kernel: Linux 2.6.38-bpo.2-loongson-2f
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages wget depends on:
ii  dpkg           1.16.12
ii  install-info   4.13a.dfsg.1-10
ii  libc6          2.13-38
ii  libgcrypt11    1.5.0-5+deb7u1
ii  libgnutls26    2.12.20-7
ii  libgpg-error0  1.10-3.1
ii  libidn11       1.25-2
ii  zlib1g         1:1.2.7.dfsg-13

wget recommends no packages.

wget suggests no packages.

-- no debconf information

-- 
GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk2.gpg
Fingerprint: B63B 6AF2 4EEB F033 46F7  7F1D 935E 6F08 E457 205F

Attachment: pgpqDyEC4BGFQ.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
Hello,

the problem is reproducible in 1.13.4-3 in wheezy on different archs and
it is fixed in 1.14-4 in testing/jessie and sid.
I don't think it is possible to get the new upstream release 1.14 into
wheezy.:( So it will be fixed for the stable users with the next stable
release (afaik 2014).

Regards.

-- 
Noël Köthe <noel debian.org>
Debian GNU/Linux, www.debian.org

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply via email to