On Wed, May 9, 2012 at 8:16 AM, Schwab,Wilhelm K <[email protected]>wrote:
> The attached is diagnostic output from the Linux vm. I am doing some > iterative numerical analysis that won't always work out, so I expect errors > and non-sense results at times - it all depends on whether a particular > segment of a signal is clean or noisy; if the latter, all assumptions are > off. > > One thought is that early terminated iterations (or maybe ones that go too > long?) are leaving conditions that finalization can't clean, or maybe does > not clean before the next iteration begins. A segmentation fault seems a > bit harsh, but they are happening and I need to find a way around them. > > Is there anything in the attached dump that strikes you as significant? > Maybe something that says whether its the main thread or a background > thread that's blowing up, or some other clue that is obvious to the correct > eye? As it is, I see the #iterate, #basicIterate part of the stack, which > is what I would expect the code to be trying to do - fit curves to data. > > The numbers at the beginning are trace info (using C++ cout) to confirm > sanity of the arriving parameters. > > My next thought is to add some more tracing to show which segment/harmonic > is being attacked as it blows up. Then I might be able to set clever > breakpoints and get some handle on it. Suggestions are welcome. > Put instrumentation around the calls that allow you to write a C program that makes the exact same calls and see if that crashes? > Bill > > > > > > -- best, Eliot
