| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] URGENT potentially serious regression in 3.7.0 |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Sat, 9 Mar 2013 16:45:49 -0500 (EST) |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <868073999.17618770.1362864996185.JavaMail.root@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
----- Original Message ----- > Ah, looks like the crazy level of diagnostics is coming from here > in pmcd... > > 671 #ifdef PCP_DEBUG > 672 if (pmDebug & DBG_TRACE_APPL0) > 673 for (i = 0; i <= maxClientFd; i++) Yeah, so thinking about it a bit - its because with NSS, we have this sparse fd number space where the "native" fds are from zero through FD_SETSIZE, and the nspr fds are numbered starting above that range. Everything in-between is space-junk, we should just skip over it ... just need to a way to do that without exposing these low-level libpcp details up at the pmcd/higher levels. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] URGENT potentially serious regression in 3.7.0, Nathan Scott |
|---|---|
| Next by Date: | pcp updates: qa, resolve debug pmcd meltdown, Nathan Scott |
| Previous by Thread: | Re: [pcp] URGENT potentially serious regression in 3.7.0, Nathan Scott |
| Next by Thread: | Re: [pcp] URGENT potentially serious regression in 3.7.0, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |