Re: Threads Per Process. Help!

From: Bor-Ming Hsieh (bmhsieh.online_at_microsoft.com)
Date: 08/24/04 

Date: Tue, 24 Aug 2004 17:55:50 GMT

I just discovered that the "WaitForDebugEvent" has a limit of 64
(MAXIMUM_WAIT_OBJECTS) objects, which is also the limit for
"WaitForMultipleObjects". The maximum debuggable threads per-process is
therefore 64 because of this.

Sorry for my previous misleading mail.

    -- Bor-Ming

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright (c) Microsoft Corporation. All rights reserved.

--------------------
| X-Tomcat-ID: 500208735
| References: <et06R3b8DHA.1804@TK2MSFTNGP12.phx.gbl>
<ululA#b8DHA.1632@TK2MSFTNGP12.phx.gbl>
<IuUWb.13233$um1.3576@twister.nyroc.rr.com>
<eRbuGvj8DHA.712@tk2msftngp13.phx.gbl>
<KrBrdGLAEHA.616@cpmsftngxa06.phx.gbl>
<eXQF7$hAEHA.3248@TK2MSFTNGP11.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: bmhsieh.online@microsoft.com (Bor-Ming Hsieh)
| Organization: Microsoft
| Date: Mon, 12 Apr 2004 20:49:34 GMT
| Subject: Re: Threads Per Process. Help!
| X-Tomcat-NG: microsoft.public.windowsce.platbuilder
| Message-ID: <Guyz0#MIEHA.660@cpmsftngxa06.phx.gbl>
| Newsgroups: microsoft.public.windowsce.platbuilder
| Lines: 169
| NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
| Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.windowsce.platbuilder:48579
|
| Please let me know if you get a repro case. It's hard to guess what's
going
| on here.
|
| -- Bor-Ming
|
|
| This posting is provided "AS IS" with no warranties, and confers no
rights.
| You assume all risk for your use. ?2004 Microsoft Corporation. All rights
| reserved.
|
| --------------------
| | From: "George McCollister" <georgem@novatech-llc.com>
| | References: <et06R3b8DHA.1804@TK2MSFTNGP12.phx.gbl>
| <ululA#b8DHA.1632@TK2MSFTNGP12.phx.gbl>
| <IuUWb.13233$um1.3576@twister.nyroc.rr.com>
| <eRbuGvj8DHA.712@tk2msftngp13.phx.gbl>
| <KrBrdGLAEHA.616@cpmsftngxa06.phx.gbl>
| | Subject: Re: Threads Per Process. Help!
| | Date: Thu, 4 Mar 2004 13:36:21 -0600
| | Lines: 152
| | X-Priority: 3
| | X-MSMail-Priority: Normal
| | X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| | Message-ID: <eXQF7$hAEHA.3248@TK2MSFTNGP11.phx.gbl>
| | Newsgroups: microsoft.public.windowsce.platbuilder
| | NNTP-Posting-Host: 64-126-95-172.biztyp1.ksle.everestkc.net
64.126.95.172
| | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
| | Xref: cpmsftngxa06.phx.gbl microsoft.public.windowsce.platbuilder:46687
| | X-Tomcat-NG: microsoft.public.windowsce.platbuilder
| |
| | I'll work on providing something that replicates the problem. Currently
I
| am
| | extremely busy working on various areas of development.
| |
| | Thread creation succeeds! When a thread over 64 starts one of the other
| | threads mysteriously halts. When the new thread ends the other thread
| picks
| | back up again. If I remove some unrelated low priority threads from
| running,
| | the problem never occurs. Initially we are dealing with the problem by
| | attempting to reduce the number of threads in use (this has solved all
| | problems so far). However we are likely going to exceed 64 threads
| sometime
| | in the near future.
| |
| | Since Windows CE does not support asynchronous serial/file I/O we are
some
| | what limited in our ability to reduce our thread counts to a more
| reasonable
| | level. It is typical for our device to be aggressively using 16 serial
| ports
| | simultaneously.
| |
| | Regards,
| | George McCollister
| |
| | "Bor-Ming Hsieh" <bmhsieh.online@microsoft.com> wrote in message
| | news:KrBrdGLAEHA.616@cpmsftngxa06.phx.gbl...
| | > CE kernel does not have any limitation for the number of thread per
| | process
| | > being debugged. The only limitation is virtual memroy available per
| | process.
| | >
| | > Can you describe the problem in more detail? Does the thread gets
| created
| | > or the thread creation fails? Does your debugger get notified for
thread
| | > creation? It'll be much easier to diagnose the problem if you can
| provide
| | a
| | > repro case.
| | >
| | > -- Bor-Ming
| | >
| | >
| | > This posting is provided "AS IS" with no warranties, and confers no
| | rights.
| | > You assume all risk for your use. ?2004 Microsoft Corporation. All
| rights
| | > reserved.
| | >
| | > --------------------
| | > | From: "George McCollister" <georgem@novatech-llc.com>
| | > | References: <et06R3b8DHA.1804@TK2MSFTNGP12.phx.gbl>
| | > <ululA#b8DHA.1632@TK2MSFTNGP12.phx.gbl>
| | > <IuUWb.13233$um1.3576@twister.nyroc.rr.com>
| | > | Subject: Re: Threads Per Process. Help!
| | > | Date: Fri, 13 Feb 2004 08:14:59 -0600
| | > | Lines: 68
| | > | X-Priority: 3
| | > | X-MSMail-Priority: Normal
| | > | X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| | > | Message-ID: <eRbuGvj8DHA.712@tk2msftngp13.phx.gbl>
| | > | Newsgroups: microsoft.public.windowsce.platbuilder
| | > | NNTP-Posting-Host: 64-126-95-172.biztyp1.ksle.everestkc.net
| | 64.126.95.172
| | > | Path:
| | >
| |
|
cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08
| | > phx.gbl!tk2msftngp13.phx.gbl
| | > | Xref: cpmsftngxa07.phx.gbl
| microsoft.public.windowsce.platbuilder:45624
| | > | X-Tomcat-NG: microsoft.public.windowsce.platbuilder
| | > |
| | > | I saw this thread, I was going to reply to it, but its a bit old. In
| | that
| | > | thread Bor-Ming hypothesizes that the limit is due to the eVC
| debugger.
| | > | Since I am not using the eVC debugger, I believe his hypothesis to
be
| | > | incorrect. My debugger is using the Windows CE Debugging API
specified
| | > here:
| | > |
| | > |
| | >
| |
|
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcesdk40/ht
| | > ml/cecondebuggingreference.asp
| | > |
| | > | Today I will verify that my debugger is causing this limitation by
| | running
| | > | my main executable as a normal process.
| | > |
| | > | George
| | > |
| | > |
| | > |
| | > | "Ten" <nick.bartolotti@_re_move_tentechnologies.com> wrote in
message
| | > | news:IuUWb.13233$um1.3576@twister.nyroc.rr.com...
| | > | > There was a similar thread recently about this subject.
| | > | >
| | > | >
| | > |
| | >
| |
|
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=%23IVI4UZjDHA.2328%4
| | > 0TK2MSFTNGP10.phx.gbl
| | > | >
| | > | > Nick.
| | > | >
| | > | >
| | > | >
| | > | > "George McCollister" <georgem@novatech-llc.com> wrote in message
| | > | > news:ululA%23b8DHA.1632@TK2MSFTNGP12.phx.gbl...
| | > | > > Here is some additional information that may be VERY
important!!!!
| | > | > >
| | > | > > Our main executable is a child process of our custom debugger.
We
| | run
| | > | > > everything compiled for release, but have a custom debugger that
| | > catches
| | > | > > critical exceptions and logs important information to a file.
It
| is
| | > | > > essential to our design to run our main process in this manner,
| such
| | > | that
| | > | > we
| | > | > > can analyse errors generated in the field.
| | > | > >
| | > | > > I will try to verify it but I am guessing that Windows CE does
not
| | > allow
| | > | > > more than 64 threads on a process which is being debugged. Even
if
| | the
| | > | > > debugger is completely contained within the CE machine.
| | > | > >
| | > | > > Thanks,
| | > | > > George McCollister
| | > | > >
| | > | > >
| | > | > > "George McCollister" <georgem@novatech-llc.com> wrote in message
| | > | > > news:et06R3b8DHA.1804@TK2MSFTNGP12.phx.gbl...
| | > | > > > I am using Windows CE .NET 4.1 on an X86. When I exceed 64
| threads
| | > per
| | > | > > > process I have noticed that some threads are halted until the
| | number
| | > | of
| | > | > > > threads goes below 64.
| | > | > > >
| | > | > > > I am compiling my program in Platform Builder with Stack
Reserve
| | set
| | > | to
| | > | > > > 0x20000, and Stack Commit set to 0x1000 under the link
settings
| | tab.
| | > | > > >
| | > | > > > Is this a bug?
| | > | > > >
| | > | > > > Thanks!
| | > | > > > George McCollister
| | > | > > >
| | > | > > >
| | > | > >
| | > | > >
| | > | >
| | > | >
| | > |
| | > |
| | > |
| | >
| |
| |
| |
|
|

