On 01/04/2013 17:50, Dan Williams
wrote:
I updated it a few days ago... I don't remember precisely which day. So I re-updated the package about an hour ago from Marius Kotsbak repositories (I'm testing on Ubuntu 12.10).Any idea what exact date your ModemManager checkout/package is from? The line numbers in the gdb crash indicate a very recent checkout from git (or recent package) but they don't line up with any actual source lines... Tried, but it gives meIf you wouldn't mind triggering the crash one more time, when you have ModemManager stopped in gdb, can you run this command at the (gdb) prompt: list and we'll see what line it detected the issue at. (gdb) list 95 main.c: File o directory non esistente. [missing file or directory] (gdb) list 95 in main.c (gdb) and nothing else. I've attached the logs of both gdb and valgrind, using MM from updated package (see above). I've ran valgrind with leak-check=full.Also, if you have some time and the ability to run valgrind on the system, could you run ModemManager under valgrind like so? mv /usr/sbin/ModemManager / killall -TERM ModemManager G_SLICE=always-malloc valgrind /ModemManager --debug and grab the resulting log output to see if valgrind can detect where the problem is coming from? Let me know if you have any questions. Thanks! Dan Thank you very much |
Attachment:
MM-logs_20130402.zip
Description: Zip compressed data