[#30995] [Bug #3523] win32 exception c0000029 on exit using fibers — B Kelly <redmine@...>

Bug #3523: win32 exception c0000029 on exit using fibers

19 messages 2010/07/02

[#31100] [rubysoc] Queue C-extension patch to come — Ricardo Panaggio <panaggio.ricardo@...>

Hello,

26 messages 2010/07/07
[#31148] Re: [rubysoc] Queue C-extension patch to come — Roger Pack <rogerdpack2@...> 2010/07/09

> As this it my first patch to Ruby, I don't know where to begin with.

[#31320] Re: [rubysoc] Queue C-extension patch to come — Ricardo Panaggio <panaggio.ricardo@...> 2010/07/16

Sorry for leaving this thread for so long. I've tried to finish the

[#31322] Re: [rubysoc] Queue C-extension patch to come — Aaron Patterson <aaron@...> 2010/07/16

On Sat, Jul 17, 2010 at 06:55:35AM +0900, Ricardo Panaggio wrote:

[#31324] Re: [rubysoc] Queue C-extension patch to come — Caleb Clausen <vikkous@...> 2010/07/17

NB: I am Ricardo's mentor for this project.

[#31331] Re: [rubysoc] Queue C-extension patch to come — Benoit Daloze <eregontp@...> 2010/07/17

On 17 July 2010 06:00, Caleb Clausen <vikkous@gmail.com> wrote:

[#31332] Re: [rubysoc] Queue C-extension patch to come — Caleb Clausen <vikkous@...> 2010/07/17

On 7/17/10, Benoit Daloze <eregontp@gmail.com> wrote:

[#31138] Why is there no standard way of creating a String from a char *? — Nikolai Weibull <now@...>

Hi!

14 messages 2010/07/08
[#31146] Re: Why is there no standard way of creating a String from a char *? — Urabe Shyouhei <shyouhei@...> 2010/07/09

(2010/07/09 7:04), Nikolai Weibull wrote:

[#31149] Re: Why is there no standard way of creating a String from a char *? — Nikolai Weibull <now@...> 2010/07/09

On Fri, Jul 9, 2010 at 06:20, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:

[#31150] Re: Why is there no standard way of creating a String from a char *? — Urabe Shyouhei <shyouhei@...> 2010/07/09

(2010/07/09 18:28), Nikolai Weibull wrote:

[#31217] [Bug #3562] regression in respond_to? — Aaron Patterson <redmine@...>

Bug #3562: regression in respond_to?

14 messages 2010/07/12

[#31269] [Bug #3566] memory leak when spawning+joining Threads in a loop — Eric Wong <redmine@...>

Bug #3566: memory leak when spawning+joining Threads in a loop

14 messages 2010/07/13

[#31399] [Backport #3595] Theres no encoding to differentiate a stream of Binary data from an 8-Bit ASCII string — Dreamcat Four <redmine@...>

Backport #3595: Theres no encoding to differentiate a stream of Binary data from an 8-Bit ASCII string

17 messages 2010/07/21

[#31459] [Bug #3607] [trunk/r28731] Gem.path has disappeared? — Ollivier Robert <redmine@...>

Bug #3607: [trunk/r28731] Gem.path has disappeared?

22 messages 2010/07/23

[#31519] [Bug #3622] Net::HTTP does not wait to send request body with Expect: 100-continue — Eric Hodel <redmine@...>

Bug #3622: Net::HTTP does not wait to send request body with Expect: 100-continue

9 messages 2010/07/28

[ruby-core:31305] [Bug #3577] Segmentation fault doing simple MySQL queries

From: Jon Rosen <redmine@...>
Date: 2010-07-16 02:19:48 UTC
List: ruby-core #31305
Bug #3577: Segmentation fault doing simple MySQL queries
http://redmine.ruby-lang.org/issues/show/3577

Author: Jon Rosen
Status: Open, Priority: Normal
ruby -v: 1.9.1

I am a relative ruby-newbie (hey that rhymes!) but I am a python expert
so this error REALLY threw me.  I am doing a VERY VERY simply SQL
program that executes two queries in a row:

  require 'mysql'
  db = Mysql.connect('localhost','myname','mypswd','information_schema')
  q1 = db.query ("select * from table_constraints")
  q1.each { |row| puts row.inspect }
  q1.free
  q2 = db.query ("select * from key_column_usage")
  q2.each { |row| puts row.inspect }
  q2.free
  db.close

This SHOULD just print the data from the two schema tables.

When I execute this with EITHER of the sets of three lines for q1 or q2
commented out (i.e., only one query in the program), this works fine.
Each run gives me the correct results from the appropriate query.

When I execute this as above, I get the following:

  C:\ruby>ruby sqlcompare1.rb
  [nil, "qautil", "PRIMARY", "qautil", "qausers", "PRIMARY KEY"]
  [nil, "qautil", "PRIMARY", "qautil", "siteuimap", "PRIMARY KEY"]
  [nil, "qautil", "map_page_field", "qautil", "siteuimap", "UNIQUE"]
  [nil, "qautil", "PRIMARY", "qautil", "testusers", "PRIMARY KEY"]
  sqlcompare1.rb:6: [BUG] Segmentation fault
  ruby 1.9.1p429 (2010-07-02 revision 28523) [i386-mingw32]

  -- control frame ----------
  c:0008 p:---- s:0023 b:0023 l:000022 d:000022 CFUNC  :inspect
  c:0007 p:---- s:0021 b:0021 l:000020 d:000020 CFUNC  :inspect
  c:0006 p:0012 s:0018 b:0017 l:001264 d:000016 BLOCK  sqlcompare1.rb:6
  c:0005 p:---- s:0014 b:0014 l:000013 d:000013 FINISH
  c:0004 p:---- s:0012 b:0012 l:000011 d:000011 CFUNC  :each
  c:0003 p:0065 s:0009 b:0009 l:001264 d:000b58 EVAL   sqlcompare1.rb:6
  c:0002 p:---- s:0004 b:0004 l:000003 d:000003 FINISH
  c:0001 p:0000 s:0002 b:0002 l:001264 d:001264 TOP
  ----------Ruby level backtrace information----------
  sqlcompare1.rb:6:in `inspect'
  sqlcompare1.rb:6:in `inspect'
  sqlcompare1.rb:6:in `block in <main>'
  sqlcompare1.rb:6:in `each'
  sqlcompare1.rb:6:in `<main>'

  [NOTE]
  You may encounter a bug of Ruby interpreter. Bug reports are welcome.
  For details: http://www.ruby-lang.org/bugreport.html

  This application has requested the Runtime to terminate it in an unusual way.
  Please contact the application's support team for more information.

  C:\ruby>

Needless to say, this looks REALLY nasty and doesn't instill a lot of
confidence in me about the stability of the MySQL/Ruby code.  I am
running Ruby 1.9.1 and MySQL 2.8.1 which are the latest and greatest as
far as I know.

Just for the record, the following python version of the same code:

  import MySQLdb
  db = MySQLdb.connect('localhost','myname','mypswd','information_schema')
  q = db.cursor()
  q.execute("select * from table_constraints")
  for row in q.fetchall():
    print row
  q.execute("select * from key_column_usage")
  for row in q.fetchall():
    print row

WORKS PERFECTLY! :-)

I can't even imagine that with something this simple blowing up that
there are thousands of Ruby/MySQL applications out there running on
websites flawlessly.  There must be REALLY something weird going on
here.

Thanks,

Jon "bleurose" Rosen


----------------------------------------
http://redmine.ruby-lang.org

In This Thread

Prev Next