Re: debugging seg fault
Vladimir Tzankov <[email protected]>
| Newsgroups | gmane.lisp.clisp.general |
|---|---|
| Message-ID | <CAHWYE6+6tb-muxfAF382uuC27UNZ9FRbO=Jf7K99eCFpm0=zAA@mail.gmail.com> |
Good, thanks. Can you elaborate a little bit more what you are doing (some pseudocode)? I see the thread was interrupted and invoke-debugger called in its context. Did you kill the thread (internally calls thread-interrupt) or just execute something in thread's context? -- vlad On Mon, Jun 20, 2016 at 10:32 AM, Don Cohen <[email protected]> wrote: > Vladimir Tzankov writes: > > > Stacktraces from coredump are good starting point. Let's have a > > look on these. > please see http://chmusic.org/private/bt > > I notice in there: > Missing separate debuginfos, use: debuginfo-install glibc-2.17-78.el7.x86_64 nss-softokn-freebl-3.16.2.3-9.el7.x86_64 > > I hope you can either make progress without that or give me some idea > how to do that debuginfo-install - I had to do yum intall gdb to get > this far and yum doesn't seem to know how to install debuginfo-install. ------------------------------------------------------------------------------ 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