Skulltag Archive

Hosted by Dark-Assassin

The default theme was not avalible in the backup, sorry.
View unanswered posts | View active topics It is currently Wed Sep 28, 2022 4:06 pm

Forum rules


Name your topics well! "Help me!" won't attract a person with a solution as well as "DMFlags under Linux server" will.



Reply to topic  [ 37 posts ]  Go to page Previous  1, 2
WADSEEKER 
Author Message

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 26
Reply with quote
Well now I will try to compile myself doomseeker, if that fails, I will clean up all the doomseeker files and install the version from skulltag.com, hope it works...

I will info after I finish doing this weird stuff with the result.

Again thanks for your time and your dedication, others would just dropped out long ago :)


Sun Nov 21, 2010 1:33 pm
Profile
Developer

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 1275
Reply with quote
There might be one more thing you might want to try before reverting to the old doomseeker: set IP2CAutoUpdate to 0 in the ini (doomseeker section).


Sun Nov 21, 2010 1:39 pm
Profile YIM WWW

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 26
Reply with quote
Oh ok, I will try that if after compiling and installing it still not working. Reverting shouldn't be a real pain in the a**, since I have both repositories (.net and .com) on the repository list, just .com disabled. So if I want to revert without touching skulltag, I would need just disable .net repository and uninstall doomseeker. After that, just need to do install doomseeker-skulltag and everything should be ok (just with the old doomseeker version) or I missed anything?

Also trying to do what you said before reverting, the /home/user/.doomseeker/doomseeker.ini and irc.ini are in blank, I should add the IP2CAutoUpdate 0 thing there or I'm looking on the bad place?

Sorry for repeating myself, but thanks in advance ^^


Sun Nov 21, 2010 1:58 pm
Profile
Developer

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 1275
Reply with quote


Sun Nov 21, 2010 2:02 pm
Profile YIM WWW

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 26
Reply with quote
After doing that, a lot of things appeared on the screen, I think maybe it helps to solve this problem so I will post everything what I do, segmented on steps, for faster understanding, since there are lots of things on the console:

First I tried to run the game with that on the .ini, and this is what I got:



After that, I remembered what you said about gdb, so I tried out to run it as you explained to me, and when using run it opened a blank gui windows with the doomseeker logo, it freezed and when I tried using bt command on gdb it said that wasn't allowed to access to that memory block. Knowing that maybe with superuser powers it could access I did the same gdb doomseeker but with sudo, and it worked, here is the full console text and what gdb displayed after using the bt command:



