I'm using latrace on Ubuntu 12.04 (Precise). When I run latrace on many programs, including any graphical (e.g. GNOME) program, I see this:
$ latrace gedit
gedit finished - killed by signal 11 $
Running in pipe mode seems to make no difference.
Has anyone seen this before? Is any workaround known?
adam
On Fri, Feb 10, 2012 at 09:47:52AM -0800, Adam Dingle wrote:
I'm using latrace on Ubuntu 12.04 (Precise). When I run latrace on many programs, including any graphical (e.g. GNOME) program, I see this:
$ latrace gedit
gedit finished - killed by signal 11 $
Running in pipe mode seems to make no difference.
Has anyone seen this before? Is any workaround known?
hi, what version did you use? (latrace -V)
I've seen segfaults recently with setjmp/longjmp related functions, in latest latrace, those calls are ommited from processing.
I've also seen segfaults because application use glibc malloc hooks, and multiple threads.. latrace cannot deal with this so far.
So, please try latest git. If it does not help, let us know ;)
thanks, jirka
On 02/13/2012 06:38 AM, Jiri Olsa wrote:
On Fri, Feb 10, 2012 at 09:47:52AM -0800, Adam Dingle wrote:
I'm using latrace on Ubuntu 12.04 (Precise). When I run latrace on many programs, including any graphical (e.g. GNOME) program, I see this:
$ latrace gedit
gedit finished - killed by signal 11 $
Running in pipe mode seems to make no difference.
Has anyone seen this before? Is any workaround known?
hi, what version did you use? (latrace -V)
I've seen segfaults recently with setjmp/longjmp related functions, in latest latrace, those calls are ommited from processing.
I've also seen segfaults because application use glibc malloc hooks, and multiple threads.. latrace cannot deal with this so far.
So, please try latest git. If it does not help, let us know ;)
I just built latrace from git and I get the same behavior. I'm sure that GNOME programs use multiple threads, so perhaps that's the problem.
adam
latrace@lists.fedorahosted.org