On Dec 6, 2007, at 9:26 AM, Aaron Robotham wrote:
I know of gdb but I'm not certain how to use it with Mac OS X's
R.app, do you just do something like "gdb open R.app" in the
terminal?.
You can attach it once it's running - just type "attach R" in gdb
while R is runningm then "c", then let it crash and then "bt".
FWIW: I cannot reproduce the problem and I have tried 3 different
machines... (you didn't even tell us what machine type this is ...).
Cheers,
Simon
Interestingly I don't get this crash when I launch the X11 version of
R through the terminal, so this would suggest the bug in question is
to do with the actual Rgui in R.app. Hopefully this information might
help to narrow down the problem. Any advice for using gdb on R.app
would be appreciated, I couldn't find much in the way of guidance when
searching online.
thanks
Aaron
On 05/12/2007, Peter Dalgaard <p.dalgaard at biostat.ku.dk> wrote:
a.robotham at bris.ac.uk wrote:
Hello,
I've recently discovered a persistent issue with rpanel when running
R.app (2.6.1) on Mac OS X 10.4.11. tcltk and rpanel load without any
apparent error, and the interactive panels appear to work as
expected,
however upon closing the panels rpanel has created I get
catastrophic
errors and R crashes completely. For the most part R manages to
crash
with dignity and work can be saved, but sometimes it will crash
straight out. Below is an example of an entire work session (only
base
packages loaded) with the crash at the end typical of those
encountered:
Loading Tcl/Tk interface ... done
Package `rpanel', version 1.0-4
type help(rpanel) for summary information
density.draw <- function(panel) {
+ plot(density(panel$x, bw = panel$h))
+ panel
+ }
panel <- rp.control(x = rnorm(50))
rp.slider(panel, h, 0.5, 5, log = TRUE, action = density.draw)
*** caught bus error ***
address 0x0, cause 'non-existent physical address'
Possible actions:
1: abort (with core dump, if enabled)
2: normal R exit
3: exit R without saving workspace
4: exit R saving workspace
All packages that are required are up to date, and I can find no
evidence of similar issues from searching the mailing lists. Any
suggestions would be appreciated.
Can you run this under gdb? A breakpoint in the error handler and a
backtrace could be valuable.