[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debugging while building the documentation

From: Dmitri A. Sergatskov
Subject: Re: Debugging while building the documentation
Date: Wed, 7 Nov 2018 11:00:31 -0600

On Wed, Nov 7, 2018 at 5:03 AM Pantxo Diribarne <address@hidden> wrote:

I am currently experimenting with using std::mutex and std::unique_lock instead of our system dependent implementation of mutexes. This is for the context.

I am getting a segfault when building the documentation (when running genpropdoc.m) which I am not able to reproduce in a normal run-octave session.
To complicate things, the segfault only happens when building with "-jN" (N>1).

Hence my question: how can I get a backtrace after a crash that happens when run-octave is ran from the build system?

On redhat/fedora systemd-coredump
will capture coredumps into system logs.

E.g. if I run something like that:

        double a[3];
        int i;

        for (i=1; i++; i< 5) a[i] = 2*i;

        return 0;


I get a bus error and in the logs I see:

Nov 07 10:34:48 td-119156 systemd-coredump[26177]: Process 26175 (a.out) of user 1001 dumped core.
                                                   Stack trace of thread 26175:
                                                   #0  0x0000000000401121 main (a.out)
                                                   #1  0x00007fba29fd4413 __libc_start_main (libc.so.6)
                                                   #2  0x000000000040104e _start (a.out)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]