Missing NULL checks - qmi-proxy.c

[Aleksander Morgado]

Hey,

> > Hey,
> > the function at 0x77b5717e.
> >>
> >
> > Under gdb, could you print all the contents of the "client" struct?
> > e.g. in context #1.
> >
>
> (gdb) bt
> #0  0x77c94581 in track_implicit_cid (self=0x77958a10, client=0x41c678,
>      message=0x416b60) at qmi-proxy.c:675
> #1  0x77c94e9b in process_message (self=0x77958a10, client=0x41c678,
>      message=0x416b60) at qmi-proxy.c:853
> #2  0x77c94fad in parse_request (self=0x77958a10, client=0x41c678)
>      at qmi-proxy.c:905
> #3  0x77c9513f in connection_readable_cb (warning: GDB can't find the start of
> the function at 0x77b5717e.
> socket=0x419de0, condition=G_IO_IN,
>      client=0x41c678) at qmi-proxy.c:943
> #4  0x77b5717f in ?? ()
> (gdb) print *client
> $3 = {ref_count = 2, proxy = 0x77958a10, connection = 0x779255b0,
>    connection_readable_source = 0x4274c0, buffer = 0x416e80, device = 0x418d00,
>    internal_proxy_open_request = 0x0, qmi_client_info_array = 0x416e60,
>    indication_id = 32, device_removed_id = 33}
> (gdb)

Is that backtrace obtained upon the crash? Looks like
qmi_client_info_array is not NULL in that backtrace

-- 
Aleksander
https://aleksander.es