Custom Query (245 matches)
Results (43 - 45 of 245)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#246 | wontfix | Outdated Information about file handles | ||
Description |
If the process connects its stdin/out/err handles to pipes using DosDupHandle?() and then starts a child with spawn*() (perhaps, fork too?), isatty() called in the child one will return 1 for stdin/out/err while they are actually pipes, not character devices any longer. In fact, calling isatty() in the parent process after DosDupHandle?() will continue to return 1 too. My guess is that once LIBC has cached imported file handle information, it is never refreshed. I see these options:
|
|||
#360 | fixed | Path rewriter affected paths cause crashes in forked child | ||
Description |
Involving paths registered in the kLIBC path rewriter causes a crash when doing
In the test case I use paths starting with
Note that if execute the same |
|||
#132 | fixed | Please add a high-mem safe wrapper for DosQueryAppType() | ||
Description |
DosQueryAppType?() is not listed in the high-mem supporting APIs and indeed it acts weird (returncode=87 and appType=0 whatever the real appType is) when being passed a char* as first argument that is located above 512MB. So it would be great, if it a SafeDosQueryAppType?() wrapper could be written and then add it to os2safe.h. |