"Michael Stieler" <michael.stieler@rie.eu> wrote in message
news:478f1d80$1@newsgroups.borland.com...
> we have massive problems debugging one of our products
> depending on Indy 10.
Which build number of Indy 10 are you actually using?
> The program is multi-threaded, and works fine for hours..
> but then the program exits with an access violation and I am
> not able to track it because it never happened in the IDE yet.
Have you tried using third-party tracers yet, such as MadExcept?
> The exception was thrown a few lines later at
>
> IOHandler.Open;
That is not enough to diagnose your problem. Open() does a lot of work
internally. You are going to have to trace further than that.
> Since I can't understand why this could happen in a linear execution,
> I guess it happens because of a multi-threading issue.
Do you have threads accessing the client while Connect() is still running?
Gambit
