Re: stm32 external SRAM

2019-06-16 Thread Christian Mauderer 
If you put any sections into the external RAM that need initialization,
you have to init the RAM before the BSP copies it's sections. The STM32
BSP copies it's sections in bsp_start_hook_1(). So either put it in
bsp_start_hook_0 or in bsp_start_hook_1 before the copy_section calls.
Attention: You can't use much in these functions. They are in a very
early initialization stage. So be careful what you put there.

If you only want malloc to allocate memory from there, there might is a
later point where you can do that.

On 17/06/2019 08:32, Jython wrote:
> Thank you and the example! that is to say put extern sram init in
> bsp_start( void ) function?
> 
> On Mon, Jun 17, 2019 at 1:04 PM Christian Mauderer
>  > wrote:
> 
> On 17/06/2019 03:05, Jython wrote:
> > STM32:
> >     112KB at 2000 
> >     16KB at 2001 C000
> >
> > external sram : 1MB at 0x6800
> >
> >  does MEMORY layout support RAM2?
> 
> Hello Jython,
> 
> you can distribute the regions to the two RAMs. For example this BSP
> does that:
> 
> 
> https://git.rtems.org/rtems/tree/bsps/arm/lpc32xx/start/linkcmds.lpc32xx_phycore
> 
> Please note that you have to take a detailed look at what is used till
> your external RAM initialization run and what not. But if you put your
> external RAM initialization in an early enough step, you shouldn't get
> problems with that.
> 
> Best regards
> 
> Christian
> 
> >
> > On Fri, Jun 14, 2019 at 10:13 PM Christian Mauderer
> >  
> >  >> wrote:
> >
> >     If you have already added the chip and it is initialized
> during startup,
> >     you most likely have to add a section for it in your linker
> command
> >     file. Depending on where your internal RAM is located and
> where the
> >     external one is: If they are continuous that can be enough.
> >
> >     Best regards
> >
> >     Christian
> >
> >     On 14/06/2019 04:42, Jython wrote:
> >     > we have added 1M ram by FSMC,  and want to manage it by
> system malloc
> >     > controler
> >     >
> >     > On Fri, Jun 14, 2019 at 10:26 AM Mr. Andrei Chichak
> >     mailto:gro...@chichak.ca>
> >
> >     > 
>  >     >
> >     >     A 407 doesn’t normally have external RAM.
> >     >
> >     >     ARMs have flash at 0 and the 407 has RAM at 0x2000 
> as you
> >     >     discussed earlier.
> >     >
> >     >     If you want to work with external flash or RAM, you have
> to set up
> >     >     the FSMC or FMC to support it, but that isn’t a part of
> the dev
> >     >     board that Sebastian used for the BSP port.
> >     >
> >     >     The external memory is going to be very specific to your
> board.
> >     >     Which board are you working with?
> >     >
> >     >     A
> >     >
> >     >     > On 2019-June-13, at 06:23, Christian Mauderer
> >     >      
> >      >
> >     >      
> >       >     >     >
> >     >     > On 05/06/2019 02:55, Jython wrote:
> >     >     >> Hello!
> >     >     >>
> >     >     >>     2. In the normal (non-debugging) case, the linker
> >     script still
> >     >     >>        places the
> >     >     >>
> >     >     >>    .text section near zero, but places the start of the
> >     .data and
> >     >     .bss
> >     >     >>    sections at the start location of the MPC555's
> internal
> >     RAM. The
> >     >     >>    system startup code then configures the external
> RAM just
> >     >     after the
> >     >     >>    internal RAM in memory, forming one large block
> from the
> >     two RAM
> >     >     >>    devices.
> >     >     >>
> >     >     >> from https://devel.rtems.org/wiki/TBR/BSP/Ss555
> >     >     >>
> >     >     >> but i dont know how to configure the external RAM just
> >     after the
> >     >     >> internal RAM in memory?
> >     >     >> hope you could give me some guide!
> >     >     >> 
> >     >     >>
> >     >     >
> >     >     > Hello Jython,
> >     >     >
> >   

Re: stm32 external SRAM

2019-06-16 Thread Jython 
Thank you and the example! that is to say put extern sram init in
bsp_start( void ) function?

