Wiki Page Content

Differences between revisions 3 and 4
Revision 3 as of 2011-04-19 17:18:42
Size: 558
Editor: SheenaSmith
Comment: minor change
Revision 4 as of 2013-08-08 16:59:40
Size: 976
Editor: RyanGordon
Comment: Improved docs
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:
If the program is running under a debugger this function will trigger a breakpoint. It is typically used temporarily during debugging or with other error handling. If the program is running under a debugger this function will trigger a breakpoint. It is typically used temporarily during debugging or with other error handling. Note that if a debugger isn't running, on some platforms this can terminate your application.

This isn't actually a function, but rather a macro. The intention is that the debugger will stop on exactly this line of code instead of somewhere inside the SDL library. As such, [[CategoryAssertions|the assertion facility]] uses this so that the debugger stops on the exact line of code where an [[SDL_assert]] failed.

SDL_TriggerBreakpoint

Use this function to trigger a breakpoint during debugging.

Syntax

void SDL_TriggerBreakpoint(void)

Code Examples

You can add your code example here

Remarks

If the program is running under a debugger this function will trigger a breakpoint. It is typically used temporarily during debugging or with other error handling. Note that if a debugger isn't running, on some platforms this can terminate your application.

This isn't actually a function, but rather a macro. The intention is that the debugger will stop on exactly this line of code instead of somewhere inside the SDL library. As such, the assertion facility uses this so that the debugger stops on the exact line of code where an SDL_assert failed.


CategoryAPI, CategoryAssertions

None: SDL_TriggerBreakpoint (last edited 2013-08-08 16:59:40 by RyanGordon)

(Page Info.)
Feedback
Please include your contact information if you'd like to receive a reply.
Submit