Stack trace for Plugin Errors?

I am recently developing a plugin, and some NullPointerException seem to be happening.
I am working on debugging the plugin, but I think providing stack trace when reporting a plugin error would be nice.
I'm using OBVE v1.5.3.9.

Can't you just run the plugin in a debugger?
A dead easy alternative would be to add a global exception handler to the plugin & save the stack traces yourself.

I don't think off the top of my head I can pull in stack traces from an external proxied assembly easily, but I can certainly test this easily enough.

@leezer3 Thank you! I've fixed the problem. It was quite stupid.
BTW How can I debug a plugin? Do I need to link a debugger to openBVE.exe?

my guess is yes. that would be the most logical idea. try to get one that's 32x not 64x or 86x, those tend to crash. at least for myself anyways. maybe a different story on your computer. or i am talking crap, this whole system modifications topic is not my strong point at all 

With Visual Studio, all you should need to do is copy your output plus PDB to the train folder, launch openBVE with the train and attach to the running openBVE process.