Re: [avrdude-dev] [bug #41292] Crash when uploading with JTAGICE3

[guyzmo]

Hi,

On Tue, Jan 21, 2014 at 06:39:01PM +0100, Joerg Wunsch wrote:
> As anonymous wrote:
> > on the ICSP/ISP header, I'm getting the following error, and the flasher is
> > stuck with the
> > "flashing status" led on (core dump attached).
> 
> A coredump is not useful without the binary, and actually even with
> the binary, it only makes sense if there are symbols in it (at least,
> the non-debugging symbols so one can trace the function call stack).
> 
> This doesn't appear to be the case for you:
> 
> >     Reading |                                                    | 0% 
> > 0.00s***
> > glibc detected *** /usr/local/bin/avrdude: free(): invalid next size (fast):
> > 0x0000000000fe8080 ***
> >     ======= Backtrace: =========
> >     /lib/x86_64-linux-gnu/libc.so.6(+0x76d76)[0x7f35a0dacd76]
> >     /lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7f35a0db1aac]
> >     /usr/local/bin/avrdude[0x410957]
> >     /usr/local/bin/avrdude[0x411ddf]
> >     /usr/local/bin/avrdude[0x4122f9]
> >     /usr/local/bin/avrdude[0x4130a5]
> >     /usr/local/bin/avrdude[0x4090b7]
> >     /usr/local/bin/avrdude[0x41be2e]
> >     /usr/local/bin/avrdude[0x404bf2]
> >     /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7f35a0d54ead]
> >     /usr/local/bin/avrdude[0x405659]
> 
> (Note that there are no names inside avrdude here, only for libc.)
> 
> Can you recompile with symbols (at best, with debugging symbols,
> i. e. option -g), and then upload both, the executable as well as the
> coredump file?

> Alternatively, you can of course look into the coredump yourself using:
> 
> gdb /usr/local/bin/avrdude /var/crash/<name of your coredump file>
> 
> and then issue a "bt" command.
> 
> Without that (and without a way for anyone else to reproduce the
> problem), I'm afraid it will be difficult to find this.

sorry for not having done that... though that bug would have been
interesting to investigate, I was on a hurry and I've done something I
did not try for 15 years: rebooting to see if that fixes it.

And it did fix it, I don't get the fault anymore. I promess, next time,
I'll add the gdb backtrace.

Cheers,

-- 
Guyzmo