From ricardo_anguiano at mentor.com Mon Dec 5 17:51:24 2011 From: ricardo_anguiano at mentor.com (Ricardo Anguiano) Date: Mon, 5 Dec 2011 09:51:24 -0800 Subject: [arm-gnu] Suscribing. In-Reply-To: References: Message-ID: <4EDD049C.1040806@mentor.com> On 11/29/2011 01:26 PM, ARTHUR WOLF wrote: > A colleage would like to suscribe to this mailing list, but can't > find any information about how to do that on the web ( maybe because > of the recent changes ? ). Hello Arthur, You can point your colleague here: http://sourcerytools.com/cgi-bin/mailman/listinfo/arm-gnu Thanks, -- Ricardo Anguiano Mentor Graphics From jbsnyder at fanplastic.org Mon Dec 5 18:29:22 2011 From: jbsnyder at fanplastic.org (James Snyder) Date: Mon, 5 Dec 2011 12:29:22 -0600 Subject: [arm-gnu] Suscribing. In-Reply-To: References: Message-ID: I'm not completely sure whether it works (with all the recent changes), but the mailman page for the list (listed at the end of messages sent by the list) can be found here: http://sourcerytools.com/cgi-bin/mailman/listinfo/arm-gnu On Tue, Nov 29, 2011 at 3:26 PM, ARTHUR WOLF wrote: > Hello. > > A colleage would like to suscribe to this mailing list, but can't find any > information about how to do that on the web ( maybe because of the recent > changes ? ). > Any help ? > > Thanks a lot. > > -- > Courage et bonne humeur. > > > _______________________________________________ > arm-gnu mailing list > arm-gnu at codesourcery.com > http://sourcerytools.com/cgi-bin/mailman/listinfo/arm-gnu > From carlos_odonell at mentor.com Tue Dec 6 05:40:19 2011 From: carlos_odonell at mentor.com (Carlos O'Donell) Date: Tue, 6 Dec 2011 00:40:19 -0500 Subject: [arm-gnu] Suscribing. In-Reply-To: References: Message-ID: <4EDDAAC3.7020204@mentor.com> On 11/29/2011 4:26 PM, ARTHUR WOLF wrote: > Hello. > > A colleage would like to suscribe to this mailing list, but can't find any information about how to do that on the web ( maybe because of the recent changes ? ). > Any help ? > > Thanks a lot. I've forwarded your request on to the appropriate people. I'm sorry that this information appears to have been lost in the shuffle. Cheers, Carlos. -- Carlos O'Donell Mentor Graphics / CodeSourcery carlos at codesourcery.com +1 (613) 963 1026 From david at westcontrol.com Tue Dec 6 07:49:43 2011 From: david at westcontrol.com (David Brown) Date: Tue, 06 Dec 2011 08:49:43 +0100 Subject: [arm-gnu] Suscribing. In-Reply-To: References: Message-ID: <4EDDC917.4010501@westcontrol.com> On 29/11/2011 22:26, ARTHUR WOLF wrote: > Hello. > > A colleage would like to suscribe to this mailing list, but can't find > any information about how to do that on the web ( maybe because of the > recent changes ? ). > Any help ? > You can use the link in the mailing list signature at the bottom of every post: mvh., David > Thanks a lot. > > -- > Courage et bonne humeur. > > > > _______________________________________________ > arm-gnu mailing list > arm-gnu at codesourcery.com > http://sourcerytools.com/cgi-bin/mailman/listinfo/arm-gnu From jaconzar at gmail.com Sun Dec 11 19:50:19 2011 From: jaconzar at gmail.com (JZarnow) Date: Sun, 11 Dec 2011 20:50:19 +0100 Subject: [arm-gnu] When is the next (2011-q3) release? In-Reply-To: <9377404.3ZsoPVX4sG@kishore-zeus> References: <9377404.3ZsoPVX4sG@kishore-zeus> Message-ID: <4EE5097B.9050200@gmail.com> -----Original Message----- > In the past years the q3 release was usually out by this time. Is there a delay this year? As usual: Small & effective company bought by a giant monster = death of valuable projects... Stakeholders & CxO's apparently don't get anything from Lite version delivery on-time... From david at westcontrol.com Tue Dec 13 07:51:01 2011 From: david at westcontrol.com (David Brown) Date: Tue, 13 Dec 2011 08:51:01 +0100 Subject: [arm-gnu] When is the next (2011-q3) release? In-Reply-To: <4EE5097B.9050200@gmail.com> References: <9377404.3ZsoPVX4sG@kishore-zeus> <4EE5097B.9050200@gmail.com> Message-ID: <4EE703E5.2080207@westcontrol.com> On 11/12/2011 20:50, JZarnow wrote: > -----Original Message----- > >> In the past years the q3 release was usually out by this time. Is >> there a delay this year? > > As usual: > > Small & effective company bought by a giant monster > = death of valuable projects... > > Stakeholders & CxO's apparently don't get anything > from Lite version delivery on-time... Let's not jump to pessimistic conclusions. I'm sure the change of ownership meant a number of changes, and some delays while things stabilise is not unexpected, but my understanding is that CodeSourcery development continues much as it always has done. It could also be that there have been changes in emphasis or priority - after all, ARM gcc is only one of CodeSourcery's products, and the combination of Mentor and CodeSourcery must figure out where their products complement each other, and where they compete with themselves. As long as we continue to see posts from CodeSourcery email addresses in the gcc development mailing list, we can see that the team are still pulling gcc forward. And as "giant monsters" go, I think one could do a lot worse than Mentor. They need gcc, so it's in their interest to help develop it further, and they have always had a reputation for quality tools (though their price-points have traditionally been higher than CodeSourcery's). Of course, I've no inside information, and have no idea when the next release will be out - but I certainly don't think it's time to give up on CodeSourcery. mvh,. David From mark_mitchell at mentor.com Tue Dec 13 15:41:32 2011 From: mark_mitchell at mentor.com (Mitchell, Mark) Date: Tue, 13 Dec 2011 15:41:32 +0000 Subject: [arm-gnu] When is the next (2011-q3) release? In-Reply-To: <4EE703E5.2080207@westcontrol.com> References: <9377404.3ZsoPVX4sG@kishore-zeus> <4EE5097B.9050200@gmail.com> <4EE703E5.2080207@westcontrol.com> Message-ID: > Of course, I've no inside information, and have no idea when the next > release will be out - but I certainly don't think it's time to give up > on CodeSourcery. David, thank you for the kind words! We are, as you say, very much continuing on our traditional path within Mentor. Of course, our business continues to evolve, but we're still very much focused on the GNU toolchain. The next ARM Lite Edition release will be available shortly. We are working through a number of web and release issues, as all of our web infrastructure has been recently updated as part of our transition into Mentor, but the development of the Fall 2011 is very nearly complete, and you can expect an announcement here shortly. Thank you, Mark Mitchell CodeSourcery / Mentor Graphics From kitts.mailinglists at gmail.com Wed Dec 14 18:43:19 2011 From: kitts.mailinglists at gmail.com (Kishore Jonnalagadda) Date: Thu, 15 Dec 2011 00:13:19 +0530 Subject: [arm-gnu] When is the next (2011-q3) release? In-Reply-To: References: <9377404.3ZsoPVX4sG@kishore-zeus> <4EE5097B.9050200@gmail.com> <4EE703E5.2080207@westcontrol.com> Message-ID: Thanks for the information mark. The only reason I asked was to know if the transition was over and if it brought with it any process changes that we users might need to know. On Dec 14, 2011 10:04 PM, "Mitchell, Mark" wrote: > > Of course, I've no inside information, and have no idea when the next > > release will be out - but I certainly don't think it's time to give up > > on CodeSourcery. > > David, thank you for the kind words! > > We are, as you say, very much continuing on our traditional path within > Mentor. Of course, our business continues to evolve, but we're still very > much focused on the GNU toolchain. > > The next ARM Lite Edition release will be available shortly. We are > working through a number of web and release issues, as all of our web > infrastructure has been recently updated as part of our transition into > Mentor, but the development of the Fall 2011 is very nearly complete, and > you can expect an announcement here shortly. > > Thank you, > > Mark Mitchell > CodeSourcery / Mentor Graphics > _______________________________________________ > arm-gnu mailing list > arm-gnu at codesourcery.com > http://sourcerytools.com/cgi-bin/mailman/listinfo/arm-gnu > -------------- next part -------------- An HTML attachment was scrubbed... URL: From johnsolmac at gmail.com Tue Dec 20 09:31:08 2011 From: johnsolmac at gmail.com (solmac john) Date: Tue, 20 Dec 2011 15:01:08 +0530 Subject: [arm-gnu] Issue with gdb 7.0 backtrace Message-ID: Dear All, As we know, generally, we run bt command in gdb, gdb show the seg fault location in last backtrace. I found one strange behaviour If i run bt command in gdb, at that itme, gdb didn?t show the segment fault location in backtrace by default. Can some one tell the reason and is this expected in SMP warning: Unable to find dynamic linker. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. Core was generated by `./myapp'. Program terminated with signal 11, Segmentation fault. #0 malloc_consolidate (av=0x47600010) at malloc.c:5201 //not fault point thread running on CPU1 5201 malloc.c: No such file or directory. in malloc.c (gdb) bt #0 malloc_consolidate (av=0x47600010) at malloc.c:5201 #1 0x426eb1a8 in _int_malloc (av=0x47600010, bytes=) at malloc.c:4435 gdb) info reg r0 0xfffe8ed4 4294872788 r1 0x427a8000 1115324416 r2 0x91 145 r3 0x708812d8 1887965912 r4 0x47600040 1197473856 r5 0x708812d8 1887965912 r6 0xb7e81318 3085439768 r7 0x47600040 1197473856 r8 0x476ec930 1198442800 r9 0x47600010 1197473808 r10 0x28 40 r11 0x70881130 1887965488 r12 0x47600018 1197473816 sp 0x431aeb20 0x431aeb20 lr 0x426eb1a8 1114550696 pc 0x426e819c 0x426e819c // also , program count show the CPU1 info fps 0x0 0 cpsr 0x60000010 1610612752 (gdb) info thread 225 Thread 190 0x00000000 in ?? () // real user fault point 224 Thread 132 __pthread_cond_wait (cond=0x41ddf060, mutex=0x41ddf090) Quit (gdb) thread 225 [Switching to thread 225 (Thread 190)]#0 0x00000000 in ?? () (gdb) bt #0 0x00000000 in ?? () (gdb) info reg r0 0x6de22ba0 1843538848 r1 0x476e1648 1198397000 r2 0x0 0 r3 0x0 0 r4 0x83407ef0 2202042096 r5 0x476e1648 1198397000 r6 0x68b3888 109787272 r7 0x0 0 r8 0x6de22ba0 1843538848 r9 0x6de22bf0 1843538928 r10 0x83407f44 2202042180 r11 0x6de22bd4 1843538900 r12 0x23f 575 sp 0x6de22b88 0x6de22b88 lr 0x1808774 25200500 pc 0x0 0 // program show the user fault info correctly of CPU0 fps 0x0 0 cpsr 0x20000010 536870928 Thanks, John -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlos_odonell at mentor.com Wed Dec 21 18:27:41 2011 From: carlos_odonell at mentor.com (Carlos O'Donell) Date: Wed, 21 Dec 2011 13:27:41 -0500 Subject: [arm-gnu] Issue with gdb 7.0 backtrace In-Reply-To: References: Message-ID: <4EF2251D.1000301@mentor.com> [trimming CC]. On 12/20/2011 4:31 AM, solmac john wrote: > As we know, generally, we run bt command in gdb, gdb show the seg fault location in last backtrace. > > I found one strange behaviour If i run bt command in gdb, at that itme, gdb didn?t show the segment fault location in backtrace by default. That's normal, `bt' shows only the backtrace for the last active thread. You must run `thread apply backtrace' (or some shortcut form) to get a backtrace of *all* threads to see which one most likely faulted. > Can some one tell the reason > and is this expected in SMP > > warning: Unable to find dynamic linker. > GDB will be unable to debug shared library initializers > and track explicitly loaded dynamic code. I assume you are going remote debug. Until you fix the "warning: ..." you're going to have problems debugging anything with threads. The warning indicates that gdb, and the target do not agree about the libraries they are using for debugging. You must keep the target in sync with the runtimes you use for debugging, otherwise debugging is unreliable. Cheers, Carlos. -- Carlos O'Donell Mentor Graphics / CodeSourcery carlos at codesourcery.com +1 (613) 963 1026 From johnsolmac at gmail.com Thu Dec 22 10:59:08 2011 From: johnsolmac at gmail.com (solmac john) Date: Thu, 22 Dec 2011 16:29:08 +0530 Subject: [arm-gnu] Issue with gdb 7.0 backtrace In-Reply-To: <4EF2251D.1000301@mentor.com> References: <4EF2251D.1000301@mentor.com> Message-ID: Hi Carlos/Santosa, After detail dump analysis I found current thread crash with malloc_consolidate function only Thanks a Lot. Thanks, John On Wed, Dec 21, 2011 at 11:57 PM, Carlos O'Donell wrote: > [trimming CC]. > > On 12/20/2011 4:31 AM, solmac john wrote: > > As we know, generally, we run bt command in gdb, gdb show the seg fault > location in last backtrace. > > > > I found one strange behaviour If i run bt command in gdb, at that itme, > gdb didn?t show the segment fault location in backtrace by default. > > That's normal, `bt' shows only the backtrace for the last active thread. > > You must run `thread apply backtrace' (or some shortcut form) to get a > backtrace of *all* threads to see which one most likely faulted. > > > Can some one tell the reason > > and is this expected in SMP > > > > warning: Unable to find dynamic linker. > > GDB will be unable to debug shared library initializers > > and track explicitly loaded dynamic code. > > I assume you are going remote debug. > > Until you fix the "warning: ..." you're going to have problems debugging > anything with threads. > > The warning indicates that gdb, and the target do not agree about the > libraries they are using for debugging. > > You must keep the target in sync with the runtimes you use for debugging, > otherwise debugging is unreliable. > > Cheers, > Carlos. > -- > Carlos O'Donell > Mentor Graphics / CodeSourcery > carlos at codesourcery.com > +1 (613) 963 1026 > -------------- next part -------------- An HTML attachment was scrubbed... URL: