Decode StackTrace

rcd.guerra

Hi there,

we were unable to decode an obfuscated stack trace.
Firtly, we were using Unicode obfuscation and we realize, as someone advised, it was not supported and then moved to ASCII.
Even with ASCII obfuscation, the StackTrace was not decoded.

What are the main reasons for this ?
Is there any feature restriction regarding the trial version ?

We just need to open the SA tool and paste the encoded stack trace and hit decode, correct ?

Any help would be appreciated!

Thanks,
Ricardo

Brian Donahue

Hi Ricardo,

The stack trace decoding depends on the availability of the map file produced during the SmartAssembly build. To retain map files indefinitely, you must use the mark as released button on the post-build screen. If you do not do this, map files are still retained for 15 days, so the problem must be that the map file could not be found.

If you are using SA on multiple computers, you should put the map files on a network share, otherwise they are only available on the machine on which the build was done. To configure a network share for map files, please see the help.

garethhayter

We create builds, then run final tests, then decide to release or not. Marking a build as 'release' at build time seems backward - how are we to know if it's going to be a release or not?

It would be nice to be mark 'the last build' as a 'release build', after the fact.

Thanks,
Gareth.

Brian Donahue

Hi Gareth,

You have 15 days to decide if you want to release that particular build before SA deletes the map file.

garethhayter

Hi Brian

That's fantastic. Where can I find the list of previous builds? I can't see it anywhere in the SmartAssembly UI.

Thanks,
Gareth.

Brian Donahue

Hi Gareth,

You cannot see a build history from withing the SmartAssembly UI, but this can be done using the SA SDK. There is a VS project in the SmartAssembly program files folder called SmartAssembly.Database. This is a windows forms application that will show your projects and builds.

Brian Donahue

Hi Gareth,

Sorry, the stack trace decoding information is in the SA database, not the map file. The map files are used for automated reporting, which is a slight distinction. Unless you're using a shared SQL database, though, the information is still not available to other developers and you have to decode the stack trace on the machine with which the assembly had been built.

garethhayter

Hi Brian

Thanks. My point still stands - it's not *easy* to retroactively mark a build as 'released'.

Kind regards,
Gareth.