From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Memory corruption when submitting a huge number of SMS
Date: Mon, 12 Nov 2012 13:29:10 -0600 [thread overview]
Message-ID: <50A14E06.5020204@gmail.com> (raw)
In-Reply-To: <20121111084408.GA10708@xiaoyu.lan>
[-- Attachment #1: Type: text/plain, Size: 4132 bytes --]
Hi Holger,
> gdb backtrace:
> #0 0xb7e51c02 in dbus_connection_get_dispatch_status ()
> from /lib/i386-linux-gnu/libdbus-1.so.3
> #1 0x08054be6 in watch_func (chan=0x8712e78, cond=0, data=0x8713590) at gdbus/mainloop.c:105
> #2 0xb7f1b6fe in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
> #3 0xb7eda6d3 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
> #4 0xb7edaa70 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
> #5 0xb7edaecb in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
> #6 0x080d378a in main (argc=1, argv=0xbffff764) at src/main.c:247
>
Not a whole lot to go on. Looks like the crash happens in gdbus. Is
the dbus daemon crashing or bumping ofono off the bus by any chance?
>
> valgrind:
> ==10495== Invalid read of size 4
> ==10495== at 0x8054BDB: watch_func (mainloop.c:105)
> ==10495== by 0x410C6FD: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x40CB6D2: g_main_context_dispatch (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x40CBA6F: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x40CBECA: g_main_loop_run (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x4208E45: (below main) (libc-start.c:228)
> ==10495== Address 0x47ba830 is 8 bytes inside a block of size 12 free'd
> ==10495== at 0x402768C: free (vg_replace_malloc.c:446)
> ==10495== by 0x40D177A: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x41A81AC: ??? (in /lib/i386-linux-gnu/libdbus-1.so.3.7.2)
> ==10495== by 0x418AD21: ??? (in /lib/i386-linux-gnu/libdbus-1.so.3.7.2)
> ==10495== by 0x41A6BEC: ??? (in /lib/i386-linux-gnu/libdbus-1.so.3.7.2)
> ==10495== by 0x41A7901: ??? (in /lib/i386-linux-gnu/libdbus-1.so.3.7.2)
> ==10495== by 0x41A6028: ??? (in /lib/i386-linux-gnu/libdbus-1.so.3.7.2)
> ==10495== by 0x418DA0A: ??? (in /lib/i386-linux-gnu/libdbus-1.so.3.7.2)
> ==10495== by 0x410C6FD: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x40CB6D2: g_main_context_dispatch (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x40CBA6F: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x40CBECA: g_main_loop_run (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495==
> ==10495== Invalid read of size 4
> ==10495== at 0x8054BE6: watch_func (mainloop.c:106)
> ==10495== by 0x410C6FD: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x40CB6D2: g_main_context_dispatch (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x40CBA6F: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x40CBECA: g_main_loop_run (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x4208E45: (below main) (libc-start.c:228)
> ==10495== Address 0x47ba830 is 8 bytes inside a block of size 12 free'd
> ==10495== at 0x402768C: free (vg_replace_malloc.c:446)
> ==10495== by 0x40D177A: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x41A81AC: ??? (in /lib/i386-linux-gnu/libdbus-1.so.3.7.2)
> ==10495== by 0x418AD21: ??? (in /lib/i386-linux-gnu/libdbus-1.so.3.7.2)
> ==10495== by 0x41A6BEC: ??? (in /lib/i386-linux-gnu/libdbus-1.so.3.7.2)
> ==10495== by 0x41A7901: ??? (in /lib/i386-linux-gnu/libdbus-1.so.3.7.2)
> ==10495== by 0x41A6028: ??? (in /lib/i386-linux-gnu/libdbus-1.so.3.7.2)
> ==10495== by 0x418DA0A: ??? (in /lib/i386-linux-gnu/libdbus-1.so.3.7.2)
> ==10495== by 0x410C6FD: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x40CB6D2: g_main_context_dispatch (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x40CBA6F: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495== by 0x40CBECA: g_main_loop_run (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4)
> ==10495==
Have you tried making a debug build and seeing if you get slightly
better debug information? Just set CFLAGS to -O0 and --enable-debug
when configuring.
Regards,
-Denis
next prev parent reply other threads:[~2012-11-12 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 8:44 Memory corruption when submitting a huge number of SMS Holger Hans Peter Freyther
2012-11-12 19:29 ` Denis Kenzior [this message]
2012-11-12 23:02 ` Holger Hans Peter Freyther
2012-11-13 0:26 ` Denis Kenzior
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=50A14E06.5020204@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.