On Wed, Nov 27, 2013 at 11:41 AM, Darin Perusich <[email protected]> wrote: > On Tue, Nov 26, 2013 at 2:15 PM, Darin Perusich <[email protected]> wrote: >> On Tue, Nov 26, 2013 at 12:59 PM, dan (ddp) <[email protected]> wrote: >>> On Tue, Nov 26, 2013 at 12:57 PM, Darin Perusich <[email protected]> wrote: >>>> This "fixed" remoted. What's so special about this included zlib, >>>> other then being 8.5 years old and getting ever more unmaintained? I >>>> haven't had a chance to diff it against upstream yet. >>>> >>> >>> I don't know actually. I remember the Debian folks mentioning >>> differences and possibly trying to push some upstream. >>> >> >> Looks I spoke to soon, I'm still getting the segfault with >> ossec-remoted built against the provided zlib. This is giving me a bit >> of a headache. Let me keep poking around and see if I can come up with >> anything else. > > Ok, so I'm looking at this again and ossec-remoted is built with the > provided zlib and it's still segfaulting. What other info can I > provide to keep this moving, any additional gdb output, valgrind, > building w/specify debug flags (other then -g)? >
Is the trace in gdb the same? > Thanks! > > -- > > --- > You received this message because you are subscribed to the Google Groups > "ossec-list" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
