| Summary: | net-misc/gwibber-1.2.0_pre340: Segfault | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Norman Rieß <norman> |
| Component: | Current packages | Assignee: | Jesus Rivero (RETIRED) <neurogeek> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | python, SebastianLuther, sergio.rodriguez.inclan |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
strace of gwibber
gwibber backtrace |
||
|
Description
Norman Rieß
2009-10-30 19:10:15 UTC
Please provide a backtrace. See [1] for instructions. [1] http://www.gentoo.org/proj/en/qa/backtraces.xml Created attachment 208788 [details]
strace of gwibber
Using gdb as in your instruction link did not work because gwibber is a python skript and gdb does not recognize the format.
So this is a strace. I hope it will suffice.
Sorry, it wasn't obvious from the strace output where the problem is. However, I can help you out with getting the backtrace, which seems pretty important since this app is managing to cause python interpreter itself to crash. BTW in order to get useful info, you'll probably need to recompile python with debugging turned on (use '-g' in CFLAGS and 'splitdebug' in FEATURES -- link about backtraces has more details). A nice way for running scripts in gdb is the '--args' flag to gdb (which is mentioned in 'gdb --help' message but not in the gdb man page...) gdb --args <interpreter> <full path to script> In your case, that should be: gdb --args python /usr/bin/gwibber Created attachment 210042 [details]
gwibber backtrace
Thank you for the information.
Here is the trace.
I do not know how it is supposed to look like, so let me know what else you need.
This seems to be fixed with the new python-webkit version. |