Make the exception handler ignore WinDbg breakpoints?

I’m trying to make a breakpoint (in kernel mode) to print some data, and continue execution immediately. I put g (or gc) to the list of commands to execute.

Unfortunately, in some contexts it still breaks into debugger, which prints:
Single step exception - code 80000004 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.

I suspect it happens when there is an exception handler installed on the current stack. How can I make Windbg ignore an existing exception handler and continue execution from breakpoint?

Use of hardware (access) breakpoint did the trick:

ba e 1 address “command”

>Use of hardware (access) breakpoint did the trick:

Nope, spoke too soon. Still stopping.

What works is:

set ‘gc’ command for first chance single-step exception. I did it through WinDbg GUI, but there is an equivalent command.