On Mon, 20 Apr 2015, Nathann Cohen wrote:

I made http://trac.sagemath.org/ticket/16865 from this 8 months ago, but nobody has said which should be defined correct way.

Given the following output, it would indeed make more sense if 2 were... at the 
top.

sage: Poset([[1,2],[[1,2]]]).top()
2

Good point. :=)

Write the code - -

I tried to see where the error jumps in. But after long series of 'c' in trace("P.plot()") I got, at

ipdb> s
/home/jm58660/sage/local/lib/python2.7/site-packages/sage/graphs/generic_graph.py(9923)edge_iterator()
   9922         elif self._directed:
-> 9923             return self._backend.iterator_out_edges(vertices, labels)
   9924         else:

, the result

------------------------------------------------------------------------
/home/jm58660/sage/local/lib/libcsage.so(print_backtrace+0x31)[0x7f3263410859]
/home/jm58660/sage/local/lib/libcsage.so(sigdie+0x1e)[0x7f3263410a13]
/home/jm58660/sage/local/lib/libcsage.so(sage_signal_handler+0x1cb)[0x7f32634102ad]
/lib64/libpthread.so.0[0x36a46100d0]
/home/jm58660/sage/local/lib/libpython2.7.so.1.0(PyObject_GetAttr+0x3a)[0x7f326e4f48ca]
/home/jm58660/sage/local/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x166d)[0x7f326e55a90d]
 . . .
Attaching gdb to process id 31921.
 . . .
Missing separate debuginfos, use: debuginfo-install glibc-2.20-8.fc21.x86_64 keyutils-libs-1.5.9-4.fc21.x86_64 krb5-libs-1.12.2-15.fc21.x86_64 libcom_err-1.42.12-3.fc21.x86_64 libselinux-2.3-5.fc21.x86_64 openssl-libs-1.0.1k-6.fc21.x86_64 pcre-8.35-8.fc21.x86_64 xz-libs-5.1.2-14alpha.fc21.x86_64
 . . .
warning: File "/home/jm58660/sage/local/lib64/libstdc++.so.6.0.20-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
  File "<string>", line 4
SyntaxError: from __future__ imports must occur at the beginning of the file
Error while executing Python code.

Saved trace to /home/jm58660/.sage/crash_logs/sage_crash_K_eIoF.log
------------------------------------------------------------------------
Unhandled SIGSEGV: A segmentation fault occurred in Sage.

and so I don't yet even know where to look at.

--
Jori Mäntysalo

Reply via email to