Re: [opendx-users] signal 11 caused by WriteImage module

I am running into the same problem.

- The error occurs when trying to write using writeImage in any format. (at least both 'miff' and 'ps'). The error occurs after the file has been written and the file seems to be correct.

It occurs with the precompiled Dx.4.3.0-1 (from opendx-4.3.0-1.rh9.rpm pack) under Suse8.2, both on a P3 laptop and on a dual processor Xeon. Compiling from 4.3.0 sources gives the same behaviour on the laptop.

A backtrace from gdb:

..
#6  0x408ad895 in __pthread_sighandler () from /lib/libpthread.so.0
#7  <signal handler called>
#8  0x08088ac6 in DXForkChild ()
#9  0x08089c16 in DXFree ()
#10 0x08149c4b in m_WriteImage ()
#11 0x0808f4ed in ExQueueSubGraph ()
#12 0x080a7974 in _dxf_ExRQDequeue ()
#13 0x0808a159 in _dxf_ExEnvp ()
#14 0x08089d71 in DXmain ()
#15 0x08084ab5 in main ()

- There are no problems under Suse8.1/Suse7.3 when either using the opendx-4.3.0-1.rh73.rpm or own compiled sources.

- Saving the file 'by hand' in miff format from the 'Save Image' window works fine.

I could dig a bit further but need some pointers as where to look. I don't see why DXFree should need to 'fork' a child but haven't looked at the source code.

Kind regards,

Mattijs

--
/*---------------------------------------------------------*\
| ===========           Mattijs Janssens                    |
| \\        /           Development Engineer                |
|  \\      /                                                |
|   \\    /             Nabla Ltd.                          |
|    \\  /              The Mews, Picketts Lodge            |
|     \\/               Picketts Lane, Salfords,            |
|     F ield            Surrey RH1 5RG.                     |
|     O peration        Tel: +44 (0)1293 821272             |
|     A nd              Email: [EMAIL PROTECTED]       |
|     M anipulation     URL: http://www.Nabla.co.uk         |
\*---------------------------------------------------------*/

Reply via email to