[#4346] Segmentation fault — Andrew Walrond <andrew@...>
FYI, just got this random unexpected crash
On 01 Feb 2005, at 07:33, Andrew Walrond wrote:
[#4360] Adding lastlog info to etc — "Berger, Daniel" <Daniel.Berger@...>
Hi all,
[#4368] 'when (cond):' causes SyntaxError — "NAKAMURA, Hiroshi" <nakahiro@...>
Hi,
[#4385] add color_set support to curses.c — Paul Duncan <pabs@...>
I'm not sure why this is missing from the Curses binding, but the
[#4392] HTTP Basic authentication for open_uri — Kent Sibilev <ksibilev@...>
Can somebody apply the following patch for open_uri in order to enable
[#4402] BUG: Struct.new(:a?).instance_methods — "Cs. Henk" <csaba-ml@...>
Hi, getting an ArgumentError with "NULL pointer given" doesn't seem to
[#4403] Re: Unknown OS X 10.2 Socket constants (+script to generate) — Sam Roberts <sroberts@...>
Quoteing matz@ruby-lang.org, on Tue, Feb 08, 2005 at 01:21:18PM +0900:
[#4427] Re: windows socket connection freeze — ville.mattila@...
[#4432] curses + threads = non-blocking getch — William Morgan <wmorgan-ruby-core@...>
Hello experts,
In article <20050214231544.GE26414@masanjin.net>,
[#4439] Thread-safe Ruby Status? — Vincent Isambart <vincent.isambart@...>
Hello,
[#4448] add persistent history to irb — "David A. Black" <dblack@...>
Hi --
[#4453] bug in IRB with $_ matching a range of regexps — Ryan Davis <ryand-ruby@...>
> % ruby -v
[#4468] Re: Strange argc check in stable snapshot — "Berger, Daniel" <Daniel.Berger@...>
> -----Original Message-----
[#4475] Re: Strange argc check in stable snapshot — "Berger, Daniel" <Daniel.Berger@...>
> -----Original Message-----
[#4479] Requesting addition to IRB (configurable standard output) — Sascha Ebach <se@...>
Hello,
Quoting se@digitale-wertschoepfung.de, on Fri, Feb 25, 2005 at 01:22:34AM +0900:
On 24 Feb 2005, at 19:51, Sam Roberts wrote:
Quoting drbrain@segment7.net, on Sat, Feb 26, 2005 at 02:43:31AM +0900:
On 25 Feb 2005, at 16:03, Sam Roberts wrote:
Quoting drbrain@segment7.net, on Sat, Feb 26, 2005 at 10:24:52AM +0900:
On 25 Feb 2005, at 18:55, Sam Roberts wrote:
Quoting drbrain@segment7.net, on Sat, Feb 26, 2005 at 03:49:49PM +0900:
Re: [BUG] Segmentation fault
On Tuesday 01 February 2005 18:27, Yukihiro Matsumoto wrote: > Hi, > > In message "Re: [BUG] Segmentation fault" > > on Wed, 2 Feb 2005 02:03:05 +0900, Eric Hodel <drbrain@segment7.net> writes: > |> Hope it might mean something to someone :) > | > |It would mean more with a backtrace, and if your Ruby was compiled with > |debugging symbols... > > And if the error reproducing Ruby program (along with input data) is > supplied. > Sorry guys. I always try my best to provide a patch, a testcase etc (google me and you'll see what I mean) But I'm afraid its another of those inherently unreproducible bugs. You're welcome to the code, but It's been run thousands of times with the same dataset andlib/modules/fglrx/build_mod/ this is the first (and last) time I've seen this particular segfault... I am pushing ruby quite hard with Rubyx, and do seem to turn up these unreproducible bugs (search back a couple months and you'll find the last one I was shouting about which turned out to be a nasty garbage collector bug, and really had me pulling my hair out :)) The purpose of my brief post was because, from (...long...) experience, it often useful for the author of code in question to have a quick look at possible failure modes in that area. I guess thats why the segfault notice has file name and linenumber... If I can turn anything else up, I'll be sure to post it here. Andrew Walrond