Re: How to debug a segmentation fault?
| From: | tyson andre | Date: | Thu, 30 Jan 2020 02:59:42 +0000 |
| Subject: | Re: How to debug a segmentation fault? | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-108328@lists.php.net to get a copy of this message | ||
> Sorry, I didn't notice
> that https://bugs.php.net/bug.php?id=79194 was already [solved
> and] closed with a similar answer.
In addition to phpspy, a tool I forgot to mention was Phan. (https://github..com/phan/phan)
phan --redundant-condition-detection will enable many of Phan's checks, including
code that looks like a function or method calling itself unconditionally, or with the same args.
I got the idea for adding a check for PhanInfiniteRecursion
(and PhanPossiblyInfiniteRecursionSameParams) after investigating a similar segfault over a year
ago ago
(and considering most of those solutions),
to detect that type of bug before it ran.
https://github.com/phan/phan/blob/master/internal/Issue-Types-Caught-by-Phan.md#phaninfiniterecursion
has an example of what it detects