[rkward-tracker] [ rkward-Bugs-1727030 ] rkward segfaults R

SourceForge.net noreply at sourceforge.net
Tue May 29 09:31:24 UTC 2007

Bugs item #1727030, was opened at 2007-05-28 19:47
Message generated for change (Comment added) made by tfry
You can respond by visiting: 

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Skander Morgenthaler (smorg)
Assigned to: Nobody/Anonymous (nobody)
Summary: rkward segfaults R

Initial Comment:
When I try to edit (display) a (my) data.frame within rkward, R segfaults with the following message:

Assert failed at rkvariable.cpp - function getText line 461
output without receiver'
 *** caught segfault ***
address (nil), cause 'memory not mapped'

Possible actions:
1: abort (with core dump, if enabled)
2: normal R exit
3: exit R without saving workspace
4: exit R saving workspace

Steps to reproduce:
1. start rkward
2. open my workspace*
3. open the "workspace" tab
4. try to edit the "mydata" data.frame (via right-click -> edit) from my workspace*
5. wait (or click somewhere in the data.frame window)
6. R segfaults

* as the data is personal data of other people I would rather not put it some place with public access.

This happens with a gentoo (rkward-0.4.7) build as well as with a fresh manual build of rkward-0.4.7a.

If you could use further information, do not hesitate to tell me so.


>Comment By: Thomas Friedrichsmeier (tfry)
Date: 2007-05-29 11:31

Logged In: YES 
Originator: NO

In the development version of RKWard, I found and fixed some bugs in the
data editor, recently. If possible, could you try, whether you can
reproduce the crash, there

Could you perhaps anonymize the data in some way or another and/or strip
it down to just a few cases (in a way that it still triggers the crash),
and make it available, then? This would help a lot in trying to figure out,
what exactly is going wrong.


You can respond by visiting: 

More information about the rkward-tracker mailing list