Re: [Rlib-devel] Memory leaks

[Shannon W. <we...@ro...>]

Bob Doan wrote:

> I'm not sure that not freeing something would cause a segfault...
> 

True, may be a stretch.

> I think the #1 cause for a segfault in RLIB is bad query/datasource and
> not checking the return codes...
> 

Well, the segfaults do only happen when it should be showing an error 
message (ie, a failed sql query or an unknown pcode). But like I said, 
at any one time, I can get at least 5 or 6 error messages out of it ok 
(which show up in apache error log) before it starts segfaulting 
(instead of showing error messages - it just says the apache child died 
in the error log). When I restart apache, it works again for another 5 
or 6. So something is starting out ok and getting corrupted along the way.

It's been hard for me to track down because running it in gdb (apache 
single process) isn't giving much information and I don't have a way to 
reproduce it without apache. I'm willing to try any suggestions you guys 
have.

You say the #1 cause is a bad query/datasouce -- why should that ever
actually segfault, as opposed to issuing an error message and exiting 
cleanly?

Thanks,
Shannon