Search found 5 matches

by phileee
Mon Jan 25, 2010 10:37 am
Forum: devkitARM
Topic: Just upgraded to latest devkit arm and...
Replies: 1
Views: 3885

Just upgraded to latest devkit arm and...

Hi, following on from my recent problems with the Yagarto toolchain, I have upgraded to the latest devkitarm release. unfortunately I get many linker errors, including the undefined reference to __dso_handle. my linker output is below... obj/system_overview.o: In function `global constructors keyed ...
by phileee
Mon Jan 25, 2010 9:15 am
Forum: Bug Reports
Topic: undefined reference to '__dso_handle' problem
Replies: 3
Views: 8528

Re: undefined reference to '__dso_handle' problem

Hi, thanks both for your replies. I hadn't fully appreciated that the yagarto tool chain was using an older modified devkitarm toolchain. My situation is simple, I am trying to get a JTAG debug module working with the output from a GNU compiler. I will have a look at the latest devkitarm and see if ...
by phileee
Fri Jan 22, 2010 10:00 am
Forum: Bug Reports
Topic: undefined reference to '__dso_handle' problem
Replies: 3
Views: 8528

undefined reference to '__dso_handle' problem

I have just decided to try and update my gnu arm toolchain so that I have a coretex M3 compatible compiler setup working before my new project starts. I have downloaded the yagarto toolchain which uses: binutils: 2.20, gcc: 4.4.2, newlib: .18.0, gdb:7.0.1. I have managed to get my existing code to c...
by phileee
Mon Nov 10, 2008 12:19 pm
Forum: devkitARM
Topic: Dynamic memory checking
Replies: 0
Views: 2894

Dynamic memory checking

Dear all, I am currently investigating dynamic memory monitoring on my arm target. The application code is large, complicated, and uses a lot of memory allocations and deallocations using the "new" and "delete" operators. Does the compiler include any overloaded operators which m...
by phileee
Mon Sep 22, 2008 4:12 pm
Forum: devkitARM
Topic: Catching exceptions
Replies: 1
Views: 3491

Catching exceptions

Hi All, I am hoping that someone can point out my mistake... I am trying to catch exceptions in order to debug a problem where my app seems to crash.. I am suspecting that memory is not being released, so I am using: try { something created with "new" } catch () { print a debug message. } ...