Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-debug-dev] Re: Line breakpoint does not seem to work
In workspace. Again: source lookup works fine; the batch compile options are identical with the eclipse project properties ( only diff: -MMD,-MP);
 
I think eclipse must have some recognition mechanism to include source files to debug session, just dont know how.
 
Could you check it out yourself with a helloworld batch build managed c project, I will be surprised if you result is different than mine.
Since I am doing remote debug, hope i could provide you my test project, but wouldn't help you see the problem.Sorry for the inconvenience.
 
Thanks a lot. 

 
On 12/6/06, Mikhail Khodjaiants <Mikhail.Khodjaiants@xxxxxxx> wrote:
Where are the source files? In the project or outside of the workspace? 

From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto: cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Haoquan JIANG
Sent: 06 December 2006 15:23

To: CDT Debug developers list
Subject: Re: [cdt-debug-dev] Re: Line breakpoint does not seem to work

 
HI Mikhail
 
I found out the hello world project works if with default build, but not with external build batch.
 
Any suggestion then?

 
On 12/5/06, Mikhail Khodjaiants <Mikhail.Khodjaiants@xxxxxxx > wrote:
Create a simple managed build project - Hello World or something like that and try it. If it works then the problem is with your project structure. 

From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto: cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Haoquan JIANG
Sent: 05 December 2006 15:49

To: CDT Debug developers list
Subject: Re: [cdt-debug-dev] Re: Line breakpoint does not seem to work
 

 
If the source lookup fails entire source would not be shown, not just breakpoint filtered out.
New launch didnt have any luck. I found that my test.exe file doesnot locate in Debug (eclipse default) folder but outside, since I am using my batch compile. Has this something to do with it?
I even created a new project, this time located in workspace, but still not working.
 
How can i do further testing to check wether the main file is attached to the debug session?
 
 
Best,
 
On 12/5/06, Mikhail Khodjaiants <Mikhail.Khodjaiants@xxxxxxx > wrote:
This has nothing to do with gdb if there is no "break-insert" in the gdb console. If you can set the same breakpoint from the console then your executable is compiled with the right options. The source lookup is the only possible reason why the breakpoint is filtered. Try to create a new launch configuration.

From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto: cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Haoquan JIANG
Sent: 05 December 2006 15:03

To: CDT Debug developers list
Subject: Re: [cdt-debug-dev] Re: Line breakpoint does not seem to work
 

 
Thanks Mikhail
 
I checked the souce lookup, by default it contained the src folder I have together with my include folder inc, as well as the cgwin path mapping and anything should be alright.
What else could be the reason since the suorce lookup were correct?
 
When starting debug the main program still be the first breakpoint, shouldnt that mean GDB recognise the source file, but as you said, somehow excluded from the debug session/target?

Thanks
On 12/5/06, Mikhail Khodjaiants <Mikhail.Khodjaiants@xxxxxxx > wrote:
When a launch configuration is created it adds the project and the referenced projects to the source lookup. Look at the "Source" tab of your launch configuration.

From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto: cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Haoquan JIANG
Sent: 05 December 2006 14:34

To: CDT Debug developers list
Subject: Re: [cdt-debug-dev] Re: Line breakpoint does not seem to work
 

 
Hi Mikhail
 
How  would I "include" my main c file into the debug session? I assumed the debuger would recognise it automatically. or should it be done via a compiler option in my batch complie? The older version didnt need me to do anything but it works.
During debug in the bp properties the filter is not checked.It did not even if I checked the filter.
 
Could you give further hints?
Many thanks

 
On 12/5/06, Mikhail Khodjaiants <Mikhail.Khodjaiants@xxxxxxx > wrote:
The check mark on the breakpoint image means that the breakpoint is set on the target. In your case the breakpoint is not set that's why it doesn't have a check mark.
The CDT debugger filters the existing breakpoints before trying to set them. The filter is using the source lookup to check if the breakpoint is set in the source file that "belongs" to the debug session. I suspect this is the reason why your breakpoint is not getting set.

From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto: cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Haoquan JIANG
Sent: 05 December 2006 12:35
To: CDT Debug developers list
Subject: Re: [cdt-debug-dev] Re: Line breakpoint does not seem to work

 
I found further out that the breakpoint I set would not be ticked in front of the breakpoint dot.
What can that be meaning?
 
Thanks,

 
On 12/5/06, Haoquan JIANG <haoquan.jiang@xxxxxxxxx> wrote:
Hi Mikhail,
 
The break-insert is not issued for Eclipse source line by double click, though the bp monitor has its entry. However, gdb console break XXX works fine.
 
Could you understand where the problem is?

 
On 12/5/06, Mikhail Khodjaiants < Mikhail.Khodjaiants@xxxxxxx > wrote:
Set the verbose console mode and check if the "break-insert" command is being issued for you breakpoint.

From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto: cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Haoquan JIANG
Sent: 04 December 2006 19:02
To: cdt-debug-dev@xxxxxxxxxxx
Subject: [cdt-debug-dev] Re: Line breakpoint does not seem to work

 

Hello all,
 
I am using zylin embededcdt with cdt version 3.1.0.20060407 and a mips-elf gdb for embeded debug.
 
Anyhow, the line breakpoint (I mean source file line breakpoint click) would not be set via gdb(  one can see from the gdb console by "info break", no entry was made when line break inserted) and therefore not hit.
 
Could some one point out where this failure can lie in? I had a old version of micro code to my processor, where line breakpoints functioned correctly. Just after I use my new(complete different) micro code, which might have used a little different complied settings(-g, everything i think that would matter stays), I found the dissasmbly is not quite in order than what I expected. Could that be the problem? If yes, how can I change the settings to make dissasmbly accord to the source file?
 

Thanks for the help,
 


--
Jiang,Haoquan

Apartment.4.20
Kassernenstrasse 12. c/o NIT
21073 Hamburg

--

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.


 
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev





--
Jiang,Haoquan

Apartment.4.20
Kassernenstrasse 12. c/o NIT
21073 Hamburg



--
Jiang,Haoquan

Apartment.4.20
Kassernenstrasse 12. c/o NIT
21073 Hamburg

--

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.


_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev





--
Jiang,Haoquan

Apartment.4.20
Kassernenstrasse 12. c/o NIT
21073 Hamburg

--

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.


_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev





--
Jiang,Haoquan

Apartment.4.20
Kassernenstrasse 12. c/o NIT
21073 Hamburg

--

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.


_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev





--
Jiang,Haoquan

Apartment.4.20
Kassernenstrasse 12. c/o NIT
21073 Hamburg

--

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.


_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev





--
Jiang,Haoquan

Apartment.4.20
Kassernenstrasse 12. c/o NIT
21073 Hamburg

--

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.


_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev





--
Jiang,Haoquan

Apartment.4.20
Kassernenstrasse 12. c/o NIT
21073 Hamburg

Back to the top