Core Build for 9.2

classic Classic list List threaded Threaded
38 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Core Build for 9.2

Doug Schaefer-3
Hey gang, with 9.2 only a few weeks away, I’m quickly realizing I won’t get both CMake and Qt plug-ins in shape for then. My priority is Qt so I’ll focus on that and see if I can get it ready. Anything else new like will have to wait.

I really like how Core Build is turning out. There’s still a lot of questions to answer so refocusing on Oxygen just seems to be the right thing to do.

Let me know if you have thoughts, or would like to help accelerate the program.
Doug.

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Core Build for 9.2

Martin Weber
Am Dienstag, 1. November 2016, 20:49:38 schrieb Doug Schaefer:
> Hey gang, with 9.2 only a few weeks away, I’m quickly realizing I won’t get
> both CMake and Qt plug-ins in shape for then. My priority is Qt so I’ll
> focus on that and see if I can get it ready. Anything else new like will

Focus on QT support.
After you favorited the 'CMake Editor' in the marketplace a while ago, I took
over maintenance and resolved some of its issues. And I am still maintaining
cmake4eclipse which can build projects.

Martin

--
Cd wrttn wtht vwls s mch trsr.


_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Core Build for 9.2

Doug Schaefer-3
On 2016-11-01, 5:28 PM, "[hidden email] on behalf of Martin
Weber" <[hidden email] on behalf of
[hidden email]> wrote:

>Am Dienstag, 1. November 2016, 20:49:38 schrieb Doug Schaefer:
>> Hey gang, with 9.2 only a few weeks away, I¹m quickly realizing I won¹t
>>get
>> both CMake and Qt plug-ins in shape for then. My priority is Qt so I¹ll
>> focus on that and see if I can get it ready. Anything else new like will
>
>Focus on QT support.
>After you favorited the 'CMake Editor' in the marketplace a while ago, I
>took
>over maintenance and resolved some of its issues. And I am still
>maintaining
>cmake4eclipse which can build projects.

OK. I will be adding CMake with the new Core Build in Oxygen. I consider
the existing build system deprecated and a candidate for removal in an
upcoming release just like we did with CDI. Once I have everything in
place for Oxygen, I highly recommend people start working with those
things, and why I wouldn¹t mind help on those things now.

Doug.

>
>Martin
>
>--
>Cd wrttn wtht vwls s mch trsr.
>
>
>_______________________________________________
>cdt-dev mailing list
>[hidden email]
>To change your delivery options, retrieve your password, or unsubscribe
>from this list, visit
>https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Core Build for 9.2

Mark Goodchild
In reply to this post by Doug Schaefer-3

Hi Doug,

 

Sorry for the very slow reply in this area.

 

How are you getting on with the builder work and in particular CMake?

 

I was wondering if and how Renesas can help you with this. We do have an interest in this area as you know.

 

With regards to assisting you – would it make sense to spin this into a small CDT working group for interested parties?

Perhaps then we could then decide what jobs are needed and the effort required to implement.

 

We may be able to commit some effort to this area.

 

What do you think? Perhaps this could be discussed in an upcoming CDT call?

 

Best regards,
Mark.

 

 

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Doug Schaefer
Sent: 01 November 2016 20:50
To: CDT General developers list. <[hidden email]>
Subject: [cdt-dev] Core Build for 9.2

 

Hey gang, with 9.2 only a few weeks away, I’m quickly realizing I won’t get both CMake and Qt plug-ins in shape for then. My priority is Qt so I’ll focus on that and see if I can get it ready. Anything else new like will have to wait.

 

I really like how Core Build is turning out. There’s still a lot of questions to answer so refocusing on Oxygen just seems to be the right thing to do.

 

Let me know if you have thoughts, or would like to help accelerate the program.

Doug.




Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.


_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Neon.2 does not start GDB 7.12 on macOS

Liviu Ionescu-2

> On 27 Jan 2017, at 13:51, Mark Goodchild <[hidden email]> wrote:
>
>  with 9.2 only a few weeks away

Hi,

With this tight schedule, I just wanted to know if anyone else experienced problems with starting GDB 7.12 debug sessions on Neon.2? (apart from the non-functioning step/halt)

On my Mac environment, none of the debug plug-ins are able to start arm-none-eabi-gdb 7.12 (from GCC 6.2); windows & linux seem ok. arm-none-eabi-gdb 7.10 is ok.

The GDB process quits right after starting, the GDB trace windows shows only:

058,589 2-gdb-show language
058,591 2^done,value="auto"
058,592 (gdb)
058,596 3-data-evaluate-expression "sizeof (void*)"
058,599 3^done,value="4"
058,599 (gdb)
058,602 4-gdb-set language auto

The GDB console is empty.



I planned to further investigate next week, but any suggestions will be appreciated.


Regards,

Liviu

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Neon.2 does not start GDB 7.12 on macOS

Marc Khouzam

It must be what was reported here:

http://eclip.se/509737 GDB 7.12 freezes at 62% on Mac using new console


It turns out to be a special (possibly buggy) behaviour of Mac OS when

using the full GDB console.  It seems GDB cannot answer on the 

dedicated MI channel until CDT has created the full console, but CDT 

waits for an MI answer before creating the console.  And we are stuck.


On Linux, the MI channel is functional right away, even before the 

full console is created by CDT.


We've disabled the full console on Mac for CDT 9.2.1 due in March

(although we can do an earlier release if needed).

But you can fix it yourself easily right away in your plugins

by overriding


GDBBackend_7_12#isFullGdbConsoleSupported()


