Remove this ad

Lead

Nov 28 13 11:04 AM

Tags : :

This has happened twice in as many days. Any ideas?

2013-11-28 03:45:33: amule.cpp(330): aMule shutdown completed.
aMule Version: aMuleD SVN compiled with wxGTK2 v2.8.12 and Boost 1.53 (Debugging) (Snapshot: rev. 10814)

Terminated after throwing an instance of 'CInvalidStateEx'
what(): CRunTimeException::CInvalidStateException: Cannot seek on closed file.
backtrace:
[2] ?? in amuled[0x43bab7]
[3] wxEntry(int&, wchar_t**) in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f29710e7e5f]
[4] ?? in amuled[0x42dae5]
[5] __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6[0x7f297027ede5]
[6] ?? in amuled[0x42d989]

Aborted (core dumped)
Quote    Reply   
Remove this ad
Remove this ad

#3 [url]

Nov 30 13 9:54 AM

Re: odd shutdown

Can you try inserting an aborting instruction before the exception is thrown? Like
[code]
Index: CFile.cpp
===================================================================
--- CFile.cpp (revision 10816)
+++ CFile.cpp (working copy)
@@ -367,6 +367,7 @@

sint64 CFile::doSeek(sint64 offset) const
{
+ if (!IsOpened()) wxFAIL_MSG(wxT("Trying to seek() on closed file."));
MULE_VALIDATE_STATE(IsOpened(), wxT("Cannot seek on closed file."));
MULE_VALIDATE_PARAMS(offset >= 0, wxT("Invalid position, must be positive."));


[/code]
You can use abort() instead of wxFAIL_MSG or anything that causes immediate program failure, so the program stops at the point just before throwing the exception. The main problem with unhandled exceptions is that it's impossible to recover the state in which the exception was thrown... That's why your backtraces didn't show anything.

concordia cum veritate

Quote    Reply   
Add Reply

Quick Reply

bbcode help