[#11073] segfault printing instruction sequence for iterator — <noreply@...>
Bugs item #10527, was opened at 2007-05-02 14:42
Hi,
On Thu, May 10, 2007 at 04:51:18PM +0900, Nobuyoshi Nakada wrote:
Hi,
Hi,
This seems to make valgrind much happier.
On Thu, May 17, 2007 at 11:14:35PM +0900, Paul Brannan wrote:
Hi,
Now 'a' shows up twice in the local table:
Hi,
[#11082] Understanding code: Kernel#require and blocks. — Hugh Sasse <hgs@...>
I'm trying to debug a Rails application which complains about an
On 5/4/07, Hugh Sasse <hgs@dmu.ac.uk> wrote:
On Fri, 4 May 2007, George wrote:
On Fri, May 04, 2007 at 06:18:19PM +0900, Hugh Sasse wrote:
[#11108] pattern for implementation-private constants? — David Flanagan <david@...>
Hi,
I believe there isn't a way, but I don't think it's really necessary. Just
[#11127] Bugs that can be closed — "Jano Svitok" <jan.svitok@...>
I propose closing these bugs as invalid:
[#11145] Rational comparison to 0 fails when denominator is != 1 — <noreply@...>
Bugs item #10739, was opened at 2007-05-10 22:06
Hi,
[#11169] Allow back reference with nest level in Oniguruma for Ruby again — =?ISO-8859-15?Q?Wolfgang_N=E1dasi-Donner?= <wonado@...>
Remark: I posted this text in comp.lang.ruby first, but Matz told me,
Does it make sense or is it required to write this as a RCR?
[#11176] FileUtils.rm_rf misfeature? — johan556@...
Hi!
[#11210] Pathname ascend and descend inclusive parameter — TRANS <transfire@...>
I would like to suggest that Pathname#ascend and Pathname#descend
[#11234] Planning to release 1.8.6 errata — Urabe Shyouhei <shyouhei@...>
Hi all.
On 25/05/07, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:
[#11252] Init_stack and ruby_init_stack fail to reinit stack (threads problem?) — <noreply@...>
Bugs item #11134, was opened at 2007-05-25 12:14
Hi,
Nobuyoshi Nakada wrote:
[#11255] ruby_1_8_6 build problem (make install-doc) — johan556@...
Hi!
[#11271] providing better support through rubyforge tracker categories — Ryan Davis <ryand-ruby@...>
I'm going to make more categories for the trackers (bugs and patches)
[#11367] BUG: next in lambda: 1.8.6 differs from 1.8.4 and 1.9.0 — David Flanagan <david@...>
A toplevel next statement in a lambda does not return a value in 1.8.6,
[#11368] $2000 USD Reward for help fixing Segmentation Fault in GC — Brent Roman <brent@...>
Hi Brent,
Re: Segmentation Fault in GC
> -----Original Message----- > From: Brent Roman [mailto:brent@mbari.org] > Sent: Monday, May 21, 2007 5:19 PM > To: ruby-core@ruby-lang.org > Subject: Segmentation Fault in GC > > > Help! > > Our Ruby controlled Robotic Marine Laboratory started failing > with segmentation faults just a few days before it was to be > deployed. We had seen random, very occasional segmentation > faults for some months, as our application grew larger and > more complex. Then, just days before the ship was scheduled > to sail, after we'd integrated a couple new and exciting > features, we started getting segfaults regularly. > > We have not been able to correlate the fault to a particular > operation in our application. However, it never occurs > sooner than 30 minutes or so after the application starts. > The application is heavily multithreaded and uses 3 RS-232 > serial ports accessed via the ruby termios library. > > Can anyone give me any hints as to what's going on by > looking at the attached stack backtrace? > > It appears to be deep into a GC cycle while executing Marshal.dump. > > Some notes on the target environment: > ARM9 processor (ep9312) running Linux kernel v2.4.26 > (cross-)Compiled with gcc version 3.4.5 -Os (not omitting > framepointer!) > glibc 2.2.5 > Ruby 1.6.8 <snip> Whoa, what? You're using 1.6.8? Seriously consider an upgrade to 1.8.6. The 1.6.x branch is dead, and much less reliable than the 1.8.x branch. Please consider upgrading asap. Regards, Dan This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.