Re: Segmentation fault running lttctl on SH4 target.

"Giuseppe Cavallaro" <[email protected]> Wed, 14 Nov 2007 12:08:33 +0100
Newsgroups gmane.linux.kernel.tracing
Message-ID <[email protected]>
Mathieu,
it was not an LTT issue but a system-wide memory resource problem.
Indeed, using the kernel debugger and reducing, at runtime, the subbuf_size
from 1M to 64K (see gdb log below) I was able to trace the system without
any segmentation fault.

----------------------------------------------------------------------------------------------------------
(gdb)
Continuing.

Breakpoint 6, ltt_relay_create_channel (trace_name=0x87b44010 "trace",
    trace=0x84577200, dir=0x87264098, channel_name=0x842fd414 "cpu",
    ltt_chan=0x84577360, subbuf_size=1048576, n_subbufs=2, overwrite=0)
    at ltt/ltt-relay.c:491
491             if (!tmpname)
(gdb) set subbuf_size=65536
(gdb) c
Continuing.
-----------------------------------------------------------------------------------------------------------

Note that I actually work in an embedded system where some resources are
limited (e.g. memory is 32M).

So I wonder how I can tune that within LTT.
Maybe, do I need to modify the LTT_DEFAULT_SUBBUF_SIZE_HIGH macro?
Is it worth making arch dependent these kind of macros?
Please, let me know.
Please remember that I'm not familiar with the ltt internals.

Ciao
Giuseppe

_______________________________________________
Ltt-dev mailing list
[email protected]
http://listserv.shafik.org/mailman/listinfo/ltt-dev