Welcome to the forums. Please post in English or French.

You are not logged in.

#1 2012-12-02 20:54:31

Thomas DE SOZA
From: EDF
Registered: 2007-11-23
Posts: 3,066

Submitting a proper bug report or crash detail

Submitting a proper bug report or crash detail

This sticky post deals with bug reports. Here are the steps to follow when submitting a bug report or when asked to provide further details about a crash or error.
These steps require a compiled-from-source Aster install in order to have a debug executable, Salome-Meca does not provide a debug version.

1. Please make sure the problem does not arise at least in the latest testing or stable version

Bugs that you encounter might indeed have been fixed in recent releases. Latest testing or stable versions are available here.
If you are able to, try to launch the faulty case with the latest development releases : unstable or stable-updates. See this post to update a pre-existent testing or stable version.

2. Once the bug has been confirmed in recent releases, add the following statement to the DEBUT command of your command file


3. Launch the calculation with the "debug" executable

The debug executable is available after having selected the "debug" button above the "Launch" button of ASTK.
Make sure you're using a standalone version of Code_Aster and not Salome_Meca.

4. Retrieve the output of the job from the ASJOB window and attach it to your post on the forum

This output should contain at the time of the crash an history of the source code being called. This will help us narrow the problem.
The history looks like this :

coredump analysis...                                                    [  OK  ]

warning: Can't read pathname for load map: Input/output error.
Core was generated by `./asterp Python/Execution/E_SUPERV.py -eficas_path ./Python -commandes fort.1 -'.
Program terminated with signal 11, Segmentation fault.
[New process 6893]
[New process 6894]
#0  0x0000000000524225 in dxqpgl_ ()
#0  0x0000000000524225 in dxqpgl_ ()
#1  0x00000000008f0cd8 in te0031_ ()
#2  0x0000000000835312 in te0000_ ()
#3  0x00000000007e0fad in calcul_ ()
#4  0x00000000005ed2ff in pemain_ ()
#5  0x00000000005c9e5e in op0107_ ()
#6  0x000000000059a174 in ex0100_ ()
#7  0x0000000000542912 in execop_ ()
#8  0x0000000000541c90 in expass_ ()
#9  0x00000000005292e9 in aster_oper ()

5. If the problem does not arise with the debug version or if something goes wrong, attach the files necessary to reproduce the problem

Required files include : a mesh, a command file, any additional input file. An astk profile or an export file is also welcome.
If your case is too big either to upload or to solve, please try to reduce the problem with a smaller model.


#2 2013-12-27 09:51:59

From: EDF R&D
Registered: 2007-12-12
Posts: 837

Re: Submitting a proper bug report or crash detail

In addition, post your files in the issue tracker too : https://bitbucket.org/code_aster/codeaster-src/issues

Code_Aster release : unstable on (Ubuntu Precise Pangolin 12.04 64 bits) - GNU + Intel

Code_Aster. What else ?