Debug areas were found but removed

I’m trying to work out how to debug module code using what appears to be a standard method. The module in question is the URL Fetcher. There are various dprintf() commands in the source. I’m building just the URL module, by setting Builder up as for a disc build but just double-clicking the !MkDebug TaskObey file in the Fetchers.URL direcory. The output contains a worrying message: “Debug areas were found but removed, since no -d”. Calls that I’ve put in to dprintf() do not appear as a result of executing *DADPrint in a task window.

I’ve not used this method of debugging before, so I’m sure I’m doing something wrong or failing to something that I should. Help would be appreciated!

Hi Dave, I’ve not tried this either but it looks like changing

debug_set_device(DEBUGIT_OUTPUT);

to

debug_set_device(DADEBUG_OUTPUT);

in the module_init function in URL.c.module will get you going!

RiscOS.Sources.Lib.DebugLib.Docs has the help for this.

Thanks, Julie, that works!

The warning message from the linker is still there, but, as it’s only a warning, it doesn’t stop things from working.

I appreciate your help!