Reply to Re: Fedora 19 freedink segfaults on load
If you don't have an account, just leave the password field blank.
That shouldn't happen. But you knew that.
Beuc tried to fix all segfaults and other "real" bugs (as opposed to bugs which some dmods abuse as features), and has been very successful. So running dink.exe in wine will likely make it crash sooner.
The first thing I would look at, is if you can run the 32 bit version. If that works, please let us know so we can figure out what the problem is.
No matter what, I would very much appreciate a stack backtrace. For this to be useful, you do need to recompile it with debugging symbols enabled; I hope that isn't too hard. If you have it compiled, use:
(Ok, for some reason it's impossible to write & followed by > here. The ; that's after it mustn't be there.)
You shouldn't see any feedback in the terminal (except the text you're typing yourself). When you're done, path/to/log is the file I want to see. My e-mail is wijnen@debian.org
I'm not sure how bug reporting works in Fedora (as I'm sure you guessed I'm using Debian); they probably want to see it as well.
Thanks for reporting!
Beuc tried to fix all segfaults and other "real" bugs (as opposed to bugs which some dmods abuse as features), and has been very successful. So running dink.exe in wine will likely make it crash sooner.
The first thing I would look at, is if you can run the 32 bit version. If that works, please let us know so we can figure out what the problem is.
No matter what, I would very much appreciate a stack backtrace. For this to be useful, you do need to recompile it with debugging symbols enabled; I hope that isn't too hard. If you have it compiled, use:
gdb path/to/freedink &> path/to/log run -w // make it segfault; then bt full c quit
(Ok, for some reason it's impossible to write & followed by > here. The ; that's after it mustn't be there.)
You shouldn't see any feedback in the terminal (except the text you're typing yourself). When you're done, path/to/log is the file I want to see. My e-mail is wijnen@debian.org
I'm not sure how bug reporting works in Fedora (as I'm sure you guessed I'm using Debian); they probably want to see it as well.
Thanks for reporting!