From: jan.glauber@gmail.com (Jan Glauber)
Subject: [lttng-dev] [PATCH lttng-modules] Fix: Building the event list fails on fragmented memory
Date: Tue, 23 Jun 2015 15:46:39 +0200 [thread overview]
Message-ID: <20150623134638.GA3944@hal> (raw)
In-Reply-To: <1586680029.1815.1434223948187.JavaMail.zimbra@efficios.com>
On Sat, Jun 13, 2015 at 07:32:28PM +0000, Mathieu Desnoyers wrote:
> ----- On Jun 10, 2015, at 9:17 AM, Martin Leisener martin at leisener.de wrote:
>
> > Hi Mathieu,
> >
> > sorry for sending the broken patch, I fell for some "smart" formating of my
> > email client, I cannot utilize it myself the way I send it.
> > Hence I now send the patch again as it was original intended. Sent to myself, I
> > can apply it, so I hope it now works in general as well
> > I examined as recommended diff -urN, it seems the output can be utilized by
> > patch the same way as git diff.
> > Hope it is now received the way I intended.
>
> Hi Martin,
>
> I tried you patch on a x86-64 machine (my laptop), and although taking a
> single kernel trace worked fine, it appears to OOPS when I run
>
> (in lttng-tools)
> cd tests
> ./run.sh root_regression
Hi Mathieu,
can you please share the oops message so I can have a look?
Thanks,
Jan
next prev parent reply other threads:[~2015-06-23 13:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 9:19 Martin Leisener
2015-06-10 7:14 ` Mathieu Desnoyers
2015-06-10 13:17 ` Martin Leisener
2015-06-13 19:32 ` Mathieu Desnoyers
2015-06-15 18:27 ` Martin Leisener
2015-06-15 19:30 ` Mathieu Desnoyers
2015-06-23 13:46 ` Jan Glauber [this message]
2015-06-23 19:46 ` Mathieu Desnoyers
2015-06-23 20:21 ` Mathieu Desnoyers
2015-06-23 21:04 ` Mathieu Desnoyers
2015-06-25 8:08 ` Jan Glauber
2015-06-25 13:00 ` Mathieu Desnoyers
2015-06-25 13:37 ` Mathieu Desnoyers
2015-06-25 13:50 ` Jan Glauber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150623134638.GA3944@hal \
--to=jan.glauber@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox