From: Marko Saukko <marko.saukko@gmail.com>
To: ofono@ofono.org
Subject: Re: Segmentation fault
Date: Fri, 07 Aug 2009 08:15:35 +0300 [thread overview]
Message-ID: <4A7BB877.8010709@gmail.com> (raw)
In-Reply-To: <200908061703.37562.denkenz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1841 bytes --]
Hi Denis,
Something changed as the segfault is different. With adding and removing
the modem like previously showed it now results to one of the following
segmentation faults.
Program received signal SIGSEGV, Segmentation fault.
0x0000013c in ?? ()
(gdb) where
#0 0x0000013c in ?? ()
#1 0xb7e382b6 in ?? () from /usr/lib/libglib-2.0.so.0
#2 0xb7e37b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#3 0xb7e3b0eb in ?? () from /usr/lib/libglib-2.0.so.0
#4 0xb7e3b5ba in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#5 0x0804d345 in main (argc=3, argv=0xabcdef) at main.c:148
(gdb)
Program received signal SIGSEGV, Segmentation fault.
update_network_operator_list_init (user_data=0x8e67500) at network.c:806
806 if (netreg->flags &
NETWORK_REGISTRATION_FLAG_REQUESTING_OPLIST)
(gdb) where
#0 update_network_operator_list_init (user_data=0x8e67500) at network.c:806
#1 0xb7f172b6 in ?? () from /usr/lib/libglib-2.0.so.0
#2 0xb7f16b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#3 0xb7f1a0eb in ?? () from /usr/lib/libglib-2.0.so.0
#4 0xb7f1a5ba in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#5 0x0804d345 in main (argc=3, argv=0xabcdef) at main.c:148
(gdb)
Here is a small script which can be used to test this. With Nokia E51 it
always segfaults before the 100 is reached. Sometimes it is able to do
sequence multiple times and sometimes only create-destroy-create is enough.
#!/bin/sh
if [ ! $1 ]; then
echo "Usage example: $0 dev:/dev/ttyACM0"
return;
fi
for i in `seq 1 100`; do
dbus-send --print-reply --system --dest=org.ofono /\
org.ofono.at.Manager.Create string:"$1" string:"at"
dbus-send --print-reply --system --dest=org.ofono /\
org.ofono.at.Manager.Destroy objpath:"/modem$i"
done
Regards,
Marko
next prev parent reply other threads:[~2009-08-07 5:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 11:51 Segmentation fault Marko Saukko
2009-08-06 22:03 ` Denis Kenzior
2009-08-07 5:15 ` Marko Saukko [this message]
2009-08-08 1:15 ` Denis Kenzior
-- strict thread matches above, loose matches on Subject: below --
2023-08-21 12:09 Michael John
2023-08-21 12:13 ` James Prestwood
2023-08-21 12:50 ` James Prestwood
2010-02-15 8:32 Marco Sarzi Madidini
2010-02-15 9:09 ` Frantisek Hanzlik
2004-12-20 5:56 segmentation fault ubberalles
2004-12-20 8:50 ` primero
2004-12-20 10:01 ` R. DuFresne
2004-04-06 18:08 Segmentation fault ppclinux
2003-02-24 9:55 Zealous
2003-01-27 17:31 segmentation fault Andrew Langdon-Davies
[not found] <OF5DFD5B6D.7D47A4C9-ON65256B98.0022D8F5@pune.tcs.co.in>
2002-04-16 19:30 ` Segmentation fault Kurt Kehler
[not found] <20020411084352.65e693fe.subscript@free.fr>
2002-04-16 19:30 ` Kurt Kehler
[not found] <1328439575.20020411104849@kgpa.ru>
2002-04-16 19:29 ` Kurt Kehler
2001-12-05 13:52 Segmentation Fault Tom Beer
2000-10-06 8:39 Segmentation fault H.S. Kim
2000-10-06 13:57 ` Wolfgang Denk
2000-08-10 6:52 Li Guangdong
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=4A7BB877.8010709@gmail.com \
--to=marko.saukko@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.