[solved] Crash logs

Found a bug? Report it here.

Moderator: PPS-Leaders

Post Reply
The Jo
General DuGalle
Posts: 121
Joined: Mon Mar 01, 2010 7:43 pm

[solved] Crash logs

Post by The Jo » Sat Jun 26, 2010 6:19 pm

I've just installed a new orxonox branch on Ubuntu 10.04.
It crashed two times when I was trying to open "princessaeryn" and "test_quest". The concerning crash logs should be attached to this message.
------- test_quest crash-log-----------------
=======================================================
= time: Sat Jun 26 20:13:20 2010
=======================================================
Program received signal SIGSEGV, Segmentation fault.
0x00ee44c5 in orxonox::WorldEntity::getWorldPosition (this=0xbf290f8)
at /home/jo/orxonox/trunk/src/orxonox/worldentities/WorldEntity.cc:600
600 return this->node_->_getDerivedPosition();
(gdb)
#0 0x00ee44c5 in orxonox::WorldEntity::getWorldPosition (this=0xbf290f8)
at /home/jo/orxonox/trunk/src/orxonox/worldentities/WorldEntity.cc:600
#1 0x0271429f in orxonox::DistanceMultiTrigger::letTrigger (this=0xae688f8)
at /home/jo/orxonox/trunk/src/modules/objects/triggers/DistanceMultiTrigger.cc:101
#2 0x0274431c in orxonox::MultiTrigger::tick (this=0xae688f8, dt=0.0253749993)
at /home/jo/orxonox/trunk/src/modules/objects/triggers/MultiTrigger.cc:147
#3 0x00d4c33d in orxonox::GSRoot::update (this=0x9ca90d0, time=...)
at /home/jo/orxonox/trunk/src/orxonox/gamestates/GSRoot.cc:112
#4 0x01888694 in orxonox::Game::updateGameStates (this=0x9bdbf78)
at /home/jo/orxonox/trunk/src/libraries/core/Game.cc:260
#5 0x01887ec2 in orxonox::Game::run (this=0x9bdbf78)
at /home/jo/orxonox/trunk/src/libraries/core/Game.cc:192
#6 0x00cb7946 in orxonox::main (strCmdLine=...)
at /home/jo/orxonox/trunk/src/orxonox/Main.cc:93
#7 0x08049717 in main (argc=1, argv=0xbfca1b14)
at /home/jo/orxonox/trunk/src/Orxonox.cc:67
(gdb)
Kill the program being debugged? (y or n) [answered Y; input not from terminal]
(gdb)
---------- princessaeryn crash log----------------------

=======================================================
= time: Sat Jun 26 20:10:35 2010
=======================================================
Program received signal SIGSEGV, Segmentation fault.
0x021ee08a in orxonox::NotificationManager::registerNotification (
this=0x9028e88, notification=0xb76df80)
at /home/jo/orxonox/trunk/src/modules/questsystem/notifications/NotificationManager.cc:98
98 std::set<std::string> set = it->first->getTargetsSet();
(gdb)
#0 0x021ee08a in orxonox::NotificationManager::registerNotification (
this=0x9028e88, notification=0xb76df80)
at /home/jo/orxonox/trunk/src/modules/questsystem/notifications/NotificationManager.cc:98
#1 0x021ea0c3 in orxonox::Notification::send (this=0xb76df80, sender=...)
at /home/jo/orxonox/trunk/src/modules/questsystem/notifications/Notification.cc:104
#2 0x021e5e3f in orxonox::QuestNotification::send (this=0xb76df80)
at /home/jo/orxonox/trunk/src/modules/questsystem/QuestNotification.cc:53
#3 0x021a4988 in orxonox::QuestDescription::notificationHelper (
this=0xb824ba0, item=..., status=...)
at /home/jo/orxonox/trunk/src/modules/questsystem/QuestDescription.cc:125
#4 0x021954ab in orxonox::QuestDescription::sendAddQuestNotification (
this=0xb824ba0)
at /home/jo/orxonox/trunk/src/modules/questsystem/QuestDescription.h:107
#5 0x021952f7 in orxonox::Quest::start (this=0xa84bb98, player=0xb26f0b0)
at /home/jo/orxonox/trunk/src/modules/questsystem/Quest.cc:413
#6 0x02154a9d in orxonox::AddQuest::invoke (this=0xb21e700, player=0xb26f0b0)
at /home/jo/orxonox/trunk/src/modules/questsystem/AddQuest.cc:94
#7 0x021ab4cd in orxonox::QuestEffect::invokeEffects (player=0xb26f0b0,
effects=...)
at /home/jo/orxonox/trunk/src/modules/questsystem/QuestEffect.cc:76
#8 0x021ae31a in orxonox::QuestEffectBeacon::execute (this=0xb1e2cf8, b=true,
trigger=0xa60c9b8)
at /home/jo/orxonox/trunk/src/modules/questsystem/QuestEffectBeacon.cc:151
#9 0x021b65eb in orxonox::FunctorMember12<orxonox::QuestEffectBeacon, bool, bool, orxonox::BaseObject*>::operator() (this=0xb780e88, object=0xb1e2cf8,
param1=..., param2=..., param3=..., param4=..., param5=...)
Fail. Fail again. Fail better.

User avatar
greenman
Baron Vladimir Harkonnen
Posts: 360
Joined: Wed Oct 03, 2007 2:53 pm
Contact:

Re: Crash logs

Post by greenman » Sun Jun 27, 2010 5:52 am

in you logs it seems that you installed the trunk, is that right?

i'm not sure, but these problems could already be fixed in the presentation3 branch which was not yet merged back into trunk. do these crashes also appear in presentation3 ?
There are only 10 types of people in the world: Those who understand binary, and those who don't.

The Jo
General DuGalle
Posts: 121
Joined: Mon Mar 01, 2010 7:43 pm

Re: Crash logs

Post by The Jo » Sun Jun 27, 2010 3:25 pm

greenman wrote:in you logs it seems that you installed the trunk, is that right?
Yes. I assumed that all major changes already had been merged.
greenman wrote: do these crashes also appear in presentation3 ?
Not yet :-)
Fail. Fail again. Fail better.

User avatar
greenman
Baron Vladimir Harkonnen
Posts: 360
Joined: Wed Oct 03, 2007 2:53 pm
Contact:

Re: Crash logs

Post by greenman » Mon Jun 28, 2010 7:24 am

we are still waiting for the cleaning up of the presentation branch to be finished (or even to begin) until we merge everything back. this way we make sure that not too much hacks make it into the trunk ;)
There are only 10 types of people in the world: Those who understand binary, and those who don't.

User avatar
Mozork
Mogthorgar, the mighty
Posts: 134
Joined: Wed Sep 24, 2008 3:27 pm

Re: Crash logs

Post by Mozork » Mon Jun 28, 2010 9:09 pm

Actually I am in the process of cleaning up (at the moment in the pickups module) but since I'm not done yet and at the moment it's a bit of a mess (I had to change some things) I have not committed anything, yet. ;)

@The Jo
I can't say with 100% certainty, but I would expect the problems you are referring to to have been fixed in the presentation3 branch. I remember fixing that issue with the DistanceMultiTrigger and the notifications have undergone some changes as well since they last were in the trunk. But I will check these two levels out as soon as the pickups are cleaned up and working.

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests