Hi,
On 27.06.2017 21:09, Mathieu Desnoyers wrote:
> We would need links to the actual tarballs/build scripts and patches of
> your specific distribution, for the version you use. The ptxdist packages
> on http://www.pengutronix.de/software/ptxdist/ appear to target kernel 3.10,
> but yours seems t
Hi,
On 27.06.2017 16:25, Michael Jeanson wrote:
> I forgot to ask for your kernel .config file.
Attached is the content of /proc/config.gz.
Regards,
Thomas
--
Thomas McGuire | thomas.mcgu...@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-5213
- On Jun 26, 2017, at 5:55 AM, Thomas McGuire thomas.mcgu...@kdab.com wrote:
> Hi Michael,
>
> On 23.06.2017 21:55, Michael Jeanson wrote:
>> I see from the metadata file you provided that your kernel version is
>> 4.9.28-20170428-1, is it built from vanilla kernel sources? If not,
>> could
On 2017-06-26 05:55, Thomas McGuire wrote:
> Hi Michael,
>
> On 23.06.2017 21:55, Michael Jeanson wrote:
>> I see from the metadata file you provided that your kernel version is
>> 4.9.28-20170428-1, is it built from vanilla kernel sources? If not,
>> could you point us to a git repo or source arc
Hi Michael,
On 23.06.2017 21:55, Michael Jeanson wrote:
> I see from the metadata file you provided that your kernel version is
> 4.9.28-20170428-1, is it built from vanilla kernel sources? If not,
> could you point us to a git repo or source archive? It would help a lot
> to figure this out.
The
On 2017-06-23 11:48, Thomas McGuire wrote:
>>> Any idea what can cause the corrupted trace?
>> Based on your babeltrace backtrace, the possible culprits would be the
>> events that have a sequence (variable-sized array):
>>
>> syscalls: select, poll, ppoll, pselect6, epoll_wait, epoll_pwait
>>
>> b
Hi,
On 14.06.2017 18:39, Mathieu Desnoyers wrote:
>> On 14.06.2017 17:12, Mathieu Desnoyers wrote:
>>> Can you provide a copy of the metadata file ? And ideally the data
>>> streams too ? This would give us a better idea of what is happening.
>>>
>>> Do you perform kernel or user-space tracing ? D
- On Jun 14, 2017, at 11:55 AM, Thomas McGuire thomas.mcgu...@kdab.com
wrote:
> Hi,
>
> On 14.06.2017 17:12, Mathieu Desnoyers wrote:
>> Can you provide a copy of the metadata file ? And ideally the data
>> streams too ? This would give us a better idea of what is happening.
>>
>> Do you pe
Hi,
On 14.06.2017 17:12, Mathieu Desnoyers wrote:
> Can you provide a copy of the metadata file ? And ideally the data
> streams too ? This would give us a better idea of what is happening.
>
> Do you perform kernel or user-space tracing ? Do you trace huge
> sequences of bytes within your own tr
- On Jun 14, 2017, at 4:43 AM, Thomas McGuire thomas.mcgu...@kdab.com wrote:
> Hi,
>
> I have a recurring problem of tools like babeltrace and TraceCompass
> exiting because of an allocation failure.
>
> For example running babeltrace on a captured trace leads to babeltrace
> processing some
Hi,
I have a recurring problem of tools like babeltrace and TraceCompass
exiting because of an allocation failure.
For example running babeltrace on a captured trace leads to babeltrace
processing some events, and then exiting with:
GLib-ERROR **: gmem.c:168: failed to allocate 17179869184 byte
11 matches
Mail list logo
