abrt 1.0.3 detected a crash. How to reproduce ----- 1. tcpprep -a server -i tsol-bad.cap -o test Comment: tcpprep always crashes instead of printing any useful info. I admit I may provide wrong command line arguments or input pcap file, but it should show what's wrong and not to crash. Attached file: backtrace cmdline: tcpprep -a server -i /home/jsafrane/download/tsol-bad.cap -o /home/jsafrane/download/t.pcap component: tcpreplay executable: /usr/bin/tcpprep kernel: 2.6.31.9-174.fc12.x86_64 package: tcpreplay-3.4.3-2.fc12 rating: 4 reason: Process was terminated by signal 6 (Aborted)
Created attachment 385410 [details] File: backtrace
Created attachment 385411 [details] the magic pcap file which makes tcpprep crash
i have another problem with the same program [root@fedora ~]# tcpprep -i http.pcap -o tmp1.prep -p *** buffer overflow detected ***: tcpprep terminated ======= Backtrace: ========= /lib/libc.so.6(__fortify_fail+0x4d)[0x3821ed] /lib/libc.so.6(+0xf230a)[0x38030a] /lib/libc.so.6(__strncpy_chk+0x176)[0x37f8f6] tcpprep[0x804e757] tcpprep[0x804b400] /lib/libc.so.6(__libc_start_main+0xe6)[0x2a4bb6] tcpprep[0x8049d21] ======= Memory map: ======== 0028e000-003fd000 r-xp 00000000 fd:00 11008 /lib/libc-2.11.1.so 003fd000-003ff000 r--p 0016e000 fd:00 11008 /lib/libc-2.11.1.so 003ff000-00400000 rw-p 00170000 fd:00 11008 /lib/libc-2.11.1.so 00400000-00403000 rw-p 00000000 00:00 0 00585000-005b9000 r-xp 00000000 fd:00 9346 /usr/lib/libpcap.so.1.0.0 005b9000-005ba000 rw-p 00034000 fd:00 9346 /usr/lib/libpcap.so.1.0.0 005ba000-005bb000 rw-p 00000000 00:00 0 007f4000-007f5000 r-xp 00000000 00:00 0 [vdso] 00974000-0097b000 r-xp 00000000 fd:00 12795 /lib/librt-2.11.1.so 0097b000-0097c000 r--p 00006000 fd:00 12795 /lib/librt-2.11.1.so 0097c000-0097d000 rw-p 00007000 fd:00 12795 /lib/librt-2.11.1.so 009cd000-009eb000 r-xp 00000000 fd:00 9681 /lib/ld-2.11.1.so 009eb000-009ec000 r--p 0001d000 fd:00 9681 /lib/ld-2.11.1.so 009ec000-009ed000 rw-p 0001e000 fd:00 9681 /lib/ld-2.11.1.so 00a3a000-00a51000 r-xp 00000000 fd:00 11164 /lib/libnsl-2.11.1.so 00a51000-00a52000 r--p 00016000 fd:00 11164 /lib/libnsl-2.11.1.so 00a52000-00a53000 rw-p 00017000 fd:00 11164 /lib/libnsl-2.11.1.so 00a53000-00a55000 rw-p 00000000 00:00 0 00aae000-00ac4000 r-xp 00000000 fd:00 12598 /lib/libpthread-2.11.1.so 00ac4000-00ac5000 r--p 00015000 fd:00 12598 /lib/libpthread-2.11.1.so 00ac5000-00ac6000 rw-p 00016000 fd:00 12598 /lib/libpthread-2.11.1.so 00ac6000-00ac8000 rw-p 00000000 00:00 0 00dde000-00dfb000 r-xp 00000000 fd:00 15011 /lib/libgcc_s-4.4.2-20091222.so.1 00dfb000-00dfc000 rw-p 0001c000 fd:00 15011 /lib/libgcc_s-4.4.2-20091222.so.1 08048000-08068000 r-xp 00000000 fd:00 39553 /usr/bin/tcpprep 08068000-0806a000 rw-p 00020000 fd:00 39553 /usr/bin/tcpprep 0806a000-0808a000 rw-p 00000000 00:00 0 0855e000-0857f000 rw-p 00000000 00:00 0 [heap] b7878000-b787a000 rw-p 00000000 00:00 0 b788a000-b788b000 rw-p 00000000 00:00 0 bfd6a000-bfd7f000 rw-p 00000000 00:00 0 [stack] Aborted (core dumped)
This bug has been reported upstream.
(In reply to comment #3) > i have another problem with the same program > [root@fedora ~]# tcpprep -i http.pcap -o tmp1.prep -p Can I ask you to do: sudo debuginfo-install tcpreplay Then run the above and post the backtrace. Thanks.
(In reply to comment #5) > Can I ask you to do: > > sudo debuginfo-install tcpreplay > > Then run the above and post the backtrace. Disregard please. It crashes on my i686 machine as well. Have the full backtrace already.
tcpreplay-3.4.3-3.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/tcpreplay-3.4.3-3.fc12
tcpreplay-3.4.3-3.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update tcpreplay'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/tcpreplay-3.4.3-3.fc12
tcpreplay-3.4.3-3.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.