Debugging ASCEND - Revision history

Jpye: /* Using GDB */

2015-04-29T11:49:42Z

Using GDB

← Older revision		Revision as of 11:49, 29 April 2015
Line 21:		Line 21:
	=== Using GDB ===		=== Using GDB ===

	ASCEND loads its [[solvers]] from shared libraries using <tt>dlopen</tt>. This sometimes causes difficulties with ~~libthread~~.so when using <tt>gdb</tt> for debugging. A solution that sometimes works is along these lines (the exact file location may depend on your Linux distro) is given here.		ASCEND loads its [[solvers]] from shared libraries using <tt>dlopen</tt>. This sometimes causes difficulties with libpthread.so when using <tt>gdb</tt> for debugging. A solution that sometimes works is along these lines (the exact file location may depend on your Linux distro) is given here.
	For example:		For example:

2015-04-03T08:05:29Z

@@ Line 18: / Line 18: @@
 <div style="border:solid 1pt orange;padding:10px;margin-top:10px;margin-bottom: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]]

2011-05-06T02:19:15Z

← Older revision		Revision as of 02:19, 6 May 2011
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,

	<div style="border:solid 1pt orange;padding:10px">		<div style="border:solid 1pt orange;padding:10px;margin-top:10px;margin-bottom: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>		''“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]]

2011-05-06T02:18:57Z

← Older revision		Revision as of 02:18, 6 May 2011
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,

	<div style="border:solid 1pt ~~yellow~~;padding:10px">		<div style="border:solid 1pt orange;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>		''“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]]

2011-05-06T02:18:48Z

← Older revision		Revision as of 02:18, 6 May 2011
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,

	<div style="border:solid ~~1 pt~~ yellow;padding:10px">		<div style="border:solid 1pt 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>		''“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]]

2011-05-06T02:18:40Z

← Older revision		Revision as of 02:18, 6 May 2011
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]]

2011-05-06T02:18:13Z

← Older revision		Revision as of 02:18, 6 May 2011
Line 15:		Line 15:
	* using 'pygtk/ascdev' and 'tcltk/asc4dev' from within your working folder		* using 'pygtk/ascdev' and 'tcltk/asc4dev' from within your working folder
	* 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)''

	[[Category:Development]]		[[Category:Development]]

2011-05-04T03:07:00Z

← Older revision		Revision as of 03:07, 4 May 2011
Line 3:		Line 3:
	===Reporting a bug===		===Reporting a bug===

	There is a '''[http://~~ascendbugs~~.~~cheme~~.~~cmu.edu~~ Bug tracker]''' for ascend outside of this wiki.		There is a '''[http://bugs.ascend4.org Bug tracker]''' for ascend outside of this wiki.

	Some useful additional information relating to debugging:		Some useful additional information relating to debugging:

2011-02-15T06:41:19Z

← Older revision		Revision as of 06:41, 15 February 2011
Line 4:		Line 4:

	There is a '''[http://ascendbugs.cheme.cmu.edu Bug tracker]''' for ascend outside of this wiki.		There is a '''[http://ascendbugs.cheme.cmu.edu Bug tracker]''' for ascend outside of this wiki.

			Some useful additional information relating to debugging:
			* about test suites (see [[CUnit]])
			* using [[Valgrind]] to track down segfaults and memory leaks

	Also to be added here:		Also to be added here:
	* about test suites (see [[CUnit]])
	* about Buildbot (currently inactive/offline)		* about Buildbot (currently inactive/offline)
	* using GDB		* using GDB
	* using [[Valgrind]].
	* correct use of SVN during debugging on the trunk		* correct use of SVN during debugging on the trunk
	* using 'pygtk/ascdev' and 'tcltk/asc4dev' from within your working folder		* using 'pygtk/ascdev' and 'tcltk/asc4dev' from within your working folder

2011-02-15T06:38:16Z

← Older revision		Revision as of 06:38, 15 February 2011
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]]