Re: libweston program segfaults on weston_compositor_load_backend

2018-05-04 Thread adlo
On Fri, 2018-05-04 at 10:13 +0300, Pekka Paalanen wrote: > > Is that perhaps the very first call to weston_log()? > > You need to initialize the logging mechanism before anything can call > weston_log(). Yeah, it's awkward, could probably be improved, but > OTOH > one would always want all log me

Re: libweston program segfaults on weston_compositor_load_backend

2018-05-04 Thread Matt Hoosier
On Fri, May 4, 2018 at 8:46 AM, Pekka Paalanen wrote: > On Fri, 4 May 2018 07:55:10 -0500 > Matt Hoosier wrote: > > > On Fri, May 4, 2018 at 2:13 AM, Pekka Paalanen > wrote: > > > > > The crucial call to make is weston_log_set_handler() with non-NULL > > > arguments before any other libweston c

Re: libweston program segfaults on weston_compositor_load_backend

2018-05-04 Thread Pekka Paalanen
On Fri, 4 May 2018 07:55:10 -0500 Matt Hoosier wrote: > On Fri, May 4, 2018 at 2:13 AM, Pekka Paalanen wrote: > > > The crucial call to make is weston_log_set_handler() with non-NULL > > arguments before any other libweston calls. > > > > I wonder if this could be made clearer by adding an a

Re: libweston program segfaults on weston_compositor_load_backend

2018-05-04 Thread Matt Hoosier
On Fri, May 4, 2018 at 2:13 AM, Pekka Paalanen wrote: > On Thu, 03 May 2018 23:38:55 +0100 > adlo wrote: > > > On Thu, 2018-05-03 at 14:12 +0300, Pekka Paalanen wrote: > > > > > > what's the backtrace from gdb for that? > > > > > > > Is this any help? > > > > #0 0x in () > > #1

Re: libweston program segfaults on weston_compositor_load_backend

2018-05-04 Thread Pekka Paalanen
On Thu, 03 May 2018 23:38:55 +0100 adlo wrote: > On Thu, 2018-05-03 at 14:12 +0300, Pekka Paalanen wrote: > > > > what's the backtrace from gdb for that? > > > > Is this any help? > > #0 0x in () > #1 0x7799c88c in weston_log (fmt=fmt@entry=0x779b6a7e > "Loadi

Re: libweston program segfaults on weston_compositor_load_backend

2018-05-03 Thread adlo
On Thu, 2018-05-03 at 14:12 +0300, Pekka Paalanen wrote: > > what's the backtrace from gdb for that? > Is this any help? #0 0x in () #1 0x7799c88c in weston_log (fmt=fmt@entry=0x779b6a7e "Loading module '%s'\n") at libweston/log.c:75 #2 0x779a603c in west

Re: libweston program segfaults on weston_compositor_load_backend

2018-05-03 Thread Pekka Paalanen
On Wed, 02 May 2018 22:19:21 +0100 adlo wrote: > I am trying to write a simple test compositor using libweston, but it > segfaults on weston_compositor_load_backend. Hi, what's the backtrace from gdb for that? Thanks, pq pgpICfTI7YcVf.pgp Description: OpenPGP digital signature _

libweston program segfaults on weston_compositor_load_backend

2018-05-02 Thread adlo
I am trying to write a simple test compositor using libweston, but it segfaults on weston_compositor_load_backend. Here is my code: main.c: #include #include #include #include #include #include #include #include int main (intargc, char **argv) { struct wl_display *