orem (Chris Schlaeger)
- Login: orem
- Email: cschlaeger@gmail.com
- Registered on: 02/20/2009
- Last sign in: 03/30/2010
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 0 | 5 | 5 |
Activity
04/23/2010
- 02:33 AM Ruby master Bug #3052: DRb::start_service fails to detect used port
- =begin
On Thu, Apr 22, 2010 at 6:58 PM, Yusuke ENDOH <mame@tsg.ne.jp> wrote:
> This may be side effect of ipv6 supp... - 12:06 AM Ruby master Bug #3052: DRb::start_service fails to detect used port
- =begin
I did some more tests and the problem is most likely not DRb specific.
I can reproduce this with TCPSocket a...
03/30/2010
- 04:08 PM Ruby master Bug #3052 (Rejected): DRb::start_service fails to detect used port
- =begin
When I call DRb.start_service('druby://localhost:1234') and port 1234 is already in use, I silently end up wi...
11/15/2009
- 11:17 PM Ruby master Bug #2371: [BUG] thread_free: locking _mutex must be NULL
- =begin
Thanks for the very quick response!
> The following patch should fix the issue. Could you try?
Sure.
... - 05:26 PM Ruby master Bug #2371 (Closed): [BUG] thread_free: locking _mutex must be NULL
- =begin
During the development of a project management application I encountered the following problem. Every 10th ru... - 05:11 PM Ruby master Bug #2370 (Closed): Forked process generates spurious signal errors
- =begin
The attached test program demonstrates the problem. About 25% percent of the time the forked-off program term...
03/09/2009
- 06:33 PM Ruby master Bug #1227: [BUG] object allocation during garbage collection phase
- =begin
Yes, I was using Ruby 1.9.1 (or rather a post 1.9.1 SVN snapshot).
Chris
On Mon, Mar 9, 2009 at 8:00 AM...
03/01/2009
- 02:01 AM Ruby master Bug #1227 (Third Party's Issue): [BUG] object allocation during garbage collection phase
- =begin
I'm trying to profile sections of a large application (taskjuggler) with ruby-prof. As soon as I hit the Ruby...
02/23/2009
- 04:35 PM Ruby master Bug #1181: [BUG] thread_free: keeping_mutexes must be NULL
- =begin
I can confirm that your patch fixes the problem. Thanks for your quick help!
Chris
=end
02/20/2009
- 05:10 AM Ruby master Bug #1181 (Closed): [BUG] thread_free: keeping_mutexes must be NULL
- =begin
I've tried to run taskjuggler with ruby 1.9 CVS from today and got internal error messages. The applications ...
Also available in: Atom