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
Created attachment 678354 [details] File: backtrace
Created attachment 678355 [details] File: cgroup
Created attachment 678356 [details] File: dso_list
Created attachment 678357 [details] File: environ
Created attachment 678358 [details] File: limits
Created attachment 678359 [details] File: maps
Created attachment 678360 [details] File: open_fds
Created attachment 678361 [details] File: proc_pid_status
Created attachment 678362 [details] File: var_log_messages
Hi Jan, could you please provide the input that triggers the crash? Thank you
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(?)
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
session.log doesn't cause any trouble with the sed command.
Jan, Did abrt save a core dump? If you could attach that it'd be helpful. Look in /var/spool/abrt/
Created attachment 686919 [details] core dump
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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.
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.