Hi
Some time ago but now something to add.... (see thread around 4th June
for full details)
A colleague found the cause of my DBG1477 error when it became a problem
for him. It was a declaration of a set which Delphi didn't like:
const
WideDigits = [WideChar('0')..WideChar('9')];
We're not sure what's so offensive about this in conjunction with TD32
debug info, any ideas?
Dave
Walter Prins wrote:
>----- Original Message -----
>From: "Dave Sellers" <[EMAIL PROTECTED]>
>To: <[email protected]>
>Sent: Saturday, June 04, 2005 6:31 PM
>Subject: [list] Re: [delphi-en] TObjectList.Sort issues
>
>
>
>
>>With a simple test program I can use MemChk with no problem - and what a
>>wonderful thing it is!
>>
>>However, with the apparently leaky project I cannot compile with TD32
>>debug info or I get the wretched DBG1477 error - regardless of whether
>>I'm trying to use MemChk or not.
>>
>>I'm using D7. The project does include several 3rd party components
>>(including ActiveX) which are fundamental - if I chopped them all out to
>>try and get MemChk to work there would be nothing meaningful left to test.
>>
>>I did also try to use Memory Sleuth at some point but as I recall it
>>needed an activation key and there was only a dead link to TurboPower to
>>get one..
>>
>>
>
>Hmm, OK. This does actually sound like a bug in Delphi to some extent (I'm
>usually very loathe to call any problem a problem in the compiler since
>99.99% of the time if a program doesn't work or has a problem it's my fault,
>however this is somewhat special in that these types of internal compiler
>type errors are not really "meant to happen" I think.) It might be worth
>posting on the borland newsgroups about this and/or on qc.borland.com. The
>key issue though is that for any meaningful help or fix to be given
>(including on this list) with this type of issue you ideally need to isolate
>what causes the problem and provide a test case/test application that
>demonstrates the problem. This is sometimes very time consuming,
>difficultor impossible. Nevertheless, can you have a look and try and
>establish through a process of elimination which component/aspect of your
>app is causing Delphi to be unhappy and post an as simple as possible
>application that causes delphi to break?
>
>One other thing (in the face of MemProof not being an option in this case)
>I'd try using MemProof as well (j.meier/Bob suggested it as well), it's
>pretty good (though I prefer MemCheck for the most part, as you can no doubt
>tell.) However, MemProof has the advantage of being seperate/independent
>from the IDE/compiler. It's available here:
>http://www.automatedqa.com/downloads/memproof/
>
>Note, IIRC, you need to install the older complete Installation program
>version first, install it, *and* you must then update the exe file with the
>latest exe file (you'll see there's several downloads on that page.)
>
>HTH
>
>Walter
>
>
>
>-----------------------------------------------------
>Home page: http://groups.yahoo.com/group/delphi-en/
>To unsubscribe: [EMAIL PROTECTED]
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
>
-----------------------------------------------------
Home page: http://groups.yahoo.com/group/delphi-en/
To unsubscribe: [EMAIL PROTECTED]
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/delphi-en/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
