Almost all actions produce default OS "bell" sound, which gets old pretty quickly
This slipped through for quite some time as I have all of those sounds disabled. But will finally go away with the next update.
UI reacts only to full trackpad clicks, "taps" are not enough. Not sure how is that possible, all other applications respect the OS setting to treat taps as clicks (though Firefox has sometimes similar problems on some buttons, not sure what is going on there).
The main problem here is probably that "tap to click" on macOS behaves only as a "click" event without any involvement of "mouse down" or "mouse up". I will look into fixing this without changing too much in the input handling.
Source and symbols don't load. I can manually force some files to open, sometimes, but in general, there are no source files. LLDB (and its frontends) don't have problems on the same executable. Since the symbols are missing, stacktraces only contain the current instruction pointer and the library name. Sometimes a notification that "main" has been found pops up and offers to run to it, however it doesn't stop at "main" and keeps running through the application.
lldb is definitely more "intelligent" in finding debug information. codeclap currently scans the directory of the module for any .dSYM with a matching UUID which hopefully is the cause for your problems. The next update will improve in finding debug information and should be more on par with lldb.
Scrolling is not very smooth (although this seems to be a problem with input, not with general application responsiveness). Sometimes it breaks, so that scrolling up (towards line 1) works only for a few lines and then stops (starting to scroll up again does nothing until I've scrolled down a bit, then it works again but only for a few lines again), but scrolling down works always. Scrollbars would be nice to see the approximate location in the file. EDIT: It turns out, that this isn't limited to just mouse/touchpad scrolling - arrow keys exhibit similar behavior - only down arrow works.
Scrolling will be a lot better with debug information. I've seen a few remaining problems when viewing a plain assembly region without debug information which should also improve over time but codeclap is intended as a source-level debugger. Scroll bars will be included in the next update.
Pausing all threads (which works perfectly btw.) causes all threads to open in the source view, which is not that useful when the application has more than a couple of threads, because each source "tab" is only a few characters tall.
This will also change soon and codeclap will behave more expected. Panels will not open on a thread basis, provide tab support and the ability to reorder more freely.