Board index » cppbuilder » help: NTDLL.DLL causes access violation?

help: NTDLL.DLL causes access violation?


2004-04-20 10:04:08 PM
cppbuilder3
hello ng,
i've a really strange problem and worked on it for several days but did
not find a clue.
an application (using indy, mprapi) i've wrote works fine on windows nt
4 and 2000 server. but trying to run it on the 2003 server nothing
happends - only an hourglass for about 1 second.
so, i decided to debug my code on this maschine and installed cbuilder5.
and everything else i need.
compiling the project file was no problem (including code guard). then i
run it in the cbuilder de{*word*81}. after a few seconds the de{*word*81} stops
and shows an information box " Project ... raised to many consecutive
exceptions: 'access violation at 0x77f5d61b: write of address
0x00000010'." and shows the cpu window. in the call stack window i see
that the address point to the ntdll.dll. as often as i try to continue
i'll get the same message.
then i set a breakpoint into the main form constuctor and in the first
line of WinMain but the program never reaches these lines.
even with activated code guard no corde guard file was created. there
seems to be something wrong before the program reaches my code.
does anyone has a clue?
any information that might help is welcome.
tia
peter
 
 

Re:help: NTDLL.DLL causes access violation?

finally,
i found out what is responsible for the described behaviour.
because the windows 2003 stands physically in a server room i interact
with this machine via windows terminal services console. when starting
my app (on matter if under cppbuilder de{*word*81} or not) it is crashing.
working directly on this machine everything is working well.
it seems that the terminal services console is doing more than only
sending "screen information" (like vnc or pc duo) and the runtime
evironment of cppbuilder has problems with it. maybe.
deactivating "dynamic rtl" (tab linker), "build with runtime packages"
(tab packages), and delay load of mprapi.dll has the effect that the app
is running. but why? why is there a problem with the use of dynamic rtl?
tia for any tip.
peter