Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[wild_oscar]

My amuled is crashing daily. I want to help you out sorting the program, but I don't know how to.

I installed amuled building debs from daily SVN. For every program, I also have a -dbg deb package, but I can't figure out how to work with it.

1) Can I have both amuled and amule-dbg debs installed simultaneously?

2) How can I start amuled's -dbg version so I can then follow http://www.amule.org/wiki/index.php/Backtraces to log backtraces?

[Vollstrecker]

That's what the -dbg debs are for. If you need the debugging symbols, you install them with the -dbg wehich fits to your binary i.e. amule-dbg for amule, and then you can do the backtrace as usual.

[wild_oscar]

That's what the -dbg debs are for. If you need the debugging symbols, you install them with the -dbg wehich fits to your binary i.e. amule-dbg for amule, and then you can do the backtrace as usual.

So I basically just need to install the amuled-dbg in addition to amuled and then follow the wiki guide to run the backtrace?

[Vollstrecker]

Basically yes, It would work like this, but I prefer to install the dbg's of the dependencies, too. In amuled-dbg are only the symbols for amuled. If the error occurs in wx and you don't have wx-dbg installed, you'll get at this point some question-marks which doesn't help much. But at least for a first test amuled-dbg should be enough.

[wild_oscar]

Reading the wiki:

To create a backtrace, open a console and do the following:

$ gdb /where/to/install/aMule/bin/amule
(gdb) run

Now use aMule normally until it crashes. If it crashes do the following:


How can I perform this with my amuled, where I usually run "amuled &" and then exit the remote server shell?

[Vollstrecker]

Don't exit.

Do gdb `which amuled` -> run and wait till it crashes without closing the shell.

[wild_oscar]

Don't exit.

Do gdb `which amuled` -> run and wait till it crashes without closing the shell.

iive advised me on using "screen". I need to exit, as I'm accessing amuled on a remote server and leave it on during the night. It is usually when I check the server in the following morning that I see the process no longer exists.