[strongSwan-dev] charon immediately killed when attaching with gdb

[Ansis Atteka]

After commenting out code that sets SIGINT handler in the charon.c file the
charon daemon does not exit early any more. I bet that charon somehow
consumes SIGINT signal that was actually addressed to GDB (this is how gdb
interrupts inferior process).



On 29 October 2013 14:04, Ansis Atteka <ansisatteka at gmail.com> wrote:

> I tried to attach to charon with following gdb command (as recommended in
> one of the older threads in this mailing list):
> gdb /usr/lib/strongswan/charon <pid>
>
> but charon is immediately killed after I try to interrupt it second time
> (ctrl+c). I am suspicious that signal handlers somehow get into way.
>
> Has anyone had any success with debugging charon with GDB? Am I missing
> some preparation steps?
>
> Both ubuntu 13.04 and 13.10 are affected by this.
>
> Thanks,
> Ansis
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.strongswan.org/pipermail/dev/attachments/20131029/4d0e0482/attachment.html>