On Thu, Jun 21, 2012 at 9:05 AM, [email protected] wrote: > For now I conected arm-non-eabi-gdb to gvim via pyclewn. > I can: > set breakpoint (see it in my code window and in (clewn)_console), > sent Ccommand to debuger and have response in (clewn)_console > run aplication, stop aplication, next, step and so on via > (clewn)_console, but > I have one ugly problem ie > Information on the state of the program are not visualized in the code > file, ie > Although I have set a breakpoint in my code (as I mentioned is a light > blue marker on the line in the code and it shows Clist breakpoints) at > the stop on it (what I see in (clewn) _console) do not see this in file > with the code.
Please use only [email protected] to subscribe or unsubscribe this mailing list. Do not use this address to send messages to the mailing list. > Do you have idea where coultd be the problem or how to debug to find it? arm-non-eabi-gdb is possibly non compliant with the gdb/mi interface. -- Xavier Les Chemins de Lokoti: http://lokoti.alwaysdata.net ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
