Access violation in delphi?

This very low address is indicative of an offset to a member field of a nil object reference. Run under the debugger and make sure the debugger is set to break on exceptions. When it does, you should be able to work out which object reference is nil.

Read of address 0000026C This very low address is indicative of an offset to a member field of a nil object reference. Run under the debugger and make sure the debugger is set to break on exceptions. When it does, you should be able to work out which object reference is nil.

Quite possibly the AV happens in VCL code although it will almost certainly be due to an error in your code. If the debugger doesn't break at a very helpful location, enable Debug DCUs in the project options in order to see the VCL source code at the point where the exception is raised. The stack trace you provide suggests that the error is in TApplication.

Set whilst performing a string comparison. The first line of TApplication. Setnt reads: if Fnt Value then I bet the offset to the Fnt of TApplication is $026C and that, somehow, your Application variable is set to nil.

That said, I don't understand why the error would not have been raised earlier at Length(Application. It's quite hard to debug this remotely! Having looked at the layout of TApplication, I think we can rule out Application being nil.

Perhaps Fnt itself has somehow been corrupted, or perhaps even Value. I think it's going to take access to the actual code and a debugging environment to track this down.

I Use " RAD Studio 2009 Version 12.0.3170.16989", My Component is "BitBtn" ,this component is on a child form and the form is created at run-time. – user1073024 Nov 30 at 10:05 Give us the details of the exception with a stack trace and we'll tell you what code we need to help you solve your problem. Tellingus what development environment you use is of no use.

– Russell Troywest Nov 30 at 10:09 Where is Stack trace window? – user1073024 Nov 30 at 10:15 When I enable Debug DCUs in the project options I see this error: "Exception class EIntOverflow with message 'Integer overflow'. Process Plibrary.

Exe (3164)" – user1073024 Nov 30 at 10:35 Are you running under the debugger? If so, do so. When you do so the debugger should break at the failing code.

– David Heffernan Nov 30 at 10:37.

Based on the information provided in the stacktrace: TApplication. Idle: Control := DoMouseIdle; if FShownt and (FMouseControl = nil) then Cancelnt := GetLong // Setnt is called next: TApplication. Setnt: if Fnt Value then // This is the UStrCmp which fails with a Int overflow String + IntOverflow -> non terminating string.So the most probable cause is a string without a terminator.

So where does the string come from... Getnt(Control) searches the control (which is at the places you clicked with the cursor) and its parent for a hint that is not empty. GetLongnt searches the string for a | and if found, uses the part following the | else it uses the complete string. UStrCmp, is a long pieces of assembler code, that calls other pieces of assembler code.

Some of them can raise the EIntegerOverflow error. Advise Use the debugger (with debug dcu's on) to see which string has no terminator (0 character at the end). And if you find it, try to solve it or expand the question if you want some more help from us.

– David Heffernan Nov 30 at 11:45 Yes, UStrCmp() does rely on the strings' embedded length fields and not on null terminators. So it is more likely that either Fnt or Value does not point to a valid String variable to begin with (I am guessing F which would suggest the Application object pointer is nil). – Remy Lebeau - TeamB Nov 30 at 22:31.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.