Bug 82279 - setting breakpoint in multiline statement sets bp on next statement
Summary: setting breakpoint in multiline statement sets bp on next statement
Status: RESOLVED NOT A BUG
Alias: None
Product: kdevelop
Classification: Applications
Component: CPP Debugger (show other bugs)
Version: git master
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-26 23:25 UTC by Jon Smirl
Modified: 2005-12-08 09:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jon Smirl 2004-05-26 23:25:21 UTC 
Version:           CVS (using KDE Devel)
Installed from:    Compiled sources

screen_info->root_drawable =
      XCreateWindow (display, RootWindow (display, screen),
                     0, 0, 100, 100, 0, vinfo->depth, InputOutput,
                     vinfo->visual,
                     CWBackPixel | CWBorderPixel | CWColormap | CWEventMask,
                     &win_attrib);
    
    screen_info->root_context.context =
      glXCreateContext (display, vinfo, NULL, 1);


If I set the bp on XCreateWindow the program is stopping at 'screen_info->root_context.context =' instead of 'screen_info->root_drawable ='. I think this used to work as expected. 

I am using GNU gdb 6.1
Comment 1 Vladimir Prus 2005-12-08 09:33:07 UTC 
I believe this is an issue with gdb, or with debug info that gcc produces.
If you find that gdb stops on the right line but KDevelop shows another, please send a test case to me.