[#22684] [Bug #1247] YAML::load converts some dates into strings — Matthew Wilson <redmine@...>

Bug #1247: YAML::load converts some dates into strings

10 messages 2009/03/05

[#22725] [Bug #1253] Fix MSVC Build Issues — Charlie Savage <redmine@...>

Bug #1253: Fix MSVC Build Issues

13 messages 2009/03/07

[#22727] Moving ruby 1.9.1 forward on windows — Charlie Savage <cfis@...>

Hi everyone,

14 messages 2009/03/08

[#22731] [Bug #1255] += for large strings egrigiously slow — James Lee <redmine@...>

Bug #1255: += for large strings egrigiously slow

11 messages 2009/03/08

[#22736] Ruby 1.9.1 and tail recursion optimization — =?ISO-8859-15?Q?Wolfgang_N=E1dasi-Donner?= <ed.odanow@...>

Moin, moin!

13 messages 2009/03/08
[#22739] Re: Ruby 1.9.1 and tail recursion optimization — =?ISO-8859-15?Q?Wolfgang_N=E1dasi-Donner?= <ed.odanow@...> 2009/03/08

Wolfgang N疆asi-Donner schrieb:

[#22748] [Feature #1256] Add constant TAILRECURSION to let a program recognize if tail recursion optimization is implemented — Wolfgang Nádasi-Donner <redmine@...>

Feature #1256: Add constant TAILRECURSION to let a program recognize if tail recursion optimization is implemented

7 messages 2009/03/08

[#22803] Relegate 1.8.6 to Engine Yard, part II — Urabe Shyouhei <shyouhei@...>

Hello and sorry for my being slow for this issue. It's OK now for me to pass

21 messages 2009/03/10

[#22812] [Bug #1261] cross-compiling Ruby extensions using mkmf doesn't fully respect DESTDIR — Daniel Golle <redmine@...>

Bug #1261: cross-compiling Ruby extensions using mkmf doesn't fully respect DESTDIR

8 messages 2009/03/10

[#22892] Ruby Time — valodzka <valodzka@...>

Got tired of current ruby Time limitation, I have written this -

24 messages 2009/03/14
[#22949] Re: Ruby Time — Tanaka Akira <akr@...> 2009/03/19

In article <9e19ed87-9d12-4f98-af3c-bd49a71b0bd4@p11g2000yqe.googlegroups.com>,

[#22974] Re: Ruby Time — valodzka <valodzka@...> 2009/03/20

[#22977] Re: Ruby Time — Urabe Shyouhei <shyouhei@...> 2009/03/20

valodzka wrote:

[#22981] Re: Ruby Time — valodzka <valodzka@...> 2009/03/21

> I bet you'll get tired of updating that database. There's a major difference

[#22893] [Feature #1291] O_CLOEXEC flag missing for Kernel::open — David Martin <redmine@...>

Feature #1291: O_CLOEXEC flag missing for Kernel::open

10 messages 2009/03/15

[#22939] [Bug #1303] A name considered a local variable on RHS of an assignment that defines it — Tomas Matousek <redmine@...>

Bug #1303: A name considered a local variable on RHS of an assignment that defines it

8 messages 2009/03/19

[#23063] [Bug #1332] Reading file on Windows is 500x slower then with previous Ruby version — Damjan Rems <redmine@...>

Bug #1332: Reading file on Windows is 500x slower then with previous Ruby version

11 messages 2009/03/30

[#23075] [Bug #1336] Change in string representation of Floats — Brian Ford <redmine@...>

Bug #1336: Change in string representation of Floats

37 messages 2009/03/31
[#23179] [Bug #1336] Change in string representation of Floats — Roger Pack <redmine@...> 2009/04/11

Issue #1336 has been updated by Roger Pack.

[#23181] Re: [Bug #1336] Change in string representation of Floats — Brent Roman <brent@...> 2009/04/11

[#23186] Re: [Bug #1336] Change in string representation of Floats — Yukihiro Matsumoto <matz@...> 2009/04/12

Hi,

[#23187] Re: [Bug #1336] Change in string representation of Floats — Brent Roman <brent@...> 2009/04/13

[#23188] Re: [Bug #1336] Change in string representation of Floats — Yukihiro Matsumoto <matz@...> 2009/04/13

Hi,

[ruby-core:22688] Re: MBARI8 patch fixes bugs caused by incorrect volatile variable declarations

From: Michael King <kingmt@...>
Date: 2009-03-05 21:37:43 UTC
List: ruby-core #22688
gdb -core core
bt full
#0  0xffffe410 in __kernel_vsyscall ()
No symbol table available.
#1  0xb7dac9a1 in ?? ()
No symbol table available.

I'm thinking that this is much shorter than it should be. This build was
compiled with -O0 -g.

At the moment it takes about 10 minutes for the test case to run and
segfault.

- Michael

On Thu, Mar 5, 2009 at 12:28 PM, Brent Roman <brent@mbari.org> wrote:

>
> Michael,
>
> A 'C'-stack backtrace from gdb would be nice.
> Trim the top off it if it is deeper than 50 levels or so.
> The core file would be troublesome, as it will likely be very large
> and require my duplicating your execution environment to load it.
>
> How difficult is it to reproduce the bug there? (seconds or days?)
> To produce the best stack trace, compile with -O0  -g and
>  use the "full" qualifier in gdb.
>
> - brent
>
>
> Michael King-2 wrote:
> >
> > by back trace do you mean the output of
> > gdb -core core
> > bt
> >
> > or do you want the actual core file?
> >
> > - Michael
> >
> > On Wed, Mar 4, 2009 at 5:06 PM, Roger Pack <rogerdpack@gmail.com> wrote:
> >
> >> a back trace and ruby -v would be nice.
> >>
> >> > I am having an issue with the MBARI patches. In our app the test suite
> >> has a
> >> > segfault at line 1413 in drb.rb. I am compiling Ruby on Ubuntu 6.06,
> >> 32bit,
> >> > GCC 4.0.3. The segfault shows up when compiling at O2 and O0(zero).
> >>
> >> -=r
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/MBARI8-patch-fixes-bugs-caused-by-incorrect-volatile-variable-declarations-tp22259357p22357591.html
> Sent from the ruby-core mailing list archive at Nabble.com.
>
>
>

In This Thread