Your message dated Sun, 5 Jun 2016 13:03:59 -0300
with message-id
<cap+dxjdjh9cwsauyrxs_d8lkwppp5nkunafdtaudu+3pjpq...@mail.gmail.com>
and subject line Re: axel: Segmentation fault when we execute it with a
connection negative values
has caused the Debian Bug report #703453,
regarding axel: Segmentation fault when we execute it with a connection
negative values
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.)
--
703453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703453
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: axel
Version: 2.4-1
Severity: normal
Tags: squeeze
-- System Information:
Debian Release: 6.0.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-0.bpo.3-amd64 (SMP w/8 CPU cores)
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages axel depends on:
ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib
axel recommends no packages.
axel suggests no packages.
-- no debconf information
I found a bug with axel 2.4 (on Debian 6 stable), it throws an Segmentation
Fault when we execute it with a connection negative values.
If we debug the application with an incorrect launch value, we'll see:
---
GNU gdb (GDB) 7.0.1-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/axel...(no debugging symbols found)...done.
(gdb) run -n -1 google.es
Starting program: /usr/bin/axel -n -1 google.es
[Thread debugging using libthread_db enabled]
Initializing download: google.es
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff78df7df in memset () from /lib/libc.so.6
-------
If we see the backtrace:
---
(gdb) backtrace
#0 0x00007ffff78df7df in memset () from /lib/libc.so.6
#1 0x0000000000402c9a in ?? ()
#2 0x00000000004076fa in ?? ()
#3 0x00007ffff787fc8d in __libc_start_main () from /lib/libc.so.6
#4 0x0000000000401a09 in ?? ()
#5 0x00007fffffffe3e8 in ?? ()
#6 0x000000000000001c in ?? ()
#7 0x0000000000000004 in ?? ()
#8 0x00007fffffffe697 in ?? ()
#9 0x00007fffffffe6a5 in ?? ()
#10 0x00007fffffffe6a8 in ?? ()
#11 0x00007fffffffe6ab in ?? ()
#12 0x0000000000000000 in ?? ()
---
I suspect, it maybe the following line:
memset( axel->conn, 0, sizeof( conn_t ) * axel->conf->num_connections );
Only maybe!
Thanks.
-----
Àngel Ollé Blázquez
--- End Message ---
--- Begin Message ---
Hi,
This bug was fixed in 2.7 upstream version (2.7-1 revision in Debian).
So, I am closing this bug.
Regards,
Eriberto
--- End Message ---
