On Tue, 26 Apr 2005, Peter Dalgaard wrote:
> [EMAIL PROTECTED] writes:
>
>>> Thanks you, however Marc omitted to mention that you need to type
>>> signal SIGINT
>>> before running the backtrace (bt), because gdb will catch the INT
>>> signal thus not leading to the desired crash and the backtrace just
>>> shows when you hit Ctrl-C, not what happens after. Only after the
>>> signal SIGINT you should get the crash (if at all).
> ...
>> Manuel, I should have asked earlier, but I presume that you installed
>> from source as I don't see RPMs for 2.1.0 yet?
>>
>> Marc
>
> The effect seem to have been neatly backported to 2.0.1 though...
>
> Gdb doesn't seem to help. If you run a ps while "sudo R" is running,
> you'll see something like this:
>
> root 30416 0.0 0.1 2356 252 pts/5 S+ 19:48 0:00 sesh /usr/bin/R
> root 30417 10.0 7.2 18016 13860 pts/5 S+ 19:48 0:01
> /usr/lib/R/bin/exec/R
>
> What I suspect is happening is that the ^C kills the sesh process, but
> that in turn does not manage to kill R.
Should it? R traps that signal.
I'll now make the comment I thought when I first saw this:
Why is this a bug report against R not sudo?
--
Brian D. Ripley, [EMAIL PROTECTED]
Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/
University of Oxford, Tel: +44 1865 272861 (self)
1 South Parks Road, +44 1865 272866 (PA)
Oxford OX1 3TG, UK Fax: +44 1865 272595
______________________________________________
R-devel@stat.math.ethz.ch mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
