From: Brent Roman <brent@...>
Date: 2009-03-07T16:05:02+09:00
Subject: [ruby-core:22714] Re: MBARI8 patch fixes bugs caused by incorrect  volatile variable declarations


Michael,

Look looks like there are three Ruby threads on the stack at the time of the
segfault.

'C' extensions and Ruby threads are a bit of a volatile mix..

What does the 'C' extension do?  Is it open source?
Do you invoke it from multiple threads?

You can first try applying this attached patch to either MBARI8B 1.8.7 or
1.8.6
It disables the thread stack copying optimization introduced with MBARI2.

http://www.nabble.com/file/p22385077/rmMBARI2.patch rmMBARI2.patch 

You know MBARI2 has been disabled if the bogus1.rb and bogus2.rb tests on my
website
take much (3x-8x) longer to complete.

- brent



Michael King-2 wrote:
> 
> Its been way too long since I have used gdb, and I haven't ever had to
> look
> at core files before so the tutorial filled in the gaps of my memory and
> knowledge. It was just as simple as gdb ruby core, previously I was trying
> to use just the core file, chalk it up to user error.
> 
> ...
> 
> 

-- 
View this message in context: http://www.nabble.com/MBARI8-patch-fixes-bugs-caused-by-incorrect-volatile-variable-declarations-tp22259357p22385077.html
Sent from the ruby-core mailing list archive at Nabble.com.