Re: [libodbcxx-devel] segmentation fault help please

[Simon W. <si...@gi...>]

On 06/07/2012 01:34 PM, Buck wrote:
>
> looks like the ``leak'' is in the C library's getpwuid(), which allocates
> a ``static buffer'' for the returned struct passwd, no?  if you're suggest-
> ing that libodbc should call (the reentrant, and non-static struct passwd-
> returning) getpwuid_r() directly, then you need to talk to the unixODBC
> folks.  but if you're saying GNU libc's getpwuid() should clean up at exit
> or something, that's a different political arena
>
> anyways, thanks for sussing out the correct release semantics for the var-
> ious libodbc++ objects

Hi Buck,

Thanks for setting me straight. I'm relatively new to c/c++ development 
on nix platforms and wasn't sure what I was seeing. I'm kind of 
surprised/annoyed that things are in this state - at least on Debian. It 
affects multi-threaded applications quite a bit. If I can't get them to 
sort it out, I'll have to steer clear of unixODBC for now. Or maybe use 
a different OS.

Cheers,

Simon

-- 
simonsmicrophone.com