D
David Vallner
I was trying to do some remote bugsquashing by SSHing on a Windows computer=
=20
running the Cygwin sshd. It's a clean Cygwin ruby setup, with the minimum=20
required for Rails, and the SQLite3 Driver compiled with gcc 3.4.4 (cygming=
=20
special), which seems to fallback to the DL driver after I hacked api.rb to=
=20
recognize cygwin as a host.
Whatever Rails is doing to connect to the database, it threw a can't open=20
exception or some such. I then tried to recreate that in "irb", and got thi=
s=20
weird beaviour:
(I edited some gruesome gemspec dum spam from the log)
irb(main):001:0> require 'rubygems'
=3D> true
irb(main):002:0> 'require require 'sqlite3'
=3D> false
irb(main):003:0> require 'irb/omp completion'
=3D> true
irb(main):004:0> require 'pp'
=3D> true
irb(main):005:0> pp SQLite3. :
atabase.new ' 'production.sqlitwe =
e3'
#<SQLite3:atabase:0x661fce0
=A0@closed=3Dfalse,
=A0@driver=3D#<SQLite3:river:L:river:0x693f480>,
=A0@gempath_searcher=3D
=A0 #< ... >,
=A0@handle=3D#<DL:trData:0x0x102a2430 ptr=3D0x0x6803430 size=3D0 free=3D0=
x0x0>,
=A0@results_as_hash=3Dfalse,
=A0@statement_factory=3DSQLite3::Statement,
=A0@translator=3Dnil,
=A0@type_translation=3Dfalse>
=3D> nil
irb(main):006:0> quit
I didn't test if this DB handle actually worked. The next ones I created in=
=20
another session looked perfectly normal.
Is this just a really, really weird coinkydink related to my obscure setup=
=20
where some DLLs seem to clash and cause strange interpreter states, or can =
it=20
be considered a proper bug in one of the parties involved?
David Vallner
=20
running the Cygwin sshd. It's a clean Cygwin ruby setup, with the minimum=20
required for Rails, and the SQLite3 Driver compiled with gcc 3.4.4 (cygming=
=20
special), which seems to fallback to the DL driver after I hacked api.rb to=
=20
recognize cygwin as a host.
Whatever Rails is doing to connect to the database, it threw a can't open=20
exception or some such. I then tried to recreate that in "irb", and got thi=
s=20
weird beaviour:
(I edited some gruesome gemspec dum spam from the log)
irb(main):001:0> require 'rubygems'
=3D> true
irb(main):002:0> 'require require 'sqlite3'
=3D> false
irb(main):003:0> require 'irb/omp completion'
=3D> true
irb(main):004:0> require 'pp'
=3D> true
irb(main):005:0> pp SQLite3. :
atabase.new ' 'production.sqlitwe =e3'
#<SQLite3:
atabase:0x661fce0=A0@closed=3Dfalse,
=A0@driver=3D#<SQLite3:
river:L:river:0x693f480>,=A0@gempath_searcher=3D
=A0 #< ... >,
=A0@handle=3D#<DL:
trData:0x0x102a2430 ptr=3D0x0x6803430 size=3D0 free=3D0=x0x0>,
=A0@results_as_hash=3Dfalse,
=A0@statement_factory=3DSQLite3::Statement,
=A0@translator=3Dnil,
=A0@type_translation=3Dfalse>
=3D> nil
irb(main):006:0> quit
I didn't test if this DB handle actually worked. The next ones I created in=
=20
another session looked perfectly normal.
Is this just a really, really weird coinkydink related to my obscure setup=
=20
where some DLLs seem to clash and cause strange interpreter states, or can =
it=20
be considered a proper bug in one of the parties involved?
David Vallner