Hi Marcus,
sorry for the late answer but I was sick.
Mario Lüttich wrote:
I use now the Daily Build and i have new problems. If I start my
program the Error is:
"Managed Debugging Assistant 'LoaderLock' has detected a problem in
'D:\\Projects\Debug\test.exe'.
Additional Information: Attempting managed execution inside OS Loader
lock. Do not attempt to run managed code inside a DllMain or image
initialization function since doing so can cause the application to
hang."
It sound like you are compiling for .NET/CLR in some way, using the /clr
switch. Otherwise you shouldn't get stuff about 'managed' things (which
is MS-speak for their .NET virtual machine doing stuff).
the CLR switch is disabled and doesn't work.
Are you building managed/.net stuff?
Yes it is managed/.net stuff.
If so, can you try doing a regular
win32 exe build? (I know OpenSG works with Java, which is a bit less
intrusive, but I haven't tried .NET yet..)
Compiling a win32 exe does not work. (it's a C# program)
Also, can you provide a stack trace to the function causing that
problem? (it might have some unknown opensg functions in it, if you run
in release, but it'd still be interesting to see what part of the OS
calls OpenSG which then fails.)
No, I have found the problem only with filemon (a tool that shows me the
system calls). And it is a OpenSG problem.
No I found the Problem does not occur if I use opensg in debug mode.
(OSGBaseD.lib OSGSystemD.lib OSGWindowWin32D.lib) I think if my dll
is initialized then the opensg is initialized and opensg sets a thread
lock and the init function is never left.
Hm? The message above seems to indicate a problem in a debug build, but
here you say it does not occur in debug? What is the right thing?
It was a another Daily Build. With the Release 1.6 the Code is working
(without OrthographicCamera (which I need)) with the "Daily Build" I
have the problems.
Please check that you do not call call osginit from DLLMain. That
probably a very bad thing to do. (I'm guessing here..)
I don't write a DLLMain function (automatical generate). I have only
included the OpenSG header file and my DLL tried to load osgbase.dll
(Above mentioned "filemon" showed me that)
If you do, try calling it from a static variable initializer function
outside dllmain, i.e.:
static bool init = osginit(), true;
void dllmain() { .. }
Because dllmain will be called _before_ any static variables are
initialized, and the OS is quite picky about what can be done in there.
(See Win32 SDK docs for DLLMain)
Cheers,
/Marcus
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
Once again, thank you very much for your help
Cheers,
Mario
begin:vcard
fn;quoted-printable:Mario L=C3=BCttich
n;quoted-printable:L=C3=BCttich;Mario
org:MPI for Biophysical Chemistry
adr;quoted-printable;quoted-printable:;;Fa=C3=9Fberg 11;G=C3=B6ttingen;37077;;Germany
email;internet:[EMAIL PROTECTED]
title:Diplom Physiker
tel;work:+49 (0) 551 201 1454
tel;fax:+49 (0) 551 201 1197
version:2.1
end:vcard
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
