Hi Dirk,

On Tue, Dec 05, 2006 at 06:36:53AM -0600, Dirk Eddelbuettel wrote:
> 
> Hi  Michael,
>  
> On 5 December 2006 at 11:34, Michael Hanke wrote:
<snip>
> | As long as the output window is in the foreground and not outside the
> | visible screen everything is ok. But as soon as the window is (partly)
> | covered by other windows and any action is done to it (move the window,
> | put in foreground, ...) I get this:
> 
> Isn't that a window manager issue?
Well, it sound like window manager, but this is the *only* window that
produces such behavior.

> |     >>> Error during wrapup: C stack usage is too close to the limit
> | 
> |      *** caught segfault ***
> |     address (nil), cause 'memory not mapped'
> | 
> |     Possible actions:
> |     1: abort (with core dump)
> |     2: normal R exit
> |     3: exit R without saving workspace
> |     4: exit R saving workspace
> |     Selection:
> | 
> | And python dies :(
> 
> Not for me. Currnetly the R window is 'behind' Emacs and the (KDE) konsole
> (xterm emulator) and I can happily replot:
Replotting works for me as well, but python dies if the plot window
comes back to foreground again (no need to replot anything). Actually I
do not know what process is dying, but the python interpreter is heavily
affected.

> All on testing too.  Not a bug in R as far I can tell (and the other way to
> tell is to open a file device (png(), pdf(), .... in R, not sure what the RPy
> way is) and plot there.
Strange.

This is obviously not an R bug. I can do all this with plain R and
everything is fine. I tested i386 sarge, i386 and amd64 etch.

But doing it from python with rpy segfaults on both testing machines,
but *not* on sarge.

> You may need to tweak your window manager, though....
Well, I have no clue what I should tweak. I'm using the package defaults
on all machines and they work well for all other windows. 

BTW: I tried to run it remotely from the sarge machine (connected to amd64 
etch via ssh) therefore using a different xserver and the *same* window manager 
that proved to work when running rpy locally. The bug is still present, but the
error message is slightly different:

         *** caught segfault ***
        address 0x16e8790, cause 'invalid permissions'

Creating PDFs with R via RPy works well, with no problems at all.

I don't think that this is a window manager issue, but OTOH I have no
idea what else it could be.


Best,

Michael

-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to