[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 122430] New: Debugger doesn break when break address is out of code
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2006-02-21 17:13:00
Message-ID: 20060221181259.122430.leonp () plris ! com
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=122430         
           Summary: Debugger doesn break when break address is out of code
           Product: kdevelop
           Version: 3.3.1
          Platform: Fedora RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: leonp plris com


Version:           3.3.1 (using KDE KDE 3.5.1)
Installed from:    Fedora RPMs
OS:                Linux

I am an embedded developer. Application is started by some code, let's say residing \
at addresses 0-0x10000. The start code receives the application, puts it into RAM \
(let's say at addresses 0x100000-0x200000) and runs it. If something abnormal happens \
in the application, the control is returned to the start code. Now, if I run the \
Kdevelop debugger and the application does not crashes (which causes the control to \
return back to start code), everything is OK - break points work fine, the code is \
displayed... When the application crashes, any attempt to stop debugging fails - \
debugger continues to "run" the application, Ctrl-C button been pressed has no \
effect.

Exactly the same code in exactly the same conditions been run in DDD shows that \
control is in start code and Ctrl-C breaks the CPU and simply shows the address with \
'?' sign.

Regards


[prev in list] [next in list] [prev in thread] [next in thread]