http://www.slony.info/bugzilla/show_bug.cgi?id=71





--- Comment #2 from Christopher Browne <cbbrowne at ca.afilias.info>  2009-02-18 15:05:19 ---
Do you get any output before the crash, or is it buffered, and therefore lost?

That crash takes place while it's logging the set of configuration parameters
to the slon log (file, or standard output).

If you have a way to capture the output in an unbuffered fashion, that would be
pretty useful, as that would let us get closer to finding where it fails.

*Apparently*, as it's trying to dump the config parameters, one of them is
failing to be accessed properly, hence the seg fault.  Perhaps one of them
isn't properly enough initialized, and it would seem a mighty good thing if we
can figure out at what point the failure takes place.

I'm not so familiar with Solaris; can you submit output to an unbuffered
destination so that you capture as much log as possible?  If you can do that,
that should make it pretty easy to track down where the problem would take
place.


-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.