aMule Bug Tracker - aMule
View Issue Details
0001753aMuleMiscpublic2015-07-12 14:342015-11-06 18:21
sirkay2006 
 
lowminoralways
newopen 
linux amd_64 bitlinux debian8
SVN 
2.3.2 
linux debian
0001753: [memcheck] Conditional jump or move depends on uninitialised value in CUInt128::CompareTo
When running aMule on valgrind, the following conditional jump or move depends on uninitialised value(s) is detected:

==6205== Thread 1:
==6205== Conditional jump or move depends on uninitialised value(s)
==6205== at 0x6A137A: Kademlia::CUInt128::CompareTo(Kademlia::CUInt128 const&) const (UInt128.cpp:139)
==6205== by 0x456CB8: Kademlia::CUInt128::operator<(Kademlia::CUInt128 const&) const (UInt128.h:159)
==6205== by 0x503DAF: std::_Rb_tree<Kademlia::CUInt128, std::pair<Kademlia::CUInt128 const, Kademlia::CContact*>, std::_Select1st<std::pair<Kademlia::CUInt128 const, Kademlia::CContact*> >, std::less<Kademlia::CUInt128>, std::allocato
r<std::pair<Kademlia::CUInt128 const, Kademlia::CContact*> > >::_M_lower_bound(std::_Rb_tree_node<std::pair<Kademlia::CUInt128 const, Kademlia::CContact*> > const*, std::_Rb_tree_node<std::pair<Kademlia::CUInt128 const, Kademlia::CContac
t*> > const*, Kademlia::CUInt128 const&) const [clone .isra.106] (stl_tree.h:1277)
==6205== by 0x50AB4C: std::_Rb_tree<Kademlia::CUInt128, std::pair<Kademlia::CUInt128 const, Kademlia::CContact*>, std::_Select1st<std::pair<Kademlia::CUInt128 const, Kademlia::CContact*> >, std::less<Kademlia::CUInt128>, std::allocato
r<std::pair<Kademlia::CUInt128 const, Kademlia::CContact*> > >::find(Kademlia::CUInt128 const&) const (stl_tree.h:1926)
==6205== by 0x50ABCF: std::map<Kademlia::CUInt128, Kademlia::CContact*, std::less<Kademlia::CUInt128>, std::allocator<std::pair<Kademlia::CUInt128 const, Kademlia::CContact*> > >::count(Kademlia::CUInt128 const&) const (stl_map.h:887)
==6205== by 0x509663: Kademlia::CSearch::JumpStart() (Search.cpp:284)
==6205== by 0x69D300: Kademlia::CSearchManager::JumpStart() (SearchManager.cpp:390)
==6205== by 0x4FE644: Kademlia::CKademlia::Process() (Kademlia.cpp:260)
==6205== by 0x443444: CamuleApp::OnCoreTimer(CTimerEvent&) (amule.cpp:1203)
==6205== by 0x655207B: wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) (in /home/ttt/_bin/bin/wxWidgets-2.8.12/lib/libwx_baseu-2.8.so.0.8.0)
==6205== by 0x6552132: wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) (in /home/ttt/_bin/bin/wxWidgets-2.8.12/lib/libwx_baseu-2.8.so.0.8.0)
==6205== by 0x65524CA: wxEvtHandler::ProcessEvent(wxEvent&) (in /home/ttt/_bin/bin/wxWidgets-2.8.12/lib/libwx_baseu-2.8.so.0.8.0)
==6205== by 0x6551FD7: wxEvtHandler::ProcessPendingEvents() (in /home/ttt/_bin/bin/wxWidgets-2.8.12/lib/libwx_baseu-2.8.so.0.8.0)
==6205== by 0x64C9078: wxAppConsole::ProcessPendingEvents() (in /home/ttt/_bin/bin/wxWidgets-2.8.12/lib/libwx_baseu-2.8.so.0.8.0)
==6205== by 0x5E12E1D: wxAppBase::ProcessIdle() (in /home/ttt/_bin/bin/wxWidgets-2.8.12/lib/libwx_gtk2u_core-2.8.so.0.8.0)
==6205== by 0x5D7664F: wxapp_idle_callback (in /home/ttt/_bin/bin/wxWidgets-2.8.12/lib/libwx_gtk2u_core-2.8.so.0.8.0)
==6205== by 0x9241B6C: g_main_context_dispatch (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==6205== by 0x9241F47: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==6205== by 0x9242271: g_main_loop_run (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==6205== by 0x74C2596: gtk_main (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.25)
==6205== by 0x5D8CC89: wxEventLoop::Run() (in /home/ttt/_bin/bin/wxWidgets-2.8.12/lib/libwx_gtk2u_core-2.8.so.0.8.0)
==6205== by 0x5E12BBA: wxAppBase::MainLoop() (in /home/ttt/_bin/bin/wxWidgets-2.8.12/lib/libwx_gtk2u_core-2.8.so.0.8.0)
==6205== by 0x64FAA39: wxEntry(int&, wchar_t**) (in /home/ttt/_bin/bin/wxWidgets-2.8.12/lib/libwx_baseu-2.8.so.0.8.0)
==6205== by 0x42F741: main (amule-gui.cpp:93)
==6205== Uninitialised value was created by a stack allocation
==6205== at 0x51B0B0: Kademlia::CRoutingZone::RandomLookup() const (RoutingZone.cpp:820)

I am sorry, I have no idea about this bug.

Do you have an idea?
No tags attached.
Issue History
2015-07-12 14:34sirkay2006New Issue
2015-10-17 23:17GonoszTopiTarget Version => 2.3.2
2015-11-06 18:21sirkay2006Note Added: 0003668

Notes
(0003668)
sirkay2006   
2015-11-06 18:21   
Problem still occurring with g0023527