[chrisegerer]

hi,
I get the following error message after running fluentMeshToFoam.
Is there anything wrong with the .msh file or how do I have to interpret the error message?
I'm quite new to OpenFOAM so I would be glad for any help!
Thanks in advance!

error message:
FINISHED LEXING


dimension of grid: 3
Creating shapes for 3-D cells
sh: gaddr2line: command not found
sh: gaddr2line: command not found
sh: gaddr2line: command not found
sh: gaddr2line: command not found
sh: gaddr2line: command not found


--> FOAM FATAL ERROR : Cannot find match for face 4.
Model: pyr model face: 3(0 1 4) Mesh faces:
5
(
3(52802 8982 172140)
3(8982 52802 706)
3(1789 706 52802)
4(172140 1789 706 8982)
3(172140 52802 1789)
)
Matched points: 5(172140 8982 172140 8982 52802)#0 Foam::error::printStack(Foam:: Ostream&) addr2line failed
#1 Foam::error::abort() addr2line failed
#2 Foam::create3DCellShape(int, Foam::List<int> const&, Foam::List<foam::face> const&, Foam::List<int> const&, Foam::List<int> const&, int) addr2line failed
#3 main addr2line failed
#4 start addr2line failed


From function create3DCellShape(const label cellIndex, const labelList& faceLabels, const labelListList& faces, const labelList& owner, const labelList& neighbour, const label fluentCellModelID)
in file create3DCellShape.C at line 281.

FOAM aborting

Abort trap

[mattijs]

Try running fluent3DMeshToFoam.

[chrisegerer]

fluent3DMeshToFoam doesn't work either. When running I get this error message:

--> FOAM FATAL ERROR : Do not understand characters:

From function fluentMeshToFoam::lexer
in file fluentMeshToFoam.L at line 704.

I also tried to convert it on a different OpenFOAM installation this morning. Same errors.

[caw]

try dos2unix on the meshfile before using fluent3DMeshToFoam

regards
Christian

[chrisegerer]

dos2unix didn't resolve the problem. After "FINISHED LEXING" there's an FOAM Warning. program aborts saying "segmentation fault".

[dmoroian]

Hi Christian,
Do you have the possibility to run the same command but under valgrind?

Dragos

[chrisegerer]

Hi Dragos,
while running valgrind, there was the following output:

==14024== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 2)
==14024== malloc/free: in use at exit: 85,479,992 bytes in 1,915,608 blocks.
==14024== malloc/free: 11,416,411 allocs, 9,500,803 frees, 879,490,377 bytes allocated.
==14024== For counts of detected errors, rerun with: -v
==14024== searching for pointers to 1,915,608 not-freed blocks.
==14024== checked 64,396,024 bytes.
==14024==
==14024== LEAK SUMMARY:
==14024== definitely lost: 0 bytes in 0 blocks.
==14024== possibly lost: 38,955,197 bytes in 3,505 blocks.
==14024== still reachable: 46,524,795 bytes in 1,912,103 blocks.
==14024== suppressed: 0 bytes in 0 blocks.
==14024== Rerun with --leak-check=full to see details of leaked memory.

Does this make any sense to you?
Thanks for your help.

Christian

[dmoroian]

So you don't get any more segfaults?
Are you running on 32bit or 64bit?

Dragos

[chrisegerer]

no, I don't get any more segfaults.
running on 64bit.

At the moment I think that the problem could base on the export-process from ICEM, because I tried with some other .msh files and there were no errors.