Re: debugging seg fault

Stacktraces from coredump are good starting point. Let's have a look on these.
Of course the best is to figure out small self contained reproducible artefact.

--
vlad

On Sun, Jun 19, 2016 at 5:44 AM, Don Cohen
<[email protected]> wrote:
>
> I have a fairly reproducible seg fault from an MT build.
> Unfortunately, I don't have a small self contained example.
>
> If I arrange to have a core file saved, can someone give me
> an idea what to do with it to help someone who knows a lot more
> than I do about this stuff figure out what's wrong?
> Or is there something else I should do to (help someone else)
> debug it?
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports. http://sdm.link/zohomanageengine
> _______________________________________________
> clisp-list mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/clisp-list

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine
_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list