ZTE MF683

Aleksander Morgado aleksander at lanedo.com
Fri Sep 21 00:38:55 PDT 2012


On 09/20/2012 04:49 PM, Shawn J. Goff wrote:
> This should be better:
> 
> Breakpoint 2, qmi_utils_read_guint8_from_buffer (buffer=0xbeff6ae0,
>     buffer_size=0xbeff6ae4, out=0xbeff6ad8 "\030\300\003") at qmi-utils.c:69
> 69      in qmi-utils.c
> (gdb) bt
> #0  qmi_utils_read_guint8_from_buffer (buffer=0xbeff6ae0,
>     buffer_size=0xbeff6ae4, out=0xbeff6ad8 "\030\300\003") at qmi-utils.c:69
> #1  0x4031ebe8 in qmi_message_nas_get_signal_strength_response_parse (
>     message=0x31b30, error=<optimized out>) at qmi-nas.c:7848
> #2  0x4031ef78 in get_signal_strength_ready (device=<optimized out>,
>     res=<optimized out>, simple=0x2e4f0) at qmi-nas.c:44350
> #3  0x403db1d4 in g_simple_async_result_complete ()
>    from /usr/lib/libgio-2.0.so.0
> #4  0x403db220 in ?? () from /usr/lib/libgio-2.0.so.0
> Cannot access memory at address 0x0
> #5  0x403db220 in ?? () from /usr/lib/libgio-2.0.so.0
> Cannot access memory at address 0x0
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
> (gdb) continue
> Continuing.
> **
> ERROR:qmi-utils.c:72:qmi_utils_read_guint8_from_buffer: assertion
> failed: (*buffer_size >= 1)
> [Thread 0x40eb5470 (LWP 466) exited]
> 
> Program received signal SIGABRT, Aborted.
> 0x405b17cc in raise () from /lib/libc.so.6
> (gdb) bt
> #0  0x405b17cc in raise () from /lib/libc.so.6
> #1  0x405b2c54 in abort () from /lib/libc.so.6
> #2  0x405b2c54 in abort () from /lib/libc.so.6
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
> (gdb) continue
> Continuing.
> 
> Program terminated with signal SIGABRT, Aborted.
> The program no longer exists.
> (gdb)

Are you able to compile it with -DMESSAGE_ENABLE_TRACE passed in CFLAGS
during configure? Like:
./configure CFLAGS="-ggdb -O0 -DMESSAGE_ENABLE_TRACE"

And re-run?

It's as if we didn't read the whole message before starting to process
it, but cannot really tell without the full message traces.

BTW, I should make that a --enable-message-traces instead...

-- 
Aleksander


More information about the libqmi-devel mailing list