[#1834] New syck bug — Chad Fowler <chad@...>
There is a new syck bug that appears to be caused by the recent fix for
[#1836] exit inside test/unit — nobu.nokada@...
Hi,
On Dec 1, 2003, at 02:55, nobu.nokada@softhome.net wrote:
[#1843] DRb tests hang on OS X 10.3.1 — Nathaniel Talbott <nathaniel@...>
I haven't yet been able to test this on another platform to see if it
[#1846] Re: Constants, class variables and the cbase field — george.marrows@...
> What kind of behavior do you want (to change)? Remember you're saying
Hi,
On Monday 01 December 2003 06:44 pm, Yukihiro Matsumoto wrote:
Hi,
On Tuesday 02 December 2003 04:02 am, Yukihiro Matsumoto wrote:
[#1884] multiple exceptions for assert_raises — nobu.nokada@...
Hi,
Hi,
On Dec 4, 2003, at 02:34, Yukihiro Matsumoto wrote:
On Dec 4, 2003, at 01:35, nobu.nokada@softhome.net wrote:
On Dec 4, 2003, at 10:39, Nathaniel Talbott wrote:
[#1901] Test::Unit problem — "Sean E. Russell" <ser@...>
-----BEGIN PGP SIGNED MESSAGE-----
Hi,
[#1914] -Wall warnings from 1.8.1 p3 — Daniel Berger <djberge@...>
Here are some potentially significant warnings from 1.8.1 p3
nobu.nokada@softhome.net wrote:
[#1932] --enable-pthread broken? — Nathaniel Talbott <nathaniel@...>
[ruby-talk: 87759] and the surrounding thread seem to indicate that
Hi,
On Dec 11, 2003, at 11:49, Yukihiro Matsumoto wrote:
>>>>> "N" == Nathaniel Talbott <nathaniel@talbott.ws> writes:
Hi,
On Dec 11, 2003, at 16:10, nobu.nokada@softhome.net wrote:
Hi,
Hi,
On Dec 11, 2003, at 20:48, Yukihiro Matsumoto wrote:
Hi,
>>>>> "Y" == Yukihiro Matsumoto <matz@ruby-lang.org> writes:
Hi,
>>>>> "Y" == Yukihiro Matsumoto <matz@ruby-lang.org> writes:
Hi,
>>>>> "Y" == Yukihiro Matsumoto <matz@ruby-lang.org> writes:
Hi,
[#1936] Can't define +@ for Symbol (plus ruby install problem) — "T. Onoma" <transami@...>
I wanted to see if the +@ problem was fixed in 1.8.1 preview 3 but when I do
Hi,
On Friday 12 December 2003 02:39 am, Yukihiro Matsumoto wrote:
Hi,
Hi.
Hi,
[#1973] Where to install documentation — Dave Thomas <dave@...>
Folks:
Hi,
Dave Thomas (dave@pragprog.com) wrote:
>
>> Using the standard install.rb, anything you include in a project's
Hi,
On Tue, Dec 16, 2003 at 03:52:26PM +0900, Dave Thomas wrote:
Hi,
[#2013] Mixin Module, Possible Bug? — "T. Onoma" <transami@...>
According to Pickaxe, Ch. 19, pg. 245, under Mixin Modules:
[#2037] --enable-pthread still segfaults... — Nathaniel Talbott <nathaniel@...>
I've finally been able to test my application under load using the
Hi,
On Dec 23, 2003, at 14:17, Yukihiro Matsumoto wrote:
Hi,
On Dec 23, 2003, at 14:34, Yukihiro Matsumoto wrote:
Hi,
On Dec 23, 2003, at 14:44, Yukihiro Matsumoto wrote:
Hi,
> I'm afraid you're using old configure file. Can you wipe off old
On Dec 23, 2003, at 15:18, Nathaniel Talbott wrote:
In message "Re: --enable-pthread still segfaults..."
On Dec 23, 2003, at 16:34, Yukihiro Matsumoto wrote:
Hi,
On Dec 23, 2003, at 17:04, Yukihiro Matsumoto wrote:
Hi,
On Dec 23, 2003, at 17:29, Yukihiro Matsumoto wrote:
Hi,
[#2071] rdoc is broken in 1.8.1 — Alexander Bokovoy <a.bokovoy@...>
Greetings!
[#2084] Error with Socket.getaddrinfo on OS X — Richard Kilmer <rich@...>
On OS X Panther:
[#2101] Can't call to_s on a frozen Date — Gavin Sinclair <gsinclair@...>
Interesting...
[#2102] syck segfaults when used in rdoc — Alexander Bokovoy <a.bokovoy@...>
Greetings!
>>>>> "A" == Alexander Bokovoy <a.bokovoy@sam-solutions.net> writes:
On Sun, Dec 28, 2003 at 11:41:49PM +0900, ts wrote:
>>>>> "A" == Alexander Bokovoy <a.bokovoy@sam-solutions.net> writes:
Hi,
[#2122] Bad interaction between timeout.rb and --enable-pthread — Nathaniel Talbott <nathaniel@...>
Here's a testcase that shows the problem:
I should have reduced it more before posting...
Nathaniel Talbott wrote:
Hi,
Hi,
On Jan 1, 2004, at 11:29, Yukihiro Matsumoto wrote:
On Jan 1, 2004, at 12:14, Nathaniel Talbott wrote:
Re: --enable-pthread broken?
>>>>> "Y" == Yukihiro Matsumoto <matz@ruby-lang.org> writes:
Y> Sorry for being stupid, but rb_trap_immediate is turned off in the
Y> restore_context, so thread_timer only set rb_thread_pending to 1 at
Y> most during the function execution, thus context switch would not
Y> happen even when tb_thread_critical is not set, right?
Another example (yesterday it was easier to see that that was io_fflush()
which give him the possibility to block easily). Same here I stop it
immediately when it block
(gdb) r
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /home/ts/ruby/ruby-1.8.1/ruby c.rb
[New Thread 16384 (LWP 8256)]
[New Thread 32769 (LWP 8257)]
[New Thread 16386 (LWP 8258)]
- 1- 1- 2- 3- 4- 5- 6- 7- 8- 9- 10- 11- 12- 13- 14- 15- 16||- 17- 17- 18- 19- 20- 21- 22- 23- 24- 25- 26- 27- 28- 29- 30- 31- 32- 33- 34- 35- 36- 37- 38- 39- 40- 41- 42- 43- 44- 45- 46- 47- 48- 49- 50|||||||||- 51- 51- 51- 51- 51- 51- 51- 51- 52- 52- 52- 52- 54- 54|- 55|||||||- 56||||||- 57- 58- 58- 58- 59- 59- 59- 59- 59- 59- 59- 59- 60- 60- 60- 61- 61- 61- 61- 62||||||- 63|- 63- 63- 63|- 64- 64- 64- 65|||||- 66- 66- 67|||||- 67- 68- 68- 68||- 69|||- 69- 69- 69- 70|
Program received signal SIGINT, Interrupt.
[Switching to Thread 16386 (LWP 8258)]
0x40033156 in nanosleep () from /lib/i686/libpthread.so.0
(gdb) t 1
[Switching to thread 1 (Thread 16384 (LWP 8256))]#0 0x420459c6 in setcontext
() from /lib/i686/libc.so.6
(gdb) bt
#0 0x420459c6 in setcontext () from /lib/i686/libc.so.6
#1 0x081cdd70 in ?? ()
#2 0x080629a0 in rb_thread_schedule () at eval.c:8943
#3 0x4003274e in __pthread_sighandler () from /lib/i686/libpthread.so.0
#4 0xbffe9dd8 in ?? ()
(gdb) stepi 32
8427 switch (n) {
(gdb) bt
#0 rb_thread_switch (n=1) at eval.c:8427
#1 0x08062945 in rb_thread_schedule () at eval.c:8930
#2 0x4003274e in __pthread_sighandler () from /lib/i686/libpthread.so.0
#3 <signal handler called>
#4 0x420459c6 in setcontext () from /lib/i686/libc.so.6
#5 0x081cdd70 in ?? ()
#6 0x080629a0 in rb_thread_schedule () at eval.c:8943
#7 0x4003274e in __pthread_sighandler () from /lib/i686/libpthread.so.0
#8 0xbffe9dd8 in ?? ()
(gdb)
Guy Decoux