I'm just curious what the developers know about the "print_trace" functions in
libMesh. I decided to add that functionality to our applications here at the
INL yesterday since we expended the use of libmesh_error greatly to the point
where we need more contextual information. Derek and I noted
On Thu, 13 May 2010, Cody Permann wrote:
> I'm just curious what the developers know about the "print_trace"
> functions in libMesh.
It's just something I added a few years back to make debugging
unexpected assertion failures (of both the libmesh_assert() and
libmesh_error() forms) easier. I ha
On May 13, 2010, at 8:04 AM, Roy Stogner wrote:
>
> On Thu, 13 May 2010, Cody Permann wrote:
>
>> I'm just curious what the developers know about the "print_trace"
>> functions in libMesh.
>
> It's just something I added a few years back to make debugging
> unexpected assertion failures (of bot
On Thu, 13 May 2010, Cody Permann wrote:
Actually this is exactly what I was look for: "found some code online",
"didn't have Mac libMesh builds" and "non-standardized voodoo". I just
didn't want to dive into it if it had been disabled or never enabled in the
first place if it had been done fo
On Thu, 13 May 2010 08:40:22 -0600, Cody Permann wrote:
> On May 13, 2010, at 8:04 AM, Roy Stogner wrote:
>
> >
> > On Thu, 13 May 2010, Cody Permann wrote:
> >
> >> I'm just curious what the developers know about the "print_trace"
> >> functions in libMesh.
> >
> > It's just something I added
