[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[tcf-dev] FW: [cdt-dev] Inserting Breakpoints Question
|
Hi all,
I've seen the below message on cdt-dev and I was wondering if we do things any different in TCF with respect to disabled breakpoints that are in the workspace but outside the project / context I'm currently debugging ?
See the original message from Anna at the bottom of the Thread.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Owner - Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mikhail Khodjaiants
Sent: Thursday, May 22, 2014 9:31 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Inserting Breakpoints Question
Hi Anna,
Unfortunately it's a very difficult task to filter breakpoints associated with a particular session from other breakpoints set in Eclipse. Originally we used the source lookup for filtering. This approach required manual customization of the source lookup to make it work with breakpoints set in referenced projects or external files. Many users found it confusing and too complicated.
Currently we just apply all C/C++ breakpoints defined in Eclipse to any active session. As a downside of this approach, users get "No source file named..." messages or address breakpoints are set on invalid addresses. There is patch to associate address breakpoints with the binaries but it's still under review.
Re enabled/disabled state. The state of a platform breakpoint is mapped to the state of the associated gdb breakpoint, a disabled platform breakpoint is set but disabled in gdb.
Mikhail
On 22/05/2014 1:58 PM, Anna Dushistova wrote:
> Hi All,
> I noticed that all breakpoints regardless of their
> status(disabled/enabled) and project they belong to get inserted each
> time I start debugging session and it results in gdb complaining "No
> source file named..." for all the out of context breakpoints.
>
> Is this the expected behavior?
>
> Thanks!
> Anna.
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
