Overview
| Artifact ID: | 11203e8a83616d09e860f745f3d23a5a3cc504e53a780b33091fc284dfc773c7 |
|---|---|
| Ticket: | 6de8494984e49b052d3ad82b8cd7e900b67274b3
Tcl_CreateCommandChannel() documentation bug |
| User & Date: | ralfixx 2019-08-14 13:18:01 |
Changes
- assignee changed to: "nobody"
- closer changed to: "nobody"
- cmimetype changed to: "text/x-fossil-wiki"
- comment changed to:
[https://www.tcl.tk/man/tcl/TclLib/OpenFileChnl.htm#M7] states for Tcl_OpenCommandChannel(): <pre> If an error occurs while opening the channel, [...] In addition, Tcl_OpenCommandChannel leaves an error message in the interpreter's result if interp is not NULL. </pre> The code in generic/TclPipe.c however states that interp cannot be NULL: <pre> Tcl_Channel Tcl_OpenCommandChannel( Tcl_Interp *interp, /* Interpreter for error reporting. Can NOT be NULL. */ </pre> And indeed, calling Tcl_OpenCommandChannel(NULL, ...) dumps core in case of an error when opening the pipeline (e.g. command not found). => Documentation should be adjusted: "interp cannot be NULL". - foundin changed to: "8.6.9"
- is_private changed to: "0"
- login: "ralfixx"
- priority changed to: "5 Medium"
- private_contact changed to: "1d3c95db24e116878d6afed7cf890a89a0effe62"
- resolution changed to: "None"
- severity changed to: "Minor"
- status changed to: "Open"
- submitter changed to: "ralfixx"
- subsystem changed to: "24. Channel Commands"
- title changed to: "Tcl_CreateCommandChannel() documentation bug"
- type changed to: "Bug"