[m-dev.] Stack dump not available in this grade.

Paul Bone pbone at csse.unimelb.edu.au
Wed Jan 6 10:57:13 AEDT 2010

On Wed, Jan 06, 2010 at 08:54:46AM +1100, Zoltan Somogyi wrote:
> > Am I misunderstanding asm_fast.gc.decldebug or do I need an extra flag or grade
> > component to convince Mercury that it can do this.
> If you compile the whole program in a debugging grade, including
> asm_fast.gc.decldebug, you should get a stack dump when running the program
> outside the debugging. If you compile only some modules in a debugging grade,
> but the program itself is in a nondebugging grade (which is possible, in fact
> it was a design objective for it to be possible), then you will not get a stack
> dump when running the program outside the debugger, but running the program
> inside the debugger, the debugger will generate a best-effort (usually partial)
> stack dump.

I spoke with Ian over coffee yesterday.  We think it's most-likely that my
workspace wasn't clean enough when I rebuilt files in the debugging grade.  I
havn't verified this yet.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 489 bytes
Desc: Digital signature
URL: <http://lists.mercurylang.org/archives/developers/attachments/20100106/832a6d90/attachment.sig>

More information about the developers mailing list