[Issue 13727] std.stdio.File not thread-safe

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 Iain Buclaw changed: What|Removed |Added Priority|P1 |P2 --

[Issue 13727] std.stdio.File not thread-safe

2021-01-22 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #22 from Dlang Bot --- @WalterBright updated dlang/dmd pull request #5747 "fix Issue 13727 - std.stdio.File not thread-safe" fixing this issue: - fix Issue 13727 - std.stdio.File not thread-safe https://github.com/dlang/dmd/pull/5747 --

[Issue 13727] std.stdio.File not thread-safe

2019-05-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #21 from Dlang Bot --- dlang/dmd pull request #9911 "Workaround issue 13727 only for DigitalMars CRuntime" was merged into master: - 97c4d5e0b2719a29a1ce1c617d77fac3d9f86c73 by Jonathan Marler: Workaround issue 13727 only for

[Issue 13727] std.stdio.File not thread-safe

2019-05-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #20 from Dlang Bot --- @marler8997 created dlang/dmd pull request #9911 "Workaround issue 13727 only for DigitalMars CRuntime" mentioning this issue: - Workaround issue 13727 only for DigitalMars CRuntime

[Issue 13727] std.stdio.File not thread-safe

2019-05-28 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #19 from Dlang Bot --- dlang/dmd pull request #9907 "Workaround issue 13727 (std.stdio.File not thread-safe)" was merged into master: - 9f7229407b56fef77dfcca50f2d3b41535fac34c by Jonathan Marler: Workaround issue 13

[Issue 13727] std.stdio.File not thread-safe

2019-05-28 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #18 from Dlang Bot --- @marler8997 created dlang/dmd pull request #9907 "Workaround issue 13727 (std.stdio.File not thread-safe)" mentioning this issue: - Workaround issue 13727 https://github.com/dlang/dmd/pull/9907 --

[Issue 13727] std.stdio.File not thread-safe

2019-05-28 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 Jonathan Marler changed: What|Removed |Added CC||johnnymar...@gmail.com --- Comment #17

[Issue 13727] std.stdio.File not thread-safe

2018-04-02 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 Seb changed: What|Removed |Added CC||greensunn...@gmail.com ---

[Issue 13727] std.stdio.File not thread-safe

2018-03-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #15 from Steven Schveighoffer --- (In reply to Steven Schveighoffer from comment #14) > It seems to be passing more frequently, but still seems to have issues: I take it back, it seems this is the only time the

[Issue 13727] std.stdio.File not thread-safe

2018-03-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #14 from Steven Schveighoffer --- It seems to be passing more frequently, but still seems to have issues: https://auto-tester.puremagic.com/show-run.ghtml?projectid=1=3072904=true Logged output: Test

[Issue 13727] std.stdio.File not thread-safe

2018-03-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #13 from Walter Bright --- (In reply to Steven Schveighoffer from comment #12) > This was pulled in May 2016, so I'm assuming dmd release has been > updated with new snn.lib? The test case passes, so yes. > In

[Issue 13727] std.stdio.File not thread-safe

2018-03-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #12 from Steven Schveighoffer --- (In reply to Walter Bright from comment #11) > (In reply to Vladimir Panteleev from comment #8) > > https://github.com/DigitalMars/dmc/pull/2 (access required) > > This was pulled.

[Issue 13727] std.stdio.File not thread-safe

2018-03-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #11 from Walter Bright --- (In reply to Vladimir Panteleev from comment #8) > https://github.com/DigitalMars/dmc/pull/2 (access required) This was pulled. --

[Issue 13727] std.stdio.File not thread-safe

2018-02-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 Steven Schveighoffer changed: What|Removed |Added See Also|

[Issue 13727] std.stdio.File not thread-safe

2017-12-09 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 Walter Bright changed: What|Removed |Added See Also|

[Issue 13727] std.stdio.File not thread-safe

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 det <2k...@gmx.net> changed: What|Removed |Added CC||2k...@gmx.net --

[Issue 13727] std.stdio.File not thread-safe

2016-06-29 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 ZombineDev changed: What|Removed |Added Keywords||safe

[Issue 13727] std.stdio.File not thread-safe

2016-06-23 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 Jack Stouffer changed: What|Removed |Added CC||j...@jackstouffer.com

[Issue 13727] std.stdio.File not thread-safe

2016-05-09 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #9 from Walter Bright --- Adding test case: https://github.com/dlang/dmd/pull/5747 --

[Issue 13727] std.stdio.File not thread-safe

2015-10-07 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 Vladimir Panteleev changed: What|Removed |Added Keywords||pull ---

[Issue 13727] std.stdio.File not thread-safe

2014-11-13 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 Steven Schveighoffer schvei...@yahoo.com changed: What|Removed |Added CC|

[Issue 13727] std.stdio.File not thread-safe

2014-11-13 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #3 from Vladimir Panteleev thecybersha...@gmail.com --- (In reply to Steven Schveighoffer from comment #2) I'm going to throw a shot in the dark out here, and say it's an issue with DMC runtime. Which means it's really a problem with

[Issue 13727] std.stdio.File not thread-safe

2014-11-13 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #4 from Steven Schveighoffer schvei...@yahoo.com --- (In reply to Vladimir Panteleev from comment #3) (In reply to Steven Schveighoffer from comment #2) I'm going to throw a shot in the dark out here, and say it's an issue with DMC

[Issue 13727] std.stdio.File not thread-safe

2014-11-13 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #5 from Vladimir Panteleev thecybersha...@gmail.com --- (In reply to Steven Schveighoffer from comment #4) Oh god! More locks :) Assuming we don't need to lock for the actual I/O operations (read/write), I think the impact for locking

[Issue 13727] std.stdio.File not thread-safe

2014-11-13 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #6 from Vladimir Panteleev thecybersha...@gmail.com --- I strongly believe we should fix the issue in DMC. BTW, I agree in principle, but I don't know how realistic this is, considering it's closed-source and I don't know how hard or

[Issue 13727] std.stdio.File not thread-safe

2014-11-13 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 Steven Schveighoffer schvei...@yahoo.com changed: What|Removed |Added CC|

[Issue 13727] std.stdio.File not thread-safe

2014-11-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 Vladimir Panteleev thecybersha...@gmail.com changed: What|Removed |Added See Also|

[Issue 13727] std.stdio.File not thread-safe

2014-11-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727 --- Comment #1 from Vladimir Panteleev thecybersha...@gmail.com --- Note that even though the above example has all threads reading from the same file, this doesn't matter, as the problem occurs even when accessing distinct files. --