Debugging ASCEND: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
Also to be added here: | Also to be added here: | ||
* about test suites | * about test suites (see [[CUnit]]) | ||
* about Buildbot (currently inactive/offline) | * about Buildbot (currently inactive/offline) | ||
* using GDB | * using GDB | ||
* using Valgrind. | * using [[Valgrind]]. | ||
* correct use of SVN during debugging on the trunk | * correct use of SVN during debugging on the trunk | ||
* using 'ascdev' and 'asc4dev' from within your working folder | * using 'pygtk/ascdev' and 'tcltk/asc4dev' from within your working folder | ||
* possible library wrong-loading issues | * possible library wrong-loading issues: <tt>export LD_LIBRARY_PATH=~/ascend</tt> for example, | ||
[[Category:Development]] | [[Category:Development]] | ||
Revision as of 06:38, 15 February 2011
The content from this page was lost in a recent server failure. We will be working to restore this content as soon as possible.
Reporting a bug
There is a Bug tracker for ascend outside of this wiki.
Also to be added here:
- about test suites (see CUnit)
- about Buildbot (currently inactive/offline)
- using GDB
- using Valgrind.
- correct use of SVN during debugging on the trunk
- using 'pygtk/ascdev' and 'tcltk/asc4dev' from within your working folder
- possible library wrong-loading issues: export LD_LIBRARY_PATH=~/ascend for example,