GDB 17.1 / Linux setting limits for the debugged process?

GDB 17.1 / Linux setting limits for the debugged process?

[Basile Starynkevitch]

Hello all,

(this is motivated by https://github.com/RefPerSys/RefPerSys/issues/30 - a bug in a GPL licensed inference engine project coded in C++)

Using GDB 17.1 on an open source software compiled by GCC 16 snapshot (or latest GCC 15) on a Debian/Linux desktop (or laptop), 
how can I set limits (in the https://man7.org/linux/man-pages/man2/getrlimit.2.html sense, for elapsed CPU time limit)
on the debugged process, but not on the GDB 17.1 debugging process?

Regards

PS. Maybe such hint might be useful in the documentation. I am French so not at ease in writing English
-- 

Basile STARYNKEVITCH                    basile AT starynkevitch DOT net
8 rue de la Faïencerie                       http://starynkevitch.net/Basile/  
92340 Bourg-la-Reine                         https://github.com/bstarynk
France                                https://github.com/RefPerSys/RefPerSys
                  https://orcid.org/0000-0003-0908-5250

Re: GDB 17.1 / Linux setting limits for the debugged process?

[Simon Marchi via Gdb]

On 1/26/26 9:08 AM, Basile Starynkevitch wrote:
> Hello all,
> 
> (this is motivated by https://github.com/RefPerSys/RefPerSys/issues/30 - a bug in a GPL licensed inference engine project coded in C++)
> 
> Using GDB 17.1 on an open source software compiled by GCC 16 snapshot (or latest GCC 15) on a Debian/Linux desktop (or laptop), 
> how can I set limits (in the https://man7.org/linux/man-pages/man2/getrlimit.2.html sense, for elapsed CPU time limit)
> on the debugged process, but not on the GDB 17.1 debugging process?

Try to set "prlimit" as the exec-wrapper:

(gdb) set exec-wrapper prlimit --cpu=1234
(gdb) run

Simon