CF app running but not executing

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an image that includes CF. when I run an application it seems to be
executing but does not do anything and then exits - even if a
Console.WriteLine is run there is no output. below is debug from a sample run,
Any Ideas as to what might be going wrong and how to identify the problem
greatly appreciated - NB there is nothing wrong with the exe file as we can
run it on other images:

0x83ecdab0: FATFS!FAT_GetFileAttributesW(\LMemDebug.DLL) returned 0xffffffff
(2)PI:Perfo
0x83d28628: A
0x83ff13e0: ATAPI:ReadBuffus: 58ector

0x83ecdab0: FATFS!FAT_CreateFileW(\LMemDebug.DLL) returned 0x0 (2)0x8
0x83c49160: ATAPI:ReadBuffer Entry

T_GetFileAttributesW(\mscoree.dll) returned 0xffffffff (2)
0x83ecdab0:
FATFS!FAT_
CreateFileW(\mscoree.dll) returned 0x0 (2)
0x83ecdab0: >>> Loading module
mscoree.dll at address 0x033E0000-0x033E6000 (RW data at
0x01F09000-0x01F09124)
0x83ecdab0: >>> Loading module filesplitter.exe at address
0x14010000-0x14018000
0x83ecdab0: >>> Loading module mscoree1_0.dll at address
0x03390000-0x033DF000 (RW data at 0x01F05000-0x01F07FE0)
0x83ecdab0: Process filesplitter.exe loaded Module mscoree1_0.dll without
freein
g it before process exit
0x83ecdab0: Winsock: WSAStartup and WSACleanup have not been
called--potential memory leak!
0x83ecdab0: <<< Unloading module mscoree1_0.dll at address
0x03390000-0x033DF000 (RW data at 0x01F05000-0x01F07FE0)
0x83ecdab0: Process filesplitter.exe loaded Module ole32.dll without freeing
it before process exit
0x83ecdab0: WARNING: Cleaned up 1 leaked registry handles for process
0xE3C46952
0x83ecdab0: <<< Unloading module filesplitter.exe at address
0x14010000-0x14018000
0x83ecdab0: <<< Unloading module mscoree.dll at address
0x033E0000-0x033E6000 (RW data at 0x01F09000-0x01F09124)
 
It is possible that your device doesn't support console. Thus instead of
Console.WriteLine try to implement something different - e.g. try to
create file or show MessageBox to make sure that application was
executed correctly.
 
I have already tried that.

The problem seems to be directly related to the inclusion or not of the
Standard SDK.

Ie if I include the Standard SDK then all is OK, if not then I see this
problem. Unfortunately the SDK requires Professional license and I only have
Core.
 
Standard SDK is just a collectionm of other catalog components. You're
missing something basic. Do you have toolhelp in your image? Imgdecmp?

-Chris
 
imgdecmp.dll is included and I just tried a new build including "Core OS
Services->Debugging Tools->Toolhelp API" but to no avail.

Dylan.
 
Well then process of elimiantion is the way to go.

1. Build an image that works.
2. Archive ceconfig.h
3. Build a Core image that doesn't
4. Archive ceconfig.h
5. Diff #2 and #4
6. Add one item from the diff in #5 to the core build.
7. Rebuild and test
8. Goto #6 until it works

The alternate is to run depends.exe on the CF binaries to see if you can
determine everything it's expecting. That's a lot more work though, as you
have to verify all entry points of all dependencies.

-Chris
 
Im not sure how to achieve step 6. Bear in mind that I am only used to using
the PB interface - not manipulating files directly.

If I edit ceconfig.h directly I lose the changes when I build. How do I add
an item based on inspection of ceconfig.h?

I have tried building
 
6. Find the corresponding item for one of the differences in the catalog and
add it to the build.

Paul T.
 
Problem solved buy includeing SOAPTK_CLIENT. It seems that it was XML
related problem. Thanks to all for your help.

By the way it is much easier to inspect and compare the <platform>.plg files
as the SYSGEN_ names correspond directly to the Catalog names.
 
Back
Top