Let's use something that specializes in that task and does a better job of it
than whatever we'll come up with. Due to how it's implemented the stacktrace
will always show waitpid() as frame 0 now but we can live with that.
gstack prints to stdout but litest_log() uses stderr, so we cannot just
On Tue, 7 Aug 2018 19:05:04 +0530
Harsha M M wrote:
> Signed-off-by: Harsha M M
> ---
> ivi-shell/ivi-shell.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/ivi-shell/ivi-shell.c b/ivi-shell/ivi-shell.c
> index 58f53bc..92e8f17 100644
> --- a/ivi-shell/ivi-shell.c
> +++
> -Original Message-
> From: Pekka Paalanen [mailto:ppaala...@gmail.com]
> Sent: Wednesday, August 08, 2018 3:15 PM
> To: Harsha Manjula Mallikarjun (RBEI/ECF3)
>
> Cc: wayland-devel@lists.freedesktop.org
> Subject: Re: [PATCH weston 3/3] ivi-shell: clean up remaining ivisurface
> during
On Tue, 7 Aug 2018 19:05:02 +0530
Harsha M M wrote:
> During de-init ensure removal of added signals from list. Otherwise
> a dongling pointer is left behind which will affect other plugins.
>
> Signed-off-by: Harsha M M
> ---
> compositor/text-backend.c | 3 +++
>
On Tue, 7 Aug 2018 19:05:01 +0530
Harsha M M wrote:
> valgrind reports several invalid memory access during shutdown of
> weston. In general problem is with components which do not remove
> the signals added using wl_signal_emit, but free their memory.
>
> This patch series fixes invalid memory
This new function allows listeners to remove themselves or any
other listener when called. This version only works if listeners
are properly removed before they are free'd.
wl_signal_emit tries to be safe but it fails: it works fine if a
handler removes its own listener, but not if it removes