with something like


@Override
public boolean isFullGdbConsoleSupported() {
if (Platform.getOS().equals(Platform.OS_MACOSX)) return false;
return super.isFullGdbConsoleSupported();
}

Note that it turns out that GDB on MAC does not support asynchronous
MI communication, which is necessary when using the full console,
or else we cannot interrupt the inferior.  So, we will need to keep
the full console disabled on Mac until GDB support MI async on Mac.

Let us know if that fixes things for you.

Marc




From: [hidden email] <[hidden email]> on behalf of Liviu Ionescu <[hidden email]>
Sent: January 27, 2017 7:53
To: CDT General developers list.
Subject: [cdt-dev] Neon.2 does not start GDB 7.12 on macOS
 

> On 27 Jan 2017, at 13:51, Mark Goodchild <[hidden email]> wrote:
>
>  with 9.2 only a few weeks away

Hi,

With this tight schedule, I just wanted to know if anyone else experienced problems with starting GDB 7.12 debug sessions on Neon.2? (apart from the non-functioning step/halt)

On my Mac environment, none of the debug plug-ins are able to start arm-none-eabi-gdb 7.12 (from GCC 6.2); windows & linux seem ok. arm-none-eabi-gdb 7.10 is ok.

The GDB process quits right after starting, the GDB trace windows shows only:

058,589 2-gdb-show language
058,591 2^done,value="auto"
058,592 (gdb)
058,596 3-data-evaluate-expression "sizeof (void*)"
058,599 3^done,value="4"
058,599 (gdb)
058,602 4-gdb-set language auto

The GDB console is empty.



I planned to further investigate next week, but any suggestions will be appreciated.


Regards,

Liviu

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
dev.eclipse.org
Mailing list: cdt-dev CDT General developers list. About cdt-dev



_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Core Build for 9.2

Doug Schaefer-3
In reply to this post by Doug Schaefer-3
Hey Mark, good to hear from you.

I think for the most part CMake is working. I demoed it at a ESE Kongress a couple of months ago so gave it a good work out. Feel free to give it a try and see if there’s anything missing that you may need.

I have an example here of how I used it for the ESP8266 micro controller and it’s FreeRTOS SDK. I really like how it turned out and showed me how good CMake is for things like this.


I don’t think we need anything formal. We can certainly talk about it at the next CDT call. Our Mattermost channel is also a good vehicle for more immediate discussions.


I’m not planning on working on it the next few weeks as we’re in crunch mode with our next QNX product release coming up. So if there’s something you see that needs to be fixed or worked on, please raise a bug in Bugzilla and we can discuss things there. I do receive all new CDT Bugzilla reports so will keep an eye out for them.

Also if anyone else is interested in working on our CMake integration, please respond so we can co-ordinate.

Cheers,
Doug.

From: <[hidden email]> on behalf of Mark Goodchild <[hidden email]>
Reply-To: "CDT General developers list." <[hidden email]>
Date: Friday, January 27, 2017 at 6:51 AM
To: "CDT General developers list." <[hidden email]>
Subject: Re: [cdt-dev] Core Build for 9.2

Hi Doug,

 

Sorry for the very slow reply in this area.

 

How are you getting on with the builder work and in particular CMake?

 

I was wondering if and how Renesas can help you with this. We do have an interest in this area as you know.

 

With regards to assisting you – would it make sense to spin this into a small CDT working group for interested parties?

Perhaps then we could then decide what jobs are needed and the effort required to implement.

 

We may be able to commit some effort to this area.

 

What do you think? Perhaps this could be discussed in an upcoming CDT call?

 

Best regards,
Mark.

 

 

 

From: [hidden email] [[hidden email]] On Behalf Of Doug Schaefer
Sent: 01 November 2016 20:50
To: CDT General developers list. <[hidden email]>
Subject: [cdt-dev] Core Build for 9.2

 

Hey gang, with 9.2 only a few weeks away, I’m quickly realizing I won’t get both CMake and Qt plug-ins in shape for then. My priority is Qt so I’ll focus on that and see if I can get it ready. Anything else new like will have to wait.

 

I really like how Core Build is turning out. There’s still a lot of questions to answer so refocusing on Oxygen just seems to be the right thing to do.

 

Let me know if you have thoughts, or would like to help accelerate the program.

Doug.




Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.


_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Neon.2 does not start GDB 7.12 on macOS

Liviu Ionescu-2
In reply to this post by Marc Khouzam

> On 27 Jan 2017, at 16:12, Marc Khouzam <[hidden email]> wrote:
>
> It must be what was reported here:
> http://eclip.se/509737 GDB 7.12 freezes at 62% on Mac using new console

aha, I guess this is also my case.

> But you can fix it yourself easily right away in your plugins
> by overriding
>
> GDBBackend_7_12#isFullGdbConsoleSupported()
>
> with something like
>
> @Override
> public boolean isFullGdbConsoleSupported() {
> if (Platform.getOS().equals(Platform.OS_MACOSX)) return false;
> return super.isFullGdbConsoleSupported();
> }

I'm not sure I can do this, my code is quite old and I do not have specific support for 7.12 (*).

but I tried a different approach, I disabled the following attribute when starting the GDB process:

        attributes.put(IGdbDebugConstants.PROCESS_TYPE_CREATION_ATTR,
                GdbDebugConstants.GDB_PROCESS_CREATION_VALUE);

now, if I got it right, the process should use the old console.

the tracing console reads:

        exec arm-none-eabi-gdb --interpreter=mi2 --nx

