Bug 891121

Summary: [abrt] wxMaxima-12.09.0-1.fc18: Process /usr/bin/wxmaxima was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jan Teichmann <jan.teichmann>
Component: wxMaximaAssignee: Rex Dieter <rdieter>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: jamatos, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d0e56d19c89fb210b4041926e0389a8e73e671e7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-10 09:05:22 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: core_backtrace
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

Description Jan Teichmann 2013-01-01 21:50:39 UTC 
Version-Release number of selected component:
wxMaxima-12.09.0-1.fc18

Additional info:
backtrace_rating: 3
cmdline:        wxmaxima /home/jan/Documents/CITY/models/TDLeaningCpp/Documentation/Q_Appeareance/probabilities.wxm
executable:     /usr/bin/wxmaxima
kernel:         3.6.10-4.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ??
 #1 MathCtrl::InsertLine at MathCtrl.cpp:369
 #2 wxMaxima::DoRawConsoleAppend at wxMaxima.cpp:437
 #3 wxMaxima::ConsoleAppend at wxMaxima.cpp:333
 #4 wxMaxima::ReadMath at wxMaxima.cpp:852
 #5 wxMaxima::ClientEvent at wxMaxima.cpp:560
 #6 ProcessEventIfMatches at src/common/event.cpp:1239
 #7 wxEvtHandler::ProcessEventIfMatches at src/common/event.cpp:1214
 #8 wxEventHashTable::HandleEvent at src/common/event.cpp:906
 #9 ProcessEvent at src/common/event.cpp:1301
Comment 1 Jan Teichmann 2013-01-01 21:50:43 UTC 
Created attachment 671138 [details]
File: backtrace
Comment 2 Jan Teichmann 2013-01-01 21:50:45 UTC 
Created attachment 671139 [details]
File: cgroup
Comment 3 Jan Teichmann 2013-01-01 21:50:47 UTC 
Created attachment 671140 [details]
File: core_backtrace
Comment 4 Jan Teichmann 2013-01-01 21:50:49 UTC 
Created attachment 671141 [details]
File: dso_list
Comment 5 Jan Teichmann 2013-01-01 21:50:51 UTC 
Created attachment 671142 [details]
File: environ
Comment 6 Jan Teichmann 2013-01-01 21:50:53 UTC 
Created attachment 671143 [details]
File: limits
Comment 7 Jan Teichmann 2013-01-01 21:50:55 UTC 
Created attachment 671144 [details]
File: maps
Comment 8 Jan Teichmann 2013-01-01 21:50:57 UTC 
Created attachment 671145 [details]
File: open_fds
Comment 9 Jan Teichmann 2013-01-01 21:50:59 UTC 
Created attachment 671146 [details]
File: proc_pid_status
Comment 10 Jan Teichmann 2013-01-01 21:51:01 UTC 
Created attachment 671147 [details]
File: var_log_messages
Comment 11 Jan Teichmann 2013-01-10 09:05:22 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.