Re: [PATCH wayland 2/4] wl_array: Set data to null after free

On Sep 19, 2016, at 4:08 AM, Eric Engestrom wrote: > > On Mon, Sep 19, 2016 at 11:59:03AM +0100, Eric Engestrom wrote: >> On Fri, Sep 16, 2016 at 03:37:37PM -0700, Yong Bakos wrote: >>> From: Yong Bakos >>> >>> Explicitly set the data member

Re: [PATCH wayland 2/4] wl_array: Set data to null after free

On Mon, Sep 19, 2016 at 11:59:03AM +0100, Eric Engestrom wrote: > On Fri, Sep 16, 2016 at 03:37:37PM -0700, Yong Bakos wrote: > > From: Yong Bakos > > > > Explicitly set the data member to NULL during wl_array_release, preventing > > the > > dangling pointer but, more

Re: [PATCH wayland 2/4] wl_array: Set data to null after free

On Fri, Sep 16, 2016 at 03:37:37PM -0700, Yong Bakos wrote: > From: Yong Bakos > > Explicitly set the data member to NULL during wl_array_release, preventing the > dangling pointer but, more importantly, making it testable. > > Signed-off-by: Yong Bakos

Re: [PATCH wayland v1 1/1] wayland-scanner.pc.in: prepend pc_sysrootdir

On 15 September 2016 at 23:22, Joe Konno wrote: > From: Joe Konno > > In a cross-compilation environment with packages depending on > wayland-scanner, ensure the path to wayland-scanner is correct. Without > this patch, the path will _not_ point to

Re: [PATCH wayland 0/4] Untangle the symbol export duplication

Hi, I do think this is best discussed in-person later in the week, but one quick note ... On 16 September 2016 at 14:47, Emil Velikov wrote: > On 16 September 2016 at 10:46, Pekka Paalanen wrote: >> The static approach can break only when the