On Mon, Jun 17, 2019 at 1:04 PM Christian Mauderer <
christian.maude...@embedded-brains.de> wrote:

> On 17/06/2019 03:05, Jython wrote:
> > STM32:
> > 112KB at 2000 
> > 16KB at 2001 C000
> >
> > external sram : 1MB at 0x6800
> >
> >  does MEMORY layout support RAM2?
>
> Hello Jython,
>
> you can distribute the regions to the two RAMs. For example this BSP
> does that:
>
>
> https://git.rtems.org/rtems/tree/bsps/arm/lpc32xx/start/linkcmds.lpc32xx_phycore
>
> Please note that you have to take a detailed look at what is used till
> your external RAM initialization run and what not. But if you put your
> external RAM initialization in an early enough step, you shouldn't get
> problems with that.
>
> Best regards
>
> Christian
>
> >
> > On Fri, Jun 14, 2019 at 10:13 PM Christian Mauderer
> >  > > wrote:
> >
> > If you have already added the chip and it is initialized during
> startup,
> > you most likely have to add a section for it in your linker command
> > file. Depending on where your internal RAM is located and where the
> > external one is: If they are continuous that can be enough.
> >
> > Best regards
> >
> > Christian
> >
> > On 14/06/2019 04:42, Jython wrote:
> > > we have added 1M ram by FSMC,  and want to manage it by system
> malloc
> > > controler
> > >
> > > On Fri, Jun 14, 2019 at 10:26 AM Mr. Andrei Chichak
> > mailto:gro...@chichak.ca>
> > > >> wrote:
> > >
> > > A 407 doesn’t normally have external RAM.
> > >
> > > ARMs have flash at 0 and the 407 has RAM at 0x2000  as you
> > > discussed earlier.
> > >
> > > If you want to work with external flash or RAM, you have to
> set up
> > > the FSMC or FMC to support it, but that isn’t a part of the dev
> > > board that Sebastian used for the BSP port.
> > >
> > > The external memory is going to be very specific to your board.
> > > Which board are you working with?
> > >
> > > A
> > >
> > > > On 2019-June-13, at 06:23, Christian Mauderer
> > >  > 
> > >  > >> wrote:
> > > >
> > > > On 05/06/2019 02:55, Jython wrote:
> > > >> Hello!
> > > >>
> > > >> 2. In the normal (non-debugging) case, the linker
> > script still
> > > >>places the
> > > >>
> > > >>.text section near zero, but places the start of the
> > .data and
> > > .bss
> > > >>sections at the start location of the MPC555's internal
> > RAM. The
> > > >>system startup code then configures the external RAM just
> > > after the
> > > >>internal RAM in memory, forming one large block from the
> > two RAM
> > > >>devices.
> > > >>
> > > >> from https://devel.rtems.org/wiki/TBR/BSP/Ss555
> > > >>
> > > >> but i dont know how to configure the external RAM just
> > after the
> > > >> internal RAM in memory?
> > > >> hope you could give me some guide!
> > > >>
> > > >>
> > > >
> > > > Hello Jython,
> > > >
> > > > the documentation you linked is for an MPC. But your subject
> > line
> > > > mentions an STM32. What controller / BSP are you using?
> > > >
> > > > Best regards
> > > >
> > > > Christian Mauderer
> > > > --
> > > > 
> > > > embedded brains GmbH
> > > > Herr Christian Mauderer
> > > > Dornierstr. 4
> > > > D-82178 Puchheim
> > > > Germany
> > > > email: christian.maude...@embedded-brains.de
> > 
> > >  > >
> > > > Phone: +49-89-18 94 741 - 18
> > > > Fax:   +49-89-18 94 741 - 08
> > > > PGP: Public key available on request.
> > > >
> > > > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne
> > des EHUG.
> > > > ___
> > > > users mailing list
> > > > users@rtems.org 
> > >
> > > > http://lists.rtems.org/mailman/listinfo/users
> > >
> > >
> > > ___
> > > users mailing list
> > > users@rtems.org 
> > > http://lists.rtems.

Re: gdb-8.2.1 build failed on macos 10.11.6

