A binary that you want to debug must be built with symbolic information (a .sym file). You can debug a DLL just as you would any other executable with full support of the Carbide debugger. Basically, the following situations can occur:
NOTE Breakpoints inside a DLL will not be resolved until the DLL is loaded into memory by the calling binary.
You can use the Modules view to determine if a particular DLL or binary is loaded and available for debugging.