BCB5 no line numbers

delphi package - automated exception handling
Post Reply
UForstmann
Posts: 2
Joined: Fri Feb 04, 2005 8:19 am
Contact:

BCB5 no line numbers

Post by UForstmann »

Hello all,

I´m using madExcept with BCB5 and
I still got some problems with the handling.

I don`t get line numbers in the debug report.
Is there something wrong with my
compiler/linker settings? :confused:

UForstmann
madshi
Site Admin
Posts: 10753
Joined: Sun Mar 21, 2004 5:25 pm

Post by madshi »

Try full debug settings. Do you still get no line numbers? Which madExcept version are you using? Can you please post a callstack where you would expect line numbers but don't get any?
UForstmann
Posts: 2
Joined: Fri Feb 04, 2005 8:19 am
Contact:

Post by UForstmann »

Hallo madshi,

I`m using madExcept Version 2.7f. I tryed the full debug settings and the following bugreport shows the result.


*************************************************
date/time : 2005-02-07, 08:22:40, 78ms
computer name : KONSTR_IND_15
user name : Forstmann
operating system : Windows 2000 Service Pack 4 build 2195
system language : German
system up time : 22 minutes 23 seconds
program up time : 2 seconds
processor : Intel(R) Pentium(R) 4 CPU 1.50GHz
physical memory : 677/1023 MB (free/total)
free disk space : (C:) 22,42 GB (D:) 4,37 GB
display mode : 1280x1024, 32 bit
process id : $800
executable : Datei_oeff.exe
exec. date/time : 2005-02-07 08:22
madExcept version : 2.7f
exception class : EAccessViolation
exception message : Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000.

main thread ($a94):
00000000 +000 ???
7789ff69 +009 ntdll.dll KiUserExceptionDispatcher
00468f7c +00c Datei_oeff.exe Stdctrls TButton.CNCommand
0048c009 +111 Datei_oeff.exe Controls TControl.WndProc
0048eaca +1d2 Datei_oeff.exe Controls TWinControl.WndProc
00468dfc +06c Datei_oeff.exe Stdctrls TButtonControl.WndProc
0048be50 +024 Datei_oeff.exe Controls TControl.Perform
0048ebf7 +023 Datei_oeff.exe Controls _16813
0048f0fb +00b Datei_oeff.exe Controls TWinControl.WMCommand
0048c009 +111 Datei_oeff.exe Controls TControl.WndProc
0048eaca +1d2 Datei_oeff.exe Controls TWinControl.WndProc
0048e6cc +02c Datei_oeff.exe Controls TWinControl.MainWndProc
0047adbc +014 Datei_oeff.exe Forms _16460
7789ff54 +010 ntdll.dll KiUserCallbackDispatcher
77e039e0 +03e USER32.dll SendMessageW
77e03d95 +014 USER32.dll CallWindowProcA
0048eba2 +0ca Datei_oeff.exe Controls TWinControl.DefaultHandler
0048c52c +010 Datei_oeff.exe Controls TControl.WMLButtonUp
0048c009 +111 Datei_oeff.exe Controls TControl.WndProc
0048eaca +1d2 Datei_oeff.exe Controls TWinControl.WndProc
00468dfc +06c Datei_oeff.exe Stdctrls TButtonControl.WndProc
0048e6cc +02c Datei_oeff.exe Controls TWinControl.MainWndProc
0047adbc +014 Datei_oeff.exe Forms _16460
77e05f64 +006 USER32.dll DispatchMessageA
004836fb +083 Datei_oeff.exe Forms TApplication.ProcessMessage
0048371a +00a Datei_oeff.exe Forms TApplication.HandleMessage
00483925 +081 Datei_oeff.exe Forms TApplication.Run
00401306 +046 Datei_oeff.exe Datei_oeff.cpp 25 +6 WinMain
004ca100 +14c Datei_oeff.exe __startup

thread $6d8: <priority:1>
7788287e +0b ntdll.dll NtWaitForMultipleObjects
77e9a1ad +e8 KERNEL32.dll WaitForMultipleObjectsEx
77e9a0bd +12 KERNEL32.dll WaitForMultipleObjects
004de377 +27 Datei_oeff.exe madExcept _16716
>> created by main thread ($a94) at:
10006edf +00 SUPERCOM.DLL

thread $450:
77882870 +0b ntdll.dll NtWaitForSingleObject
77e99fe2 +6f KERNEL32.dll WaitForSingleObjectEx
77e7b3d6 +0a KERNEL32.dll WaitForSingleObject
77e85444 +22 KERNEL32.dll GetOverlappedResult
004de377 +27 Datei_oeff.exe madExcept _16716
>> created by main thread ($a94) at:
10006edf +00 SUPERCOM.DLL

modules:
00230000 QLIB32.DLL 1.9.8.20 C:\WINNT\system32
00400000 Datei_oeff.exe D:\Daten\Gerhardi\Prog_Gerhardi
00b20000 QMULTI32.DLL 1.9.8.20 C:\WINNT\system32
010b0000 hcdll2_6.dll C:\Programme\Hardcopy
10000000 SUPERCOM.DLL D:\Daten\Gerhardi\Prog_Gerhardi
71710000 COMCTL32.DLL 5.81.4916.400 C:\WINNT\system32
74f90000 WS2HELP.DLL 5.0.2134.1 C:\WINNT\system32
74fa0000 WS2_32.DLL 5.0.2195.6601 C:\WINNT\system32
74fc0000 WSOCK32.dll 5.0.2195.6603 C:\WINNT\system32
75940000 LZ32.DLL 5.0.2195.6611 C:\WINNT\system32
76b00000 COMDLG32.DLL 5.0.3700.6693 C:\WINNT\system32
772a0000 SHLWAPI.DLL 6.0.2800.1584 C:\WINNT\system32
77540000 WINMM.dll 5.0.2161.1 C:\WINNT\system32
77580000 SHELL32.DLL 5.0.3900.6975 C:\WINNT\system32
777f0000 WINSPOOL.DRV 5.0.2195.6659 C:\WINNT\system32
77810000 VERSION.DLL 5.0.2195.6623 C:\WINNT\system32
77880000 ntdll.dll 5.0.2195.6899 C:\WINNT\system32
779a0000 OLEAUT32.DLL 2.40.4522.0 C:\WINNT\system32
77a40000 OLE32.DLL 5.0.2195.6906 C:\WINNT\system32
77d20000 RPCRT4.DLL 5.0.2195.6904 C:\WINNT\system32
77e00000 USER32.dll 5.0.2195.6897 C:\WINNT\system32
77e70000 KERNEL32.dll 5.0.2195.6946 C:\WINNT\system32
77f40000 GDI32.DLL 5.0.2195.6945 C:\WINNT\system32
78000000 MSVCRT.DLL 6.1.9844.0 C:\WINNT\system32
782f0000 MPR.DLL 5.0.2195.6824 C:\WINNT\system32
79350000 ADVAPI32.DLL 5.0.2195.6876 C:\WINNT\system32
***********************************************************
madshi
Site Admin
Posts: 10753
Joined: Sun Mar 21, 2004 5:25 pm

Post by madshi »

Look, here:

00401306 +046 Datei_oeff.exe Datei_oeff.cpp 25 +6 WinMain

you do have a line number, namely line 25. The exception looks like one of the controls of one of your forms is getting a WM_COMMAND message and crashes as a result of that for unknown reasons. Your own sources don't seem to be involved that much.

If you want to see line numbers for the RTL/VCL sources, too, you have to turn on "Use debug libraries" in the linker settings.
Post Reply