mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-24 17:35:35 +02:00
Code Issues Wiki Activity

updated.

Browse source
This commit is contained in:
Alain Magloire 2002-10-19 19:21:24 +00:00
parent 7c45b6aa42
commit b1b68787e3
1 changed files with 28 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
debug/org.eclipse.cdt.debug.mi.core/ChangeLog
View file

@ -1,3 +1,31 @@
2002-10-19 Alain Magloire
The responsability to generate Events for modify memory blocks is push
on the CDI implementation. The way we do this is every time consuming,
when the inferior is suspended(see EventManager.processSuspendedEvent()),
MemoryManager.update() is called, the method will go through the list of MemoryBlocks
that are not MemoryBlocks.setFrozen() and fetch the new memories, the data is compare
and MemoryChangedEvents are fired for blocks with changed values.
Gdb/mi var objects does not seem to provide any support for Memory ranges.
* src/.../core/cdi/MemoryChangedEvent.java: New File implements ICDIMemoryChangedEvent.
* src/.../core/cdi/EventManager.java (update): Process MIMemoryChangedEvent's.
(processSuspendedEvent): call MemoryManager.update().
* src/.../core/cdi/MemoryBlock.java (getExpression): New method.
(getMIDataReadMemoryInfo): New method.
(setMIDataReadMemoryInfo): New method.
* src/.../core/cdi/MemoryManager.java (update): New method.
(compareBlock): New method.
(listMemoryBlocks): New method.
* src/.../core/cdi/CTarget.java (setCurrentThread): Catch null pointer.
(getCThreads): Likewise.
* src/.../core/event/MIMemoryChangedEvent.java: New File.
* src/.../core/event/MIThreadExitEvent.java: Indentation fixes.
* src/.../core/event/MIVarChangedEvent.java: Indentation fixes.
2002-10-16 Alain Magloire
* src/.../mi/core/cdi/MemoryManager.java (createMemoryBlock):