erwingosepa
asked on
Access Error [Fatal Error] Internal Error: LA30
I'm getting Internal Error: LA30 every time I Run the application in delphi. The exact error is "Access violation at address 07262AF7 in module 'RLINK32.DLL' Read of Address 00000000"
I did remove all DCU files as indicated and rebuils but the same error still. Is their ay to troubleshoot this or bypass this error?
I did remove all DCU files as indicated and rebuils but the same error still. Is their ay to troubleshoot this or bypass this error?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ciuly can provide me with detailed instruction how install the madexcept into delphi to have working to find the error?
well, you download it to your computer, you close delphi (it will ask you to do so if you don't) it will install itself in the IDE.
then you open the faulty project and go in the menu to project->mad except settings.
there you check the "enable madexcept" checkbox
compile and run (preferably outside the IDE)
when the error happens, you will get a dialog with a show bugreport button somewhere click on it. you will gfet another window. first tab, down, last line tels you the exception class and message. next tab has the stacktrace. first thread is the one that causes the problem. among the first lines you can track down the actual unit and line where the call was made.
alternativly you can save the bugreport (tehre should be anotehr button for that) which saves it into a text file and you can upload that text file to like pastebin.com or something and we'll take a look at it (don't post it here because it is really big :) )
then you open the faulty project and go in the menu to project->mad except settings.
there you check the "enable madexcept" checkbox
compile and run (preferably outside the IDE)
when the error happens, you will get a dialog with a show bugreport button somewhere click on it. you will gfet another window. first tab, down, last line tels you the exception class and message. next tab has the stacktrace. first thread is the one that causes the problem. among the first lines you can track down the actual unit and line where the call was made.
alternativly you can save the bugreport (tehre should be anotehr button for that) which saves it into a text file and you can upload that text file to like pastebin.com or something and we'll take a look at it (don't post it here because it is really big :) )
Ciuly, the problem is located INSIDE Delphi. LA30 is an internal error of the Delphi IDE/Linker. The LA error message indicates that it is the linker itself causing problems. Then again, the MadExcept Components can also detect errors in the IDE itself, once you've installed it so it's usage is good advise. :-)
ASKER
I did review the code and the problem was as follows: The last thing I did was load Icon into the application. I did remove it and the application is compiling without problem.
But why did you accept the answer of ciuly if you found the problem yourself? You could have asked for a refund instead.
ASKER
I just look who drive me to the solution.
And I didn't help?
ASKER
how can split points here?
I'm going out for an a couple of hours and when I return everything is a mess :P
erwin: post a message in communicty support asking to reopen the question. then you'll be able to split points via the split points link.
alex: tell you the truth I didn't notice that IA30 thing :)) I just saw the message and my brain suddenly pushed the answer on the stack. I tend to overlook details on apparently easy questions :D
erwin: post a message in communicty support asking to reopen the question. then you'll be able to split points via the split points link.
alex: tell you the truth I didn't notice that IA30 thing :)) I just saw the message and my brain suddenly pushed the answer on the stack. I tend to overlook details on apparently easy questions :D
Lol, ciuly. I already noticed that you were going a bit into the wrong direction so I tried to put you back on a straight path. But Erwin found the solution all by himself so actually I wonder if he should ask for a refund instead. ;-)
Of course, having the points split between the participants just for their participation isn't bad either. :-) It's not that the points are that important to me anyways but it shows future readers which remarks were most helpful in finding the answer.
And Erwin, you can go to community support and ask them to re-open thquestion so you can split the points if you want to, or ask for a refund since you solved the problem yourself. The latter is advisable when your question points are limited at EE. Not everyone here has an unlimited amount.
Of course, having the points split between the participants just for their participation isn't bad either. :-) It's not that the points are that important to me anyways but it shows future readers which remarks were most helpful in finding the answer.
And Erwin, you can go to community support and ask them to re-open thquestion so you can split the points if you want to, or ask for a refund since you solved the problem yourself. The latter is advisable when your question points are limited at EE. Not everyone here has an unlimited amount.
It is reported as fix, though. Have you installed the latest service packs? Which Delphi version anyways?