Bug 396904 - support for gdb breakpoint expressions support in windows
Summary: support for gdb breakpoint expressions support in windows
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 8.1.1   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-19 05:34 EST by David CLA
Modified: 2020-09-04 15:17 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David CLA 2012-12-19 05:34:17 EST
Having taken the patch for Bug 392512 and tried it, I found that the support did not work too well in windows 7.

The command "delete break" would not remove breakpoints from the view.
Also the following commands failed to add breakpoints correctly to the view:

break ../src/test.c:main
break main

The commands were accepted by gdb and by entering info break provided a list of breakpoints.
Comment 1 Nobody - feel free to take it CLA 2012-12-19 14:04:10 EST
(In reply to comment #0)
> Having taken the patch for Bug 392512 and tried it, I found that the support
> did not work too well in windows 7.
> 
> The command "delete break" would not remove breakpoints from the view.
> Also the following commands failed to add breakpoints correctly to the view:
> 

"delete break" is not supposed to remove the breakpoint from the Breakpoints view. It just changes the breakpoint's state from installed to uninstalled. It should remove the little check mark next to the dot in the breakpoint image.

> break ../src/test.c:main
> break main
>
> The commands were accepted by gdb and by entering info break provided a list
> of breakpoints.

What is the working directory? What does entering "info sources" in GDB console return in your case?
When I try the same command on Linux I get "No source file named ../src/test.c." message and the breakpoint set in GDB is pending which is correct because the working directory is the project path. The breakpoint appears in the Breakpoints view but not in the source editor which is expected.
Comment 2 David CLA 2012-12-20 09:45:12 EST
(In reply to comment #1)
> (In reply to comment #0)
> > Having taken the patch for Bug 392512 and tried it, I found that the support
> > did not work too well in windows 7.
> > 
> > The command "delete break" would not remove breakpoints from the view.
> > Also the following commands failed to add breakpoints correctly to the view:
> > 
> 
> "delete break" is not supposed to remove the breakpoint from the Breakpoints
> view. It just changes the breakpoint's state from installed to uninstalled.
> It should remove the little check mark next to the dot in the breakpoint
> image.
> 
"delete break" had no effect on the breakpoints view it did not disable the breakpoint.

> > break ../src/test.c:main
> > break main
> >
> > The commands were accepted by gdb and by entering info break provided a list
> > of breakpoints.
> 
> What is the working directory? What does entering "info sources" in GDB
> console return in your case?
In my case it from the console it shows the the breakpoint is set, e.g.

(gdb) info breakpoints
Num Type           Disp Enb Address    What
3   breakpoint     keep y   0x080483da in func1 at test.c:10


the working directory is the $workspace_loc\project\build_configuration\executable

> When I try the same command on Linux I get "No source file named
> ../src/test.c." message and the breakpoint set in GDB is pending which is
> correct because the working directory is the project path. The breakpoint
> appears in the Breakpoints view but not in the source editor which is
> expected.
I get the "No souce" message when I do not specify the path

I tried all ways to set the breakpoint using path as well as just function name, line number etc. they do not show a breakpoint set in the breakpoint view.

Also why would you not expect the breakpoint to show in the editor?