[RTEMS Project] #2830: throwing std::runtime on PC BSP fails.

[RTEMS trac]

#2830: throwing std::runtime on PC BSP fails.
-------------------------+----------------------------
 Reporter:  Chris Johns  |       Owner:  Needs Funding
     Type:  defect       |      Status:  assigned
 Priority:  normal       |   Milestone:  Indefinite
Component:  unspecified  |     Version:  5
 Severity:  normal       |  Resolution:
 Keywords:               |  Blocked By:
 Blocking:               |
-------------------------+----------------------------

Comment (by Joel Sherrill):

 I think that's the extent of the source changes which we think will
 resolve the issue. Someone may point to documentation but it is Friday and
 I am going to point to an example of adding a patch and talk you through
 it. This assumes the 5 branch because we won't get a patch merged into gcc
 7. We can address RTEMS master after 5 is fixed. The patch for gcc should
 be the same. We just have more latitude to merge it to gcc master and
 newer release branches.

 How to generate a patch:
 https://devel.rtems.org/wiki/Developer/Coding/GenerateAPatch which should
 also be in the Software Engineering Guide.

 The easiest example I saw was in rtems/config/5/rtems-lm32.bset which adds
 a gdb patch only for lm32 builds. You would be adding a gcc patch to
 rtems/config/5/rtems-i386.bset.

 For merging, a patch needs an Internet home (attaching to a ticket gives
 you a URL) but for testing, you can just drop the diff into the patches
 subdirectory config/rtems/patches. The RSB will see it there and not try
 to fetch it. But you need an sha checksum.

 After that, it is build as normal for testing purpose. If this gives you a
 toolset that works, we can address changing the URL. But attaching it to
 this ticket and getting the URL for the "raw" attachment should work just
 fine.

--
Ticket URL: <http://devel.rtems.org/ticket/2830#comment:15>
RTEMS Project <http://www.rtems.org/>
RTEMS Project