Printing Stack Trace is not possible #484

Activity

1. willemneal commented on Feb 11, 2019

   

   willemneal

   on Feb 11, 2019

   Contributor

   More actions

   This is hard because AS has such a minimal runtime and this will probably become provided by wasm when there is exception support. So perhaps this should be a special debug version that does trace the stacks.
2. jtenner commented on Feb 19, 2019

   

   jtenner

   on Feb 19, 2019

   ContributorAuthor

   More actions

   I actually found a solution for this. It was very hacky though.
3. vgrichina commented on Feb 21, 2019

   

   vgrichina

   on Feb 21, 2019

   More actions

   @jtenner what did you end up doing?
4. jtenner commented on Feb 21, 2019

   

   jtenner

   on Feb 21, 2019

   ContributorAuthor

   More actions

   In as-pect I wrote some glue code that runs functions with the following signature:

   type NoPropsNoReturnCallback = () => void;
   

   Then in my glue code, I did stuff like this:

     /**
      * This is a web assembly utility function that wraps a function call in a try catch block to
      * report success or failure.
      *
      * @param {number} pointer - The function pointer to call. It must accept no parameters and return
      * void.
      * @returns {1 | 0} - If the callback was run successfully without error, it returns 1, else it
      * returns 0.
      */
     tryCall(pointer: number): 1 | 0 {
       if (pointer === -1) return 1;
   
       var func = this.wasm!.getFunction(pointer);
       try {
         func();
       } catch (ex){
         this.stack = this.getErrorStackTrace(ex);
         return 0;
       }
       return 1;
     }

   Now in order to LOG the current stack trace, I had to call into javascript to get it, throw an error, then filter the lines that contain wasm in the string.

     /**
      * Gets a log stack trace.
      */
     getLogStackTrace(): string {
       try {
         throw new Error("Get stack trace.");
       } catch (ex) {
         return ex.stack.toString()
           .split("\n")
           .slice(1)
           .filter(wasmFilter)
           .join("\n");
       }
     }

   It was hacky, and I'm not proud of it.
5. vgrichina commented on Feb 21, 2019

   

   vgrichina

   on Feb 21, 2019

   More actions

   @jtenner interesting, so basically WASM runtimes embedded into JS VMs already provide wasm-side stack traces?
6. jtenner commented on Feb 21, 2019

   

   jtenner

   on Feb 21, 2019

   ContributorAuthor

   More actions

   Yes. That was as good as I could get it. I'm currently working on using generated sourcemaps to display more relevant information, but it appears that sourcemaps are broken on the master branch, at least pre-resolver commit.
7. MaxGraey

   added

   question

   on Feb 24, 2019
8. stale commented on Mar 26, 2019

   

   staleBot

   on Mar 26, 2019

   More actions

   This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
9. stale

   added

   stale

   on Mar 26, 2019
10. stale

    closed this as completedon Apr 2, 2019