public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: nae@forbidden.co.uk To: gdb-gnats@sources.redhat.com Subject: gdb/2459: source_command cannot read from fifos Date: Mon, 19 May 2008 10:58:00 -0000 [thread overview] Message-ID: <20080519105001.29031.qmail@sourceware.org> (raw) >Number: 2459 >Category: gdb >Synopsis: source_command cannot read from fifos >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: external >Submitter-Id: net >Arrival-Date: Mon May 19 10:58:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: nae@forbidden.co.uk >Release: GNU gdb 6.4.90 >Organization: >Environment: Linux 2.6.18-6-k7 gcc version 4.1.2 GDB was configured as "i486-linux-gnu" >Description: Cannot use fifos to pass commands to gdb via -x option, eg using bash syntax as below gdb -x <(echo "set <something>") <program> There is an explicit check in openp for a regular file - can this be changed to also allow a fifo? >How-To-Repeat: Run something like this at a bash prompt: gdb -x <(echo "set height 0") ls >Fix: openp in source.c needs to also allow fifos when checking is_regular_file. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2008-05-19 10:58 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20080519105001.29031.qmail@sourceware.org \ --to=nae@forbidden.co.uk \ --cc=gdb-gnats@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).