[Moved] Can't load debugging symbols (on-device)

[Theril]

Hello,

I've already had quite a fight to get on-device debugging working and finally I have the debugger to upload the .sisx and start the program. However, I can only break to the E32Main and attempting to insert a breakpoint to anywhere else gives "Unresolved breakpoint" in Carbide and won't break to them at all.

When the debugger starts, in the modules tab it says for my .exe that "Symbols: not loaded" and when I try to load them from the menu, it gives error message "Unable to load symbols. Target request failed: not supported." At this point it also doesn't send anything to the phone according to the debugging protocol dump.

For loading the symbols I have tried both the .exe and the .sym files and have ensured from the gcce.mk that -g flag is on There's however a bit weird lines at that point:

# Option to ensure that the debug format is of DWARF3 format
DEBUG_FORMAT=

# Specific compiler options for a UDEB build
SYMBIAN_UDEB_CCFLAGS= $(DEBUG_OPTION) $(DEBUG_FORMAT)

So the DEBUG_FORMAT is empty and there's a gap between the -g and the debug format, which is illegal syntax for gcc. I tried to change these so that the resulting flag is -gdwarf-2 (which should also do DWARF3 according to gcc's documentation), but this didn't nail it either.

I have made sure that I'm building in debug-mode. I have also disabled optimization and even enabled the Symbian 9.4+ debugging in the .mmp files.

AFAIU even the .mmp shouldn't really have effect on the debugging and I'm not aware that the .pkg nor the .bld should have anything to do with enabling debugging, so is it possible that I have overlooked something in there?

[Theril]

Also if it's of any indicator, there's following output in the protocol dump just after loading the exe:

---IDE------------------------------------------------------
Command: 0x1B Set Break
BreakType: 0x82
Options: 0x00
Address: 0x7d4580a8 (2101706920)
Length: 0x00000001 (1)
Count: 0x00000000 (0)
ProcessID: 0x0000045e (1118)
ThreadID: 0xffffffff (-1)
[1B 29 82 00 7D 45 80 A8 00 00 00 01 00 00 00 00
00 00 04 5E FF FF FF FF]
---TRK------------------------------------------------------
Command: 0x80 Acknowledge
Error: 0x00
[80 29 00 00 00 00 0A]
---IDE------------------------------------------------------
Command: 0x1B Set Break
BreakType: 0x82
Options: 0x00
Address: 0x7d45a324 (2101715748)
Length: 0x00000001 (1)
Count: 0x00000000 (0)
ProcessID: 0x0000045e (1118)
ThreadID: 0xffffffff (-1)
[1B 2A 82 00 7D 45 A3 24 00 00 00 01 00 00 00 00
00 00 04 5E FF FF FF FF]
---TRK------------------------------------------------------
Command: 0x80 Acknowledge
Error: 0x00
[80 2A 00 00 00 00 0B]
---IDE------------------------------------------------------
Command: 0x42 Read Info
[42 2B 00 06 00 00 00 00 00 18 66 6C 6F 6F 62 73
5F 6D 6F 62 69 6C 65 5F 74 65 73 74 73 2E 65 78...]
---TRK------------------------------------------------------
Command: 0x80 Acknowledge
Error: 0x20 Unspecified general OS-related error
[80 2B 20]
---IDE------------------------------------------------------

[Theril]

OK, the breakpoints not sticking was due to a leave early in the code and now after fixing it the debugging works. The debugger could handle leaves more gracefully. The symbols still aren't loaded but this doesn't seem to really have an effect on whether debugging works or not.

However, I encountered another minor problem: sometimes the variables aren't automatically populated in to the Variables-tab and to fix this the tab has to be closed and re-opened from the menu.