On Tue, 2005-04-26 at 11:30 -0500, Marc Schwartz wrote:
> On Tue, 2005-04-26 at 11:41 -0400, Manuel Morales wrote:
> > On Tue, 2005-04-26 at 10:34 -0500, Marc Schwartz wrote:
> > > On Tue, 2005-04-26 at 16:47 +0200, [EMAIL PROTECTED] wrote:
> > > > I tried to submit this in R, but not sure if it worked.
> > > >
> > > > When running R as sudo, using ctrl-c dumps me to the command line.
> > > > Hitting exit to exit the terminal window results in R taking 100% of
> > > > resources.
> > > >
> > > > I am using R-2.1.0 on Fedora Core 3.
> > > >
> > > > Thanks.
> > > >
> > > > Manuel
> > >
> > > I suspect that we are going to need more information.
> > >
> > > Running on a fully updated FC3 box using Xfce's Terminal, gnome-terminal
> > > and kconsole, I cannot duplicate this issue either as a user or as root
> > > using sudo.
> > >
> > Note that this doesn't happen if I run R as a normal user or as root.
> > I.e.,
> >
> > R
> > <ctrl-c>
> > or
> >
> > su
> > R
> > <ctrl-c>
> > works fine.
> >
> > sudo R
> > <ctrl-c>
> > does not.
> >
> > > Attach the output of:
> > >
> > > > R.version
> > >
> >
> > > R.version
> > _
> > platform i686-pc-linux-gnu
> > arch i686
> > os linux-gnu
> > system i686, linux-gnu
> > status
> > major 2
> > minor 1.0
> > year 2005
> > month 04
> > day 18
> > language R
> >
> >
> > > Was there a program running in R at the time, or were you at the R
> > > prompt when you hit ctrl-c?
> > >
> >
> > R prompt
> >
> > > Which desktop environment and terminal emulator are you using?
> > >
> >
> > Gnome and gnome-terminal, although the problem also happens when using
> > xterm.
> >
> > > Have you perhaps re-mapped ctrl-c using modified keybindings?
> >
> > No. And ctrl-c works fine as a normal user or as root.
>
> Manuel,
>
> Please be sure to copy [EMAIL PROTECTED] when you reply so that the
> thread is properly archived in the bug tracking system.
>
> I tried this under GNOME using gnome-terminal and the unpatched version
> of R 2.1.0 and still could not duplicate the problem.
>
> Can you post back with the contents of /etc/sudoers?
>
> The other possibility would be to run:
>
> sudo R -d gdb
>
> in gnome-terminal. When you get to the (gdb) prompt, type 'r' (without
> the quotes) for run, which will start up R.
>
> If you can replicate the problem under gdb and R exits after a ctrl-c,
> you should be left at a (gdb) prompt. If that occurs, type 'bt' (without
> the quotes), which will display a backtrace. If that all works, post the
> output of gdb from the crtl-c through and including the backtrace here.
>
> Marc
>
>
Program received signal SIGINT, Interrupt.
0x006547a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
(gdb) bt
#0 0x006547a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x0072da1d in ___newselect_nocancel () from /lib/tls/libc.so.6
#2 0x0813e060 in R_SelectEx (n=1, readfds=0x825dde0, writefds=0x0,
exceptfds=0x0, timeout=0x0, intr=0x813e5a8 <handleInterrupt>)
at sys-std.c:138
#3 0x0813e281 in R_checkActivityEx (usec=-1, ignore_stdin=0,
intr=0x813e5a8 <handleInterrupt>) at sys-std.c:302
#4 0x0813e6f0 in Rstd_ReadConsole (prompt=0x0, buf=0xbfffb33c "",
len=1024,
addtohistory=-514) at sys-std.c:642
#5 0x080cac4a in Rf_ReplIteration (rho=0x9522cb8, savestack=-514,
browselevel=0, state=0xbfffb330) at main.c:208
#6 0x080cadef in R_ReplConsole (rho=0x9522cb8, savestack=0,
browselevel=0)
at main.c:306
#7 0x080cb03d in run_Rmainloop () at main.c:685
#8 0x0805d948 in main (ac=1, av=0xbfffb844) at Rmain.c:31
The relevant line in my /etc/sudoers:
mmorales ALL=(ALL) ALL
______________________________________________
R-devel@stat.math.ethz.ch mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
