| To: | Nathan Scott <nathans@xxxxxxxxxx> |
|---|---|
| Subject: | Re: pmRegisterDerived return values |
| From: | fche@xxxxxxxxxx (Frank Ch. Eigler) |
| Date: | Wed, 20 Jan 2016 20:55:28 -0500 |
| Cc: | Marko Myllynen <myllynen@xxxxxxxxxx>, Ken McDonell <kenj@xxxxxxxxxxxxxxxx>, pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <1305297915.11201184.1453261568406.JavaMail.zimbra@xxxxxxxxxx> (Nathan Scott's message of "Tue, 19 Jan 2016 22:46:08 -0500 (EST)") |
| References: | <569CB025.4070603@xxxxxxxxxx> <569CB7C5.7030803@xxxxxxxxxxxxxxxx> <1305297915.11201184.1453261568406.JavaMail.zimbra@xxxxxxxxxx> |
| User-agent: | Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) |
nathans wrote: > [...] Real problem arises when we subsequently call > pmDerivedErrStr() - this is using thread-local-storage for the error > message (in libpcp). However, from trawling the internets, it seems > python may be switching the threads underneath us ... [...] Could the error message go into the __pmContext structure instead? - FChE |
| Previous by Date: | RE: [pcp] pmRegisterDerived return values, Ken McDonell |
|---|---|
| Next by Date: | RE: pmRegisterDerived return values, Ken McDonell |
| Previous by Thread: | RE: [pcp] pmRegisterDerived return values, Ken McDonell |
| Next by Thread: | RE: pmRegisterDerived return values, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |