ofonod segfaulting in a loop on n4
Bug #1206537 reported by
Steve Langasek
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
touch-preview-images |
Invalid
|
Undecided
|
Unassigned | ||
ofono (Ubuntu) |
Invalid
|
Undecided
|
Tony Espy |
Bug Description
On my n4, ofonod is crashing in a loop (ofono 1.12phablet10). Since this is an unofficial package, I can't submit the crash report to errors.u.c (and it currently wouldn't get retraced here anyway). But I can attach the apport crash file.
Changed in ofono (Ubuntu): | |
assignee: | nobody → Tony Espy (awe) |
Changed in touch-preview-images: | |
status: | New → Incomplete |
Changed in ofono (Ubuntu): | |
status: | New → Incomplete |
To post a comment you must log in.
@Steve
I can't make sense of the crash, which is a segfault caused by a strlen call in libdbus, however the rest of stack trace is corrupted.
Could you try to enable debug logging for onfod and then attach your syslog to the bug?
The other separate debug output that would help would be to stop both ofono and network-manager via upstart, then start ofonod in the foreground ( capturing it's output via script ) like this:
# OFONO_RIL_TRACE=y ofonod -n -P atmodem
and then if it doesn't crash at first, try enabling network-manager again via initctl.