Yes. It's always the trampoline, the signal handler, and the stack
trace printer.
Brian
On Wed, 2006-08-30 at 17:37 -0400, Jeff Squyres wrote:
> As long as it's always 3 function calls -- do we know that it will be?
>
>
> On 8/30/06 5:32 PM, "Brian Barrett" wrote:
>
> > Hi all-
> >
> > A q
As long as it's always 3 function calls -- do we know that it will be?
On 8/30/06 5:32 PM, "Brian Barrett" wrote:
> Hi all-
>
> A question about stack tracing. Currently, we have it setup so that,
> say, a segfault results in:
>
> [0]func:/u/jjhursey/local/odin/ompi/devel/lib/libopal.so.0(op
Hi all-
A question about stack tracing. Currently, we have it setup so that,
say, a segfault results in:
[0]func:/u/jjhursey/local/odin/ompi/devel/lib/libopal.so.0(opal_backtrace_print+0x2b)
[0x2a959166ab]
[1] func:/u/jjhursey/local/odin/ompi/devel/lib/libopal.so.0 [0x2a959150bb]
[2] func:/lib6
We have changed how we generate snapshot tarballs (previously called
"nightly" tarballs). The old way was that if there had been any commits at
all to the SVN repository in the previous 24 hours, we would generate new
tarballs for all active OMPI development trees. For example, if there had
been
