[Annouce] Woodchuck: A Network Transmission Manager - Page 3 - maemo.org

petur | # 21 | 2012-01-05, 14:49 | Report

I'd also like a GUI with options to configure. Since I'm never on wifi, woodchuck is kinda useless right now although I like it's features of doing the transmissions when idle, could use minimal battery level and timeframes

neal | # 22 | 2012-01-05, 16:40 | Report

Originally Posted by petur View Post

I'd also like a GUI with options to configure. Since I'm never on wifi, woodchuck is kinda useless right now although I like it's features of doing the transmissions when idle, could use minimal battery level and timeframes

This would indeed be good and would be relatively easy to implement. I've created a bug here: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10438

Unfortunately, I don't have time to create a GUI in the near future. It would be great if someone else volunteered to do this. I'd be more than willing to help.

Thanks,

Neal

llucax | # 23 | 2012-07-18, 07:40 | Report

Hi, I noticed that after installing the package the daemon wasn't running. running it manually gives me just a segfault message. Any ideas? I'm using the latest stable CSSU. Thanks.

neal | # 24 | 2012-07-18, 08:03 | Report

Can you try running it under gdb?

Also, can you please post the output of:

Code:

sqlite3 debug-output.db 'select * from log' | tail -n 20

(You might need to install the sqlite3 package).

Thanks!

llucax | # 25 | 2012-07-21, 14:41 | Report

Originally Posted by neal View Post

Can you try running it under gdb?

Also, can you please post the output of:

Code:

sqlite3 debug-output.db 'select * from log' | tail -n 20

(You might need to install the sqlite3 package).

Thanks!

The file debug-output.db doesn't exist in the cwd where I'm running the program. I don't have gdb installed in the phone. The weird thing is earlier today, I've seen murmeltier running when taking a peek to top, but I forgot to try to run it manually then. Now I don't see it running and I still get the segfault when trying to run it manually.

Any other ideas about what could be going on? Is murmeltier supposed to be running all the time as a daemon?

llucax | # 26 | 2012-07-25, 18:11 | Report

btw, here's the gdb output:

Code:

$ gdb -q murmeltier
(no debugging symbols found)
(gdb) r
Starting program: /usr/bin/murmeltier 
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
0x00014914 in ?? ()
0x00014914 <dbus_message_append_args+35924>:	ldr	lr, [r4, #8]
(gdb) bt
#0  0x00014914 in ?? ()
#1  0x000148e8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)

Not very helpful I guess (and not very good either). I takes a couple of seconds to segfault. Don't know if that infotmation is relevant though.