2019-06-16 Thread Chris Johns 
On 17/6/19 5:31 am, Juan Rafael García Blanco wrote:
> Hi,
> 
> I have installed macOS 10.9.5, for which Xcode includes the following 
> compiler:
> Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn)
> Target: x86_64-apple-darwin13.4.0
> Thread model: posix
> 
> Compilation of gdb 8.2 fails also with this setup, although the error seems 
> to be caused by the compiler itself. Please find below the error log:
>   CXXcli/cli-script.o
> Stack dump:
> 0.  Program arguments: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
>  -cc1 -triple x86_64-apple-macosx10.9.0 -emit-obj -disable-fr\
> ee -disable-llvm-verifier -main-file-name cli-script.c -mrelocation-model pic 
> -pic-level 2 -mdisable-fp-elim -masm-verbose -munwind-tables -target-cpu 
> core2 -target-linker-version \
> 241.9 -gdwarf-2 -coverage-file 
> /Users/juanrgar/Projects/rtems/src/rsb/rtems/build/sparc-rtems5-gdb-8.2.1-x86_64-apple-darwin13.4.0-1/build/gdb/cli/cli-script.o
>  -resource-dir /Appli\
> cations/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/6.0
>  -dependency-file cli/.deps/cli-script.Tpo -MP -MT cli/cli-script.o -D 
> LOCALEDIR="/\
> Users/juanrgar/Projects/rtems/rtems/5/share/locale" -D HAVE_CONFIG_H -D TUI=1 
> -I 
> /Users/juanrgar/Projects/rtems/src/rsb/rtems/build/tmp/sb-juanrgar/5/rtems-sparc/Users/juanrgar/Pro\
> jects/rtems/rtems/5/include -I . -I ../../gdb-8.2.1/gdb -I 
> ../../gdb-8.2.1/gdb/common -I ../../gdb-8.2.1/gdb/config -I 
> ../../gdb-8.2.1/gdb/../include/opcode -I ../../gdb-8.2.1/gdb/\
> ../opcodes/.. -I ../../gdb-8.2.1/gdb/../readline/.. -I 
> ../../gdb-8.2.1/gdb/../zlib -I ../bfd -I ../../gdb-8.2.1/gdb/../bfd -I 
> ../../gdb-8.2.1/gdb/../include -I ../libdecnumber -I .\
> ./../gdb-8.2.1/gdb/../libdecnumber -I ../../gdb-8.2.1/gdb/gnulib/import -I 
> build-gnulib/import -I 
> /Users/juanrgar/Projects/rtems/src/rsb/rtems/build/tmp/sb-juanrgar/5/rtems-sparc/U\
> sers/juanrgar/Projects/rtems/rtems/5/include -I 
> /opt/local/Library/Frameworks/Python.framework/Versions/3.7/include/python3.7m
>  -I /opt/local/Library/Frameworks/Python.framework/Ver\
> sions/3.7/include/python3.7m -stdlib=libc++ -O2 -Wall -Wpointer-arith 
> -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts 
> -Wempty-body -Wno-sign-compare -\
> Wno-narrowing -Wno-mismatched-tags -Wno-error=deprecated-register 
> -Wformat-nonliteral -std=gnu++11 -fdeprecated-macro -fdebug-compilation-dir 
> /Users/juanrgar/Projects/rtems/src/rsb\
> /rtems/build/sparc-rtems5-gdb-8.2.1-x86_64-apple-darwin13.4.0-1/build/gdb 
> -fbracket-depth 1024 -ferror-limit 19 -fmessage-length 0 -stack-protector 1 
> -mstackrealign -fblocks -fobjc\
> -runtime=macosx-10.9.0 -fencode-extended-block-signature -fcxx-exceptions 
> -fexceptions -fdiagnostics-show-option -vectorize-loops -vectorize-slp -o 
> cli/cli-script.o -x c++ ../../gd\
> b-8.2.1/gdb/cli/cli-script.c
> 1.   parser at end of file
> 2.  Per-module optimization passes
> 3.  Running pass 'CallGraph Pass Manager' on module 
> '../../gdb-8.2.1/gdb/cli/cli-script.c'.
> 4.  Running pass 'SROA' on function 
> '@_Z16get_command_line20command_control_typePKc'
>   CXXcli/cli-setshow.o
> clang: error: unable to execute command: Segmentation fault: 11
> clang: error: clang frontend command failed due to signal (use -v to see 
> invocation)

