Finding Memory Leaks: Difference between revisions

Finding Memory Leaks (edit)

Revision as of 17:08, 14 September 2017

2 bytes added , 14 September 2017

m

→‎Finding Leaks

Rik

1,072

edits

Revision as of 17:06, 14 September 2017 (edit) Rik (talk \| contribs) m (Correct formatting) ← Older edit		Revision as of 17:08, 14 September 2017 (edit) (undo) Rik (talk \| contribs) m (→‎Finding Leaks) Newer edit →
Line 44:		Line 44:
	== Finding Leaks ==		== Finding Leaks ==

	Now that Octave has been built with the Address Sanitizer, and the Sanitizer itself has been configured by its environment variable, the next step is to launch Octave (typically ./run-octave), and execute code. This might mean running the default set of tests that come with Octave, "__run_test_suite__". It could mean a particular function, "test ls". Or it could be simply running your own scripts, commands, etc. to see if a leak is triggered. If memory error is detected the Sanitizer will dump a summary and backtrace to stderr. Make a new bug report at [[bugs.octave.org]] and include the backtrace in the report.		Now that Octave has been built with the Address Sanitizer, and the Sanitizer itself has been configured by its environment variable, the next step is to launch Octave (typically ./run-octave), and execute code. This might mean running the default set of tests that come with Octave, "__run_test_suite__". It could mean a particular function, "test ls". Or it could be simply running your own scripts, commands, etc. to see if a leak is triggered. If a memory error is detected the Sanitizer will dump a summary and backtrace to stderr. Make a new bug report at [[bugs.octave.org]] and include the backtrace in the report.