Bug 886624 - [abrt] bash-4.2.39-3.fc18: discard_pipeline: Process /usr/bin/bash was killed by signal 11 (SIGSEGV)
Summary: [abrt] bash-4.2.39-3.fc18: discard_pipeline: Process /usr/bin/bash was killed...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: bash
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Roman Rakus
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:269861fb84e5d979a85de486dff...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-12 17:13 UTC by Jan Teichmann
Modified: 2014-01-13 00:14 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-10 09:13:46 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (34.00 KB, text/plain)
2012-12-12 17:13 UTC, Jan Teichmann 		no flags Details
File: build_ids (246 bytes, text/plain)
2012-12-12 17:13 UTC, Jan Teichmann 		no flags Details
File: cgroup (156 bytes, text/plain)
2012-12-12 17:13 UTC, Jan Teichmann 		no flags Details
File: environ (235 bytes, text/plain)
2012-12-12 17:13 UTC, Jan Teichmann 		no flags Details
File: limits (1.29 KB, text/plain)
2012-12-12 17:13 UTC, Jan Teichmann 		no flags Details
File: maps (3.07 KB, text/plain)
2012-12-12 17:13 UTC, Jan Teichmann 		no flags Details
File: open_fds (232 bytes, text/plain)
2012-12-12 17:13 UTC, Jan Teichmann 		no flags Details
File: proc_pid_status (877 bytes, text/plain)
2012-12-12 17:13 UTC, Jan Teichmann 		no flags Details
View All

Description Jan Teichmann 2012-12-12 17:13:13 UTC 
Version-Release number of selected component:
bash-4.2.39-3.fc18

Additional info:
backtrace_rating: 4
cmdline:        /bin/sh -c 'if [ -f uid ]; then getent passwd \"`cat uid`\" | cut -d: -f1 >username; fi'
crash_function: discard_pipeline
executable:     /usr/bin/bash
kernel:         3.6.9-4.fc18.x86_64
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #18 discard_pipeline at jobs.c:1085
 #19 delete_job at jobs.c:1027
 #21 cleanup_dead_jobs at jobs.c:843
 #23 wait_for at jobs.c:2611
 #24 execute_command_internal at execute_cmd.c:787
 #26 execute_pipeline at execute_cmd.c:2238
 #27 execute_connection at execute_cmd.c:2350
 #28 execute_command_internal at execute_cmd.c:903
 #30 execute_command at execute_cmd.c:386
 #31 execute_if_command at execute_cmd.c:3265
Comment 1 Jan Teichmann 2012-12-12 17:13:16 UTC 
Created attachment 662505 [details]
File: backtrace
Comment 2 Jan Teichmann 2012-12-12 17:13:19 UTC 
Created attachment 662506 [details]
File: build_ids
Comment 3 Jan Teichmann 2012-12-12 17:13:21 UTC 
Created attachment 662507 [details]
File: cgroup
Comment 4 Jan Teichmann 2012-12-12 17:13:22 UTC 
Created attachment 662508 [details]
File: environ
Comment 5 Jan Teichmann 2012-12-12 17:13:24 UTC 
Created attachment 662509 [details]
File: limits
Comment 6 Jan Teichmann 2012-12-12 17:13:27 UTC 
Created attachment 662510 [details]
File: maps
Comment 7 Jan Teichmann 2012-12-12 17:13:29 UTC 
Created attachment 662511 [details]
File: open_fds
Comment 8 Jan Teichmann 2012-12-12 17:13:31 UTC 
Created attachment 662512 [details]
File: proc_pid_status
Comment 9 Jan Teichmann 2013-01-10 09:13:46 UTC 
I noticed more strange memory corruption in other programs recently and as it turned out I had a defective RAM module. Effects were very random and rare but could be the cause of most memory corruption I lately reported. I assumed it is related to the beta state of F18 so I didnt suspect the RAM at first but MemTest found a small address range with errors.
I am extremely sorry for taking up your time hunting down bugs which are most likely not there. I decided to close my latest bug reports as I can not assure that the memory corruption was actually caused by the program rather than the defect RAM module.
Note You need to log in before you can comment on or make changes to this bug.