Bug 892405 - [abrt] wxMaxima-12.09.0-1.fc18: GroupCell::BreakUpCells: Process /usr/bin/wxmaxima was killed by signal 11 (SIGSEGV)
Summary: [abrt] wxMaxima-12.09.0-1.fc18: GroupCell::BreakUpCells: Process /usr/bin/wxm...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: wxMaxima
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:221a5b4d9753b85ad8c90049da2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-07 02:24 UTC by Jan Teichmann
Modified: 2013-01-10 15:42 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
File: backtrace (64.81 KB, text/plain)
2013-01-07 02:24 UTC, Jan Teichmann 		no flags Details
File: cgroup (126 bytes, text/plain)
2013-01-07 02:24 UTC, Jan Teichmann 		no flags Details
File: core_backtrace (3.19 KB, text/plain)
2013-01-07 02:24 UTC, Jan Teichmann 		no flags Details
File: dso_list (11.46 KB, text/plain)
2013-01-07 02:24 UTC, Jan Teichmann 		no flags Details
File: environ (1.40 KB, text/plain)
2013-01-07 02:24 UTC, Jan Teichmann 		no flags Details
File: limits (1.29 KB, text/plain)
2013-01-07 02:24 UTC, Jan Teichmann 		no flags Details
File: maps (53.79 KB, text/plain)
2013-01-07 02:24 UTC, Jan Teichmann 		no flags Details
File: open_fds (659 bytes, text/plain)
2013-01-07 02:24 UTC, Jan Teichmann 		no flags Details
File: proc_pid_status (921 bytes, text/plain)
2013-01-07 02:24 UTC, Jan Teichmann 		no flags Details
File: var_log_messages (312 bytes, text/plain)
2013-01-07 02:24 UTC, Jan Teichmann 		no flags Details
View All

Description Jan Teichmann 2013-01-07 02:24:15 UTC 
Version-Release number of selected component:
wxMaxima-12.09.0-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        wxmaxima /home/jan/Documents/CITY/models/TDLeaningCpp/Documentation/Q_Appeareance/probabilities.wxm
crash_function: GroupCell::BreakUpCells
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 GroupCell::BreakUpCells at GroupCell.cpp:1051
 #1 GroupCell::RecalculateAppended at GroupCell.cpp:402
 #2 MathCtrl::InsertLine at MathCtrl.cpp:381
 #3 wxMaxima::DoRawConsoleAppend at wxMaxima.cpp:437
 #4 wxMaxima::ConsoleAppend at wxMaxima.cpp:333
 #5 wxMaxima::ReadMath at wxMaxima.cpp:852
 #6 wxMaxima::ClientEvent at wxMaxima.cpp:560
 #7 ProcessEventIfMatches at src/common/event.cpp:1239
 #8 wxEvtHandler::ProcessEventIfMatches at src/common/event.cpp:1214
 #9 wxEventHashTable::HandleEvent at src/common/event.cpp:906
Comment 1 Jan Teichmann 2013-01-07 02:24:18 UTC 
Created attachment 673654 [details]
File: backtrace
Comment 2 Jan Teichmann 2013-01-07 02:24:20 UTC 
Created attachment 673655 [details]
File: cgroup
Comment 3 Jan Teichmann 2013-01-07 02:24:22 UTC 
Created attachment 673656 [details]
File: core_backtrace
Comment 4 Jan Teichmann 2013-01-07 02:24:25 UTC 
Created attachment 673657 [details]
File: dso_list
Comment 5 Jan Teichmann 2013-01-07 02:24:27 UTC 
Created attachment 673658 [details]
File: environ
Comment 6 Jan Teichmann 2013-01-07 02:24:29 UTC 
Created attachment 673659 [details]
File: limits
Comment 7 Jan Teichmann 2013-01-07 02:24:31 UTC 
Created attachment 673660 [details]
File: maps
Comment 8 Jan Teichmann 2013-01-07 02:24:33 UTC 
Created attachment 673661 [details]
File: open_fds
Comment 9 Jan Teichmann 2013-01-07 02:24:35 UTC 
Created attachment 673662 [details]
File: proc_pid_status
Comment 10 Jan Teichmann 2013-01-07 02:24:37 UTC 
Created attachment 673663 [details]
File: var_log_messages
Comment 11 Jan Teichmann 2013-01-10 08:54:13 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.
Comment 12 Rex Dieter 2013-01-10 15:42:08 UTC 
Glad you figured it out, and thanks for the followup.

A moment of silence for the brave fallen memory stick... :)
Note You need to log in before you can comment on or make changes to this bug.