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

List:       kdevelop-bugs
Subject:    [Bug 149081] New: First break position in remote debugging not shown
From:       Joerg Wleklik <joerg () wleklik ! de>
Date:       2007-08-21 15:46:42
Message-ID: 20070821174641.149081.joerg () wleklik ! de
[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=149081         
           Summary: First break position in remote debugging not shown
           Product: kdevelop
           Version: 3.4.1
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: joerg wleklik de


Version:           3.4.1 (using KDE 3.5.7 "release 69.1" , openSUSE )
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.18.8-0.5-default

Hi,
when I start a new remote debugging session the first break point is not shown as the \
current execution position.

e.g. 

I have the following gdb script:
---- snip ----
set $connected=0
target remote 192.168.48.51:4444
set $connected=1
continue
---- snip ----

and a break point at main().

The debugger will stop at main but the green arrow which indicate the current \
execution position will not appear. Also if I have a different source file displayed \
the debugger will not switch to the file containing the main function.

If I have a second brake point at the beginning of main() an press the "run" button \
again the debugger will switch to the right window and display the currend execution \
position as expected on the second break point.

I assume that this is a bug because showing the first break point worked fine for me \
until I updated from 3.3.5 to 3.4.1

Ciao
Joerg

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs


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