Unable to break into a PAM module

Full Name nuncestbibendum@excite.com
Wed Jan 22 15:50:00 GMT 2020

   Thanks, that works too. Mind you, the SSH session is not properly started - I don't know why - but one can break into the relevant PAM module consistently.

-----Original Message-----
From: "Pedro Alves" [palves@redhat.com]
Date: 01/22/2020 08:09 AM
To: "Full Name" <nuncestbibendum@excite.com>, gdb@sourceware.org
Subject: Re: Unable to break into a PAM module

On 1/17/20 10:03 PM, Full Name wrote:
>      Well, I got it to work in the end. I would like to share what I did, in case it could be of use to someone.
>      Just launching the SSH daemon from the debugger and setting breakpoints in the relevant PAM source code file won't usually work. This is because the SSH forks children processes, and gdb seems to unable to follow them properly. And, yes, I tried with the different 'set follow-*' commands in gdb.

For the next time, I suggest also trying "set detach-on-fork off",
and "set schedule-multiple on".

Pedro Alves

More information about the Gdb mailing list