Relevant Pages

  • Re: Companyweb - Cannot complete this action
    ... My Domain Account that was used at the site collection owner of my intranet ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... This posting is provided "AS IS" with no warranties, and confers no rights. ...
    (microsoft.public.windows.server.sbs)
  • Re: Installing Publisher on 2 machines
    ... Perhaps instead of a purchase, it should be thought of as an open-ended ... And how many people don't read the EULA to know what rights ... MVP Microsoft [Publisher] ... And even if MS demands you destroy the materials ...
    (microsoft.public.publisher)
  • Re: OEM software
    ... > SOFTWARE includes Microsoft computer software, ... > such agreements rather than this EULA. ... > -user rights ONLY if the SOFTWARE is genuine and a genuine ... > the license agreement accompanying the applicable ...
    (microsoft.public.windowsxp.general)
  • Microsoft Security Bulletin MS02-024
    ... Authentication Flaw in Windows Debugger can Lead to ... Software: Microsoft Windows ... A successful attack requires the ability to logon interactively to the ... systems and terminal servers. ...
    (microsoft.public.security)
  • RE: IRM: service needed?
    ... PowerPoint, choose "Help -> Check for Updates".] ... If you are not hosting your own Information Rights Management server (on ... Windows Server 2003), Microsoft is hosting a limited time trial. ...
    (microsoft.public.powerpoint)