Bug 552378 - [abrt] crash detected in openssh-clients-5.2p1-31.fc12
[abrt] crash detected in openssh-clients-5.2p1-31.fc12
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: openssh (Show other bugs)
12
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Jan F. Chadima
Fedora Extras Quality Assurance
abrt_hash:02af9fae9a296009ea22269c4f9...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-01-04 15:48 EST by Tom Diehl
Modified: 2010-01-04 17:21 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-01-04 17:21:51 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
File: backtrace (560 bytes, text/plain)
2010-01-04 15:48 EST, Tom Diehl
no flags Details

  None (edit)
Description Tom Diehl 2010-01-04 15:48:10 EST
abrt 1.0.0 detected a crash.

How to reproduce
-----
1. Not sure, just using ssh to talk to another system.
2.
3.

backtrace
-----
Core was generated by `ssh -l root 71.182.142.14'.
Program terminated with signal 3, Quit.
#0  0x00007fdaae96fb70 in __connect_nocancel ()
    at ../sysdeps/unix/syscall-template.S:82
	in ../sysdeps/unix/syscall-template.S
Current language:  auto
The current source language is "auto; currently asm".

Thread 1 (Thread 9828):
#0  0x00007fdaae96fb70 in __connect_nocancel ()
    at ../sysdeps/unix/syscall-template.S:82
No locals.
#1  0x00007fdab0cc599e in ?? ()
No symbol table info available.
#2  0x00007fdab0cbbef2 in main ()
No symbol table info available.

cmdline: ssh -l root 71.182.142.14
component: openssh
executable: /usr/bin/ssh
kernel: 2.6.31.5-127.fc12.x86_64
package: openssh-clients-5.2p1-31.fc12
rating: 3
reason: Process was terminated by signal 3
Comment 1 Tom Diehl 2010-01-04 15:48:12 EST
Created attachment 381642 [details]
File: backtrace
Comment 2 Tomas Mraz 2010-01-04 17:21:51 EST
This is not a crash. You've probably pressed a Ctrl-\ generating a SIGQUIT.

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