Bug 895167

Summary: [abrt] sed-4.2.1-10.fc18: re_node_set_compare: Process /usr/bin/sed was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jan Teichmann <jan.teichmann>
Component: glibcAssignee: Carlos O'Donell <codonell>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: codonell, fweimer, jakub, law, mbriza, pbonzini, pfrankli, schwab, spoyarek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1d424e480e64c56811a01a638433b7ec5fc35b63
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 14:50:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
core dump none

Description Jan Teichmann 2013-01-14 17:56:44 UTC 
Version-Release number of selected component:
sed-4.2.1-10.fc18

Additional info:
backtrace_rating: 4
cmdline:        sed -e s/.*release.*//
core_backtrace: b7b62d4d01e98c8b31d95895cbede393b8b0c6e8 0xc9fc0 re_acquire_state_context.constprop.38 /lib64/libc.so.6 bff762671226b32d9a41b602c82d54e3c1cd36cc
crash_function: re_node_set_compare
executable:     /usr/bin/sed
kernel:         3.7.2-201.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (2 frames)
 #0 re_node_set_compare at regex_internal.c:1521
 #2 re_acquire_state_context at regex_internal.c:1541
Comment 1 Jan Teichmann 2013-01-14 17:56:48 UTC 
Created attachment 678354 [details]
File: backtrace
Comment 2 Jan Teichmann 2013-01-14 17:56:50 UTC 
Created attachment 678355 [details]
File: cgroup
Comment 3 Jan Teichmann 2013-01-14 17:56:52 UTC 
Created attachment 678356 [details]
File: dso_list
Comment 4 Jan Teichmann 2013-01-14 17:56:56 UTC 
Created attachment 678357 [details]
File: environ
Comment 5 Jan Teichmann 2013-01-14 17:56:59 UTC 
Created attachment 678358 [details]
File: limits
Comment 6 Jan Teichmann 2013-01-14 17:57:01 UTC 
Created attachment 678359 [details]
File: maps
Comment 7 Jan Teichmann 2013-01-14 17:57:04 UTC 
Created attachment 678360 [details]
File: open_fds
Comment 8 Jan Teichmann 2013-01-14 17:57:06 UTC 
Created attachment 678361 [details]
File: proc_pid_status
Comment 9 Jan Teichmann 2013-01-14 17:57:08 UTC 
Created attachment 678362 [details]
File: var_log_messages
Comment 10 Martin Bříza 2013-01-22 13:44:31 UTC 
Hi Jan,
could you please provide the input that triggers the crash?
Thank you
Comment 11 Jan Teichmann 2013-01-22 14:06:51 UTC 
it was picked up by abrt. It wasn't me on the command line working with sed so it has been some programme but I don't know which one or what the input was. Abrt doesn't seem to log that(?)
Comment 12 Martin Bříza 2013-01-22 14:19:34 UTC 
There was only the command line by which it was invoked but not the input. Probably, the file was '/home/jan/.cache/gdm/session.log' as it is in open_fds. Could you please run this command:
    sed -e 's/.*release.*//' < /home/jan/.cache/gdm/session.log
and eventually post the file (if there is no sensitive information) here if it is reproducible?
Thank you
Comment 13 Jan Teichmann 2013-01-22 16:09:09 UTC 
session.log doesn't cause any trouble with the sed command.
Comment 14 Jeff Law 2013-01-24 18:56:21 UTC 
Jan,

Did abrt save a core dump?  If you could attach that it'd be helpful.  

Look in /var/spool/abrt/
Comment 15 Jan Teichmann 2013-01-24 19:13:14 UTC 
Created attachment 686919 [details]
core dump
Comment 16 Fedora Admin XMLRPC Client 2013-01-28 20:09:30 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 17 Fedora End Of Life 2013-12-21 10:22:37 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.
Comment 18 Fedora End Of Life 2014-02-05 14:50:10 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.