unresolved dso_handle and aeabi_atexit

Login to reply to this topic.
Fri, 2006-04-07 15:53
Joined: 2005-02-21
Forum posts: 47
Hello,
  I'm building an application for Symbian OS9.1 using Series60 SDKv3 GCCE compiler. I get two errors on linking:
Link Error   : (.text+0xb8): undefined reference to `__aeabi_atexit'
Link Error   : (.text+0xe0): undefined reference to `__dso_handle'

I can't find anything on those functions. Any hint?

Ahti.

Sat, 2006-05-13 11:15
Joined: 2005-09-07
Forum posts: 16
Re: unresolved dso_handle and aeabi_atexit
Same problem. Help, somebody...  Huh

Per aspera ad astra

Mon, 2006-05-15 08:46
Joined: 2005-02-21
Forum posts: 47
Re: unresolved dso_handle and aeabi_atexit

damn, the problem is gone for me but I'm in trouble in remembering what exactlyI did Sad

It must be something in toolchain or in compiler/linker settings etc ...

Ahti.
Tue, 2006-07-04 15:49
Joined: 2005-10-03
Forum posts: 32
Re: unresolved dso_handle and aeabi_atexit
I'm also having the same problems.  Anybody know how to fix this  Huh
Thu, 2006-11-16 03:35
Joined: 2006-11-16
Forum posts: 1
Re: unresolved dso_handle and aeabi_atexit
I have found that this problem can be caused by the use of complex static variables declared in the global or file scope.

If you use a simple static variable such as:

static TInt intVar;
static CImageDecoder* classPointerVar;

Then everything is fine.

If you try something like this:
class CDummyClass;

static CDummyClass;

class CDummyClass
{
// Class declaration
}

Then you will get those errors. In some situations it seems that the compiler is not generating the code to automatically cleanup the statics when the program exits.

I've been using Carbide and carbide has this issue.  Compiling form the command line doesn't show this problem.

Reply With Quote
  • Login to reply to this topic.