Bug 890877 - [abrt] wxMaxima-12.09.0-1.fc18: GroupCell::SelectRectInOutput: Process /usr/bin/wxmaxima was killed by signal 11 (SIGSEGV)
Summary: [abrt] wxMaxima-12.09.0-1.fc18: GroupCell::SelectRectInOutput: Process /usr/b...
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:a76f1b5fde70cc9f351044f2608...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-30 22:42 UTC by Jan Teichmann
Modified: 2013-01-10 09:05 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
File: backtrace (29.54 KB, text/plain)
2012-12-30 22:42 UTC, Jan Teichmann 		no flags Details
File: cgroup (126 bytes, text/plain)
2012-12-30 22:42 UTC, Jan Teichmann 		no flags Details
File: dso_list (11.44 KB, text/plain)
2012-12-30 22:42 UTC, Jan Teichmann 		no flags Details
File: environ (1.40 KB, text/plain)
2012-12-30 22:42 UTC, Jan Teichmann 		no flags Details
File: limits (1.29 KB, text/plain)
2012-12-30 22:42 UTC, Jan Teichmann 		no flags Details
File: maps (54.01 KB, text/plain)
2012-12-30 22:42 UTC, Jan Teichmann 		no flags Details
File: open_fds (620 bytes, text/plain)
2012-12-30 22:42 UTC, Jan Teichmann 		no flags Details
File: proc_pid_status (919 bytes, text/plain)
2012-12-30 22:42 UTC, Jan Teichmann 		no flags Details
File: var_log_messages (307 bytes, text/plain)
2012-12-30 22:42 UTC, Jan Teichmann 		no flags Details
View All

Description Jan Teichmann 2012-12-30 22:42:27 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/optimal_t_predator.wxm
core_backtrace: 
crash_function: GroupCell::SelectRectInOutput
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::SelectRectInOutput at GroupCell.cpp:924
 #1 MathCtrl::OnMouseLeftDown at MathCtrl.cpp:850
 #2 ProcessEventIfMatches at src/common/event.cpp:1239
 #3 wxEvtHandler::ProcessEventIfMatches at src/common/event.cpp:1214
 #4 wxEventHashTable::HandleEvent at src/common/event.cpp:906
 #5 ProcessEvent at src/common/event.cpp:1301
 #6 wxEvtHandler::ProcessEvent at src/common/event.cpp:1272
 #7 ProcessEvent at src/common/event.cpp:1308
 #8 wxEvtHandler::ProcessEvent at src/common/event.cpp:1272
 #9 wxScrollHelperEvtHandler::ProcessEvent at src/generic/scrlwing.cpp:208
Comment 1 Jan Teichmann 2012-12-30 22:42:31 UTC 
Created attachment 670551 [details]
File: backtrace
Comment 2 Jan Teichmann 2012-12-30 22:42:33 UTC 
Created attachment 670552 [details]
File: cgroup
Comment 3 Jan Teichmann 2012-12-30 22:42:35 UTC 
Created attachment 670553 [details]
File: dso_list
Comment 4 Jan Teichmann 2012-12-30 22:42:37 UTC 
Created attachment 670554 [details]
File: environ
Comment 5 Jan Teichmann 2012-12-30 22:42:39 UTC 
Created attachment 670555 [details]
File: limits
Comment 6 Jan Teichmann 2012-12-30 22:42:41 UTC 
Created attachment 670556 [details]
File: maps
Comment 7 Jan Teichmann 2012-12-30 22:42:43 UTC 
Created attachment 670557 [details]
File: open_fds
Comment 8 Jan Teichmann 2012-12-30 22:42:45 UTC 
Created attachment 670558 [details]
File: proc_pid_status
Comment 9 Jan Teichmann 2012-12-30 22:42:47 UTC 
Created attachment 670559 [details]
File: var_log_messages
Comment 10 Jan Teichmann 2013-01-10 09:05:59 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.