On Monday, July 28, 2003, at 07:36 AM, Robert Terwilliger wrote:
> Finally! Enough said... Thanks!
If you have any addendums to my "compile.txt" file, please share.
This was my first attempt at describing the new Mac compile process.
> Now, my next question... I'd like to run the program in debug mode so
> I can
> step through the code. Do I use gdb or does wxWindows have a debugger
> Also, I probably have to build in debug-mode as well... How to?
wxWindows does have a debug mode, but it's not necessary to step through
the code, only to turn on assertions and stuff like that.
Audacity should have been compiled with debugging info by default.
Check the size of the executable - if it's something like 40 MB, then
it's got debugging info! If you run "strip" on the executable, it
gets down to about 6 MB (still large because a lot of stuff is
You can definitely run Audacity via gdb, e.g.:
> br Menus.cpp:1058
If you really want to step through line-by-line, you may want to
without optimization, though. Don't reconfigure - instead just open
src/Makefile directly and get rid of any "-O2" you find. Then type
"make clean" and then "make" from within the "src" directory to rebuild
just Audacity, but not rebuild all of the libraries again.
A few functions will run noticeably slower without optimization, but
when you step through, things will happen in the order you expect
them to. With optimization, the order can be all messed up, and
some variables may not exist at all.
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> Audacity-devel mailing list