Bug 568564 - [abrt] crash in tftp-0.49-5.fc12: Process /usr/bin/tftp was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in tftp-0.49-5.fc12: Process /usr/bin/tftp was killed by signal ...
Keywords:
Status: CLOSED DUPLICATE of bug 578643
Alias: None
Product: Fedora
Classification: Fedora
Component: tftp
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jiri Skala
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d5a53fd9f92c59ea15482deb4a7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-26 01:35 UTC by Nick Mathew
Modified: 2014-11-09 22:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-16 06:13:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (4.74 KB, text/plain)
2010-02-26 01:35 UTC, Nick Mathew
no flags Details

Description Nick Mathew 2010-02-26 01:35:23 UTC
abrt 1.0.7 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: tftp 192.168.1.1
component: tftp
executable: /usr/bin/tftp
kernel: 2.6.31.12-174.2.22.fc12.x86_64
package: tftp-0.49-5.fc12
rating: 4
reason: Process /usr/bin/tftp was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 Nick Mathew 2010-02-26 01:35:25 UTC
Created attachment 396444 [details]
File: backtrace

Comment 2 Jiri Skala 2010-03-02 07:04:15 UTC
Hi, could you add more information - mainly how to reproduce it? Eventually logs from /var/log/messages.

Thakns, Jiri

Comment 3 Jiri Skala 2010-03-04 13:03:14 UTC
I've discussed this message with abrt team. SIGABRT is no more wathced so it seems to be false positive. I'm going to close it.
Don't hesitate to reopen it if the problem persist.

Comment 4 Till Maas 2010-03-31 22:09:02 UTC

How to reproduce
-----
1. mkdir /tmp/work; cd /tmp/work
2. touch aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa{1..14}.bin {1..14}.bin
3. (echo binary; echo rexmt 1; echo timeout 60; echo trace; echo put $(ls *.bin)) | tftp 192.168.1.1


Comment
-----
This creates an instantaneous crash, no further action is needed.

Comment 5 Jiri Skala 2010-04-16 06:13:38 UTC

*** This bug has been marked as a duplicate of bug 578643 ***


Note You need to log in before you can comment on or make changes to this bug.