Segfault when starting race (SVN

[supertuxkart-sourceforge-migration]

Author: rjaguar3

I'm currently working in gdb on this. (I believe this is r9016). The culprit function appears to be KartModel::scaleKart

Program received signal SIGSEGV, Segmentation fault.
0x08144e0c in KartModel::scaleKart(Vec3 const&) ()
(gdb) backtrace
#0 0x08144e0c in KartModel::scaleKart(Vec3 const&) ()
#1 0x08140a14 in Kart::reset() ()
#2 0x0814279b in Kart::Kart(std::basic_string<char, std::char_traits, std::allocator > const&, Track*, int, bool, btTransform const&, RaceManager::KartType) ()
#3 0x08159487 in World::createKart(std::basic_string<char, std::char_traits, std::allocator > const&, int, int, int) ()
#4 0x0815ac2a in World::init() ()
#5 0x0815c9c7 in WorldWithRank::init() ()
#6 0x081541c4 in LinearWorld::init() ()
#7 0x08181f4a in RaceManager::startNextRace() ()
#8 0x0818264a in RaceManager::startNew() ()
#9 0x0818298b in RaceManager::startSingleRace(std::basic_string<char, std::char_traits, std::allocator >, int) ()
#10 0x0819d440 in TrackInfoDialog::processEvent(std::basic_string<char, std::char_traits, std::allocator > const&) ()
#11 0x080c6667 in GUIEngine::EventHandler::onWidgetActivated(GUIEngine::Widget*, int) ()
#12 0x080c6da9 in GUIEngine::EventHandler::onGUIEvent(irr::SEvent const&) ()
#13 0x080c7027 in GUIEngine::EventHandler::OnEvent(irr::SEvent const&) ()
#14 0x082449a7 in irr::gui::CGUIEnvironment::OnEvent (this=0x8786810,

event=...) at CGUIEnvironment.cpp:393

#15 0x0825e600 in irr::gui::CGUIModalScreen::OnEvent (this=0xe10fc48,

---Type to continue, or q to quit---
event=...) at CGUIModalScreen.cpp:134
#16 0x08278139 in irr::gui::CGUIWindow::OnEvent (this=0xe10f670, event=...)

at CGUIWindow.cpp:217

#17 0x08353590 in irr::gui::CGUIButton::OnEvent (this=0xe111880, event=...)

at CGUIButton.cpp:204

#18 0x082453a2 in irr::gui::CGUIEnvironment::postEventFromUser (

this=0x8786810, event=...) at CGUIEnvironment.cpp:565

#19 0x082410b4 in irr::CIrrDeviceStub::postEventFromUser (this=0x86af6f0,

event=...) at CIrrDeviceStub.cpp:214

#20 0x08235619 in irr::CIrrDeviceLinux::run (this=0x86af6f0)

at CIrrDeviceLinux.cpp:968

#21 0x080a1e26 in IrrDriver::update(float) ()
#22 0x08055c3e in MainLoop::run() ()
#23 0x08053914 in main ()

[supertuxkart-sourceforge-migration]

Author: rjaguar3
The problem appears to happen when I start a single-track race on XR591 with 1 or more AI karts.

[supertuxkart-sourceforge-migration]

Author: hikerstk
It works for me. What platform are you on (I assume Linux?)

Also interestingly you appear to have irrlicht compiled with debug information, but not STK. Could you try to configure with "--enable-debug --disable-optimization" ?

Could you also post the output on the terminal? What kart do you use? Does it always crash with the same kart? Or with any kart?

Do you have any addon karts installed?

Thanks for the report!
Joerg

[supertuxkart-sourceforge-migration]

Author: auria
Probably fixed in r9046.

The reason is probably that the original poster has animations disabled, then 'm_animated_node' is NULL.
Joerg, you will probably need to refactor the code a bit more despite my commit, so that it does something even when animations are disabled

[supertuxkart-sourceforge-migration]

Author: rjaguar3
The "no animations" setting must be it. I had graphics level 3 (animated scenery enabled, weather effects disabled, animated characters '''me only''', anti-aliasing disabled), so that explains why it only crashed when I started a multi-kart race.

r9046 does seem to solve the problem. Thanks!

[supertuxkart-sourceforge-migration]

Author: auria
Thanks for confirming it's fixed :)

However I'm reopening the ticket, because while it no more crashes, you will not get the visual effect if animations are disabled. So I'll reopen this ticket so we remember to fix the visual effect even when animations are off

[supertuxkart-sourceforge-migration]

Author: hikerstk
I fixed the squashing of non-animated karts in r9108.

There might still be one potential issue: since LOD nodes are used I am not sure what happens if the LOD node switches to use a different level (i.e. will the new model also be squashed)? Auria, can you check? Design question: wouldn't it be better if the LOD node would handle an array of meshes (instead of array of nodes)?

[supertuxkart-sourceforge-migration]

Author: auria
It is correct for the LOD node to contain nodes and not meshes, for the simple reason that in the future I will most probably implement the ability to put particle emitters in LOD nodes; or to make a mesh degrade into a billboard at a distance; etc. which would not be possible if the LOD node contained meshes

That being said, I'll try to find a way to test scaling with LOD nodes but I believe it should work fine

[supertuxkart-sourceforge-migration]

Author: auria
I just did a quick test; scaling is all fine with LOD nodes, even when the level of detail changes. So closing this bug :) thanks everyone