Version: Rev: 1097205 Last Changed Date: 2010-03-01 (using KDE 4.4.0) OS: Linux Installed from: Compiled From Sources rbqtapi terminated with segmentation fault. execute rbqtapi. rbqtapi:89: [BUG] Segmentation fault here is my patch to fix this. diff -x .svn -uNrb kdebindings-latest/ruby/qtruby/bin/rbqtapi kdebindings-fix/ruby/qtruby/bin/rbqtapi --- kdebindings-latest/ruby/qtruby/bin/rbqtapi 2010-03-05 11:10:05.000000000 +0900 +++ kdebindings-fix/ruby/qtruby/bin/rbqtapi 2010-03-06 14:04:54.000000000 +0900 @@ -70,7 +70,7 @@ else ARGV.each do |classname| classid = Qt::Internal::find_pclassid(classname) - if !classid.index + if classid.smoke < 0 or !classid.index puts "ERROR: class '#{classname}' not found" exit 1 end @@ -82,7 +82,7 @@ classnames.each do |classname| classid = Qt::Internal::find_pclassid(classname) - if !classid.index + if classid.smoke < 0 or !classid.index next end
I think we should get rid of rbqtapi in favour of smokeapi.
On Sunday 07 March 2010 09:49:04 am ruby.twiddler@gmail.com wrote: > https://bugs.kde.org/show_bug.cgi?id=229787 > > Summary: rbqtapi terminated with segmentation fault. > Product: bindings > Version: unspecified > Platform: Compiled Sources > OS/Version: Linux > Status: UNCONFIRMED > Severity: normal > Priority: NOR > Component: general > AssignedTo: kde-bindings@kde.org > ReportedBy: ruby.twiddler@gmail.com > > > Version: Rev: 1097205 Last Changed Date: 2010-03-01 (using KDE > 4.4.0) OS: Linux > Installed from: Compiled From Sources > > rbqtapi terminated with segmentation fault. > > execute rbqtapi. > rbqtapi:89: [BUG] Segmentation fault > > here is my patch to fix this. > diff -x .svn -uNrb kdebindings-latest/ruby/qtruby/bin/rbqtapi > kdebindings-fix/ruby/qtruby/bin/rbqtapi > --- kdebindings-latest/ruby/qtruby/bin/rbqtapi 2010-03-05 > 11:10:05.000000000 +0900 > +++ kdebindings-fix/ruby/qtruby/bin/rbqtapi 2010-03-06 > 14:04:54.000000000 +0900 > @@ -70,7 +70,7 @@ > else > ARGV.each do |classname| > classid = Qt::Internal::find_pclassid(classname) > - if !classid.index > + if classid.smoke < 0 or !classid.index > puts "ERROR: class '#{classname}' not found" > exit 1 > end > @@ -82,7 +82,7 @@ > > classnames.each do |classname| > classid = Qt::Internal::find_pclassid(classname) > - if !classid.index > + if classid.smoke < 0 or !classid.index > next > end This patch looks wrong to me. If find_pclassid() doesn't find the classname it returns a null module index where both the 'Smoke * smoke' value and the index are zero. 'classid.smoke' should never be less than zero. But the real problem here is the code that is mixing C++ and Ruby code, when really it all should be written in C++. This stuff is all much more complicated and error prone than it need be. -- Richard
On Sunday 07 March 2010 12:50:42 pm Arno Rehn wrote: > https://bugs.kde.org/show_bug.cgi?id=229787 > > > Arno Rehn <kde@arnorehn.de> changed: > > What |Removed |Added > --------------------------------------------------------------------------- > - CC| |kde@arnorehn.de > > > > > --- Comment #1 from Arno Rehn <kde arnorehn de> 2010-03-07 13:50:41 --- > I think we should get rid of rbqtapi in favour of smokeapi. Yes I agree, but at the moment smokeapi only show methods in C++ format, whereas rbqtapi has an option to show them in a Ruby style format. ie it doesn't show 'const char *' or QString, but just String instead. For QtScript, I completely copied smokeapi and called it 'jsmokeapi' for the JSmoke JavaScript version, and only changed the code that displayed the methods in the results. So we need a way to make smokeapi show results in non-C++ languages, either by just hard coding various languages into the current code, or by putting the code into a library that each language binding could use to create its own customized version of smokeapi. -- Richard
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!