NewLC - Finding Initialized or Uninitialised static data in a DLL - Comments

> Finding Initialized or Uninitialised static data in a DLL

Anonymous — Mon, 05 Feb 2007 20:59:35 +0100

To use the .BAT file in Carbide-c++:
  duplicate the folder named "UIQ 2.1 Phone (ARMI) Release" (or similar) of your Carbide project to a name WITHOUT SPACES (e.g. "ARMISOURCES")
  then copy NM.EXE from C:\symbian\UIQ_21\epoc32\gcc\rm-epoc-pe\bin to ARMISOURCES\SRC folder
  save the .BAT file in ARMISOURCES\SRC folder
  open a DOS box
  enter ARMYSOURCES\SRC folder
  run vsvars32.bat batch file from Visual C++ compiler installation (mine is in ....\Common7\Tools\vsvars32.bat )
  finally, run the .BAT file.

> Finding Initialized or Uninitialised static data in a DLL

euroq — Fri, 13 Oct 2006 22:37:36 +0200

Interestingly enough, the find_statics.bat will actually find more instances of initialized data than the method mentioned in the article (looking for the bss section), as there are some cases where initialized data doesn't create a bss section.

> Finding Initialized or Uninitialised static data in a DLL

Felix — Fri, 26 May 2006 18:33:25 +0200

THANK you, this tool helped me fix my problem within seconds, and it didn't require me to fully understand the why. That's really helpful.

> Finding Initialized or Uninitialised static data in a DLL

Anonymous — Mon, 08 May 2006 17:12:14 +0200

Yes, this batch file is much better than the method proposed by the orignal post. I tried both and this one helped me to find my problem. And it is much faster.

Thanks Ray

> Finding Initialized or Uninitialised static data in a DLL

amine — Fri, 21 Apr 2006 13:09:16 +0200

how can i add this option under carbide thanks

> Finding Initialized or Uninitialised static data in a DLL

Anatoly kardash — Thu, 11 Aug 2005 18:51:56 +0200

There is a simpler method to find the problematic variables (using "nm" utility provided with GCC). I created a simple batch file to find the modifiable statics:

rem ------ start of find_statics.bat ------

@echo off

for /R %%f in (*.o) do ( echo %%f & nm %%f > tmp.txt & find /I " d " < tmp.txt & find /I " b " < tmp.txt & find /I " g " < tmp.txt )

del /f tmp.txt 2> NULL:

rem ------ end of find_statics.bat ------

(Please note that it uses MSWin2K/XP CMD.EXE with Command Extensions enabled. And, of course, it is possible to write much more elegant script using UNIXish utilities :-).

Well, just copy the lines above to, say, find_statics.bat, go to BUILD directory of you application/DLL, and run the batch, e.g.

c:\> cd c:\Symbian\7.0s\Series60_v21\Epoc32\BUILD\MY_APP\GROUP

c:\Symbian\7.0s\Series60_v21\Epoc32\BUILD\MY_APP\GROUP> find_statics.bat

The result will be something like:

c:\Symbian\7.0s\Series60_v21\Epoc32\BUILD\MY_APP\GROUP\MY_APP\THUMB\UREL\GOOD1.o

c:\Symbian\7.0s\Series60_v21\Epoc32\BUILD\MY_APP\GROUP\MY_APP\THUMB\UREL\BAD.o

00000008 d PROBLEMATIC_VARIABLE1

00000004 d PROBLEM_VAR2

c:\Symbian\7.0s\Series60_v21\Epoc32\BUILD\MY_APP\GROUP\MY_APP\THUMB\UREL\GOOD2.o

Good luck!

> Finding Initialized or Uninitialised static data in a DLL

Asmo Soinio — Tue, 26 Jul 2005 14:30:10 +0200

Hi, thanks for the article!

I used this method with Metrowerks CodeWarrior: In Targets, selected settings for ARMI UDEB and added "-save-temps" to Code Generation / Symbian Compiler / Arguments.

The .s-files were generated to epoc32\gcc\bin\

> Finding Initialized or Uninitialised static data in a DLL

Lin Ma — Fri, 24 Dec 2004 10:14:47 +0100

Hi, the problem is that your sdk does not support the keyword "OPTION". As I know, the 6.0 version doesn't, you can't find the keyword in it's sdk ( » Symbian OS v6.1 Edition for C++ » Tools And Utilities » Build Tools Reference » mmp file syntax).

> Finding Initialized or Uninitialised static data in a DLL

Anonymous — Mon, 13 Dec 2004 14:15:20 +0100

I did all the testing on the UIQ toolchain as this is my primary developer platform.

Did you run makmake or bldmake and then a full rebuild using abld?

Did you search you harddrive for any of those file types?

> Finding Initialized or Uninitialised static data in a DLL

Drew Haninger — Sun, 12 Dec 2004 23:34:05 +0100

Does this method work for the UiQ builds ?

I cannot find any .s or .i file after the builds.

thanks Drew

> Finding Initialized or Uninitialised static data in a DLL

Karsten Meier — Thu, 25 Nov 2004 10:56:49 +0100

I have the problem, but only in Series60 v1.2, In Series60 v2.0 it works.

> Finding Initialized or Uninitialised static data in a DLL

Anonymous — Sat, 13 Nov 2004 17:18:08 +0100

Did you put the option key word in the mmp, and then regenerate the build files using bldmake/makmake?

What version of symbian are you using?

> Finding Initialized or Uninitialised static data in a DLL

Anonymous — Sat, 13 Nov 2004 15:20:11 +0100

There is an error when i try to compile. Unrecognize Keyword "OPTION".

How do i resolve this?

Finding Initialized or Uninitialised static data in a DLL

paul — Tue, 14 Sep 2004 15:36:26 +0200

The Symbian operating system does not support the use of writable static data in DLL's. This can be a major problem if your application uses global variables. This article will show you how to find out what is wrong in your code.