That is not nice. I have raised issues like this with Apple in the past which
they have fixed but given the age of these tools I do not think they will fix 
them.

I am not sure how we handle these older versions of MacOS with gdb now being
written in C++. Any suggestions?

(I think gdb being written in C++ is a good thing and I support the change)

Chris
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: stm32 external SRAM

2019-06-16 Thread Christian Mauderer 
On 17/06/2019 03:05, Jython wrote:
> STM32:
>     112KB at 2000 
>     16KB at 2001 C000
> 
> external sram : 1MB at 0x6800
> 
>  does MEMORY layout support RAM2?

Hello Jython,

you can distribute the regions to the two RAMs. For example this BSP
does that:

https://git.rtems.org/rtems/tree/bsps/arm/lpc32xx/start/linkcmds.lpc32xx_phycore

Please note that you have to take a detailed look at what is used till
your external RAM initialization run and what not. But if you put your
external RAM initialization in an early enough step, you shouldn't get
problems with that.

Best regards

Christian

> 
> On Fri, Jun 14, 2019 at 10:13 PM Christian Mauderer
>  > wrote:
> 
> If you have already added the chip and it is initialized during startup,
> you most likely have to add a section for it in your linker command
> file. Depending on where your internal RAM is located and where the
> external one is: If they are continuous that can be enough.
> 
> Best regards
> 
> Christian
> 
> On 14/06/2019 04:42, Jython wrote:
> > we have added 1M ram by FSMC,  and want to manage it by system malloc
> > controler
> >
> > On Fri, Jun 14, 2019 at 10:26 AM Mr. Andrei Chichak
> mailto:gro...@chichak.ca>
> > >> wrote:
> >
> >     A 407 doesn’t normally have external RAM.
> >
> >     ARMs have flash at 0 and the 407 has RAM at 0x2000  as you
> >     discussed earlier.
> >
> >     If you want to work with external flash or RAM, you have to set up
> >     the FSMC or FMC to support it, but that isn’t a part of the dev
> >     board that Sebastian used for the BSP port.
> >
> >     The external memory is going to be very specific to your board.
> >     Which board are you working with?
> >
> >     A
> >
> >     > On 2019-June-13, at 06:23, Christian Mauderer
> >      
> >      >> wrote:
> >     >
> >     > On 05/06/2019 02:55, Jython wrote:
> >     >> Hello!
> >     >>
> >     >>     2. In the normal (non-debugging) case, the linker
> script still
> >     >>        places the
> >     >>
> >     >>    .text section near zero, but places the start of the
> .data and
> >     .bss
> >     >>    sections at the start location of the MPC555's internal
> RAM. The
> >     >>    system startup code then configures the external RAM just
> >     after the
> >     >>    internal RAM in memory, forming one large block from the
> two RAM
> >     >>    devices.
> >     >>
> >     >> from https://devel.rtems.org/wiki/TBR/BSP/Ss555
> >     >>
> >     >> but i dont know how to configure the external RAM just
> after the
> >     >> internal RAM in memory?
> >     >> hope you could give me some guide!
> >     >> 
> >     >>
> >     >
> >     > Hello Jython,
> >     >
> >     > the documentation you linked is for an MPC. But your subject
> line
> >     > mentions an STM32. What controller / BSP are you using?
> >     >
> >     > Best regards
> >     >
> >     > Christian Mauderer
> >     > --
> >     > 
> >     > embedded brains GmbH
> >     > Herr Christian Mauderer
> >     > Dornierstr. 4
> >     > D-82178 Puchheim
> >     > Germany
> >     > email: christian.maude...@embedded-brains.de
> 
> >      >
> >     > Phone: +49-89-18 94 741 - 18
> >     > Fax:   +49-89-18 94 741 - 08
> >     > PGP: Public key available on request.
> >     >
> >     > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne
> des EHUG.
> >     > ___
> >     > users mailing list
> >     > users@rtems.org 
> >
> >     > http://lists.rtems.org/mailman/listinfo/users
> >
> >
> > ___
> > users mailing list
> > users@rtems.org 
> > http://lists.rtems.org/mailman/listinfo/users
> >
> 
> -- 
> 
> embedded brains GmbH
> Herr Christian Mauderer
> Dornierstr. 4
> D-82178 Puchheim
> Germany
> email: christian.maude...@embedded-brains.de
> 
> Phone: +49-89-18 94 741 - 18
> Fax:   +49-89-18 94 741 - 08
> PGP: Public key available on request.
> 
> Diese Nach

