Debugging ASCEND: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
* possible library wrong-loading issues: <tt>export LD_LIBRARY_PATH=~/ascend</tt> for example, | * possible library wrong-loading issues: <tt>export LD_LIBRARY_PATH=~/ascend</tt> for example, | ||
''“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. ” (Brian Kernighan)'' | <div style="border:solid 1 pt yellow;padding:10px"> | ||
''“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. ” (Brian Kernighan)''</div> | |||
[[Category:Development]] | [[Category:Development]] | ||
Revision as of 02:18, 6 May 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.
Some useful additional information relating to debugging:
Also to be added here:
- about Buildbot (currently inactive/offline)
- using GDB
- 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,
“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. ” (Brian Kernighan)