[#4076] Ruby/DL — Jamis Buck <jamis_buck@...>

I recently used Ruby/DL to create bindings to the SQLite3 embedded

40 messages 2005/01/03
[#4096] Re: Ruby/DL — Paul Brannan <pbrannan@...> 2005/01/04

On Tue, Jan 04, 2005 at 02:53:49AM +0900, Jamis Buck wrote:

[#4099] Re: Ruby/DL — ts <decoux@...> 2005/01/04

>>>>> "P" == Paul Brannan <pbrannan@atdesk.com> writes:

[#4119] Re: Ruby/DL — Paul Brannan <pbrannan@...> 2005/01/05

On Wed, Jan 05, 2005 at 03:05:48AM +0900, ts wrote:

[#4120] Re: Ruby/DL — ts <decoux@...> 2005/01/05

>>>>> "P" == Paul Brannan <pbrannan@atdesk.com> writes:

[#4125] Re: Ruby/DL — Paul Brannan <pbrannan@...> 2005/01/05

On Thu, Jan 06, 2005 at 01:10:34AM +0900, ts wrote:

[#4116] Test::Unit::Collector::Dir won't work with code that modifies $LOAD_PATH — Eric Hodel <drbrain@...7.net>

Any test code that depends upon modifications of $: fails when used

10 messages 2005/01/05

[#4146] The face of Unicode support in the future — Charles O Nutter <headius@...>

Hello Rubyists!

47 messages 2005/01/06
[#4152] Re: The face of Unicode support in the future — Yukihiro Matsumoto <matz@...> 2005/01/07

Hi,

[#4167] Re: The face of Unicode support in the future — Christian Neukirchen <chneukirchen@...> 2005/01/09

Yukihiro Matsumoto <matz@ruby-lang.org> writes:

[#4175] Re: The face of Unicode support in the future — Yukihiro Matsumoto <matz@...> 2005/01/10

Hi,

[#4186] Re: The face of Unicode support in the future — Paul Brannan <pbrannan@...> 2005/01/11

On Mon, Jan 10, 2005 at 11:53:48PM +0900, Yukihiro Matsumoto wrote:

[#4192] Re: The face of Unicode support in the future — Yukihiro Matsumoto <matz@...> 2005/01/12

Hi,

[#4269] Re: The face of Unicode support in the future — Wes Nakamura <wknaka@...>

19 messages 2005/01/18
[#4270] Re: The face of Unicode support in the future — Yukihiro Matsumoto <matz@...> 2005/01/18

Hi,

[#4275] Re: The face of Unicode support in the future — Wes Nakamura <wknaka@...> 2005/01/19

[#4323] test/unit doesn't rescue a Exception — Tanaka Akira <akr@...17n.org>

test/unit doesn't rescue a Exception in a test method, as follows.

14 messages 2005/01/27
[#8773] Re: test/unit doesn't rescue a Exception — Tanaka Akira <akr@...> 2006/09/02

In article <87is5jb46q.fsf@serein.a02.aist.go.jp>,

[#8776] Re: test/unit doesn't rescue a Exception — "Nathaniel Talbott" <ntalbott@...> 2006/09/03

On 9/1/06, Tanaka Akira <akr@fsij.org> wrote:

[#8777] Re: test/unit doesn't rescue a Exception — Eric Hodel <drbrain@...7.net> 2006/09/03

On Sep 2, 2006, at 6:34 PM, Nathaniel Talbott wrote:

Re: Segfault in timer.rb

From: Erlend Oye <segfault.ruby-talk@...>
Date: 2005-01-13 16:18:29 UTC
List: ruby-core #4222
Erlend Oye wrote:

> Erlend Oye wrote:
>
>> Hi Florian,
>>
>> > Florian Gross wrote:
>> >> Erlend Oye wrote:
>> >> /usr/local/lib/ruby/1.8/timeout.rb:40: [BUG] rb_gc_mark() called for
>> >> broken object
>> >> ruby 1.8.2 (2005-01-10) [i386-cygwin]
>>
>> >> [...]
>> >> zsh: 22780 abort (core dumped) ruby scrape_server.rb
>> >> --------
>> >> /usr/local/lib/ruby/1.8/timeout.rb:40: [BUG] rb_gc_mark(): unknown 
>> data
>> >> type 0x2e(0x1037d178) non object
>> >> ruby 1.8.2 (2005-01-10) [i386-cygwin]
>> >
>>
>> >Any other libraries that it's using? YAML used to do something similar.
>>
>> Here are the various requires and includes (not in order)
>>
>> require 'cgi'
>> require 'net/http'
>> require 'rexml/document'
>> require 'uri/http'
>> include WEBrick
>> require 'webrick'
>>
>> I believe timeout is being used by Webrick internally and not RSSScraper
>> directly.
>>
>> RSSScraper is at
>>
>> http://rssscraper.rubyforge.org
>>
>> Thanks
>> Erlend Oye
>
>
> All of these segfaults seemed to be happening at
>
> Thread.start
>
> statements. This hinted some trouble with thread support so I 
> recompiled using
>
> --disable-pthread
>
> and the troubles have disappeared. I wonder if this is an issue from 
> Ruby's side
> or on Cygwin's side. I am noticing other segfaults being  reported on 
> other platforms
> (e.g linux) due to pthreads support also.
>
> Thanks
> Erlend Oye
>
(Cross posting to core)

Spoke too soon. The segfault still happens at

Thread.start

-Erlend Oye


In This Thread

Prev Next