gbadev.org forum archive

This is a read-only mirror of the content originally found on forum.gbadev.org (now offline), salvaged from Wayback machine copies. A new forum can be found here.

Coding > Problem with the 'new' operator in latest devkitarm release?

#93403 - rooter - Tue Jul 18, 2006 11:52 pm

I've recently upgraded to the latest release of devkitarm and have an annoying problem. 'New' is now completely non-functional. I have used this code base across various toolchains over the past couple years with no problems in the past until updating to the latest release. Now the engine locks up whenever 'new' is called no matter what.

Anyone else experienced this problem, know what might be causing it or have a workaround?

Thanks

#93410 - tepples - Wed Jul 19, 2006 12:24 am

Did you try catching any exceptions that new may throw?
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.

#93412 - rooter - Wed Jul 19, 2006 12:36 am

bad_alloc, which is what i figured... what could that mean in terms of the GBA and what between the last version of devkitarm and the new one could have caused that?

EDIT: Give me bad_alloc even with new'ing just a single int. Hm.

#93416 - tepples - Wed Jul 19, 2006 12:51 am

malloc() is the backend of operator new, and it's broken in devkitARM R19. Downgrade to R18 or wait for R20.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.

#93418 - rooter - Wed Jul 19, 2006 1:13 am

tepples wrote:
malloc() is the backend of operator new, and it's broken in devkitARM R19. Downgrade to R18 or wait for R20.


Thanks, didn't know that. malloc seemed to work when I tested it. I'll downgrade for now.

#93447 - rooter - Wed Jul 19, 2006 4:50 am

Thanks, that took care of it.