[Kde-bindings] Segfault (as promised)

[Richard Dale]

On Sunday 03 October 2004 13:29, Han Holl wrote:
> On Sunday 03 October 2004 14:13, Richard Dale wrote:
> > Thanks - another execellent crash! This one is caused by an optimization
> > in the overloaded method resolution matching. If there is only one method
> > found in the Smoke runtime, it assumes that it must be the right one and
> > just takes that. If think it might be better to always do the matching on
> > the arguments passed. Please find a version of qtruby.rb attached without
> > the optmization.
> >
> > -- Richard
>
> The new version of qtruby has it's own problems: I get:
> /usr/lib/ruby/site_ruby/1.8/Qt/qtruby.rb:337:in `initialize': unresolved
> constructor call Qt::Application (ArgumentError)
>         from /usr/lib/ruby/site_ruby/1.8/Qt/qtruby.rb:337:in `call'
>         from /usr/lib/ruby/site_ruby/1.8/Qt/qtruby.rb:337:in
> `try_initialize' from /usr/lib/ruby/site_ruby/1.8/Qt/qtruby.rb:334:in
> `callcc' from /usr/lib/ruby/site_ruby/1.8/Qt/qtruby.rb:334:in
> `try_initialize' from client.rb:14:in `new'
>         from client.rb:14
>
> After restoring the old qtruby all is well again.
Oops, yes you're right. I was testing with a KDE Korundum app because it's 
easier to get a stack trace with the crash handler. I've removed it from the 
release branch. That's highlighted another bug in the overloaded method 
resolution - I'll fix that one now.

-- Richard