Page 1 of 1
What I need to fix to use debugger with Mod5270FactoryDemo?
Posted: Mon May 26, 2008 8:29 am
by yevgenit
After duplication the project Mod5270FactoryDemo according to
http://www.netburner.com/downloads/nndk ... tarted.pdf, the application stops only near the end of OSTaskIdle() at ucos.c - instead of my breakpoints. The application itself works Ok.
The console window shows:
Source directories searched: $cdir;$cwd
Current language: auto; currently c++
mi_cmd_disassemble: Invalid filename.
Re: What I need to fix to use debugger with Mod5270FactoryDemo?
Posted: Sun Jun 01, 2008 5:18 am
by yevgenit
The issue of non-stop on breakpoint is fixed by adding C:\Nburn\MOD5270\system to the includes according to the link in the console window.
It will nice to have this include added automatically when debug configuration is built.
The fix is implemented with NDDK Rel22_rc2.
By the way: to enable breakpoints at assembler source files, -gdwarf-2 need to be added to the assembler command line.
Re: What I need to fix to use debugger with Mod5270FactoryDe
Posted: Fri Mar 01, 2013 10:15 am
by mx270a
I'm seeing the same issue with the debugger ignoring my breakpoint and instead stopping at OSTaskIdle() in the ucos.c file. This is with a PK70 app running NNDK 2.6.1 in Windows 7 x64.
I also have a virutal machine running Windows XP x32 with NNDK 2.6.1 and the exact same application. Debug works fine on this machine.
Re: What I need to fix to use debugger with Mod5270FactoryDe
Posted: Fri Mar 01, 2013 3:16 pm
by tod
Yevgeni - you can edit the PROPERTIES file under the nburn\MOD5270 directory to manually add an include path for any new project you create. I tried adding the path you indicated to my test debug project but it didn't help me. I still need to add an OSTimeDly(x) if I want to hit a breakpoint right after the InitializeNetworkGDB_and_Wait() call (it never actually waits on that call either).
@mx270a that's very interesting that it works under XP but not Windows 7 x64, I hope NetBurner is listening, that might be a clue to get the debugger working better. I too use Win7x64 as my standard development platform.