diff options
| author | Rich Megginson <rmeggins@redhat.com> | 2005-05-24 01:14:48 +0000 |
|---|---|---|
| committer | Rich Megginson <rmeggins@redhat.com> | 2005-05-24 01:14:48 +0000 |
| commit | 4dc8d51ea2acdcddf5eff03d493da3a70990d8c0 (patch) | |
| tree | 2cf31a1b7e3baa625b55a6ed5432bcd287831a7f /lib/libaccess/method.cpp | |
| parent | 6d111727bbe53b62dfc7be792b07eecfd6c8e984 (diff) | |
| download | ds-4dc8d51ea2acdcddf5eff03d493da3a70990d8c0.tar.gz ds-4dc8d51ea2acdcddf5eff03d493da3a70990d8c0.tar.xz ds-4dc8d51ea2acdcddf5eff03d493da3a70990d8c0.zip | |
Bug(s) fixed: 158549
Bug Description: Reliab 05: chaining backend test core dumped on HPUX backend
Reviewed by: Noriko (Thanks!)
Fix Description: This is a 64 bit issue. For ber_scanf, the "i" and "e" flags require a pointer to a long. There were a couple of places in the chaining backend code where we were passing in an int instead. This works fine on 32 bit where ints and longs are both 32 bits. I did a quick check through the code - these were the only places not using longs. The only way you would see this bug is in a "hub" chaining backend - one that gets requests from a mux and chains them to another farm server, or possibly on a mux in certain conditions.
Platforms tested: HP-UX 11.i 64 bit
Flag Day: no
Doc impact: no
QA impact: rerun chaining tests
New Tests integrated into TET: none
Diffstat (limited to 'lib/libaccess/method.cpp')
0 files changed, 0 insertions, 0 deletions