GNU Arm Embedded Toolchain

Eclipse appcrash if using large elf files

Asked by Thomas Grieger

Hi,

I'm using the 4.7 2012 Q4 release of the toolchain on a WIN7 64 with Eclipse (Indigo Release 2).
Like described in the questions 230922 and 231395 I encounter regular crashes but only with larger (>2.5MB) .elf files.

The suggested fix by reducing the debug level to '-g' works at the moment but as my program is growing so is the elf file.
Will there be a fix for this problem in one the next releases?

Thanks,
Thomas

Question information

Language:
English Edit question
Status:
Answered
For:
GNU Arm Embedded Toolchain Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Terry Guo (terry.guo) said : 		#1

Let me see if I can reproduce this issue.

Revision history for this message
Terry Guo (terry.guo) said : 		#2

I think you mean the regular crash is caused by arm-none-eabi-gdb. Is my understanding right? If so, I can't reproduce it with boards I have, none of my board has big memory system. The best board I have is ST STM32F407VG which has 1MB flash.

Can you please be more specific on following things for me to reproduce?
* What's your target and what kind of gdb server are you using?
* How you use arm-none-eabi-gdb under Eclipse, through some plugin or your own debugger configuration?
* If possible, can you please share an example project of this issue?

Thanks.
Terry

Revision history for this message
Thomas Grieger (t-grieger) said : 		#3

Hi Terry,

you are correct, a crash means that the arm-none-eabi-gdb stops working and shows a windows error message.

We are using a Kinetis K70 (MK70FX512VMJ12 and MK70FN1M0VMJ12) on a board which was designed by us. The connection for debugger consists of a Segger J-Link, the Segger GDB server and the GDB plugin of Eclipse (version 7.0.0.201202111925).

Due to our own investigation we found that the crash is not entirely related to the size of the elf file but to our ethernet stack (FNET). We tried to strengthen our assumption by using another project plus a big display test pattern but it worked even with program sizes above 250kBytes (and elf files bigger than 2.5 MBytes).

Is it possible to get more information from the gdb about the by activating some log functions?
Regarding the example, do you need full source code access or only an elf file? In case of an elf I could send you one which is compatible to the K70 Tower system.

Revision history for this message
Terry Guo (terry.guo) said : 		#4

Hi Thomas,

I have TWR K70F120M board and Segger J-Link. Please send me the elf file that can trigger this issue and instructions to set up such eclipse project. I haven't tried Eclipse and its GDB plugin. My email is <email address hidden>. Thanks.

Revision history for this message
Terry Guo (terry.guo) said : 		#5

This issue is caused by gdb bug http://sourceware.org/bugzilla/show_bug.cgi?id=13568. We shall solve it in next release.

Can you help with this problem?

Provide an answer of your own, or ask Thomas Grieger for more information if necessary.

To post a message you must log in.