Return value/error code 134
This is probably more of a C++ question than a breve question, but since I can't find the answer elsewhere I'll ask here: What does it mean when breve crashes with a return value of 134? I think it might have something to do with memory ... I believe I'm leaking memory. While I'm asking, what exactly does code 139 mean? I've become familiar with this code too ... calling end-simulation seems to always result in this error code for me.
not sure...
Where are you seeing these numbers printed out? I don't know where these particular errors are coming from because they don't look like internal breve error codes to me (and breve doesn't print any out, so I'm a little confused).
- jon
Hmmm, I thought the error
Hmmm, I thought the error codes were related to C++, but it looks like they're actually related to Condor. Nevermind...
Correction
It turns out that Condor adds 128 to the standard return values, so the codes in question were actually 6 (SIGABRT) and 11 (SIGSEGV).
The one I'm particularly interested is the SIGABRT, since I can't figure out why it's happening. There seems to be a failed assertion though:
breve_ex: ../../GIMPACT/src/gim_memory.cpp:125: void* gim_alloc(size_t): Assertion `ptr' failed.
/u/schrum2/breve_2.7.2/bin/breve: line 15: 12149 Aborted $DIRECTORY/breve_ex $*
physics simulation library...
Interesting -- it appears to be originating in the physical simulation library. From the looks of it, it's possible that the process is running out of memory, though it's not totally clear -- it could be indicative of some other issue.
Can you monitor memory usage of the process? Is it possible that there is a memory or object leak? A leak could be either in the simulation code (your side) or in the breve engine code (my side).
- jon
My side
The error ended up being on my side, and is now fixed. Thanks for the help though.
It turns out this error
It turns out this error isn't entirely fixed, though I still think it's on my side. However, I've looked at the object allocation and it seems ok. Now I'm getting this error:
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
Not very helpful. I tried using "self set-output-filter to 50" to get more info, but it didn't help. Any recommendations on how to track this error down?
-Jacob