Package: gdb
Version: 6.4.90.dfsg-1
Severity: normal
When gdb runs a program, it seems to have its own executable opened on
fd#5, and some pipes on fd#3 and fd#4. Though well-behaved programs
should probably not rely on having specific file descriptors on
startup (besides perhaps std{in,out,err}), gdb should close these
after fork and before exec, or set FD_CLOEXEC.-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
