[
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
|
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.
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.
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?
Set the
verbose console mode and check if the "break-insert" command is being
issued for you breakpoint.
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.