Feature Request for Plug-In Developers

lisa · 12th October 2006, 04:22 PM

There's a feature I'd really like to see that would help plug-in developers a lot, and my hope is that it would also be easy to implement.

Right now, it's very difficult to debug plug-ins with AC3D. You can't put a breakpoint in a plug-in--at least not under Windows, I haven't tried other OSes yet--because the exception handler in AC3D traps all exceptions, including user hardware breakpoints.

It would be *super cool* if there were a start-up flag for AC3D that would filter the exceptions and allow breakpoint exceptions to be processed. (asm int 3, SIGTRAP, etc.) This would make it much easier for people writing plug-ins, because it would allow things like ASSERT macros to break into the debugger while AC3D runs.

-Lisa

View Poll Results: What do you think?
I write plug-ins, and this would be a great feature.	4	66.67%
I write plug-ins, but I wouldn't use this feature.	1	16.67%
What the heck is a breakpoint?	1	16.67%
Voters: 6. You may not vote on this poll

12th October 2006, 04:22 PM	#1
lisa Senior Member Professional user Join Date: Mar 2005 Location: Phoenix, AZ Posts: 917	Feature Request for Plug-In Developers There's a feature I'd really like to see that would help plug-in developers a lot, and my hope is that it would also be easy to implement. Right now, it's very difficult to debug plug-ins with AC3D. You can't put a breakpoint in a plug-in--at least not under Windows, I haven't tried other OSes yet--because the exception handler in AC3D traps all exceptions, including user hardware breakpoints. It would be super cool if there were a start-up flag for AC3D that would filter the exceptions and allow breakpoint exceptions to be processed. (asm int 3, SIGTRAP, etc.) This would make it much easier for people writing plug-ins, because it would allow things like ASSERT macros to break into the debugger while AC3D runs. -Lisa