- Original Message -
> From: "zhenyu.ren"
> To: "Mathieu Desnoyers"
> Cc: "lttng-dev"
> Sent: Tuesday, February 25, 2014 1:01:30 AM
> Subject: Re: [lttng-dev] epoll_wait reboot kernel?
>
> >Which gcc version do you use ?
> $g
> -Original Message-
> From: David Goulet [mailto:dgou...@efficios.com]
> Sent: Tuesday, 4 March 2014 1:13 AM
> To: David OShea
> Cc: zhenyu.ren; Mathieu Desnoyers; lttng-dev
> Subject: Re: [lttng-dev] epoll_wait reboot kernel? [or --disable-epoll
> causes lttng-sessio
February 2014 4:32 PM
> > To: Mathieu Desnoyers
> > Cc: lttng-dev
> > Subject: Re: [lttng-dev] epoll_wait reboot kernel?
> >
> > >Which gcc version do you use ?
> > $gcc --version
> > gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-46)
>
> I'm on Cen
Subject: Re: [lttng-dev] epoll_wait reboot kernel?
>
> >Which gcc version do you use ?
> $gcc --version
> gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-46)
I'm on CentOS 6, so my results ought to be relevant, but the above looks like
the default GCC version for EL5, not EL6. I'm u
1st parameter of inline_memcpy(dst,src,len)
47c: e8 00 00 00 00 callq 481
call inline_memcpy(dst,src,len)
In good case, at line 45c, rdx ,which is the 3rd parameter of
inline_memcpy(dst,src,len), comes from %r12 that is len.However,in bad case,at
line 476, rdx comes from
Hi Zhenyu,
Which gcc version do you use ?
(gcc --version)
Thanks,
Mathieu
- Original Message -
> From: "zhenyu.ren"
> To: "lttng-dev" , "zhenyu.ren"
>
> Sent: Monday, February 24, 2014 4:36:36 AM
> Subject: Re: [lttng-dev] epoll_w
Oh,It seems not epoll related . I am using DBG/ERR() as debug way ,but this
print-style method doesn't work as expected,so I mistake for epoll_wait.
It seems gcc problem because if I changed lib_ring_buffer_do_copy as the
following,all work well
#define lib_ring_buffer_do_copy(config, dest, s
Hi,lttng-dev
I am working on rhel6(2.6.32.220) and ust is working very well.But when I
use lttng-modules (after "lttng start"),the kernel reboots immediately without
any message output to console.
It took me some days finding out what results in reboot. I shortcut
__event_probe__##_name(
