multithreaded debugging

I am writing a multithreaded program for Windows CE 4.2. I'm using EVC4
(4.00.0714.0). Do you know if are there any problems with debugger? Trying
to debug graphic interface (priority level 251) cause stopping higher
priority threads (priority level 1)
I have 3 threads with different levels of priority in this scenario:
1 - priority 0 (waiting for hardware interrupt)
2 - priority 1 (waiting for SetEvent from thread 1)
3 - priority 251 (graphic interface)

May I know why does, debugging interface thread n.3 and stopping its code
with a break point, cause higher thread n.2 to stop too? In other words I
can see that after leaving interface thread break points the higher priority
thread n.2 exits time outed.
The thread n.1 is not affected by the problem and still stays alive. The 1st
one relay on hw interrupt; the 2nd one waits on events signaled by the 1st
one and stops.
Do you know any problem with SetEvent, WaitForSingleObject, or
WaitForMultipleObject?
Thanks in advance for your help


Eng. Mauro de Gennaro
Chief Electronic Department
Bierrebi S.p.A.
Via Sagittario, 23
40044 Pontecchio Marconi (BO)
ITALY
tel. +39051845868 fax. +390516782011, +390516784794
mdegennaro@xxxxxxxxxxxx
www.bierrebi.com

-----------------------------------------------------------------------------------------------------
This message is confidential and intended solely for the person or
organization to whom it is addressed; it may contain privileged or
confidential information. If you are not the intended recipient, you should
not copy, distribute, use, disclose its contents or take any action in
reliance on it. Please notify us of your reception and delete the original.

Questo messaggio è strettamente confidenziale e destinato esclusivamente
alla persona e/o la società cui è diretto, poiché potrebbe contenere
informazioni riservate e/o confidenziali. Nel caso in cui chi riceve il
messaggio non sia il destinatario designato, chiediamo di non farne copia,
diffondere, usare, divulgare il contenuto del messaggio e/o di non
intraprendere alcuna attività in relazione ad esso. Chiediamo inoltre di
segnalarci l 'errata ricezione e di distruggere l'originale.
-----------------------------------------------------------------------------------------------------



.

Relevant Pages

  • Re: multithreaded debugging
    ... > debug real time applications, ... Sorry but it is the way the application debugger is supposed to operate ... >>to debug graphic interface (priority level 251) cause stopping higher ... >> messaggio non sia il destinatario designato, ...
    (microsoft.public.windowsce.platbuilder)
  • Re: multithreaded debugging
    ... Besides I think this should be a problem for every WCE real time project, ... >to debug graphic interface (priority level 251) cause stopping higher ... strettamente confidenziale e destinato esclusivamente ... > messaggio non sia il destinatario designato, chiediamo di non farne copia, ...
    (microsoft.public.windowsce.platbuilder)
  • Re: multithreaded debugging
    ... >problems with debugger? ... Trying to debug graphic interface (priority level 251) cause stopping higher priority threads ... potrebbe contenere informazioni riservate e/o confidenziali. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Dll Security
    ... i'm using EFS to protect my plain-text dll. ... The first guy who comes along with a debugger will have little to no problem ... You can't even raise your priority ...
    (SecProg)
  • RE: Cannot run VB .Net application
    ... Can you run it under a debugger and get a callstack? ... >Importance: normal ... >Priority: normal ...
    (microsoft.public.dotnet.framework.clr)