Philip Taylor schrieb:
Hi,
Could one of two things:
a) A multi threaded DLL deleting a string created by a static DLL (or vice
versa) - a symptom of using different memory models. In an ideal world, its a
good idea to let the DLL/EXE that creates an object, delete that object so that
this situation does not occur. This ensures that the creation and destruction
mechanisms use the same memory menagment scheme.
This could well be. Maybe the osg-makefile links to the wrong
standard-library.
b) Your build is mixing VS7 DLLs with VS 8 style compilation. The string
implementation is different between the two.
This is definitely not the case, as I don´t use VC but MinGW.
Thank you, I will have a look to which libs osg is linking.
Regards,
Andreas
Regards
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Andreas Goebel
Sent: 12 November 2006 21:13
To: osg users
Subject: [osg-users] Warning on MinGW whenever osg uses a string
Hi,
whenever osg uses a string, I run into a breakpoint-trap.
This is the backtrace of osgviewer:
Program received signal SIGTRAP, Trace/breakpoint trap.
0x7c911231 in _libkernel32_a_iname ()
(gdb) warning: HEAP[osgviewer.exe]:
warning: Invalid Address specified to RtlFreeHeap( 003D0000, 101CC300 )
backtrace
#0 0x7c911231 in _libkernel32_a_iname ()
#1 0x7c97c943 in _libkernel32_a_iname ()
#2 0x7c97cd80 in _libkernel32_a_iname ()
#3 0x7c97df66 in _libkernel32_a_iname ()
#4 0x7c95a5d0 in _libkernel32_a_iname ()
#5 0x7c9368ad in _libkernel32_a_iname ()
#6 0x77bfc2de in _libkernel32_a_iname ()
#7 0x004050a5 in operator delete(void*) ()
#8 0x0043085c in std::string::_Rep::_M_destroy(std::allocator<char>
const&) ()
#9 0x0043152b in std::string::assign(std::string const&) ()
#10 0x0043340d in std::string::operator=(std::string const&) ()
#11 0x00412fe0 in osg::ApplicationUsage::setApplicationName(std::string
const&)
(this=0x101e0060, [EMAIL PROTECTED])
at ../../../include/osg/ApplicationUsage:38
#12 0x004014c4 in main (argc=1, argv=0x5ad2420) at ../osgviewer.cpp:24
I don´t know if this is harmful, but at least it´s quite bothering when
debugging a program (as it stops whenever a string is used within the
osg-library).
Any ideas how to solve / avoid this?
Regards,
Andreas
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
