Thank you both for the tips. I am trying to add the additional GCC flag, but - being new to eCos (and not an expert in Linux either) - I do not know the optimal way to integrate it.
My understanding from working with eCos on the Windows side was that I modify the install/include/pkgconf/ecos.mak file; specifically, the ECOS_GLOBAL_CFLAGS. Then I do a 'make' at the root of the synthetic build tree. But when I build, I do not see the compiler option listed in the compiler output - it appears to be cut off after the -fno-exceptions. Perhaps just the output is being truncated? Am I doing this right? Thank you, Tyler > -----Original Message----- > From: Bart Veer [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 04, 2008 9:48 AM > To: Tyler Wilson > Cc: [email protected] > Subject: Re: [ECOS] Linux Synthetic target problems > > >>>>> "Tyler" == Tyler Wilson <[EMAIL PROTECTED]> writes: > > Tyler> Good day, > Tyler> I have been attempting to build the Linux synthetic target > Tyler> on what is essentially an Ubuntu 7.10 system (actually, > Tyler> andLinux which uses coLinux). When I get to the point of > Tyler> running the hello application, I get a segmentation fault. > Tyler> If I attempt to debug with gdb, it spits out an internal > Tyler> error: > > Tyler> This GDB was configured as "i486-linux-gnu"... > Tyler> /build/buildd/gdb-6.6.dfsg/gdb/dwarf2-frame.c:1725: > internal-error: decode_frame_entry_1: Assertion `fde->cie != NULL' > failed. > Tyler> A problem internal to GDB has been detected, > > Note that this is a bug in the Ubuntu release of gdb, not in the > synthetic target. If you want to debug a synthetic target application > then you will probably have to upgrade or downgrade your version of > gdb. > > Tyler> This is using GCC version 4.1.3. A co-worker got the same > Tyler> error on a 'pure' Ubuntu install. > > Tyler> FYI, I used the instructions in this post for the build: > Tyler> http://www.nabble.com/SIGSEV,-Segmentation-Fault:-When- > attempting-to-run-%22Hello-World%27-on-Synthetic-Linux-td8250747.html > > Tyler> ecosconfig new linux default > Tyler> ecosconfig tree > Tyler> make > > Tyler> I have seen reports in other places that say the Linux > Tyler> kernel version may have an impact on the success of the > Tyler> synthetic target. On the other hand, I have seen Changelogs > Tyler> in CVS with notes about 'update for later GCC versions'. > > The synthetic target is vulnerable to changes in both the Linux kernel > and the toolchain - compiler, linker, ... Actually all of eCos is > vulnerable to toolchain changes, but for most targets people stick > with known good toolchains they have downloaded. For the synthetic > target people use whatever toolchain is installed with their Linux > distribution. Generally that is of newer vintage than the > cross-compilers so more likely to show up problems. > > For this issue, first try Andrew's suggestion of > -fno-stack-protector (not -fno-stack-protection). Hopefully you have > run into a known problem rather than a new one. > > Bart > > -- > Bart Veer eCos Configuration > Architect > eCosCentric Limited The eCos experts > http://www.ecoscentric.com/ > Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 > 245571 > Registered in England and Wales: Reg No 4422071. -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
