|
From: David L. <dav...@te...> - 2004-06-25 06:31:48
|
SGVscCwNCiANCkkndmUgcnVuIGludG8gYW4gaXNzdWUgd2l0aCB1c2luZyBWYWxncmluZCwgYW5k IGhvcGVmdWxseSBzb21lb25lIGNhbiBoZWxwLg0KIA0KSWYgSSBjYWxsIHNlbV93YWl0KCkgb24g YSBzZW1hcGhvcmUgdGhhdCBuZWVkcyB0byBibG9jaywgdmFsZ3JpbmQgc3BpbnMgdXAgdG8gMTAw JSBDUFUgdXRpbGl6YXRpb24sIGJ1dCB0aGUgb3RoZXIgdGhyZWFkcyBpbiB0aGUgcHJvY2VzcyBr ZWVwIHJ1bm5pbmcuICBIb3dldmVyLCBhbnkgY2FsbHMgdG8gc2VtX3Bvc3QoKSBvbiB0aGF0IHNl bWFwaG9yZSBuZXZlciByZXR1cm4uDQogDQpUbyBtYWtlIG1hdHRlcnMgZXZlbiBtb3JlIGNvbXBs aWNhdGVkLCBvbGRlciB2ZXJzaW9ucyBvZiB0aGUgYXBwIGluIHF1ZXN0aW9uIGFuZCBzaW1wbGUg dGVzdCBjYXNlcyBkb24ndCBleGhpYml0IHRoZSBwcm9ibGVtLg0KIA0KSSBoYXZlIHRyaWVkIHZh bGdyaW5kIDIuMS4wLCAyLjEuMSBhbmQgd2hhdCB3YXMgaW4gQ1ZTIG9uIDIwMDQtSnVuZS0yMy4g IEFsbCBleGhpYml0IHRoZSBzYW1lIGJlaGF2aW9yLiAgSSdtIGludm9raW5nIHZhbGdyaW5kIGFz ICd2YWxncmluZCAtLXRyYWNlLWNoaWxkcmVuPXllcyAtLXRvb2w9bWVtY2hlY2sgLi9teUFwcCcN CiANCiMgdW5hbWUgLWENCkxpbnV4IGRiYWNjZWwgMi42LjUtdGVyYSAjMSBTTVAgVHVlIEp1biAx IDE2OjUwOjI3IENEVCAyMDA0IGk2ODYgdW5rbm93bg0KDQpBIGNsdWUgdG8gd2hhdCBtYXkgYmUg aGFwcGVuaW5nIChvciBtYXliZSBqdXN0IGEgY29pbmNpZGVuY2UpIGlzIHRoYXQgdGhlIG9sZGVy IHZlcnNpb24gb2YgdGhlIGFwcCAod2hpY2ggdmFsZ3JpbmQncyBwcm9wZXJseSkgZGlzcGxheXMg dGhlIGZvbGxvd2luZyB3YXJuaW5nczoNCj09Mjc4PT0gd2FybmluZzogVmFsZ3JpbmQncyBwdGhy ZWFkX2F0dHJfc2V0c2NoZWRwYXJhbSBkb2VzIG5vdGhpbmcNCj09Mjc4PT0gICAgICAgICAgKHNj aGVkdWxpbmcgbm90IGNoYW5nZWFibGUpDQo9PTI3OD09ICAgICAgICAgIHlvdXIgcHJvZ3JhbSBt YXkgbWlzYmVoYXZlIGFzIGEgcmVzdWx0DQogDQpUaGUgbmV3IHZlcnNpb24gb2YgdGhlIGFwcCAo d2hpY2ggc2hvd3MgdGhlIHNlbWFwaG9yZSBsb2NrdXAgcHJvYmxlbSkgZG9lcyBub3QgZGlzcGxh eSB0aGlzIHdhcm5pbmcsIGV2ZW4gdGhvdWdoIGl0IGlzIF9kZWZpbml0ZWx5XyBzdGlsbCBiZWlu ZyBjYWxsZWQuDQogDQpkYXZlDQo8PjwNCg== |
|
From: Tom H. <th...@cy...> - 2004-06-25 07:12:08
|
In message <EFF...@ne...>
David Lee <dav...@te...> wrote:
> A clue to what may be happening (or maybe just a coincidence) is that
> the older version of the app (which valgrind's properly) displays the
> following warnings:
> ==278== warning: Valgrind's pthread_attr_setschedparam does nothing
> ==278== (scheduling not changeable)
> ==278== your program may misbehave as a result
>
> The new version of the app (which shows the semaphore lockup problem)
> does not display this warning, even though it is _definitely_ still
> being called.
Well valgrind definitely still prints that warning if that routine
is called, so perhaps you aren't picking up valgrind's libpthread.so
for some reason and it is using the system one?
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|