Closed LufyCZ closed 7 years ago
rTorrent is not running. This is unrelated to Flood.
Sorry @Lukyczk but you'll need to troubleshoot your rTorrent problems elsewhere. I'm not sure what would cause the segmentation fault.
I think it is related to Flood, as it only happens when I start it. I was already asking on the rtorrent IRC, but no answers there :-/
Hmm okay. Can you post your entire rtorrent.rc
and config.js
please?
@Lukyczk Please post your configs, otherwise I can't debug this.
Configs (Changed to txt)
please don't change the config to .txt, it can't be debugged then...
It doesnt let me upload them in .js
please change your scgi listen ip address to 127.0.0.1 unless you want to get hacked
I am now of the opinion this was most likely caused by user error.
okay well you probably need to install regular expressions on your computer, you can download them from http://www.ultrapico.com/expresso.htm
TETYYS: its a closed network without port forwarding and things, I dont care about that
can you run rtorrent in gdb?
white: Im sorry but I have to let it till tomorrow, have a nice day
Don't listen to this guy, GDB is a dangerous computer virus. I wouldn't recommend google-searching for it.
He's already shown us that he has a knowledge of illegal hacking skills like SCGI, not to be trusted
node.js has its own debugger no need to run flood under GDB
Well, ok, i guess
@Lukyczk You're being trolled pretty hard here...
What version of rtorrent are you running? What version of Node? Does rtorrent run normally before you start Flood? And does it crash immediately after starting Flood?
0.9.6, 7.5.0, yes, yes
can you run rtorrent under gdb?
it's not a virus i promise
Reopening for now
Can you please tell me how to do it ? I googled it but I dont really understand what they are talking about. And node gives me an error when trying to install the node debbuger
gdb $(which rtorrent)
Tells me reading symbols from rtorrent...done. And nothing
write run and press enter
k, got it,
pastebin.com/u095nuYu
write bt and press enter
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
uuuhhh im actually not a debugging expert but now run rtorrent in valgrind
That is ?
first hit on google: http://valgrind.org/
Valgrind is an instrumentation framework for building dynamic analysis tools. There are Valgrind tools that can automatically detect many memory management and threading bugs, and profile your programs in detail. You can also use Valgrind to build new tools.
valgrind is a program like gdb, run with valgrind rtorrent
white: yea sorry I should have done that
pastebin.com/PBnCAPTA
did it crash this time?
also looks like something's going on in line 115 of your config
Ill take a look
Line 115 was blank
something tells me you're doing something very wrong • rtorrent crashes on memcpy, yet valgrind reports no errors (???) • rtorrent complains about errors in config, but line 115 is blank
I edited out the line 115, and heres the new log
pastebin.com/htwKbJgA
where did the valgrind version go?
I didnt copy that
do you know how to copy from terminal?
I just selected it and CTRL+ALT+C
is this the whole valgrind output?
just pipe the whole output: valgrind $(which rtorrent) | nc termbin.com 9999
Where is it goin to save ?
goto to termbin.com to find out
It didnt tell me, ill try it again. Still did nothing....
pastebin.com/hsNTXwmF
I succesfully setup Flood, I got into the web-interface (login screen, and loading screen), but nothing after that. I was getting a /api/stats 500 error, so I disabled rtorrent sock in config.js. It looks like I made a step forward, but rtorrent crashes right after loading Flood. I put alot of time into setting up Flood (maybe 5 hours of time), and I would like to get it to end. Thanks
rtorrent output - http://pastebin.com/t46Khm7m flood output - http://pastebin.com/0NxJr77j