And the full text (hope the post isn't too large already):


That's all, I should have hope on this or I should revert?


Sun Nov 21, 2010 2:18 pm
Profile
Developer

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 1275
Reply with quote
Looks like something is wrong with the ZDaemon plugin. Just delete the libzdaemon.so file from your engines/ directory and it should take care of that.


Sun Nov 21, 2010 2:21 pm
Profile YIM WWW

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 26
Reply with quote
Well now doomseeker isn't on /usr/share so I don't have any idea where it is, I'm searching that file right now... I feel a bit stupid xD

Edit: Nevermind, I found it searching on the console text after trying to execute doomseeker.

Now doomseeker loads perfectly, but after I click on wadseeker, it just closes and say Segmentation error on the console


Sun Nov 21, 2010 2:27 pm
Profile
Developer

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 1275
Reply with quote


Sun Nov 21, 2010 2:41 pm
Profile YIM WWW

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 26
Reply with quote
Sure, I was just going to do it, but first I needed to find the binary, since it isn't on usr/share/doomseeker anymore, here it is (after bt):

(gdb) bt
#0 0xb6af0d9d in QMetaObject::indexOfSlot () from /usr/lib/libQtCore.so.4
#1 0xb6afcedc in QObject::connect () from /usr/lib/libQtCore.so.4
#2 0xb683db42 in Protocol::Protocol () from /usr/lib/libwadseeker.so
#3 0xb68395c2 in Ftp::Ftp () from /usr/lib/libwadseeker.so
#4 0xb684821d in WWW::WWW () from /usr/lib/libwadseeker.so
#5 0xb68484df in WWWSeeker::WWWSeeker () from /usr/lib/libwadseeker.so
#6 0xb6844bb1 in Wadseeker::Wadseeker () from /usr/lib/libwadseeker.so
#7 0x08128e25 in WadSeekerInterface::WadSeekerInterface ()
#8 0x08118aa8 in MainWindow::menuWadSeeker ()
#9 0x080ad2aa in MainWindow::qt_metacall ()
#10 0xb6b00ca8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb6b010e0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb6e1c891 in QAction::triggered () from /usr/lib/libQtGui.so.4
#13 0xb6e1de0f in QAction::activate () from /usr/lib/libQtGui.so.4
#14 0xb729801c in ?? () from /usr/lib/libQtGui.so.4
#15 0xb729e76b in ?? () from /usr/lib/libQtGui.so.4
#16 0xb729f242 in QMenu::mouseReleaseEvent () from /usr/lib/libQtGui.so.4
#17 0xb6e79b43 in QWidget::event () from /usr/lib/libQtGui.so.4
#18 0xb72a1629 in QMenu::event () from /usr/lib/libQtGui.so.4
#19 0xb6e22e9c in QApplicationPrivate::notify_helper ()
from /usr/lib/libQtGui.so.4
#20 0xb6e2bb11 in QApplication::notify () from /usr/lib/libQtGui.so.4
#21 0xb6aeaa3b in QCoreApplication::notifyInternal ()
---Type <return> to continue, or q <return> to quit---
from /usr/lib/libQtCore.so.4
#22 0xb6e2ab7e in QApplicationPrivate::sendMouseEvent ()
from /usr/lib/libQtGui.so.4
#23 0xb6e9ac06 in ?? () from /usr/lib/libQtGui.so.4
#24 0xb6e99ca7 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#25 0xb6ec4c6a in ?? () from /usr/lib/libQtGui.so.4
#26 0xb63feb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0xb64020eb in ?? () from /usr/lib/libglib-2.0.so.0
#28 0xb6402268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0xb6b16438 in QEventDispatcherGlib::processEvents ()
from /usr/lib/libQtCore.so.4
#30 0xb6ec4365 in ?? () from /usr/lib/libQtGui.so.4
#31 0xb6ae906a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#32 0xb6ae94aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#33 0xb6aeb959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#34 0xb6e22d17 in QApplication::exec () from /usr/lib/libQtGui.so.4
#35 0x0816b707 in Main::run ()
#36 0x0816bf1e in main ()

I don't think you need the full text, but I'm nobody to say what you need, so here it is:



Again, I need to say that I needed to use gdb with sudo, since it freezed and I couldn't access to the memory block with normal user access, hope it isn't a problem.


Sun Nov 21, 2010 2:45 pm
Profile
Developer

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 1275
Reply with quote
OK, one last thing (so that the back trace will be a little more useful even though I'm fairly sure it's crashing in the same place as the IP2C update). Could you run cmake with this command: `cmake . -DCMAKE_BUILD_TYPE=Debug` And then running make and sudo make install as before and get a backtrace with GDB?


Sun Nov 21, 2010 2:56 pm
Profile YIM WWW

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 26
Reply with quote
Well, so I need to download svn and all those stuff, or I could do it with the svn I downloaded before?

Edit: I don't have much time left, so I'm actually redownloading and redoing everything, hope it don't takes much time.


Last edited by Xannn on Sun Nov 21, 2010 3:30 pm, edited 1 time in total.



Sun Nov 21, 2010 3:25 pm
Profile
Developer

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 1275
Reply with quote
You can do it with the svn code you downloaded before. Just skip start at the cmake step replacing it with the new command I gave you.


Sun Nov 21, 2010 3:29 pm
Profile YIM WWW

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 26
Reply with quote


Sun Nov 21, 2010 3:51 pm
Profile
Developer

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 1275
Reply with quote
For some reason your libwadseeker.so didn't get debugging symbols, but oh well I guess (I don't think it's worth solving since I'm 95% sure that it's the same location). For now you can go ahead and install the old version of Doomseeker.


Sun Nov 21, 2010 4:05 pm
Profile YIM WWW

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 26
Reply with quote
Uhm I'm not used to this, but maybe this is the 5% thing, I will explain:

I have two libwadseeker.so, one at /usr/lib that has 200 KB aprox. (so it isn't debug) and another on usr/local/lib with 1'8 MB (so it should be the debugger one), so using the logic, maybe renaming it should do the trick (the lighter one of course), after that it didn't work, so I just copyed the one on local to where the lighter libwadseeker was and ROFL, when using gdb and using wadseeker, it WORKED, or at last it looks like it is working, so... well... I don't know what happened.

Maybe, since I don't remember well if I uninstalled aptitude installed one, it got mixed in some way, but not sure...

Edit: Now I have two questions about this thing before going to the bed, and they are:

1. Will affect to my own compiled doomseeker installed version using apt-get remove doomseeker?

And 2. How I would uninstall a manual installed program?, since I suppose that apt-get remove will not work in this case to remove it...

And again, thanks for all your time and hope this don't cause more trouble, and thanks a lot for all your time and effort.

Edit2: Well I checked Synaptic and doomseeker and their plugins are unchecked, so I uninstalled it first, the weird thing is that when using make install it put the wadseeker library on /usr/local/lib, but is using /usr/lib one, since if I rename the one on /usr/lib the program crashes.


Sun Nov 21, 2010 4:23 pm
Profile
Developer

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 1275
Reply with quote


Sun Nov 21, 2010 7:47 pm
Profile YIM WWW

Joined: Wed Dec 31, 1969 6:00 pm
Posts: 26
Reply with quote


Mon Nov 22, 2010 3:07 pm
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 37 posts ]  Go to page Previous  1, 2

Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software.