Re: stm32 external SRAM

2019-06-16 Thread Jython 
STM32:
112KB at 2000 
16KB at 2001 C000

external sram : 1MB at 0x6800

 does MEMORY layout support RAM2?

On Fri, Jun 14, 2019 at 10:13 PM Christian Mauderer <
christian.maude...@embedded-brains.de> wrote:

> If you have already added the chip and it is initialized during startup,
> you most likely have to add a section for it in your linker command
> file. Depending on where your internal RAM is located and where the
> external one is: If they are continuous that can be enough.
>
> Best regards
>
> Christian
>
> On 14/06/2019 04:42, Jython wrote:
> > we have added 1M ram by FSMC,  and want to manage it by system malloc
> > controler
> >
> > On Fri, Jun 14, 2019 at 10:26 AM Mr. Andrei Chichak  > > wrote:
> >
> > A 407 doesn’t normally have external RAM.
> >
> > ARMs have flash at 0 and the 407 has RAM at 0x2000  as you
> > discussed earlier.
> >
> > If you want to work with external flash or RAM, you have to set up
> > the FSMC or FMC to support it, but that isn’t a part of the dev
> > board that Sebastian used for the BSP port.
> >
> > The external memory is going to be very specific to your board.
> > Which board are you working with?
> >
> > A
> >
> > > On 2019-June-13, at 06:23, Christian Mauderer
> >  > > wrote:
> > >
> > > On 05/06/2019 02:55, Jython wrote:
> > >> Hello!
> > >>
> > >> 2. In the normal (non-debugging) case, the linker script still
> > >>places the
> > >>
> > >>.text section near zero, but places the start of the .data and
> > .bss
> > >>sections at the start location of the MPC555's internal RAM.
> The
> > >>system startup code then configures the external RAM just
> > after the
> > >>internal RAM in memory, forming one large block from the two
> RAM
> > >>devices.
> > >>
> > >> from https://devel.rtems.org/wiki/TBR/BSP/Ss555
> > >>
> > >> but i dont know how to configure the external RAM just after the
> > >> internal RAM in memory?
> > >> hope you could give me some guide!
> > >>
> > >>
> > >
> > > Hello Jython,
> > >
> > > the documentation you linked is for an MPC. But your subject line
> > > mentions an STM32. What controller / BSP are you using?
> > >
> > > Best regards
> > >
> > > Christian Mauderer
> > > --
> > > 
> > > embedded brains GmbH
> > > Herr Christian Mauderer
> > > Dornierstr. 4
> > > D-82178 Puchheim
> > > Germany
> > > email: christian.maude...@embedded-brains.de
> > 
> > > Phone: +49-89-18 94 741 - 18
> > > Fax:   +49-89-18 94 741 - 08
> > > PGP: Public key available on request.
> > >
> > > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des
> EHUG.
> > > ___
> > > users mailing list
> > > users@rtems.org 
> > > http://lists.rtems.org/mailman/listinfo/users
> >
> >
> > ___
> > users mailing list
> > users@rtems.org
> > http://lists.rtems.org/mailman/listinfo/users
> >
>
> --
> 
> embedded brains GmbH
> Herr Christian Mauderer
> Dornierstr. 4
> D-82178 Puchheim
> Germany
> email: christian.maude...@embedded-brains.de
> Phone: +49-89-18 94 741 - 18
> Fax:   +49-89-18 94 741 - 08
> PGP: Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: gdb-8.2.1 build failed on macos 10.11.6

2019-06-16 Thread Juan Rafael García Blanco 
Hi,

I have installed macOS 10.9.5, for which Xcode includes the following compiler:
Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin13.4.0
Thread model: posix

Compilation of gdb 8.2 fails also with this setup, although the error seems to 
be caused by the compiler itself. Please find below the error log:
  CXXcli/cli-script.o