however, it still does not work. :-(


regards,

Liviu


(*) due to the way DSF is implemented, or to my poor understanding of it, adding a second backend for the gdb server was not possible without copying lots of classes to the project, to be modified locally. the obvious disadvantage of this strategy is that improvements to the original code did not migrate automatically to my local code, so my plug-ins do not use the features of the new GDBs, and expect them to be compatible with the old ones.

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Neon.2 does not start GDB 7.12 on macOS

Marc Khouzam

> From: [hidden email] <[hidden email]> on behalf of Liviu Ionescu <[hidden email]>
> Sent: January 27, 2017 11:38
> To: CDT General developers list.
> Subject: Re: [cdt-dev] Neon.2 does not start GDB 7.12 on macOS
>  
> > On 27 Jan 2017, at 16:12, Marc Khouzam <[hidden email]> wrote:
> > 
> > It must be what was reported here:
> > http://eclip.se/509737 GDB 7.12 freezes at 62% on Mac using new console
> aha, I guess this is also my case.
> > But you can fix it yourself easily right away in your plugins
> > by overriding
> > 
> > GDBBackend_7_12#isFullGdbConsoleSupported()
> > 
> > with something like
> > 
> > @Override
> > public boolean isFullGdbConsoleSupported() {
> > if (Platform.getOS().equals(Platform.OS_MACOSX)) return false;
> > return super.isFullGdbConsoleSupported();
> > }
> I'm not sure I can do this, my code is quite old and I do not have specific support for 7.12 (*).
> but I tried a different approach, I disabled the following attribute when starting the GDB process:
>         attributes.put(IGdbDebugConstants.PROCESS_TYPE_CREATION_ATTR,
>                 GdbDebugConstants.GDB_PROCESS_CREATION_VALUE);
> now, if I got it right, the process should use the old console. 

That's not really the correct way, but looking through the code, I don't believe
you'll have side-effects of such a change except for turning off the full console. So,
it seems to be a valid way forward  until you upgrade to CDT 9.2.1 or 9.3.

> the tracing console reads:
>         exec arm-none-eabi-gdb --interpreter=mi2 --nx

So no full console.  That should work.

> however, it still does not work. :-(

What are the gdb traces?

> regards,
> Liviu
> (*) due to the way DSF is implemented, or to my poor understanding of it, adding a second backend for the gdb server was not possible without copying lots of classes to the project, to be modified locally. the obvious disadvantage of this strategy is that improvements to the original code did not migrate automatically to my local code, so my plug-ins do not use the features of the new GDBs, and expect them to be compatible with the old ones.
>


_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Neon.2 does not start GDB 7.12 on macOS

Liviu Ionescu-2

> On 27 Jan 2017, at 20:39, Marc Khouzam <[hidden email]> wrote:
>
> ... What are the gdb traces?

the gdb trace console reads only:

543,579 2-list-thread-groups
543,580 2^done,groups=[{id="i1",type="process"}]
543,583 (gdb)
543,764 3-gdb-show language
543,765 3^done,value="auto"
543,766 (gdb)
543,773 4-data-evaluate-expression "sizeof (void*)"
543,775 4^done,value="4"
543,775 (gdb)
543,780 5-gdb-set language auto


the commands are related to starting the Peripheral Register Viewer services. if I disable the PeripheralMemoryService, I get:


658,146 2-list-thread-groups
658,148 2^done,groups=[{id="i1",type="process"}]
658,152 (gdb)
658,291 3-gdb-version
658,293 ~"GNU gdb (GNU Tools for ARM Embedded Processors) 7.12.0.20161204-git\n"
658,295 ~"Copyright (C) 2016 Free Software Foundation, Inc.\n"
658,295 ~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is fre\
e software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitt\
ed by law.  Type \"show copying\"\nand \"show warranty\" for details.\n"
658,296 ~"This GDB was configured as \"--host=x86_64-apple-darwin10 --target=arm-none-eabi\".\nType \
\"show configuration\" for configuration details."
658,296 ~"\nFor bug reporting instructions, please see:\n"
658,296 ~"<http://www.gnu.org/software/gdb/bugs/>.\n"
658,297 ~"Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/soft\
ware/gdb/documentation/>.\n"
658,297 ~"For help, type \"help\".\n"
658,297 ~"Type \"apropos word\" to search for commands related to \"word\".\n"
658,297 3^done
658,299 (gdb)
658,303 4-environment-cd "/Users/ilg/My Files/MacBookPro Projects/GNU ARM Eclipse/Eclipse Workspaces\
/runtime-GAE-15/f4"
658,305 4^done
658,306 (gdb)
658,310 5-gdb-set breakpoint pending on
658,311 5^done
658,312 (gdb)
658,316 6-enable-pretty-printing
658,317 6^done
658,318 (gdb)
658,321 7-gdb-set python print-stack none
658,322 7^done
658,323 (gdb)
658,327 8-gdb-set print object on
658,328 8^done
658,328 (gdb)
658,332 9-gdb-set print sevenbit-strings on
658,334 9^done
658,334 (gdb)
658,336 10-gdb-set charset ISO-8859-1

I don't think that `gdb-set language auto` or `gdb-set charset ISO-8859-1` are the trouble makers, it might be something else that happens in parallel that kills GDB, but I have no proof of this.


regards,

Liviu

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Neon.2 does not start GDB 7.12 on macOS

Marc Khouzam

So that seems a different issue.

In the issue we've seen before with Mac and the full console

there was no MI communication at all (or maybe just the very

first command sent).


In your case, does GDB crash?

Are you able to get any of your launches to work on Mac with
the full GDB console?  The issue we saw before deadlocked,
but maybe it is not in all Mac environments... It would be interesting
to know if the full console works in some Mac setups.


From: [hidden email] <[hidden email]> on behalf of Liviu Ionescu <[hidden email]>
Sent: January 27, 2017 14:12
To: CDT General developers list.
Subject: Re: [cdt-dev] Neon.2 does not start GDB 7.12 on macOS
 

> On 27 Jan 2017, at 20:39, Marc Khouzam <[hidden email]> wrote:
>
> ... What are the gdb traces?

the gdb trace console reads only:

543,579 2-list-thread-groups
543,580 2^done,groups=[{id="i1",type="process"}]
543,583 (gdb)
543,764 3-gdb-show language
543,765 3^done,value="auto"
543,766 (gdb)
543,773 4-data-evaluate-expression "sizeof (void*)"
543,775 4^done,value="4"
543,775 (gdb)
543,780 5-gdb-set language auto


the commands are related to starting the Peripheral Register Viewer services. if I disable the PeripheralMemoryService, I get:


658,146 2-list-thread-groups
658,148 2^done,groups=[{id="i1",type="process"}]
658,152 (gdb)
658,291 3-gdb-version
658,293 ~"GNU gdb (GNU Tools for ARM Embedded Processors) 7.12.0.20161204-git\n"
658,295 ~"Copyright (C) 2016 Free Software Foundation, Inc.\n"
658,295 ~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is fre\
e software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitt\
ed by law.  Type \"show copying\"\nand \"show warranty\" for details.\n"
658,296 ~"This GDB was configured as \"--host=x86_64-apple-darwin10 --target=arm-none-eabi\".\nType \
\"show configuration\" for configuration details."
658,296 ~"\nFor bug reporting instructions, please see:\n"
658,296 ~"<<a href="http://www.gnu.org/software/gdb/bugs/&gt;.\n" id="LPlnk655770" previewremoved="true">http://www.gnu.org/software/gdb/bugs/>.\n"
658,297 ~"Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/soft\
ware/gdb/documentation/>.\n"
658,297 ~"For help, type \"help\".\n"
658,297 ~"Type \"apropos word\" to search for commands related to \"word\".\n"
658,297 3^done
658,299 (gdb)
658,303 4-environment-cd "/Users/ilg/My Files/MacBookPro Projects/GNU ARM Eclipse/Eclipse Workspaces\
/runtime-GAE-15/f4"
658,305 4^done
658,306 (gdb)
658,310 5-gdb-set breakpoint pending on
658,311 5^done
658,312 (gdb)
658,316 6-enable-pretty-printing
658,317 6^done
658,318 (gdb)
658,321 7-gdb-set python print-stack none
658,322 7^done
658,323 (gdb)
658,327 8-gdb-set print object on
658,328 8^done
658,328 (gdb)
658,332 9-gdb-set print sevenbit-strings on
658,334 9^done
658,334 (gdb)
658,336 10-gdb-set charset ISO-8859-1

I don't think that `gdb-set language auto` or `gdb-set charset ISO-8859-1` are the trouble makers, it might be something else that happens in parallel that kills GDB, but I have no proof of this.


regards,

Liviu

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Neon.2 does not start GDB 7.12 on macOS

Liviu Ionescu-2

> On 27 Jan 2017, at 21:43, Marc Khouzam <[hidden email]> wrote:
>
> So that seems a different issue.

yes.

after some more tests, it looks like the problem is arm-none-eabi-gdb 7.12 specific:

$ arm-none-eabi-gdb --interpreter=mi2 --nx
=thread-group-added,id="i1"
~"GNU gdb (GNU Tools for ARM Embedded Processors) 7.12.0.20161204-git\n"
~"Copyright (C) 2016 Free Software Foundation, Inc.\n"
~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law.  Type \"show copying\"\nand \"show warranty\" for details.\n"
~"This GDB was configured as \"--host=x86_64-apple-darwin10 --target=arm-none-eabi\".\nType \"show configuration\" for configuration details."
~"\nFor bug reporting instructions, please see:\n"
~"<http://www.gnu.org/software/gdb/bugs/>.\n"
~"Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/>.\n"
~"For help, type \"help\".\n"
~"Type \"apropos word\" to search for commands related to \"word\".\n"
(gdb)
1-gdb-set charset ISO-8859-1
Abort trap: 6

similarly:

$ arm-none-eabi-gdb --interpreter=mi2 --nx
...
(gdb)
1-gdb-set language auto
Abort trap: 6

---

$ man signal
...
6     SIGABRT      create core image    abort program (formerly SIGIOT)
...

---

so these two commands **are** the trouble makers :-(

can anyone else confirm these findings?


regards,

Liviu


_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Neon.2 does not start GDB 7.12 on macOS

Liviu Ionescu-2
In reply to this post by Marc Khouzam

> On 27 Jan 2017, at 20:39, Marc Khouzam <[hidden email]> wrote:
>
> ... it seems to be a valid way forward  until you upgrade to CDT 9.2.1 or 9.3.

without GdbDebugConstants.GDB_PROCESS_CREATION_VALUE, on Windows, I can successfully start a J-Link or QEMU debug session with GDB 7.12 and Neon.2; breakpoints are functional, stepping too, but halting or terminating the session is not functional, I have to kill the GDB server to indirectly terminate the debug session.

I also tried with the GDB Hardware Debugging plug-in, and the behaviour is similar, Halt and Terminate are not functional.


regards,

Liviu


p.s. this GDB 7.12 seems to be a "bag of hurt" (to quote the late Steve Jobs).






_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Core Build for 9.2

Jesper Eskilson-5
In reply to this post by Doug Schaefer-3


We hope to be able to spend some time in the upcoming months investigating how to leverage Core Build for our upcoming projects.


/Jesper



From: [hidden email] <[hidden email]> on behalf of Doug Schaefer <[hidden email]>
Sent: Friday, January 27, 2017 4:32 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Core Build for 9.2
 
Hey Mark, good to hear from you.

I think for the most part CMake is working. I demoed it at a ESE Kongress a couple of months ago so gave it a good work out. Feel free to give it a try and see if there’s anything missing that you may need.

I have an example here of how I used it for the ESP8266 micro controller and it’s FreeRTOS SDK. I really like how it turned out and showed me how good CMake is for things like this.


I don’t think we need anything formal. We can certainly talk about it at the next CDT call. Our Mattermost channel is also a good vehicle for more immediate discussions.


I’m not planning on working on it the next few weeks as we’re in crunch mode with our next QNX product release coming up. So if there’s something you see that needs to be fixed or worked on, please raise a bug in Bugzilla and we can discuss things there. I do receive all new CDT Bugzilla reports so will keep an eye out for them.

Also if anyone else is interested in working on our CMake integration, please respond so we can co-ordinate.

Cheers,
Doug.

From: <[hidden email]> on behalf of Mark Goodchild <[hidden email]>
Reply-To: "CDT General developers list." <[hidden email]>
Date: Friday, January 27, 2017 at 6:51 AM
To: "CDT General developers list." <[hidden email]>
Subject: Re: [cdt-dev] Core Build for 9.2

Hi Doug,

 

Sorry for the very slow reply in this area.

 

How are you getting on with the builder work and in particular CMake?

 

I was wondering if and how Renesas can help you with this. We do have an interest in this area as you know.

 

With regards to assisting you – would it make sense to spin this into a small CDT working group for interested parties?

Perhaps then we could then decide what jobs are needed and the effort required to implement.

 

We may be able to commit some effort to this area.

 

What do you think? Perhaps this could be discussed in an upcoming CDT call?

 

Best regards,
Mark.

 

 

 

From: [hidden email] [[hidden email]] On Behalf Of Doug Schaefer
Sent: 01 November 2016 20:50
To: CDT General developers list. <[hidden email]>
Subject: [cdt-dev] Core Build for 9.2

 

Hey gang, with 9.2 only a few weeks away, I’m quickly realizing I won’t get both CMake and Qt plug-ins in shape for then. My priority is Qt so I’ll focus on that and see if I can get it ready. Anything else new like will have to wait.

 

I really like how Core Build is turning out. There’s still a lot of questions to answer so refocusing on Oxygen just seems to be the right thing to do.

 

Let me know if you have thoughts, or would like to help accelerate the program.

Doug.




Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.


_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Core Build for 9.2

Mark Goodchild
In reply to this post by Doug Schaefer-3

Hi Doug,

 

Our feeling is that the jump from managed make to this new CMake system needs some additional UI for less experienced users.

Editing the toolchain definitions directly of course works well enough – but is a bit manual for some of our user base.

 

e.g. Some of our customers will still need a user interface for build settings for example.

 

So some kind of hybrid of the CMake system with a CMake editor perhaps that offers some kind of user interface assistance looks required.

We could have a think about this and make a proposal rather than diving straight into implementation if that makes sense.

 

We are still interested as there are other customers not using managed make and certainly this would help them.

 

Best regards,

Mark.

 

 

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Doug Schaefer
Sent: 27 January 2017 15:32
To: CDT General developers list. <[hidden email]>
Subject: Re: [cdt-dev] Core Build for 9.2

 

Hey Mark, good to hear from you.

 

I think for the most part CMake is working. I demoed it at a ESE Kongress a couple of months ago so gave it a good work out. Feel free to give it a try and see if there’s anything missing that you may need.

 

I have an example here of how I used it for the ESP8266 micro controller and it’s FreeRTOS SDK. I really like how it turned out and showed me how good CMake is for things like this.

 

 

I don’t think we need anything formal. We can certainly talk about it at the next CDT call. Our Mattermost channel is also a good vehicle for more immediate discussions.

 



I’m not planning on working on it the next few weeks as we’re in crunch mode with our next QNX product release coming up. So if there’s something you see that needs to be fixed or worked on, please raise a bug in Bugzilla and we can discuss things there. I do receive all new CDT Bugzilla reports so will keep an eye out for them.

 

Also if anyone else is interested in working on our CMake integration, please respond so we can co-ordinate.

 

Cheers,

Doug.

 

From: <[hidden email]> on behalf of Mark Goodchild <[hidden email]>
Reply-To: "CDT General developers list." <[hidden email]>
Date: Friday, January 27, 2017 at 6:51 AM
To: "CDT General developers list." <[hidden email]>
Subject: Re: [cdt-dev] Core Build for 9.2

 

Hi Doug,

 

Sorry for the very slow reply in this area.

 

How are you getting on with the builder work and in particular CMake?

 

I was wondering if and how Renesas can help you with this. We do have an interest in this area as you know.

 

With regards to assisting you – would it make sense to spin this into a small CDT working group for interested parties?

Perhaps then we could then decide what jobs are needed and the effort required to implement.

 

We may be able to commit some effort to this area.

 

What do you think? Perhaps this could be discussed in an upcoming CDT call?

 

Best regards,
Mark.

 

 

 

From: [hidden email] [[hidden email]] On Behalf Of Doug Schaefer
Sent: 01 November 2016 20:50
To: CDT General developers list. <[hidden email]>
Subject: [cdt-dev] Core Build for 9.2

 

Hey gang, with 9.2 only a few weeks away, I’m quickly realizing I won’t get both CMake and Qt plug-ins in shape for then. My priority is Qt so I’ll focus on that and see if I can get it ready. Anything else new like will have to wait.

 

I really like how Core Build is turning out. There’s still a lot of questions to answer so refocusing on Oxygen just seems to be the right thing to do.

 

Let me know if you have thoughts, or would like to help accelerate the program.

Doug.

 

 

Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.




Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.


_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Neon.2 does not start GDB 7.12 on macOS

Marc Khouzam
In reply to this post by Liviu Ionescu-2
> From: [hidden email] <[hidden email]> on behalf of Liviu Ionescu <[hidden email]>
> Sent: January 28, 2017 15:03
> To: CDT General developers list.
> Subject: Re: [cdt-dev] Neon.2 does not start GDB 7.12 on macOS
>    
>
> > On 27 Jan 2017, at 20:39, Marc Khouzam <[hidden email]> wrote:
> >
> > ... it seems to be a valid way forward  until you upgrade to CDT 9.2.1 or 9.3.
>
> without GdbDebugConstants.GDB_PROCESS_CREATION_VALUE, on Windows, I can successfully start a J-Link
> or QEMU debug session with GDB 7.12 and Neon.2; breakpoints are functional, stepping too, but halting or
> terminating the session is not functional, I have to  kill the GDB server to indirectly terminate the debug session.
>
> I also tried with the GDB Hardware Debugging plug-in, and the behaviour is similar, Halt and Terminate are not functional.

This is the other known bug of CDT 9.2 related to GDB 7.12.
    Bug 509812 - Unable to interrupt arm remote target with Neon and GDB 7.12
    (http://eclip.se/509812)
Note that this affects all 'GDB Hardware debugging' launches, as well as all launches
on Windows and Mac.

Alvaro has already fixed all these problems for the 9.2.1 release.
That release is scheduled for end of March.  However, with these important issues
having been found, I don't mind doing a special 9.2.1 release very soon and a 9.2.2 for March.
Let me know if that would be useful (so I don't spend time for nothing).

> p.s. this GDB 7.12 seems to be a "bag of hurt" (to quote the late Steve Jobs).

The problems actually originate in CDT's use of GDB 7.12's new awesome full console support.
The actual root cause of the problem is CDT's lack of broad testing.
We need more attention for Windows and for Mac, and for Hardware debugging.
These three areas are not covered by the core CDT Debug committers and
are the three areas that experienced serious bugs in the 9.2 release.

P.S.  There is another bug reported from someone using the GNU ARM plugins
Bug 507429 - The problem with the launch SEGGER J-Link GDB Server
http://eclip.se/507429
_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Core Build for 9.2

Doug Schaefer-3
In reply to this post by Mark Goodchild

From: <[hidden email]> on behalf of Mark Goodchild <[hidden email]>
Reply-To: "CDT General developers list." <[hidden email]>
Date: Monday, January 30, 2017 at 6:27 AM
To: "CDT General developers list." <[hidden email]>
Subject: Re: [cdt-dev] Core Build for 9.2

Hi Doug,

 

Our feeling is that the jump from managed make to this new CMake system needs some additional UI for less experienced users.

Editing the toolchain definitions directly of course works well enough – but is a bit manual for some of our user base.

 

e.g. Some of our customers will still need a user interface for build settings for example.

 

So some kind of hybrid of the CMake system with a CMake editor perhaps that offers some kind of user interface assistance looks required.

We could have a think about this and make a proposal rather than diving straight into implementation if that makes sense.


Sounds reasonable. I have no preconcieved notions of what such a UI would look like or how it would work so will be very interested in what you can come up with.

Thanks!
Doug

 

We are still interested as there are other customers not using managed make and certainly this would help them.

 

Best regards,

Mark.

 

 

 

From: [hidden email] [[hidden email]] On Behalf Of Doug Schaefer
Sent: 27 January 2017 15:32
To: CDT General developers list. <[hidden email]>
Subject: Re: [cdt-dev] Core Build for 9.2

 

Hey Mark, good to hear from you.

 

I think for the most part CMake is working. I demoed it at a ESE Kongress a couple of months ago so gave it a good work out. Feel free to give it a try and see if there’s anything missing that you may need.

 

I have an example here of how I used it for the ESP8266 micro controller and it’s FreeRTOS SDK. I really like how it turned out and showed me how good CMake is for things like this.

 

 

I don’t think we need anything formal. We can certainly talk about it at the next CDT call. Our Mattermost channel is also a good vehicle for more immediate discussions.

 



I’m not planning on working on it the next few weeks as we’re in crunch mode with our next QNX product release coming up. So if there’s something you see that needs to be fixed or worked on, please raise a bug in Bugzilla and we can discuss things there. I do receive all new CDT Bugzilla reports so will keep an eye out for them.

 

Also if anyone else is interested in working on our CMake integration, please respond so we can co-ordinate.

 

Cheers,

Doug.

 

From: <[hidden email]> on behalf of Mark Goodchild <[hidden email]>
Reply-To: "CDT General developers list." <[hidden email]>
Date: Friday, January 27, 2017 at 6:51 AM
To: "CDT General developers list." <[hidden email]>
Subject: Re: [cdt-dev] Core Build for 9.2

 

Hi Doug,

 

Sorry for the very slow reply in this area.

 

How are you getting on with the builder work and in particular CMake?

 

I was wondering if and how Renesas can help you with this. We do have an interest in this area as you know.

 

With regards to assisting you – would it make sense to spin this into a small CDT working group for interested parties?

Perhaps then we could then decide what jobs are needed and the effort required to implement.

 

We may be able to commit some effort to this area.

 

What do you think? Perhaps this could be discussed in an upcoming CDT call?

 

Best regards,
Mark.

 

 

 

From:[hidden email] [[hidden email]] On Behalf Of Doug Schaefer
Sent: 01 November 2016 20:50
To: CDT General developers list. <[hidden email]>
Subject: [cdt-dev] Core Build for 9.2

 

Hey gang, with 9.2 only a few weeks away, I’m quickly realizing I won’t get both CMake and Qt plug-ins in shape for then. My priority is Qt so I’ll focus on that and see if I can get it ready. Anything else new like will have to wait.

 

I really like how Core Build is turning out. There’s still a lot of questions to answer so refocusing on Oxygen just seems to be the right thing to do.

 

Let me know if you have thoughts, or would like to help accelerate the program.

Doug.

 

 

Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.




Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.


_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Core Build for 9.2

Marc Khouzam

I've added a bullet to the agenda of the CDT call next week. 




From: [hidden email] <[hidden email]> on behalf of Doug Schaefer <[hidden email]>
Sent: January 30, 2017 10:51
To: CDT General developers list.
Subject: Re: [cdt-dev] Core Build for 9.2
 

From: <[hidden email]> on behalf of Mark Goodchild <[hidden email]>
Reply-To: "CDT General developers list." <[hidden email]>
Date: Monday, January 30, 2017 at 6:27 AM
To: "CDT General developers list." <[hidden email]>
Subject: Re: [cdt-dev] Core Build for 9.2

Hi Doug,

 

Our feeling is that the jump from managed make to this new CMake system needs some additional UI for less experienced users.

Editing the toolchain definitions directly of course works well enough – but is a bit manual for some of our user base.

 

e.g. Some of our customers will still need a user interface for build settings for example.

 

So some kind of hybrid of the CMake system with a CMake editor perhaps that offers some kind of user interface assistance looks required.

We could have a think about this and make a proposal rather than diving straight into implementation if that makes sense.


Sounds reasonable. I have no preconcieved notions of what such a UI would look like or how it would work so will be very interested in what you can come up with.

Thanks!
Doug

 

We are still interested as there are other customers not using managed make and certainly this would help them.

 

Best regards,

Mark.

 

 

 

From: [hidden email] [[hidden email]] On Behalf Of Doug Schaefer
Sent: 27 January 2017 15:32
To: CDT General developers list. <[hidden email]>
Subject: Re: [cdt-dev] Core Build for 9.2

 

Hey Mark, good to hear from you.

 

I think for the most part CMake is working. I demoed it at a ESE Kongress a couple of months ago so gave it a good work out. Feel free to give it a try and see if there’s anything missing that you may need.

 

I have an example here of how I used it for the ESP8266 micro controller and it’s FreeRTOS SDK. I really like how it turned out and showed me how good CMake is for things like this.

 

 

I don’t think we need anything formal. We can certainly talk about it at the next CDT call. Our Mattermost channel is also a good vehicle for more immediate discussions.

 



I’m not planning on working on it the next few weeks as we’re in crunch mode with our next QNX product release coming up. So if there’s something you see that needs to be fixed or worked on, please raise a bug in Bugzilla and we can discuss things there. I do receive all new CDT Bugzilla reports so will keep an eye out for them.

 

Also if anyone else is interested in working on our CMake integration, please respond so we can co-ordinate.

 

Cheers,

Doug.

 

From: <[hidden email]> on behalf of Mark Goodchild <[hidden email]>
Reply-To: "CDT General developers list." <[hidden email]>
Date: Friday, January 27, 2017 at 6:51 AM
To: "CDT General developers list." <[hidden email]>
Subject: Re: [cdt-dev] Core Build for 9.2

 

Hi Doug,

 

Sorry for the very slow reply in this area.

 

How are you getting on with the builder work and in particular CMake?

 

I was wondering if and how Renesas can help you with this. We do have an interest in this area as you know.

 

With regards to assisting you – would it make sense to spin this into a small CDT working group for interested parties?

Perhaps then we could then decide what jobs are needed and the effort required to implement.

 

We may be able to commit some effort to this area.

 

What do you think? Perhaps this could be discussed in an upcoming CDT call?

 

Best regards,
Mark.

 

 

 

From:[hidden email] [[hidden email]] On Behalf Of Doug Schaefer
Sent: 01 November 2016 20:50
To: CDT General developers list. <[hidden email]>
Subject: [cdt-dev] Core Build for 9.2

 

Hey gang, with 9.2 only a few weeks away, I’m quickly realizing I won’t get both CMake and Qt plug-ins in shape for then. My priority is Qt so I’ll focus on that and see if I can get it ready. Anything else new like will have to wait.

 

I really like how Core Build is turning out. There’s still a lot of questions to answer so refocusing on Oxygen just seems to be the right thing to do.

 

Let me know if you have thoughts, or would like to help accelerate the program.

Doug.

 

 

Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.




Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.


_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Neon.2 does not start GDB 7.12 on macOS

Liviu Ionescu-2
In reply to this post by Marc Khouzam

> On 30 Jan 2017, at 16:37, Marc Khouzam <[hidden email]> wrote:
>
> This is the other known bug of CDT 9.2 related to GDB 7.12.
>    Bug 509812 - Unable to interrupt arm remote target with Neon and GDB 7.12
>    (http://eclip.se/509812)
> Note that this affects all 'GDB Hardware debugging' launches, as well as all launches
> on Windows and Mac.

aha, it seems to be the same problem I faced.

> having been found, I don't mind doing a special 9.2.1 release very soon and a 9.2.2 for March.
> Let me know if that would be useful (so I don't spend time for nothing).

if you have a nightly build for CDT that includes this fix, I can test it before you taking the time to make the release.

> The problems actually originate in CDT's use of GDB 7.12's new awesome full console support.

it might be awesome for most of the users, but for the average GNU ARM Eclipse user, the GDB console is pretty ignored/useless, and the previous version of the console was more then enough.

as such, without offending anyone, could you consider adding a Preferences option to enable/disable the new debug console?

another annoying behaviour of the new console is that clicking on the GDB process does not set the focus to the new console, as it does when clicking all other processes.

> The actual root cause of the problem is CDT's lack of broad testing.
> We need more attention for Windows and for Mac, and for Hardware debugging.
> These three areas are not covered by the core CDT Debug committers and
> are the three areas that experienced serious bugs in the 9.2 release.

as I said, if there are nightly builds, I can install them on a test Eclipse from time to time. if not, I might consider a configuration that uses the live git, but it is more tedious, and I cannot dedicate full time to these tests.

> P.S.  There is another bug reported from someone using the GNU ARM plugins
> Bug 507429 - The problem with the launch SEGGER J-Link GDB Server
> http://eclip.se/507429

it looks like the initial bug report used the version that created the GDB server process with the GDB console attribute. it should be fixed now.

regards,

Liviu

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Neon.2 does not start GDB 7.12 on macOS

Marc Khouzam

> From: [hidden email] <[hidden email]> on behalf of Liviu Ionescu <[hidden email]>
> Sent: January 30, 2017 13:42
> To: CDT General developers list.
> Subject: Re: [cdt-dev] Neon.2 does not start GDB 7.12 on macOS
>  
> > On 30 Jan 2017, at 16:37, Marc Khouzam <[hidden email]> wrote:
> > 
> > This is the other known bug of CDT 9.2 related to GDB 7.12.
> >    Bug 509812 - Unable to interrupt arm remote target with Neon and GDB 7.12
> >    (http://eclip.se/509812)
> > Note that this affects all 'GDB Hardware debugging' launches, as well as all launches
> > on Windows and Mac.
> aha, it seems to be the same problem I faced.
> > having been found, I don't mind doing a special 9.2.1 release very soon and a 9.2.2 for March.
> > Let me know if that would be useful (so I don't spend time for nothing).
> if you have a nightly build for CDT that includes this fix, I can test it before you taking the time to make the release.

Can you try the build at:
https://ci.eclipse.org/cdt/job/cdt-9.2/35/artifact/releng/org.eclipse.cdt.repo/target/org.eclipse.cdt.repo.zip


I believe it has all the fixes you need.


> > The problems actually originate in CDT's use of GDB 7.12's new awesome full console support.
> it might be awesome for most of the users, but for the average GNU ARM Eclipse user, the GDB console is 
> pretty ignored/useless, and the previous version of the console was more then enough.

I think, once the console works nicely, you will not regret having it.
That being said, we did make it easy for extenders to automatically disable the full console, but programatically
only.  I'll have a look at your plugins to see if I can suggest something.

> as such, without offending anyone, could you consider adding a Preferences option to enable/disable the new debug console?

I would prefer to avoid a preference.  I don't feel a user would ever want to turn off the new console.  Again, assuming it
works well, there really would be no reason to want to use the basic console, it is really a very bad user experience.

> another annoying behaviour of the new console is that clicking on the GDB process does not set the focus to the 
> new console, as it does when clicking all other processes.

When you select the GDB process, the Debugger Console view will not be brought to the top, but that view
will show the full console that corresponds to that GDB.  Bringing the view to the top was too intrusive.
However, what people do is move that view to a different place in the perspective so that I can stay
visible when the standard console view is visible.  The nice think about that is that you can use
the GDB console while looking at the output of the program you are debugging.

> > The actual root cause of the problem is CDT's lack of broad testing.
> > We need more attention for Windows and for Mac, and for Hardware debugging.
> > These three areas are not covered by the core CDT Debug committers and 
> > are the three areas that experienced serious bugs in the 9.2 release.
> as I said, if there are nightly builds, I can install them on a test Eclipse from time to time. 
> if not, I might consider a configuration that uses the live git, but it is more tedious, and I cannot 
> dedicate full time to these tests.

We have nightly builds for every upcoming release as soon as we start coding on that branch.
If you update to these builds regularly for your work, you will notice quickly if something breaks.
For example, when working on CDT, we use the upcoming Eclipse platform (Oxygen in this case)
as soon as we can, to avoid late surprises.

> > P.S.  There is another bug reported from someone using the GNU ARM plugins
> > Bug 507429 - The problem with the launch SEGGER J-Link GDB Server
> > http://eclip.se/507429
> it looks like the initial bug report used the version that created the GDB server process with the GDB console attribute. it should be fixed now.

Great.  I saw you answer on the bug.  Once the person that opened the bug confirms this theory we'll close
it and I think we'll have addressed all urgent issues.

BR,
Marc


_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
12
Loading...