Red Hat Bugzilla – Bug 1007031
echoping segfaults all the time
Last modified: 2015-04-21 15:19:39 EDT
Created attachment 796472 [details]
gdb backtrace attempt
Description of problem:
echoping doesn't work at all:
dmesg is full of:
[461892.847804] echoping: segfault at 650008 ip 0000000000402160 sp 00007fff96658860 error 6 in echoping[400000+6000]
Hard to tell what's going on - it seem to die very soon.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run echoping
Created attachment 796473 [details]
Created attachment 796474 [details]
Something very wrong with this binary, this the disassembly of the *entire* main function.
(gdb) disass main
Dump of assembler code for function main:
0x00000000004020a0 <+0>: sub $0x8,%rsp
0x00000000004020a4 <+4>: movq $0xf423f,0x2044f9(%rip) # 0x6065a8 <max_timeval+8>
0x00000000004020af <+15>: mov 0x2044f2(%rip),%rdi # 0x6065a8 <max_timeval+8>
0x00000000004020b6 <+22>: movq $0x0,0x20424f(%rip) # 0x606310 <null_timeval>
0x00000000004020c1 <+33>: movq $0x0,0x20424c(%rip) # 0x606318 <null_timeval+8>
0x00000000004020cc <+44>: mov 0x20423d(%rip),%rax # 0x606310 <null_timeval>
0x00000000004020d3 <+51>: mov 0x20423e(%rip),%rdx # 0x606318 <null_timeval+8>
0x00000000004020da <+58>: movq $0x3b9aca00,0x2044bb(%rip) # 0x6065a0 <max_timeval>
0x00000000004020e5 <+69>: mov 0x2044b4(%rip),%rsi # 0x6065a0 <max_timeval>
0x00000000004020ec <+76>: mov %rdi,0x204495(%rip) # 0x606588 <min+8>
0x00000000004020f3 <+83>: mov $0x20,%edi
0x00000000004020f8 <+88>: movl $0x0,0x2040a2(%rip) # 0x6061a4 <return_code>
0x0000000000402102 <+98>: movl $0x1,0x204064(%rip) # 0x606170 <number>
0x000000000040210c <+108>: mov %rax,0x2044ad(%rip) # 0x6065c0 <total>
0x0000000000402113 <+115>: mov %rdx,0x2044ae(%rip) # 0x6065c8 <total+8>
0x000000000040211a <+122>: mov %rax,0x2044af(%rip) # 0x6065d0 <median>
0x0000000000402121 <+129>: mov %rdx,0x2044b0(%rip) # 0x6065d8 <median+8>
0x0000000000402128 <+136>: mov %rax,0x204171(%rip) # 0x6062a0 <max>
0x000000000040212f <+143>: mov %rdx,0x204172(%rip) # 0x6062a8 <max+8>
0x0000000000402136 <+150>: mov %rsi,0x204443(%rip) # 0x606580 <min>
0x000000000040213d <+157>: mov %rax,0x20444c(%rip) # 0x606590 <stddev>
0x0000000000402144 <+164>: mov %rdx,0x20444d(%rip) # 0x606598 <stddev+8>
0x000000000040214b <+171>: callq 0x401fd0 <malloc@plt>
0x0000000000402150 <+176>: movl $0x6f686365,(%rax)
0x0000000000402156 <+182>: movb $0x0,0x4(%rax)
0x000000000040215a <+186>: mov $0x6063a0,%eax
0x000000000040215f <+191>: nop
0x0000000000402160 <+192>: movl $0x0,(%rax)
0x0000000000402166 <+198>: add $0x18,%rax
0x000000000040216a <+202>: jmp 0x402160 <main+192>
End of assembler dump.
That can't be right? Problem with the build?
Sure enough just doing a `fedpkg mockbuild` of the identical commit produces a package that looks OK.
$ yum localinstall /home/brad/working/src/fedpkg/echoping/results_echoping/6.0.2/10.fc19/echoping-6.0.2-10.fc19.x86_64.rpm
No host name indicated
Usage: echoping [-vV?dcRuSCaA46D] [-v|--verbose] [-V|--dump-configuration] [-?|--help] [-s|--size INT] [-n|--number INT] [-w|--wait FLOAT] [-d|--discard] [-c|--chargen]
[-h|--http STRING] [-R|--accept-http-redirects] [-H|--hostname STRING] [-i|--icp STRING] [-u|--udp] [-t|--timeout INT] [-f|--fill STRING] [-S|--smtp] [-C|--ssl]
[-p|--priority INT] [-P|--type-of-service INT] [-a|--check-original] [-A|--ignore-cache] [-4|--ipv4] [-6|--ipv6] [-m|--module STRING] [-D|--data-only]
Looks like it just needs to be rebuilt.
I've uploaded an rpm tha tshould work (with no guarantees whatsoever) to http://people.redhat.com/bhubbard/echoping-6.0.2-10.fc19.x86_64.rpm it should get you through until this package can be officially rebuilt.
Andreas, could you submit rebuild of echoping?
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
echoping-6.1-0.beta.r434svn.1.fc22 has been submitted as an update for Fedora 22.
echoping-6.1-0.beta.r434svn.1.fc21 has been submitted as an update for Fedora 21.
echoping-6.1-0.beta.r434svn.1.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing echoping-6.1-0.beta.r434svn.1.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
echoping-6.1-0.1.beta.r434svn.fc22 has been submitted as an update for Fedora 22.
echoping-6.1-0.beta.r434svn.1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
echoping-6.1-0.beta.r434svn.1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
echoping-6.1-0.1.beta.r434svn.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.