[#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
Hi Ville On Wednesday 02 February 2005 08:13, ville.mattila@stonesoft.com wrote: > > What optmization level you are using when compiling ruby? If it is O3, then > this patch might help? > > Fri Jan 7 18:03:35 2005 Tanaka Akira <akr@m17n.org> > > * gc.c (mark_locations_array): avoid core dump with -O3. > [ruby-dev:25424] > I'm using -O2, so should be OK > > Also I think that we should study the information from > http://rubyforge.org/tracker/index.php?func=detail&aid=1243&group_id=426&at >id=1698 > > there might be subtle 64 bit problems that are hidden because we do not see > all compiler warnings... Thanks for the pointer. "ruby defaults to using gcc c89 syntax. Use of -pedantic reveals ruby is using 'long long' and 'inline'. Compiling with gcc -std=gnu99 solves a stack management problem in the code since gnu99 treats 'long long' as 64-bit. " This certainly looks interesting. I wonder if it applies to x86_64, since I think the standard types have different sizes than ia64 (eg int=32bits, long=64bits on x86_64, but I think int=64bits on ia64?) What do people think; Is "gcc -std=gnu99" worth a shot on x86_64 ? Andrew