From: Holger Hans Peter Freyther <holger@freyther.de>
To: ofono@ofono.org
Subject: Re: Memory corruption when submitting a huge number of SMS
Date: Tue, 13 Nov 2012 00:02:43 +0100 [thread overview]
Message-ID: <20121112230243.GN31742@xiaoyu.lan> (raw)
In-Reply-To: <50A14E06.5020204@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
On Mon, Nov 12, 2012 at 01:29:10PM -0600, Denis Kenzior wrote:
> Hi Holger,
>
> 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?
the dbus-daemon is running since the start of my laptop.
>
> 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.
not yet. I might need to travel this week so it might take until Wed or Fri
to test this. Is ofono using multiple threads? this somehow sounds like a mismatch
of first deregister from the glib event loop and then free...
holger
next prev parent reply other threads:[~2012-11-12 23:02 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
2012-11-12 23:02 ` Holger Hans Peter Freyther [this message]
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=20121112230243.GN31742@xiaoyu.lan \
--to=holger@freyther.de \
--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