![](https://secure.gravatar.com/avatar/75151d6b2dfc8047688c0723f6b8960c.jpg?s=120&d=mm&r=g)
Hi R,
I was installing the latest code on my new workstation, when runTests.py exited with error. On running it on debug mode, I got the following output:
ankit@ankit-HP-Pavilion-dv4-Notebook-PC:~/sfepy$ ./runTests.py --debug tests/test_cmesh.py <<< directory: tests, test files: 1 <<< tests/test_cmesh.py sfepy: left over: ['data_dir', 'nm', '__builtins__', '_filename', '__file__', '__package__', 'expected', '__doc__', '__name__', 'os', 'TestCommon', 'verbose']
![](https://secure.gravatar.com/avatar/75151d6b2dfc8047688c0723f6b8960c.jpg?s=120&d=mm&r=g)
Also running ./postproc.py file.vtk is now throwing error with no fix as i browsed various forums ankit@ankit-HP-Pavilion-dv4-Notebook-PC:~/sfepy$ ./postproc.py cylinder.vtk The program 'python' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 696 error_code 1 request_code 154 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
The earlier sfepy version on which i was working was throwing no such errors.
Regards.
On Sunday, 16 June 2013 06:46:42 UTC+5:30, Ankit Mahato wrote:
![](https://secure.gravatar.com/avatar/27f6b03a726ccff3f7a5007b1df6bf8c.jpg?s=120&d=mm&r=g)
On 06/17/2013 12:16 AM, Ankit Mahato wrote:
Then it looks like a Mayavi/VTK installation problem - try asking at the enthought mailing list. Paraview works?
What is your mayavi version?
Mayavi 4.0.0
Same here, works ok...
r.
![](https://secure.gravatar.com/avatar/27f6b03a726ccff3f7a5007b1df6bf8c.jpg?s=120&d=mm&r=g)
Hi Ankit,
On 06/16/2013 03:16 AM, Ankit Mahato wrote:
Strange - what is your system architecture - 64 bit or 32 bit? I am running it at 64 bit linux boxes without problems.
To debug it, could you try editing site_cfg.py as follows:
compile_flags = '-g' debug_flags = '-DDEBUG_FMF -DDEBUG_MESH'
then 'make clean; make', run the failing test and send the output?
Also try running it in gdb: $ gdb --exec=python (gdb) run runTests.py --debug tests/test_cmesh.py
and when it segfaults, use 'bt' command to print the backtrace, and send the full output.
Thanks! r.
![](https://secure.gravatar.com/avatar/75151d6b2dfc8047688c0723f6b8960c.jpg?s=120&d=mm&r=g)
On Monday, 17 June 2013 00:01:33 UTC+5:30, Robert Cimrman wrote:
32 bit
ankit@ankit-HP-Pavilion-dv4-Notebook-PC:~/sfepy$ python runTests.py --debug tests/test_cmesh.py <<< directory: tests, test files: 1 <<< tests/test_cmesh.py sfepy: left over: ['data_dir', 'nm', '__builtins__', '_filename', '__file__', '__package__', 'expected', '__doc__', '__name__', 'os', 'TestCommon', 'verbose'] transpose 0 -> 2 n_incident: 6 intersect 2 -> 2 (0) n_incident: 2 n_incident: 6 max. n_incident_vertex: 12 sfepy/fem/extmods, sfepy/fem/extmods/mesh.c, conn_free, 210: ptr: 0xb5d14cc0, cookie: 0 mem_free_mem(): error exit! sfepy/fem/extmods, sfepy/fem/extmods/mesh.c, conn_free, 211: ptr: 0xb5d13ff4, cookie: 137058500 mem_free_mem(): error exit! sfepy/fem/extmods, sfepy/fem/extmods/mesh.c, conn_free, 210: ptr: 0xb5d14cc0, cookie: 0 mem_free_mem(): error exit! mem_free_mem(): error exit! sfepy/fem/extmods, sfepy/fem/extmods/mesh.c, conn_free, 211: ptr: 0xb5d09157, cookie: -3112053 mem_free_mem(): error exit! mem_free_mem(): error exit! Segmentation fault (core dumped)
(gdb) run runTests.py --debug tests/test_cmesh.py Starting program: /usr/bin/python runTests.py --debug tests/test_cmesh.py [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". <<< directory: tests, test files: 1 <<< tests/test_cmesh.py sfepy: left over: ['data_dir', 'nm', '__builtins__', '_filename', '__file__', '__package__', 'expected', '__doc__', '__name__', 'os', 'TestCommon', 'verbose'] transpose 0 -> 2 n_incident: 6 intersect 2 -> 2 (0) n_incident: 2 n_incident: 6 max. n_incident_vertex: 12 sfepy/fem/extmods, sfepy/fem/extmods/mesh.c, conn_free, 210: ptr: 0xb6585cc0, cookie: 0 mem_free_mem(): error exit! sfepy/fem/extmods, sfepy/fem/extmods/mesh.c, conn_free, 211: ptr: 0xb6584ff4, cookie: 137058500 mem_free_mem(): error exit! sfepy/fem/extmods, sfepy/fem/extmods/mesh.c, conn_free, 210: ptr: 0xb6585cc0, cookie: 0 mem_free_mem(): error exit! mem_free_mem(): error exit! sfepy/fem/extmods, sfepy/fem/extmods/mesh.c, conn_free, 211: ptr: 0xb657a157, cookie: -3112053 mem_free_mem(): error exit! mem_free_mem(): error exit!
Program received signal SIGSEGV, Segmentation fault. 0xb657bea8 in get_local_connectivity (refloc=<optimized out>, cell_vertices=<optimized out>, loc=<optimized out>) at sfepy/fem/extmods/mesh.c:733 733 loc->indices[ic] = cell_vertices->indices[refloc->indices[ic]]; (gdb) bt #0 0xb657bea8 in get_local_connectivity (refloc=<optimized out>, cell_vertices=<optimized out>, loc=<optimized out>) at sfepy/fem/extmods/mesh.c:733 #1 mesh_build (mesh=0x92624ac, dim=1) at sfepy/fem/extmods/mesh.c:428 #2 0xb657ba04 in mesh_setup_connectivity (mesh=0x92624ac, d1=1, d2=0) at sfepy/fem/extmods/mesh.c:294 #3 0xb6564c58 in __pyx_pf_5sfepy_3fem_7extmods_5cmesh_5CMesh_5setup_connectivity (__pyx_v_self=0x92624a4, __pyx_args=0x8d1610c, __pyx_kwds=0x0) at sfepy/fem/extmods/cmesh.c:4089 #4 0x081287ef in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Thanks! r.
participants (2)
-
Ankit Mahato
-
Robert Cimrman