Problem sending program a signal on hitting breakpoint - an anomaly?

Problem sending program a signal on hitting breakpoint - an anomaly?

[K]

I've being trying to run commands that will deliver a signal to the inferior
upon a breakpoint hit:

b <func>
> Breakpoint 1, <func>
commands 1
signal SIGSYS
end

unfortunately rather than deliver the signal this triggers the breakpoint again
and so loops.
is this to be expected or an unfortunate 'feature'?
my understanding is that 'signal' is a resumption-invoking command like
cont, step et al, and that the breakpoint will be executed and stepped over.
which if true means gdb is reacting to this signal rather than just
delivering it
as advertised.
is there a workaround for this?

thanks for reading.

Problem sending program a signal on hitting breakpoint - an anomaly?

[K]

ah! the signal is delivered and the program handles it. on its return
gdb announces the breakpoint being hit.
which suggests the breakpointed instruction was not stepped over.

(gdb v13.2, x86-64)

Problem sending program a signal on hitting breakpoint - an anomaly?

[K]

vaxx-induced prions eating my brain!

inserting command
ignore $bpnum 1
does the trick.

replacement question: early in my gdb endeavours I tried to use libgdb.a
but got discouraged by the entanglement with other libraries it needed
linking with
such as libreadline.a.
is there any plan to make a single library available, static or dynamic?

thanks in advance.