Re: [osg-users] [vpb] How to debug VPB step by step
Hi Wang, On Wed, Dec 1, 2010 at 1:58 AM, wang junchao wangjuncha...@126.com wrote: Thank you for your reply. But maybe I didn't make myself understood. As you know, reading source code is a very complex and boring work. If you a programmer reading source is the single most important activity you'll ever do. Yes it's complex, but that's our lot. If we wanted an easy life we'd stack shelves at the local shop ;-) So my question is that : can I input a commandline like osgdem -t -.. d.. - o output.ive and trace the execution of the program step by step like the Visual Studio's debug mode ? I haven't used VisualStudio for a decade but I'd guess it still allows you to specify command line options when running apps. You should look at the docs of VisualStudio as this really isn't an OSG/VPB question. As a general note I'd add that the OSG/VPB build system names debug builds of libs and executables with a d postfix, so you'd use osgdemd when debugging. Robert. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] [vpb] How to debug VPB step by step
Hi Robert, Thank you for your reply. But maybe I didn't make myself understood. As you know, reading source code is a very complex and boring work. So my question is that : can I input a commandline like osgdem -t -.. d.. - o output.ive and trace the execution of the program step by step like the Visual Studio's debug mode ? Thank you again for your reply! Cheers, wang -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=34284#34284 ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] [vpb] How to debug VPB step by step
On 1/12/10 12:58 , wang junchao wrote: Thank you for your reply. But maybe I didn't make myself understood. As you know, reading source code is a very complex and boring work. So my question is that : can I input a commandline like osgdem -t -.. d.. - o output.ive and trace the execution of the program step by step like the Visual Studio's debug mode ? You can do that with gdb easily. You'll need a VPB build with debug symbols and maybe some front-end to gdb to make it pretty. /ulrich ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] [vpb] How to debug VPB step by step
Hi, It isn't exactly what you are after, but you can set the OSG_NOTIFY_LEVEL to debug and that will give you a decent idea of what is happening. Having said that, I really do think the be option is to do the 'really boring' work and step through the execution with a debugger. I have done exactly this with VPBMaster and osgdem many times to gain a good understanding of how it works. It might be slow but it really is the only way you will really get to grips with what I happening. Cheers, Brad -Original Message- From: osg-users-boun...@lists.openscenegraph.org [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of wang junchao Sent: Wednesday, 1 December 2010 9:58 AM To: osg-users@lists.openscenegraph.org Subject: Re: [osg-users] [vpb] How to debug VPB step by step Hi Robert, Thank you for your reply. But maybe I didn't make myself understood. As you know, reading source code is a very complex and boring work. So my question is that : can I input a commandline like osgdem -t -.. d.. - o output.ive and trace the execution of the program step by step like the Visual Studio's debug mode ? Thank you again for your reply! Cheers, wang -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=34284#34284 ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org DISCLAIMER:--- This e-mail transmission and any documents, files and previous e-mail messages attached to it are private and confidential. They may contain proprietary or copyright material or information that is subject to legal professional privilege. They are for the use of the intended recipient only. Any unauthorised viewing, use, disclosure, copying, alteration, storage or distribution of, or reliance on, this message is strictly prohibited. No part may be reproduced, adapted or transmitted without the written permission of the owner. If you have received this transmission in error, or are not an authorised recipient, please immediately notify the sender by return email, delete this message and all copies from your e-mail system, and destroy any printed copies. Receipt by anyone other than the intended recipient should not be deemed a waiver of any privilege or protection. Thales Australia does not warrant or represent that this e-mail or any documents, files and previous e-mail messages attached are error or virus free. -- ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
[osg-users] [vpb] How to debug VPB step by step
Hi, As VPB has a large number of codes, it is very hard for me to trace it step by step by just reading the code using sourceInsight. Does anybody have any advice for debugging it step by step? And the same problem for OSG, do I have to rebuild all the libraries and tried it to make sure that the source code is OK? Thanks for your advice. Thank you! Cheers, wang -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=34180#34180 ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] [vpb] How to debug VPB step by step
Hi Wang, If you want to use debug info when running in a debugger you'll need to compile apps and libs under debug. Under Windows you have no option but to do compile everything under debug because of the brain nature of the way that things are done by VS, under all other platforms you can mix debug and optimized builds, but... if you want the debug info then you'll obviously need to compile under debug. Robert. On Sun, Nov 28, 2010 at 1:31 AM, wang junchao wangjuncha...@126.com wrote: Hi, As VPB has a large number of codes, it is very hard for me to trace it step by step by just reading the code using sourceInsight. Does anybody have any advice for debugging it step by step? And the same problem for OSG, do I have to rebuild all the libraries and tried it to make sure that the source code is OK? Thanks for your advice. Thank you! Cheers, wang -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=34180#34180 ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
