Something like Valgrind might spot some initial problem that doesn't
immediately crash but eventually spirals out of control. It seems to
support ARM linux now:
"20 October 2016: valgrind-3.12.0 is available. This release supports:
X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux,
On Fri, 2016-11-11 at 19:41 +0200, Jaak Ristioja wrote:
> After examining about 10 more core files, these all point to job.c:519
> and job.c:537, similarly to the above:
>
> #0 0x00c2bd74 in child_error (child=0x0, exit_code=0, exit_sig=0,
> coredump=0, ignored=0) at job.c:519
> pre
On Sat, 2016-11-12 at 13:06 +0200, Jaak Ristioja wrote:
> I'm guessing that PATH_MAX is 4096 on most Linux systems, while the stack is
> 8192.
There's no way the stack is so small. Virtually no userspace program
can run with an 8k stack, regardless of whether they use alloca() or
not.
I think
On 11.11.2016 19:41, Jaak Ristioja wrote:
> On 10.11.2016 09:55, Jaak Ristioja wrote:
>> On 09.11.2016 22:58, Paul Smith wrote:
>>> On Wed, 2016-11-09 at 22:42 +0200, Jaak Ristioja wrote:
I have no ARM experience myself. I don't even know where to look for
ABI
documentation. This is
