[Issue 14258] SIGSEGV in dpldocs

2015-06-18 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14258

--- Comment #13 from github-bugzi...@puremagic.com ---
Commit pushed to stable at https://github.com/D-Programming-Language/dlang.org

https://github.com/D-Programming-Language/dlang.org/commit/cc8d8123ef0dff1705e729d1faad2b710639771f
Merge pull request #925 from s-ludwig/master

--


[Issue 14258] SIGSEGV in dpldocs

2015-03-11 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14258

Vladimir Panteleev  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #12 from Vladimir Panteleev  ---
Yes, I confirmed it's fixed in git.

--


[Issue 14258] SIGSEGV in dpldocs

2015-03-11 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14258

--- Comment #11 from Walter Bright  ---
(In reply to github-bugzilla from comment #10)
> Commit pushed to master at
> https://github.com/D-Programming-Language/dlang.org
> 
> https://github.com/D-Programming-Language/dlang.org/commit/
> cc8d8123ef0dff1705e729d1faad2b710639771f
> Merge pull request #925 from s-ludwig/master
> 
> Issue 14258 - SIGSEGV in dpldocs

Does this mean this can be marked as fixed?

--


[Issue 14258] SIGSEGV in dpldocs

2015-03-10 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14258

--- Comment #10 from github-bugzi...@puremagic.com ---
Commit pushed to master at https://github.com/D-Programming-Language/dlang.org

https://github.com/D-Programming-Language/dlang.org/commit/cc8d8123ef0dff1705e729d1faad2b710639771f
Merge pull request #925 from s-ludwig/master

Issue 14258 - SIGSEGV in dpldocs

--


[Issue 14258] SIGSEGV in dpldocs

2015-03-10 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14258

--- Comment #9 from Sönke Ludwig  ---
Hm, you are right of course, totally forgot about that.

--


[Issue 14258] SIGSEGV in dpldocs

2015-03-10 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14258

--- Comment #8 from Vladimir Panteleev  ---
On Linux, what usually happens upon attempting to commit (write to) a page that
has been overcommitted (COW of a zero page), when there are no free pages and
no pages to swap or reclaim, the OOM killer is invoked and the most
memory-hungry process dies with a SIGSEGV.

--


[Issue 14258] SIGSEGV in dpldocs

2015-03-10 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14258

--- Comment #7 from Sönke Ludwig  ---
My systems all have limited swap space - what would the OS do when all that
memory is filled with data (note that the array that is piled up is actually
written to)?

I've added the termination conditions now and will file a PR as soon as the new
DDOX version is up on code.dlang.org.

--


[Issue 14258] SIGSEGV in dpldocs

2015-03-10 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14258

--- Comment #6 from Vladimir Panteleev  ---
Except for address space exhaustion, OutOfMemoryError will never realistically
occur in any OS with overcommit.

--


[Issue 14258] SIGSEGV in dpldocs

2015-03-10 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14258

--- Comment #5 from Sönke Ludwig  ---
The crash occurs because the proper termination conditions for recursive macro
calls are not implemented. I'll do that.

There could be an additional issue in the GC/array implementation, though, as I
would have expected an OutOfMemoryError instead of a segmentation fault (except
if the segfault is caused by a stack overflow).

--


[Issue 14258] SIGSEGV in dpldocs

2015-03-09 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14258

--- Comment #4 from Vladimir Panteleev  ---
I haven't actually reduced it, just added some debug logging to dpldocs and
looked with git blame.

--


[Issue 14258] SIGSEGV in dpldocs

2015-03-09 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14258

Martin Nowak  changed:

   What|Removed |Added

 CC||c...@dawg.eu

--- Comment #3 from Martin Nowak  ---
Thanks for reducing this, will try to fix it soon.

--


[Issue 14258] SIGSEGV in dpldocs

2015-03-09 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14258

Walter Bright  changed:

   What|Removed |Added

 CC||bugzi...@digitalmars.com

--- Comment #2 from Walter Bright  ---
(In reply to Vladimir Panteleev from comment #1)
> I think it's having trouble with this expansion:
> 
> LIX=$(LI $1)$(LIX $+)

That idiom is used regularly.

--


[Issue 14258] SIGSEGV in dpldocs

2015-03-07 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14258

--- Comment #1 from Vladimir Panteleev  ---
I think it's having trouble with this expansion:

LIX=$(LI $1)$(LIX $+)

Its usage might have been introduced here:

https://github.com/D-Programming-Language/phobos/commit/743303055d74cdd3e482a3af3e99af93755f3af6

--