Re: EurekaLog 5.0.3 (Catch every Exception showing Line#)
- From: "Danijel Tkalcec \(RealThinClient\)" <dtkalcec@xxxxxxxxxxx>
- Date: Wed, 21 Sep 2005 10:11:11 +0200
Hi,
I have read the information on your web site and it looks like this is an
excellent tool for any developer, but I still have a few questions ...
1.) Are there any DLLs which have to be deployed with the application (like
it's the case with FastMM4) to get detailed debug information, or is
everything compiled into the exe file?
2.) How much does the basic EurekaLog code increase the exe file size?
3.) To get unit name and line number information, do applications have to
be compiled with TD-32 debug info or some other option which would radicaly
increase the exe file size (for example, RTC AppClient demo without TD-32
info compiles to 600KB and with TD-32 info to more than 4MB).
4.) Maybe this is a stupid question, but it was not clear from your
announcement :o)
Can EurekaLog also be used to debug DLLs (for example, ISAPI extensions for
a web server)?
Thank you!
--
Danijel Tkalcec
RealThinClient components
http://www.realthinclient.com
news://news.realthinclient.com
.
- Follow-Ups:
- Re: EurekaLog 5.0.3 (Catch every Exception showing Line#)
- From: Fabio Dell'Aria
- Re: EurekaLog 5.0.3 (Catch every Exception showing Line#)
- References:
- ANN: EurekaLog 5.0.3 (Catch every Exception showing Line#)
- From: EurekaLog Team
- ANN: EurekaLog 5.0.3 (Catch every Exception showing Line#)
- Prev by Date: Network Drawing Component Required
- Next by Date: ANN: AJC Active Backup v1.2.3
- Previous by thread: Re: EurekaLog 5.0.3 (Catch every Exception showing Line#)
- Next by thread: Re: EurekaLog 5.0.3 (Catch every Exception showing Line#)
- Index(es):
Relevant Pages
|
