https://issues.dlang.org/show_bug.cgi?id=23654
--- Comment #8 from kdevel ---
(In reply to anonymous4 from comment #6)
> Doesn't fork break the GC heap? If you want to allocate from GC after fork,
> it may not work.
The corruption does not require a previous call to fork.
--
https://issues.dlang.org/show_bug.cgi?id=23654
--- Comment #7 from kdevel ---
Created attachment 1888
--> https://issues.dlang.org/attachment.cgi?id=1888&action=edit
D-Program execv-recur.d demonstrating the memory corruption
//
// execv-recur.d
// 2023-08-29 stvo
//
// disable the GC with
//
https://issues.dlang.org/show_bug.cgi?id=23609
--- Comment #5 from Robert Schadek ---
THIS ISSUE HAS BEEN MOVED TO GITHUB
https://github.com/burner/bugzilla_migration_test/issues/35
DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO
GITHUB
--
https://issues.dlang.org/show_bug.cgi?id=23609
--- Comment #4 from Robert Schadek ---
THIS ISSUE HAS BEEN MOVED TO GITHUB
https://github.com/burner/bugzilla_migration_test/issues/34
DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO
GITHUB
--
https://issues.dlang.org/show_bug.cgi?id=23609
--- Comment #3 from Robert Schadek ---
THIS ISSUE HAS BEEN MOVED TO GITHUB
https://github.com/burner/bugzilla_migration_test/issues/33
DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT THIS ISSUE HAS BEEN MOVED TO
GITHUB
--
https://issues.dlang.org/show_bug.cgi?id=23609
--- Comment #2 from Robert Schadek ---
THIS ISSUE HAS BEEN MOVED TO GITHUB
https://github.com/burner/bugzilla_migration_test/issues/32
DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT THIS ISSUE HAS BEEN MOVED TO
GITHUB
--
