• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 174
  • Last Modified:

crashed threads

how can I tell if a thread has crashed?

if Im running an additional thread, is there an easy way to tell if the thread has crashed?

for that matter, what actually happens when a thread crashes?  in my App, the other threads seem to carry on and not notice that the thread is dead, except when some task that the thread was supposed to perform doesnt happen.
if this thread crashes, somehow the other threads need to know, and shut themselves down gracefully.

thanks

Ben

0
1750
Asked:
1750
  • 3
  • 2
1 Solution
 
rwilson032697Commented:
Bascially there isn't at least in a passive way. It is equivalent to telling if your application has crashed.

One approach that you can use is to require all threads to periodically update status information in some central location. Failure to do so within a certain length of time implies that the thread may have crashed.

There is no real fool-proof way other than to be very careful how you write the code and use exception handling to catch problems and exit or otherwise deal with them gracefully.

Cheers,

Raymond.

0
 
1750Author Commented:
would putting a try..finally inside the execute method work?  ie:

procedure TMyThread.Execute;
begin
  try
    .
    .
  finally
    if not terminated then IveCrashed:=True;
  end;
end;

or would I need to use try..except?  Ive never quite understood the difference between the two.  




0
 
1750Author Commented:
oops!  if forgot to include:

Brain.Engage;

I do know the difference between try..finally and try..except!

ive tried the try..finally scenario, and it doesnt seem to work.

any ideas?


0
 
rwilson032697Commented:
The try except scenario should work if the crash is hapenning due to an exception. However, it may just be getting into an inifinite loop, or is blocked waiting access to a semaphore or mutex which it is never granted etc..

The actual crash might be happening the the synchronise method in which case it is occurring in the main VCL thread (which might explain whay a try..finally doesn't seem to work...). Though I would have thought this would still generate an exception (which it might but is being caught and ignored...)

Raymond.

0
 
1750Author Commented:
thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now