From: ali.akyurek.ext@siemens.com (Akyurek, Ali (EXT))
Subject: [ltt-dev] lttv-gui segmentation fault
Date: Mon, 12 Jan 2009 10:14:17 +0100 [thread overview]
Message-ID: <1E65288790442545B413D69F2A8D27DE04599E13@ERLD164A.ww004.siemens.net> (raw)
Message-ID: <20090112091417.LgqdjUViucv685cs2Nvm7DJoaiHwE5TOeNv-wD0YSKY@z> (raw)
Hi Mathieu,
Not a big problem, but I've been using all latest versions of Lttng, and Lttv 0.12.4.
I try to add a trace in viewer, using File -> Add Trace.
When i select a non-trace folder and click Ok, i get
"./lttv-gui: line 10 4042 Segmentation fault".
But i remember using previous versions of viewer. When i clicked a non-trace folder, it complained with a message box.
Keep up the good work.
Mit freundlichem Gruss / Best Regards
Ali G?nhan Aky?rek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20090112/9540d468/attachment-0003.htm>
next reply other threads:[~2009-01-12 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 9:14 Akyurek, Ali (EXT) [this message]
2009-01-12 9:14 ` Akyurek, Ali (EXT)
2009-01-12 9:14 ` Akyurek, Ali (EXT)
2009-01-12 16:52 ` Mathieu Desnoyers
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=1E65288790442545B413D69F2A8D27DE04599E13@ERLD164A.ww004.siemens.net \
--to=ali.akyurek.ext@siemens.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