[#5219] Segmentation fault in timeout.rb — Michel Pastor <K@...>

Hi,

18 messages 2005/06/16
[#5220] Re: Segmentation fault in timeout.rb — Eric Hodel <drbrain@...7.net> 2005/06/16

[#5221] Re: Segmentation fault in timeout.rb — Michel Pastor <K@...> 2005/06/16

On Fri, 17 Jun 2005 05:03:18 +0900

[#5223] Re: Segmentation fault in timeout.rb — nobu.nokada@... 2005/06/17

Hi,

[#5296] Subversion — Shugo Maeda <shugo@...>

Hi,

64 messages 2005/06/30
[#5297] Re: Subversion — Curt Hibbs <curt@...> 2005/06/30

Shugo Maeda wrote:

[#5298] Re: Subversion — Nikolai Weibull <mailing-lists.ruby-core@...> 2005/06/30

Curt Hibbs wrote:

[#5301] Re: Subversion — Austin Ziegler <halostatue@...> 2005/06/30

On 6/30/05, Nikolai Weibull

[#5304] Re: Subversion — Nikolai Weibull <mailing-lists.ruby-core@...> 2005/06/30

Austin Ziegler wrote:

[#5305] Re: Subversion — Austin Ziegler <halostatue@...> 2005/06/30

On 6/30/05, Nikolai Weibull

[#5307] Re: Subversion — mathew <meta@...> 2005/06/30

Austin Ziegler wrote:

[#5308] Re: Subversion — Austin Ziegler <halostatue@...> 2005/06/30

On 6/30/05, mathew <meta@pobox.com> wrote:

[#5311] Re: Subversion — mathew <meta@...> 2005/07/01

Austin Ziegler wrote:

[#5323] Re: Subversion — Austin Ziegler <halostatue@...> 2005/07/01

On 7/1/05, mathew <meta@pobox.com> wrote:

[#5325] Re: Subversion — Nikolai Weibull <mailing-lists.ruby-core@...> 2005/07/01

Austin Ziegler wrote:

Re: Segmentation fault in timeout.rb

From: Michel Pastor <K@...>
Date: 2005-06-18 20:48:18 UTC
List: ruby-core #5243
Hi,

On Sat, 18 Jun 2005 10:28:53 +0900
nobu.nokada@softhome.net wrote:

> > Program received signal SIGINT, Interrupt.
> 
> Did you hit Ctrl-C?  Then this all results seem normal.

Yes I had to hit Ctrl-C to take control over the debug session since ruby did not send ABRT
I also tested sending ABRT to generate the core but had the same problems as below

> > (gdb) p ruby_current_node
> > $5 = (struct RNode *) 0xb7e176e8
> 
> I forgot to mention about this, I'd like to know also
> *ruby_current_node.

Sorry, I can't give you this one. I retryed the same thing but can't get rb_thread_schedule() in the call chain anymore after hitting Ctrl-C. Seems I had been very lucky. Sometimes gdb even says the stack is corrupted like bellow :

deadlock 0xb75dae70: run:-  - :0
deadlock 0xb7e73798: sleep:ST(1119126226.871684) (main) - /usr/lib/ruby/1.8/webrick/server.rb:88
deadlock 0xb774d0a0: sleep:T(1119126255.847502)  - /usr/lib/ruby/1.8/timeout.rb:41

Program received signal SIGINT, Interrupt.
[Switching to Thread -1209562464 (LWP 4685)]
0x08057673 in rb_thread_restore_context (th=0x9a1, exit=69576) at eval.c:9993
9993        MEMCPY(tmp->stk_pos, tmp->stk_ptr, VALUE, tmp->stk_len);
(gdb) bt
#0  0x08057673 in rb_thread_restore_context (th=0x9a1, exit=69576) at eval.c:9993
#1  0xb7747560 in ?? ()
#2  0xb76b93a0 in ?? ()
#3  0xb7e672e0 in ?? ()
#4  0xbffefd28 in ?? ()
#5  0x0805b22e in rb_eval (self=3085391876, n=0x10fc8) at eval.c:1776
Previous frame inner to this frame (corrupt stack?)

thx
- Michel

In This Thread