[#30589] [Bug #3391] Use single exclamation mark instead of double exclamation mark for IRB — Diego Viola <redmine@...>

Bug #3391: Use single exclamation mark instead of double exclamation mark for IRB

10 messages 2010/06/04

[#30672] [Bug #3411] Time.local 1916,5,1 #=> 1916-04-30 23:00:00 +0100 — Benoit Daloze <redmine@...>

Bug #3411: Time.local 1916,5,1 #=> 1916-04-30 23:00:00 +0100

12 messages 2010/06/08

[#30699] [Bug #3419] 1.9.2-preview3 possible bug with Rails 3 active_record sqlite_adapter — Joe Sak <redmine@...>

Bug #3419: 1.9.2-preview3 possible bug with Rails 3 active_record sqlite_adapter

9 messages 2010/06/09

[#30734] [Bug #3428] ri outputs ansi escape sequences even when stdout is not a tty — caleb clausen <redmine@...>

Bug #3428: ri outputs ansi escape sequences even when stdout is not a tty

11 messages 2010/06/11

[#30756] [Feature #3436] Spawn the timer thread lazily — Maximilian Gass <redmine@...>

Feature #3436: Spawn the timer thread lazily

15 messages 2010/06/13
[#32686] [Ruby 1.9-Feature#3436] Spawn the timer thread lazily — Mark Somerville <redmine@...> 2010/10/04

Issue #3436 has been updated by Mark Somerville.

[ruby-core:30826] Re: [Bug #3454] Segfault with syscall

From: Yukihiro Matsumoto <matz@...>
Date: 2010-06-19 15:01:32 UTC
List: ruby-core #30826
Hi,

In message "Re: [ruby-core:30824] [Bug #3454] Segfault with syscall"
    on Sat, 19 Jun 2010 21:04:16 +0900, Shyouhei Urabe <redmine@ruby-lang.org> writes:

|Issue #3454 has been updated by Shyouhei Urabe.
|
|Ruby does not stop you to shoot your foot.  I believe this is not a bug.

Indeed.  syscall expected buffer of sizeof(struct stat), but you gave
it an empty string, so as natural consequence syscall overwrote memory
region, and segmentation fault was happened.  When you use syscall,
it's fundamentally C programming with Ruby syntax, so you can do
anything as bad as C can.  Same rule applied to dl and ffi.

I will restrict syscall to require $SAFE=0, just for fool proof.

							matz.

In This Thread