Skip to content

RGtk2 segfaulting on macOS

2 messages · Tom Elliott, Brian Ripley

Original
Tom Elliott
# 
Hi,


The macOS binaries were recently built for macOS, however they're still not quite right. Runing the following ...


library(RGtk2)

gtkHScaleNewWithRange(0, 5, 1)


... leads to a segfault ...


 *** caught segfault ***
address 0x0, cause 'memory not mapped'

Traceback:
 1: .RGtkCall("S_gtk_hscale_new_with_range", min, max, step, PACKAGE = "RGtk2")
 2: gtkHScaleNewWithRange(0, 5, 1)


It's preventing some other packages (notably gWidgets2RGtk2) from building on CRAN, since it's tests are running into the same segfault when running tests (gslider calls gtkHScaleNewWithRange):
https://cran.r-project.org/web/checks/check_results_gWidgets2RGtk2.html



Thanks,


Tom.

?
Brian Ripley
#
On 22/07/2019 03:47, Tom Elliott wrote:
It is likely that the segfault is in the Gtk2 libraries: which OS 
version and which Gtk2 installation?

I have not managed to get Gtk2 to work cleanly on macOS for a long time: 
the Gtk2 libs at https://mac.r-project.org/libs/ are > 6.5 years old. 
Some of the packages pass their tests some of the time: currently 
MixSIAR, Ricetl, fit4NM, gWidgets2RGtk2 and plfMA segfault on my High 
Sierra box.