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

[Joerg Wunsch]

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.
-- 
cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)