Ticket #59 (closed enhancement: fixed)

Opened 10 years ago

Last modified 10 years ago

aesop backtrace function

Reported by: carns Owned by: dkimpe
Priority: don't know Component: aesop functions
Version: Keywords:
Cc:

Description

(copied from ​http://trac.mcs.anl.gov/projects/triton/ticket/174)

It would be useful if the auto-generated aesop code could track its call stack so that a "backtrace" could be display on error or a crash. The standard stack trace isn't very meaningful because the aesop code will look like it has a random stack.

Change History

comment:1 Changed 10 years ago by carns

This is implemented in the aesop_get_stack() and aesop_print_stack() functions in resource.h.

We just need the following:

  • add a test program (part of make check) to exercise the functionality
  • convert aesop_get_stack() to use normal char* type instead of triton_string_t

comment:2 Changed 10 years ago by harms

Added a test program to the repo.

comment:3 Changed 10 years ago by dkimpe

  • Owner set to dkimpe
  • Status changed from new to assigned

comment:4 Changed 10 years ago by dkimpe

  • Status changed from assigned to closed
  • Resolution set to fixed

Fixed in 28f8bb16eae3244a7e2bdf8522029292e70dab12

Note: See TracTickets for help on using tickets.