search for: r_processx11ev

Dear R Devel, I know that someone put this line in src/modules/X11/devX11.c:2824 for a reason, because commenting it out causes R to miss an important ConfigureNotify event in my window manager. The result is that plots are initially drawn off the window borders, unreadable. R_ProcessX11Events((void*) NULL); Unfortunately for me, this line is commented in the standard release of R, it has "#if BUG ... #endif" around it. I guess it is also unfortunate for anyone who uses the same window manager as I do, namely i3, which I think is pretty popular among Unix power users thes...

...s, we proceed to create a device descriptor structure and add it to the list of open devices. >>> This approach means that X11DeviceDriver() cannot do anything that potentially accesses the dd structure because it isn't there yet, and the things it cannot do apparently includes calling R_ProcessX11Events(). [To be completely sure that this is actually still true, I'd need to have a closer look at what handleEvent() does.] >>> So to fix things, it would seem that you could (a) add the device before attempting to start the driver, preparing to back it out if the driver fails to start...

...eds, we proceed to create a device descriptor structure and add it to the list of open devices. > > This approach means that X11DeviceDriver() cannot do anything that potentially accesses the dd structure because it isn't there yet, and the things it cannot do apparently includes calling R_ProcessX11Events(). [To be completely sure that this is actually still true, I'd need to have a closer look at what handleEvent() does.] > > So to fix things, it would seem that you could (a) add the device before attempting to start the driver, preparing to back it out if the driver fails to start,...

...X11/devX11.c:2824 for >>>> a reason, because commenting it out causes R to miss an important >>>> ConfigureNotify event in my window manager. The result is that plots >>>> are initially drawn off the window borders, unreadable. >>>> >>>> R_ProcessX11Events((void*) NULL); >>>> >>>> Unfortunately for me, this line is commented in the standard release >>>> of R, it has "#if BUG ... #endif" around it. >>>> >>>> I guess it is also unfortunate for anyone who uses the same window >...

...someone put this line in src/modules/X11/devX11.c:2824 for >> a reason, because commenting it out causes R to miss an important >> ConfigureNotify event in my window manager. The result is that plots >> are initially drawn off the window borders, unreadable. >> >> R_ProcessX11Events((void*) NULL); >> >> Unfortunately for me, this line is commented in the standard release >> of R, it has "#if BUG ... #endif" around it. >> >> I guess it is also unfortunate for anyone who uses the same window >> manager as I do, namely i3, which...

...f it succeeds, we proceed to create a device descriptor structure and add it to the list of open devices. This approach means that X11DeviceDriver() cannot do anything that potentially accesses the dd structure because it isn't there yet, and the things it cannot do apparently includes calling R_ProcessX11Events(). [To be completely sure that this is actually still true, I'd need to have a closer look at what handleEvent() does.] So to fix things, it would seem that you could (a) add the device before attempting to start the driver, preparing to back it out if the driver fails to start, or (b) add...

...gt; > I know that someone put this line in src/modules/X11/devX11.c:2824 for > a reason, because commenting it out causes R to miss an important > ConfigureNotify event in my window manager. The result is that plots > are initially drawn off the window borders, unreadable. > > R_ProcessX11Events((void*) NULL); > > Unfortunately for me, this line is commented in the standard release > of R, it has "#if BUG ... #endif" around it. > > I guess it is also unfortunate for anyone who uses the same window > manager as I do, namely i3, which I think is pretty popular...

...ceeds, we proceed to create a device descriptor structure and add it to the list of open devices. >> This approach means that X11DeviceDriver() cannot do anything that potentially accesses the dd structure because it isn't there yet, and the things it cannot do apparently includes calling R_ProcessX11Events(). [To be completely sure that this is actually still true, I'd need to have a closer look at what handleEvent() does.] >> So to fix things, it would seem that you could (a) add the device before attempting to start the driver, preparing to back it out if the driver fails to start, or...

...ine in src/modules/X11/devX11.c:2824 for >>> a reason, because commenting it out causes R to miss an important >>> ConfigureNotify event in my window manager. The result is that plots >>> are initially drawn off the window borders, unreadable. >>> >>> R_ProcessX11Events((void*) NULL); >>> >>> Unfortunately for me, this line is commented in the standard release >>> of R, it has "#if BUG ... #endif" around it. >>> >>> I guess it is also unfortunate for anyone who uses the same window >>> manager a...

...width, height, @@ -2238,8 +2241,6 @@ xd->fill = 0xffffffff; /* this is needed to ensure that the first newpage does set whitecolor if par("bg") is not transparent */ - strncpy(xd->title, title, 100); - xd->title[100] = '\0'; #if BUG R_ProcessX11Events((void*) NULL); --=-=-=--

> sessionInfo() R version 2.8.0 Under development (unstable) (2008-07-07 r46046) i686-pc-linux-gnu locale: LC_CTYPE=en_US.UTF-8;LC_NUMERIC=C;LC_TIME=en_US.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=C;LC_MESSAGES=en_US.UTF-8;LC_PAPER=en_US.UTF-8;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT=en_US.UTF-8;LC_IDENTIFICATION=C attached base packages: [1] stats graphics grDevices utils

I can repeatably crash R (segfault) by doing n <- 10 z <- data.frame(a=1:n,b=1:n) View(z) and then hitting the "End" key on my keyboard. I haven't got debugging going yet, but running under gdb (without debugging symbols) does give this: 0xb7b63583 in strlen () from /lib/tls/i686/cmov/libc.so.6 R version 2.6.2 (2008-02-08) i486-pc-linux-gnu [Ubuntu Gutsy] locale:

...from gdb, edited to show what I think is going on. (gdb) bt #0 removeDevice (devNum=1, findNext=TRUE) at devices.c:307 #1 0xb7962855 in handleEvent (event= {type = 33, xany = {type = 33, serial = 15621, send_event = 1, ...(snip)... , 268686226}}) at devX11.c:627 #2 0xb796296c in R_ProcessX11Events (data=0x0) at devX11.c:665 #3 0x080fd99c in R_runHandlers (handlers=0x8263d28, readMask=0x82cf6a0) at sys-std.c:363 #4 0xb74e159e in RTcl_eventProc (evPtr=0x97dfbf0, flags=-1) at tcltk_unix.c:136 #5 0xb749d6a3 in Tcl_ServiceEvent () from /usr/lib/libtcl8.4.so.0 #6 0xb749da32 in Tcl_DoOneE...