[lttng-dev] lttng view => [error] at line 1269: token "(": syntax error, unexpected LPAREN, expecting SEMICOLON or COMMA

[Philippe Proulx]

On Thu, Dec 3, 2015 at 1:56 AM, John Smith <whalajam at gmail.com> wrote:
> Philippe,
>
> On "3.19.0-30-generic #34~14.04.1-Ubuntu", apt-get won't install anything
> else, is LTTng 2.6 (or 2.7) user space backward compatible with kernel 3.19?

I'm not sure I get this question right. LTTng-modules 2.7 supports kernels
starting from 2.6.36, so 3.19 should be okay.

> I remember a while back trying to build the 2.7 kernel LTTng modules and got
> build errors, required additional packages versions that were not available
> for 3.19 and upgrading to a newer kernel is problematic,

Here are the install steps for Ubuntu: <https://lttng.org/download/#ubuntu>.

Since you're using Ubuntu 14.04, your best bet is using the LTTng latest
stable PPA, which currently installs LTTng 2.7:

    sudo apt-add-repository ppa:lttng/ppa
    sudo apt-get update
    sudo apt-get install lttng-tools
    sudo apt-get install lttng-modules-dkms
    sudo apt-get install liblttng-ust-dev

You might have to remove the three packages first (I'm not a
Debian/Ubuntu user).

Phil

>
> thanks, John
>
>
> On Wed, Dec 2, 2015 at 6:02 PM, Philippe Proulx <eeppeliteloop at gmail.com>
> wrote:
>>
>> Okay,
>>
>> You should know, however, that LTTng 2.4 is not supported anymore. There
>> could be bugs in there not fixed in this version. Any chance you can upgrade
>> to at least LTTng 2.6 (2.7 is better)?
>>
>> Philippe Proulx
>>
>> On Wed, Dec 2, 2015 at 7:31 PM, John Smith <whalajam at gmail.com> wrote:
>>>
>>> Philippe,
>>> it doesn't work:
>>>
>>> babeltrace -o ctf-metadata /home/john.s/lttng-traces/auto-20151202-162100
>>> [error] at line 1147: token "(": syntax error, unexpected LPAREN,
>>> expecting SEMICOLON or COMMA
>>> [error] Error creating AST
>>> [warning] Unable to open trace metadata for path
>>> "/home/john.s/lttng-traces/auto-20151202-162100/ust/uid/0/64-bit".
>>> [warning] [Context] Cannot open_trace of format ctf at path
>>> /home/john.s/lttng-traces/auto-20151202-162100/ust/uid/0/64-bit.
>>> [warning] [Context] cannot open trace
>>> "/home/john.s/lttng-traces/auto-20151202-162100/ust/uid/0/64-bit" from
>>> /home/john.s/lttng-traces/auto-20151202-162100 for reading.
>>> [error] Cannot open any trace for reading.
>>> [error] opening trace "/home/john.s/lttng-traces/auto-20151202-162100"
>>> for reading.
>>>
>>> The logs are populated:
>>>
>>> ls -l  /home/john.s/lttng-traces/auto-20151202-162100/ust/uid/0/64-bit/
>>> total 884
>>> -rw-rw---- 1 john.s john.s   8192 Dec  2 16:21 channel0_0
>>> -rw-rw---- 1 john.s john.s   4096 Dec  2 16:21 channel0_1
>>> ...
>>> -rw-rw---- 1 john.s john.s   4096 Dec  2 16:21 channel0_9
>>> drwxrwx--- 2 john.s john.s 4096 Dec  2 16:21 index
>>> -rw-rw---- 1 john.s john.s   98304 Dec  2 16:21 metadata
>>>
>>> thanks, John
>>>
>>> On Wed, Dec 2, 2015 at 11:30 AM, Philippe Proulx
>>> <eeppeliteloop at gmail.com> wrote:
>>>>
>>>> John,
>>>>
>>>> Can you pastebin the trace's metadata file? Use:
>>>>
>>>>     babeltrace -o ctf-metadata /path/to/trace
>>>>
>>>> to get it.
>>>>
>>>> Thanks,
>>>>
>>>> Philippe Proulx
>>>>
>>>> On Tue, Dec 1, 2015 at 9:19 PM, John Smith <whalajam at gmail.com> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> issued the regular following lttng commands:
>>>>> [
>>>>> lttng create
>>>>> lttng enable-event -u -a
>>>>> lttng start
>>>>> <run-my-app>
>>>>> lttng stop
>>>>> lttng view
>>>>> ]
>>>>>
>>>>> "lttng view" command fails with the following:
>>>>>
>>>>> [error] at line 1269: token "(": syntax error, unexpected LPAREN,
>>>>> expecting SEMICOLON or COMMA
>>>>>
>>>>> Environment info:
>>>>> [
>>>>> $ uname -a
>>>>> Linux slab134 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2
>>>>> 22:09:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>>>>> $ lttng --version
>>>>> lttng (LTTng Trace Control) 2.4.0 - Époque Opaque
>>>>> ]
>>>>>
>>>>> I used also:
>>>>> lttng view -e "babeltrace -n all -v -d"
>>>>>
>>>>> but the output is not revealing any comprehensible details.
>>>>>
>>>>> What mistake could lead to such a disastrous failure?
>>>>>
>>>>> thanks, John
>>>>>
>>>>> _______________________________________________
>>>>> lttng-dev mailing list
>>>>> lttng-dev at lists.lttng.org
>>>>> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>>>>>
>>>>
>>>
>>
>