From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: segment fault in latest version
Date: Tue, 04 Aug 2009 15:18:50 -0500 [thread overview]
Message-ID: <200908041518.51284.denkenz@gmail.com> (raw)
In-Reply-To: <B94C62E7C2870743865418621F040C1302055CD775@pdsmsx502.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
Hi
> #0 sim_eons_pnn_is_empty (eons=0x8088ce0) at simutil.c:253
> #1 0x08060dc5 in sim_op_error (modem=0x8088ce0) at sim.c:297
> #2 0x08061758 in sim_op_info_cb (error=0xbfffefcc, length=-1,
> structure=4294967295, record_length=-1, access=0x0, data=0x8088ce0)
> at sim.c:425
> #3 0x0806a4a1 in at_crsm_info_cb (ok=1, result=0xbffff038,
> user_data=0x808a560) at atmodem/sim.c:83
> #4 0x0806fc39 in g_at_chat_finish_command (p=0x8087c30,
> ok=<value optimized out>, final=0x8089dc8 "OK") at gatchat.c:347
> #5 0x080705e7 in g_at_chat_handle_command_response (
> line=<value optimized out>, cmd=<value optimized out>,
> p=<value optimized out>) at gatchat.c:402
> #6 have_line (line=<value optimized out>, cmd=<value optimized out>,
> p=<value optimized out>) at gatchat.c:481
> #7 0x080709d6 in new_bytes (p=<value optimized out>) at gatchat.c:671
> #8 received_data (p=<value optimized out>) at gatchat.c:759
> #9 0x006a641b in ?? () from /lib/libglib-2.0.so.0
> #10 0x0066f1e8 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
> #11 0x006727f8 in ?? () from /lib/libglib-2.0.so.0
> #12 0x00672caf in g_main_loop_run () from /lib/libglib-2.0.so.0
> #13 0x0804c6ad in main (argc=1, argv=0xbffff464) at main.c:148
This should now be fixed in the latest version. Can you please check and
report if this still goes kaboom?
Regards,
-Denis
next prev parent reply other threads:[~2009-08-04 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 3:31 segment fault in latest version Li, Zhigang
2009-08-04 4:31 ` Denis Kenzior
2009-08-04 5:21 ` Li, Zhigang
2009-08-04 20:18 ` Denis Kenzior [this message]
2009-08-05 3:34 ` Li, Zhigang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200908041518.51284.denkenz@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox