[Pkg-octave-devel] Bug#743679: octave: plot(1:4) triggers segfault crash

[Hörmetjan Yiltiz <hyiltiz@gmail.com>]

Glad to hear that. About when, according to your experience, should be bugfix be present in unstable, and therefore in testing, may I ask?

祝好，
========================
He who is worthy to receive his days and nights is worthy to receive* all
else* from you (and me).
                                                 The Prophet, Gibran Kahlil

On Mon, Apr 7, 2014 at 8:36 PM, Mike Miller <mtmiller@debian.org> wrote:

Control: forcemerge 743260 -1

On Mon, Apr 07, 2014 at 15:15:34 +0800, Hörmetjan Yiltiz wrote:
> [...]
> to Octave 3.8.1-1 on 20140316, then to Octave 3.8.1-1+b1. I also reverted
> back to Octave 3.8.0-5, only to verify that the bug was introduced not by
> Octave. As you pointed out, that should be the transition of "mesa package"
> that is causing the problem.
> [...]
> The backtrace of command "axes" are as follows:
> [...]
> #1  0x00007ffff1f12779 in llvm::TargetRegistry::lookupTarget(std::string const&, std::string&) () from /usr/lib/x86_64-linux-gnu/libLLVM-3.3.so.1
> #2  0x00007ffff19b27a1 in llvm::EngineBuilder::selectTarget(llvm::Triple const&, llvm::StringRef, llvm::StringRef, llvm::SmallVectorImpl<std::string> const&) () from /usr/lib/x86_64-linux-gnu/libLLVM-3.3.so.1
> #3  0x00007fffe47c0bc8 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
> [...]

Thanks, that confirms for me that they are the same bug, merging. A fix
has already been committed and will be in the next upload of Octave
3.8.1.

--
mike