After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 596928 - auto generated RBSource search wrapper, doesn't handle NULL cur_text
auto generated RBSource search wrapper, doesn't handle NULL cur_text
Status: RESOLVED DUPLICATE of bug 613658
Product: rhythmbox
Classification: Other
Component: Plugins (other)
0.12.x
Other Linux
: Normal critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-09-30 22:35 UTC by ivan
Modified: 2010-03-26 10:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Stacktrace of segfault (3.99 KB, application/octet-stream)
2009-09-30 22:35 UTC, ivan
Details
plugin source (864 bytes, application/x-compressed-tar)
2009-09-30 22:36 UTC, ivan
Details

Description ivan 2009-09-30 22:35:46 UTC
Created attachment 144447 [details]
Stacktrace of segfault

As the description says, I've created a source, and when I open the source, it
crashes because it's trying to turn a NULL into a pystring. More specifically,
cur_text. Either cur_text should be "" initially, the wrapper function should
check it, or PyString should handle null gracefully.

I tried the second option, but the autogenerated stuff didn't like it. Tried to
put 

(define-virtual impl_search
  (of-object "RBSource")
  (return-type "none")
  (parameters
    '("RBSourceSearch*" "search")
    '("const-char*" "cur_text"  (null-ok) (default "\"\""))
    '("const-char*" "new_text")
  )
)
in rb.defs.

Stacktrace attached, along with plugin that caused the problem. You should
comment out the Spytify stuff, because it wont work without a proper username
and password.
Comment 1 ivan 2009-09-30 22:36:46 UTC
Created attachment 144448 [details]
plugin source
Comment 2 Jonathan Matthew 2010-03-26 10:14:05 UTC

*** This bug has been marked as a duplicate of bug 613658 ***