Stack dump:
0.  Program arguments: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
 -cc1 -triple x86_64-apple-macosx10.9.0 -emit-obj -disable-fr\
ee -disable-llvm-verifier -main-file-name cli-script.c -mrelocation-model pic 
-pic-level 2 -mdisable-fp-elim -masm-verbose -munwind-tables -target-cpu core2 
-target-linker-version \
241.9 -gdwarf-2 -coverage-file 
/Users/juanrgar/Projects/rtems/src/rsb/rtems/build/sparc-rtems5-gdb-8.2.1-x86_64-apple-darwin13.4.0-1/build/gdb/cli/cli-script.o
 -resource-dir /Appli\
cations/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/6.0
 -dependency-file cli/.deps/cli-script.Tpo -MP -MT cli/cli-script.o -D 
LOCALEDIR="/\
Users/juanrgar/Projects/rtems/rtems/5/share/locale" -D HAVE_CONFIG_H -D TUI=1 
-I 
/Users/juanrgar/Projects/rtems/src/rsb/rtems/build/tmp/sb-juanrgar/5/rtems-sparc/Users/juanrgar/Pro\
jects/rtems/rtems/5/include -I . -I ../../gdb-8.2.1/gdb -I 
../../gdb-8.2.1/gdb/common -I ../../gdb-8.2.1/gdb/config -I 
../../gdb-8.2.1/gdb/../include/opcode -I ../../gdb-8.2.1/gdb/\
../opcodes/.. -I ../../gdb-8.2.1/gdb/../readline/.. -I 
../../gdb-8.2.1/gdb/../zlib -I ../bfd -I ../../gdb-8.2.1/gdb/../bfd -I 
../../gdb-8.2.1/gdb/../include -I ../libdecnumber -I .\
./../gdb-8.2.1/gdb/../libdecnumber -I ../../gdb-8.2.1/gdb/gnulib/import -I 
build-gnulib/import -I 
/Users/juanrgar/Projects/rtems/src/rsb/rtems/build/tmp/sb-juanrgar/5/rtems-sparc/U\
sers/juanrgar/Projects/rtems/rtems/5/include -I 
/opt/local/Library/Frameworks/Python.framework/Versions/3.7/include/python3.7m 
-I /opt/local/Library/Frameworks/Python.framework/Ver\
sions/3.7/include/python3.7m -stdlib=libc++ -O2 -Wall -Wpointer-arith 
-Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts 
-Wempty-body -Wno-sign-compare -\
Wno-narrowing -Wno-mismatched-tags -Wno-error=deprecated-register 
-Wformat-nonliteral -std=gnu++11 -fdeprecated-macro -fdebug-compilation-dir 
/Users/juanrgar/Projects/rtems/src/rsb\
/rtems/build/sparc-rtems5-gdb-8.2.1-x86_64-apple-darwin13.4.0-1/build/gdb 
-fbracket-depth 1024 -ferror-limit 19 -fmessage-length 0 -stack-protector 1 
-mstackrealign -fblocks -fobjc\
-runtime=macosx-10.9.0 -fencode-extended-block-signature -fcxx-exceptions 
-fexceptions -fdiagnostics-show-option -vectorize-loops -vectorize-slp -o 
cli/cli-script.o -x c++ ../../gd\
b-8.2.1/gdb/cli/cli-script.c
1.   parser at end of file
2.  Per-module optimization passes
3.  Running pass 'CallGraph Pass Manager' on module 
'../../gdb-8.2.1/gdb/cli/cli-script.c'.
4.  Running pass 'SROA' on function 
'@_Z16get_command_line20command_control_typePKc'
  CXXcli/cli-setshow.o
clang: error: unable to execute command: Segmentation fault: 11
clang: error: clang frontend command failed due to signal (use -v to see 
invocation)


Regards,
Juan.

On 15 Jun 2019, at 22:37, Chris Johns  wrote:

> On 16/6/19 7:24 am, Juan Rafael García Blanco wrote:
>> Hi,
>> 
>> Sorry, I need to downgrade my macOS installation. I will not be able to 
>> check whether gdb-8.3 builds fine or not. I’m sorry I cannot be more useful.
>> 
> 
> No problem. Let me know when you can help again.
> 
> Thanks
> Chris

___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users