[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #44621] Segfault with clf.m test
From: |
Pantxo Diribarne |
Subject: |
[Octave-bug-tracker] [bug #44621] Segfault with clf.m test |
Date: |
Thu, 26 Mar 2015 11:42:38 +0000 |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0 |
Follow-up Comment #4, bug #44621 (project octave):
@Mike: Is there a central place where we can get instructions on how to
produce a gdb backtrace. On linux, I currently generally install octave and
then run gdb on the installed octave-gui binary. This produces backtraces that
only show the GUI thread calls, not the interpreter. We thus can't see how the
two threads at play may interact/interfere.
Is there a simpler and more general way to have a full backtrace?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?44621>
_______________________________________________
Message posté via/par Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #44621] Segfault with clf.m test, Guillaume, 2015/03/24
- [Octave-bug-tracker] [bug #44621] Segfault with clf.m test, Pantxo Diribarne, 2015/03/24
- [Octave-bug-tracker] [bug #44621] Segfault with clf.m test, Guillaume, 2015/03/25
- [Octave-bug-tracker] [bug #44621] Segfault with clf.m test, Mike Miller, 2015/03/25
- [Octave-bug-tracker] [bug #44621] Segfault with clf.m test,
Pantxo Diribarne <=
- [Octave-bug-tracker] [bug #44621] Segfault with clf.m test, Guillaume, 2015/03/27
- [Octave-bug-tracker] [bug #44621] Segfault with clf.m test, Guillaume, 2015/03/27
- [Octave-bug-tracker] [bug #44621] Segfault with clf.m test, Guillaume, 2015/03/30
- [Octave-bug-tracker] [bug #44621] Segfault with clf.m test, Pantxo Diribarne, 2015/03/30