CFD Online Discussion Forums

CFD Online Discussion Forums (http://www.cfd-online.com/Forums/)
-   OpenFOAM Running, Solving & CFD (http://www.cfd-online.com/Forums/openfoam-solving/)
-   -   mistake after nparcels increased, dieselFoam (http://www.cfd-online.com/Forums/openfoam-solving/66214-mistake-after-nparcels-increased-dieselfoam.html)

yejungong July 9, 2009 04:45

mistake after nparcels increased, dieselFoam
 
Hi,

I am running my version of dieselFoam using osx system. and my code works fine when nparcels=5000.

but after I increased the number of parcels, nparcels, to 20000, I got the following error messages, attached in the bottom.

I have installed binutils which includes gaddr2line.

is it happened because of osx system?

Any help is highly appreciated!

Yejun



-----------------------
Evolving Spray
#0 Foam::error::printStack(Foam::Ostream&)unable to read unknown load command 0x1b
unable to read unknown load command 0x1e
in "/Network/Servers/controller.cluster/Homedir/yegong/OpenFOAM/OpenFOAM-1.5/lib/darwinIntelDPOpt/libOpenFOAM.dylib"
#1 Foam::sigSegv::sigSegvHandler(int)unable to read unknown load command 0x1b
unable to read unknown load command 0x1e
in "/Network/Servers/controller.cluster/Homedir/yegong/OpenFOAM/OpenFOAM-1.5/lib/darwinIntelDPOpt/libOpenFOAM.dylib"
#2 _sigtrampgaddr2line: /usr/lib/libSystem.B.dylib: cannot get addresses from archive addr2line failed
#3 _sigtrampgaddr2line: /usr/lib/libSystem.B.dylib: cannot get addresses from archive
addr2line failed#4 void Foam::Cloud<Foam::parcel>::move<Foam::spray>(Foam: :spray&)unable to read unknown load command 0x1b
unable to read unknown load command 0x1e in "/Network/Servers/controller.cluster/Homedir/yegong/OpenFOAM/yegong-1.5/lib/darwinIntelDPOpt/libmydieselSpray.dylib"
#5 Foam::spray::move()unable to read unknown load command 0x1b
unable to read unknown load command 0x1e in "/Network/Servers/controller.cluster/Homedir/yegong/OpenFOAM/yegong-1.5/lib/darwinIntelDPOpt/libmydieselSpray.dylib"
#6 Foam::spray::evolve()unable to read unknown load command 0x1b

gschaider July 9, 2009 05:31

Quote:

Originally Posted by yejungong (Post 222020)
Hi,

I am running my version of dieselFoam using osx system. and my code works fine when nparcels=5000.

but after I increased the number of parcels, nparcels, to 20000, I got the following error messages, attached in the bottom.

I doubt, that the extra 15k particles pushed it over the edge memory-wise, but have you checked how much memory the 5k-case needed?

BTW: is this the first time-step with particles?

Quote:

Originally Posted by yejungong (Post 222020)
I have installed binutils which includes gaddr2line.

is it happened because of osx system?

I doubt it. The "unable to read unknown load command 0x1b" is an OS X-problem. But it was not the cause of the catastrophe.

Quote:

Originally Posted by yejungong (Post 222020)
Any help is highly appreciated!

Yejun



-----------------------
Evolving Spray
#0 Foam::error::printStack(Foam::Ostream&)unable to read unknown load command 0x1b
unable to read unknown load command 0x1e
in "/Network/Servers/controller.cluster/Homedir/yegong/OpenFOAM/OpenFOAM-1.5/lib/darwinIntelDPOpt/libOpenFOAM.dylib"
#1 Foam::sigSegv::sigSegvHandler(int)unable to read unknown load command 0x1b
unable to read unknown load command 0x1e
in "/Network/Servers/controller.cluster/Homedir/yegong/OpenFOAM/OpenFOAM-1.5/lib/darwinIntelDPOpt/libOpenFOAM.dylib"
0x1b

sigSev points to a "I accessed an address outside of an array"-problem. Which leads to the usual mantra: "have you got a debug-version handy"

Bernhard

yejungong July 9, 2009 05:44

Quote:

Originally Posted by gschaider (Post 222030)
I doubt, that the extra 15k particles pushed it over the edge memory-wise, but have you checked how much memory the 5k-case needed?

BTW: is this the first time-step with particles?

thanks, Bennard,

this error message happened after the injected parcels accessed 8000, not the first time step. and if I use nparcels=8000, my code works.

the 8000 case needs around 120M memory. and I have 8GB of memory. it should be enough.

Yejun

yejungong July 9, 2009 05:53

Quote:

Originally Posted by gschaider (Post 222030)

sigSev points to a "I accessed an address outside of an array"-problem. Which leads to the usual mantra: "have you got a debug-version handy"

Bernhard

sorry, what's "debug-version handy"?

I do defined some new variables in my code, but they are all pointers or scalars. no one is array.

gschaider July 9, 2009 10:47

Quote:

Originally Posted by yejungong (Post 222032)
sorry, what's "debug-version handy"?

What I meant to say was: compile yourself a debug-version of OF (see for instructions elsewhere on the forum) and run your program in that. Most causes for segmentation-faults ("array out of bounds" basically) are checked for in the debug-version

Quote:

Originally Posted by yejungong (Post 222032)
I do defined some new variables in my code, but they are all pointers or scalars. no one is array.

No matter what you do: as soon as you start developing you should have a debug-version. It saves you a lot of time

yejungong July 10, 2009 03:17

Quote:

Originally Posted by gschaider (Post 222114)
What I meant to say was: compile yourself a debug-version of OF (see for instructions elsewhere on the forum) and run your program in that. Most causes for segmentation-faults ("array out of bounds" basically) are checked for in the debug-version

thanks a lot, Bernhard.

I have compiled the debug version, and I will learn how to use it first.

Yejun


All times are GMT -4. The time now is 23:23.