[cdt-debug-dev] Clearing memory blocks after terminating

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[cdt-debug-dev] Clearing memory blocks after terminating

From: "Igor S. Zamyatin" <isz@xxxxxxxxxxxxx>
Date: Tue, 9 Sep 2003 10:51:29 +0400
Delivered-to: cdt-debug-dev@xxxxxxxxxxx
List-archive: <http://dev.eclipse.org/pipermail/cdt-debug-dev/>
List-help: <mailto:cdt-debug-dev-request@eclipse.org?subject=help>
List-subscribe: <http://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>, <mailto:cdt-debug-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <http://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>, <mailto:cdt-debug-dev-request@eclipse.org?subject=unsubscribe>

Hi all!

I've noticed strange thing after terminating debugging process. If you watched memory during debug session and after terminating session you click on "<terminated>Cygwin GDB Debugger (....) (Exited. Exit code = 0)" branch in Debug View you will see the memory block that you have watched. CDT simply doesn't remove this block as I understood.

Igor S. Zamyatin

Interstron Ltd.

www.interstron.ru

Follow-Ups:
- Re: [cdt-debug-dev] Clearing memory blocks after terminating
  - From: Mikhail Khodjaiants

Prev by Date: Re: [cdt-debug-dev] Update on the debugger(for 1.2)
Next by Date: Re: [cdt-debug-dev] Clearing memory blocks after terminating
Previous by thread: [cdt-debug-dev] Update on the debugger(for 1.2)
Next by thread: Re: [cdt-debug-dev] Clearing memory blocks after terminating
Index(es):
- Date
- Thread

Breadcrumbs