Bug 844754
Summary: | [abrt] ruby-1.9.3.194-13.fc17: g_logv: Process /usr/bin/ruby was killed by signal 5 (SIGTRAP) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nick H. <nck.s.hayes> | ||||||||||
Component: | fantasdic | Assignee: | Mamoru TASAKA <mtasaka> | ||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 17 | CC: | bkabrda, jeremy, mmorsi, mtasaka, tagoh, vanmeeuwen+fedora, vondruch | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | x86_64 | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | abrt_hash:bf3cf618e5107d084783f23c98884ca61c90f251 | ||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2012-08-13 02:24:48 UTC | Type: | --- | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Attachments: |
|
Description
Nick H.
2012-07-31 16:09:46 UTC
Created attachment 601544 [details]
File: backtrace
Created attachment 601545 [details]
File: maps
Created attachment 601546 [details]
File: dso_list
Created attachment 601547 [details]
File: build_ids
Although different Ruby version, it might be very well the same error as Bug 799804 Hmm, unfortunately, it runs just fine for me. Could you please try to provide more information to reproduce this bug? Thank you. "ruby's" sigtrap is definitely not a bug of fantasdic. Well, I doubt that it is bug of Ruby as well. I believe it is bug in some gem using binary extension and since fantasdic is build above GTK, it is very probably bug in one of the supporting gems. So fantasidc is probably not buggy itself, but is one layer closer to the issue then Ruby. Actually this snippet of backtrace says something which can bring us closer to the root of the troubles: #2 0x000000397bc6a238 in gdk_x_error (display=<optimized out>, error=<optimized out>) at gdkmain-x11.c:486 buf = "BadValue (integer parameter out of range for operation)\000\000\000\000\000\000\000\000" Digging deeper, I would interpret this callstack: #9 0x00007f45878a3679 in rg_m_flush (self=39448680) at rbgdk.c:311 #10 0x00007f458fab8783 in vm_call_cfunc (me=0x2893760, blockptr=0x0, recv=<optimized out>, num=0, reg_cfp=0x7f4589534bf0, th=0x20d5520) at vm_insnhelper.c:404 #11 vm_call_method (th=th@entry=0x20d5520, cfp=cfp@entry=0x7f4589534bf0, num=0, blockptr=0x0, flag=<optimized out>, id=<optimized out>, me=0x2893760, recv=39448680) at vm_insnhelper.c:534 #12 0x00007f458faae5a8 in vm_exec_core (th=th@entry=0x20d5520, initial=initial@entry=0) at insns.def:1015 #13 0x00007f458fab3c60 in vm_exec (th=th@entry=0x20d5520) at vm.c:1220 #14 0x00007f458fab4cf5 in vm_call0 (th=0x20d5520, recv=49267800, id=<optimized out>, argc=1, argv=0x7f4589435110, me=0x334fad0) at vm_eval.c:66 #15 0x00007f458fa05850 in rb_class_new_instance That is is call to Gdk::flush() in some class initialization. The only place where is this combination used is here: http://git.gnome.org/browse/fantasdic/tree/lib/fantasdic/ui/ipc.rb#n188 However, I am not sure what does it mean ;) I am not GTK expert but the gdk_flush() states "This is rarely needed by applications." which makes me wonder why is it used. Well, I do not know what to say! I reported this on July 31st, but today, I tried launching fantasdic today (August 1st), and it did not crash. O_o. So, unless an update was caried out recently, I have no clue what happened with fantasdic crashing. So here is how I ended up with fantasdic crashing in the first place: 1. I installed fantasdic. 2. I tried launching it (not through the konsole, through the menu) 3. ABRT says that fantasdic has crashed. 4. I send this bug report. If someone could give me a list of the most recent updates in the past few days, that might help. EDIT: Just tried launching fantasdic again, but through the konsole. Here is what I get: $ fantasdic (fantasdic:1776): Gdk-ERROR **: The program 'fantasdic' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 127 error_code 2 request_code 18 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped) At this point, I have no clue what is going on. First try worked succesfully, then second try about 15 minutes later failed. Could someone explain this to me? It seems like fantasdic crashes now when there is another instance running. Still doesn't explain the first time I tried launching it, when no other instances were running. I assume it is still a bug though, since it still crashes nonetheless and generates an error report. Note that the correct behavior is that when one fantasdic instance is already running, the second try of lauching fantasdic should exit immediately (of course with no error) It seems that this should be fixed on fantasdic side. fantasdic-1.0-0.12.beta7.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fantasdic-1.0-0.12.beta7.fc17 Package fantasdic-1.0-0.12.beta7.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fantasdic-1.0-0.12.beta7.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-11407/fantasdic-1.0-0.12.beta7.fc17 then log in and leave karma (feedback). The package "fantasdic-1.0-0.12.beta7.fc17" has fixed this bug. I left feedback on the update's page: https://admin.fedoraproject.org/updates/FEDORA-2012-11407/fantasdic-1.0-0.12.beta7.fc17 fantasdic-1.0-0.12.beta7.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |