[Eulero]

Posto qui, anche se non è la sezione delle mod. Magari poi si può spostare (se qualcuno traduce) oppure cancellare

Praticamente la Bastard crasha, e sarà la 7° ,8° volta che mi succede.
Il crash avviene sempre quando sono nella schermata In coda di upload e clicco nuovamente sull'icona a sinistra per ruotare la finestra su Client Conosciuti. Però non succede sempre ma solo in relazione a qualche evento che ancora devo capire.
Ad occhio, ho il sentore che ciò dipende da un misterioso client in coda, per il quale non viene disegnata la barra delle "parti ottenute".
qui lo screen:


e qui i dettagli del client in questione:


Il bello è che se riavvio la BastarD , non appena quel client entra in coda, e clicco sull'icona In coda , crasha sistematicamente.
Ho attivato il crashdumb, posto qui due file presi in crash successivi.
dmp
dmp

[CiccioBastardo]

Grazie.

Controllerò la cosa.
COmunque il fatto che non disagni le parti ottenute è pechè eDonkey non supporta trasmette lo delle parti. NOn è l'unico. E non dovrebbe esere un problema che manda in crash il client.

Comunque, investigherò.. Grazie mille

/edit: purtroppo i dump file sembrano essere completamente vuoti

This post has been edited by CiccioBastardo: 26 September 2008 - 07:13 PM

[Eulero]

uhm...per pura curiosità mi sono scaricato il Debugging tools for windows , ho aperto il dmp però mi esce qualche errore. ho scritto il comando !analyze -v e sono uscite altre informazioni.
non ci capisco niente, però sembra che qualcosa ci sia, anche se non è detto che siano utili. bho

Microsoft ® Windows Debugger Version 6.9.0003.113 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\eMule_0-49b-27_ZZUL_BastarD_1-9-6_20080926-181527.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.		   *
* Use .symfix to have the debugger choose a symbol path.				   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
Windows XP Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: SingleUserTS
Debug session time: Fri Sep 26 18:15:27.000 2008 (GMT+2)
System Uptime: not available
Process Uptime: 0 days 0:06:49.000
.................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(e78.e7c): Access violation - code c0000005 (first/second chance not available)
eax=03b90000 ebx=00172fc8 ecx=00000007 edx=7c91e4f4 esi=00172fa0 edi=00172ff8
eip=7c91e4f4 esp=0012c18c ebp=0012c19c iopl=0		 nv up ei pl zr na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000			 efl=00000246
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll - 
ntdll!KiFastSystemCallRet:
7c91e4f4 c3			  ret
0:000> !analyze -v
*******************************************************************************
*																			 *
*						Exception Analysis								   *
*																			 *
*******************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for comctl32.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for user32.dll - 
***** OS symbols are WRONG. Please fix symbols to do analysis.

*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for kernel32.dll - 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for rpcrt4.dll - 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*																   *
* The Symbol Path can be set by:									*
*   using the _NT_SYMBOL_PATH environment variable.				 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+									*
*********************************************************************
*************************************************************************
***																   ***
***																   ***
***	Your debugger is not using the correct symbols				 ***
***																   ***
***	In order for this command to work properly, your symbol path   ***
***	must point to .pdb files that have full type information.	  ***
***																   ***
***	Certain .pdb files (such as the public OS symbols) do not	  ***
***	contain the required information.  Contact the group that	  ***
***	provided you with these symbols if you need this command to	***
***	work.														  ***
***																   ***
***	Type referenced: kernel32!pNlsUserInfo						 ***
***																   ***
*************************************************************************
*************************************************************************
***																   ***
***																   ***
***	Your debugger is not using the correct symbols				 ***
***																   ***
***	In order for this command to work properly, your symbol path   ***
***	must point to .pdb files that have full type information.	  ***
***																   ***
***	Certain .pdb files (such as the public OS symbols) do not	  ***
***	contain the required information.  Contact the group that	  ***
***	provided you with these symbols if you need this command to	***
***	work.														  ***
***																   ***
***	Type referenced: kernel32!pNlsUserInfo						 ***
***																   ***
*************************************************************************

FAULTING_IP: 
eMule_0_49b_ZZUL_BastarD_1_9_6+28bbc4
0068bbc4 66833800		cmp	 word ptr [eax],0

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0068bbc4 (eMule_0_49b_ZZUL_BastarD_1_9_6+0x0028bbc4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 0000029e
Attempt to read from address 0000029e

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

PROCESS_NAME:  eMule_0.49b_ZZUL_BastarD_1.9.6.exe

FAULTING_MODULE: 7c910000 ntdll

DEBUG_FLR_IMAGE_TIMESTAMP:  48c6d3ae

ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a "0x%08lx" ha fatto riferimento alla memoria a "0x%08lx". La memoria non poteva essere "%s".

READ_ADDRESS:  0000029e 

FAULTING_THREAD:  00000e7c

PRIMARY_PROBLEM_CLASS:  WRONG_SYMBOLS

BUGCHECK_STR:  APPLICATION_FAULT_WRONG_SYMBOLS

IP_ON_STACK: 
+12df74
0012df74 0100			add	 dword ptr [eax],eax

FRAME_ONE_INVALID: 1

LAST_CONTROL_TRANSFER:  from 0012df74 to 0068bbc4

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
0012df68 0012df74 00000000 00000001 000000a5 eMule_0_49b_ZZUL_BastarD_1_9_6+0x28bbc4
0012dfa0 773e7c2d 001a8fe8 00000009 0012e114 0x12df74
0012dfb0 773f18c7 001a8fe8 00000009 0012e17c comctl32!Ordinal384+0x2bd7d
0012e114 7e398734 00010264 0000101d 00000009 comctl32!Ordinal384+0x35a17
0012e140 7e398816 7ffdf000 0012e1a8 7e39885a user32!GetDC+0x6d
0012e1a8 7e3aa013 00000000 773f0c92 00010264 user32!GetDC+0x14f
0012e1d8 7e3aa039 773f0c92 00010264 0000101d user32!IsWindowUnicode+0xa1
0012e1f8 006a60cd 773f0c92 00010264 0000101d user32!CallWindowProcW+0x1b
0012e218 006a6348 0000101d 00000009 00000000 eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a60cd
0012e234 006a82bd 0000101d 00000009 00000007 eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a6348
0012e294 006a834d 00000000 00010264 0000101d eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a82bd
0012e2b4 7e398734 00010264 0000101d 00000009 eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a834d
0012e2e0 7e398816 7ffdf000 0012e348 7e39885a user32!GetDC+0x6d
0012e34c 0067f75f 0012e360 006f0af4 0012e3b8 user32!GetDC+0x14f
0012e380 00407ad3 006f0af4 0012e3b8 031f4500 eMule_0_49b_ZZUL_BastarD_1_9_6+0x27f75f
0012e428 7e39885a 0012e444 026a1c34 033e62c0 eMule_0_49b_ZZUL_BastarD_1_9_6+0x7ad3
0012e494 005f99bc 0012e7d8 00010264 006a7fd3 user32!GetDC+0x193
0012e4a0 006a7fd3 0000002b 00000a46 0012e7d8 eMule_0_49b_ZZUL_BastarD_1_9_6+0x1f99bc
0012e4b8 006a861f 00000000 01aa5748 0012e7d8 eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a7fd3
0012e4f8 006a834d 00000000 00010250 0000004e eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a861f
0012e514 006a858a 0012e5c0 006eb062 ffffffff eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a834d
0012e528 006a89c1 00010264 00000000 01aa5748 eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a858a
0012e5cc 006a6331 0000002b 00000a46 00751af8 eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a89c1
0012e5ec 006a82bd 0000002b 00000a46 0012e7d8 eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a6331
0012e64c 006a834d 00000000 00010250 0000002b eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a82bd
0012e66c 7e398734 00010250 0000002b 00000a46 eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a834d
0012e698 7e398816 006a8319 00010250 0000002b user32!GetDC+0x6d
0012e700 7e3a927b 00000000 006a8319 00010250 user32!GetDC+0x14f
0012e73c 7e3a92e3 004b3c48 014b8928 00000a46 user32!GetParent+0x16c
0012e75c 7740d0b3 00010250 0000002b 00000a46 user32!SendMessageW+0x49
0012eac4 773e7f14 0012eb4c 00000000 0012ece8 comctl32!Ordinal384+0x51203
0012eae4 773edd14 0012eb4c 00010000 001a8fe8 comctl32!Ordinal384+0x2c064
0012ec6c 773eecba 00000012 5d0103a9 0012ece8 comctl32!Ordinal384+0x31e64
0012ed24 773f15ce 001a8fe8 00000000 0012eef0 comctl32!Ordinal384+0x32e0a
0012ee88 7e398734 00010264 0000000f 00000000 comctl32!Ordinal384+0x3571e
0012eeb4 7e398816 773f0c92 00010264 0000000f user32!GetDC+0x6d
0012ef1c 7e3aa013 00000000 773f0c92 00010264 user32!GetDC+0x14f
0012ef4c 7e3aa039 773f0c92 00010264 0000000f user32!IsWindowUnicode+0xa1
0012ef6c 006a60cd 773f0c92 00010264 0000000f user32!CallWindowProcW+0x1b
0012ef8c 006a6348 0000000f 00000000 00000000 eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a60cd
0012efa8 006a82bd 0000000f 00000000 00000000 eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a6348
0012f008 006a834d 00000000 00010264 0000000f eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a82bd
0012f028 7e398734 00010264 0000000f 00000000 eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a834d
0012f054 7e398816 006a8319 00010264 0000000f user32!GetDC+0x6d
0012f0bc 7e3a8ea0 00000000 006a8319 00010264 user32!GetDC+0x14f
0012f110 7e3a8eec 014b4498 0000000f 00000000 user32!DefWindowProcW+0x180
0012f138 7c91e453 0012f148 00000018 014b4498 user32!DefWindowProcW+0x1cc
0012f1a4 7e398a10 00160cb0 00000000 7e3aaeab ntdll!KiUserCallbackDispatcher+0x13
0012f1b4 006a409e 00160cb0 00000000 0012f2ac user32!DispatchMessageW+0xf
0012f1c4 006a75e3 00000004 0012f2ac 0012f224 eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a409e
0012f2ac 00000000 00000000 00000000 00000000 eMule_0_49b_ZZUL_BastarD_1_9_6+0x2a75e3


STACK_COMMAND:  ~0s; .ecxr; kb

FOLLOWUP_IP: 
eMule_0_49b_ZZUL_BastarD_1_9_6+28bbc4
0068bbc4 66833800		cmp	 word ptr [eax],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  eMule_0_49b_ZZUL_BastarD_1_9_6+28bbc4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: eMule_0_49b_ZZUL_BastarD_1_9_6

IMAGE_NAME:  eMule_0.49b_ZZUL_BastarD_1.9.6.exe

BUCKET_ID:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_c0000005_eMule_0.49b_ZZUL_BastarD_1.9.6.exe!base_address

Followup: MachineOwner

This post has been edited by Eulero: 26 September 2008 - 09:16 PM

[CiccioBastardo]

Mancano tutti i riferimenti ai simboli. Ci sono solo le posizioni relative delle locazioni di memoria. Non aiutano molto (no, no, non me lo faccio il reverse engineering the codice macchina per risalire a chi compie quale azione scorretta ).

Vedrò di scoprire dove si annida il problema.

Ciao