dhcpcd-discuss

On Thu, 26 May 2016 22:45:33 +0100
Roy Marples <roy@xxxxxxxxxxxx> wrote:

> On 2016-05-26 21:12, Neal P. Murphy wrote:
> > (Had to figure out how to make the build system use '-g'....) This is
> > dhcpcd.trunk (even though it looks like 6.11.0).
> > 
> > OK. Built with -g. Have gdb on the target. Run with and still get the
> > memory corruption; even gdb is hung up. So run it without gdb, then
> > attach gdb to dhcpcd once it's hung, and use 'gcore' to generate a
> > coredump. Looks like something is thoroughly stomping on the stack.
> > This is all I get:
> 
> I'm not entirely sure what to make of that really.
> Can you run dhcpcd using valgrind to try and track the memory error as 
> that's the best tool for this I find.
> 
> Roy

Nor am I, other than the memory error *seems* to happen asynchronously; it doesn't always happen at the same place in the sources.

I'll DL and build valgrind for the F/W. ... Hmmm. Wants an unstripped ld-2.18.so. It's busy. I'll just rename it and copy the new one. Whoops. Guess I'll boot the 'rescue' and put it back. I *knew* this was going to happen. Had plenty of time not to hit <ENTER>, too. :)

Smoke if you got 'em; it'll be a while.

N