Description of problem: just running it as usual Version-Release number of selected component: ltrace-0.7.2-9.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: ltrace -SfttTs 8192 ./ocl crash_function: type_pointer_destroy executable: /usr/bin/ltrace kernel: 3.19.3-100.fc20.x86_64+debug type: CCpp Truncated backtrace: Thread no. 1 (9 frames) #5 type_pointer_destroy at type.c:214 #6 type_destroy at type.c:234 #7 value_set_type at value.c:64 #8 vect_destroy at vect.c:147 #9 val_dict_destroy at value_dict.c:146 #10 callstack_pop at handle_event.c:749 #11 handle_breakpoint at handle_event.c:616 #12 handle_event at handle_event.c:179 #13 ltrace_main at libltrace.c:194
Created attachment 1015051 [details] File: backtrace
Created attachment 1015052 [details] File: cgroup
Created attachment 1015053 [details] File: core_backtrace
Created attachment 1015054 [details] File: dso_list
Created attachment 1015055 [details] File: limits
Created attachment 1015056 [details] File: maps
Created attachment 1015057 [details] File: open_fds
Created attachment 1015058 [details] File: proc_pid_status
That looks like it might be a double free. Do you happen to remember what the error message roughly said, before glibc killed the process? Can you reproduce this? And what is ocl? Do you know if it's a multi-threaded program?
Created attachment 1015114 [details] complete console output Hi Petr, luckily I still have the terminal from yesterday opened, output attached. It may very well be double free indeed. The actual message printed was: *** Error in `ltrace': free(): invalid pointer: 0x000000000062a100 *** ocl is my project using OpenCL. AFAIK it is not multithreaded (I do not believe pocl library runs it's own threads looking at the output). I was actually trying to trace out why is pocl failing, I ended up with updating to new version and it is working now. ltrace is still crashing though. Moreover everytime on the same pointer, I tried just now again. Have a nice one, --nX
I think this might be http://permalink.gmane.org/gmane.comp.debugging.ltrace.devel/691 Let me try to spin a quick update to see if it helps.
Could you please try the following build? http://koji.fedoraproject.org/koji/taskinfo?taskID=9492661 It's something of a blind shot, the address seems to come from an unmapped region, which is unexpected, and possibly indicates a different problem, but worth a try.
Cool, good spot, Petře. That indeed matches and I can confirm koji build works like a charm. Thanks, --nX
Good stuff, thanks for testing. I'll spin an update.
ltrace-0.7.2-10.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/ltrace-0.7.2-10.fc20
Package ltrace-0.7.2-10.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ltrace-0.7.2-10.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-6351/ltrace-0.7.2-10.fc20 then log in and leave karma (feedback).
ltrace-0.7.2-10.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.