Stack trace when loading extensions
We've noticed a strange Stack trace when an extension is loaded while another extension is already loaded. In this case I had the UploadScanner extension already loaded and then tried to load the Stepper extensions in Burp v.2.1. See:
It's very weird because it will include a Python Exception in the Error tab of the Stepper extension. But the Stepper extension is a Java extension. Could you maybe deobfuscate that stack trace?
However, so far everything seems to work fine, I'm just not sure where that confusing stack trace is coming from.
Thanks for this report Floyd. Does this issue only occur when using the Stepper extension?
This is my bad. I was hacking at the message controller and message editor functionality in a way other plugins didn't like to get around an issue.
Ill be pushing a fix shortly!
Thanks for the update Corey.