pc386dx exception 6 was Re: 4.6.0pre2 and docs released

Joel Sherrill joel.sherrill at OARcorp.com
Thu Apr 24 20:30:43 UTC 2003

Angelo Fraietta wrote:
> Joel Sherrill wrote:
> >I am in agreement with Ralf's hunch here.  including iostream is bound
> >to be
> >putting some ctor in the system.  It has to be doing something that is
> >not
> >legal on a vanilla i386 system.  It could be because of inline assembly
> >that
> >is not i386 pure or incorrect code generation for pure i386 that no one
> >has noticed because most people are Pentium and above for Linux, BSD,
> >etc.
> >
> >We really need to know that address of the illegal instruction so we can
> >figure out where it is coming from.  Fixing it then will probably be
> >striaghtforward.
> >
> So how do I find the address?

If you don't have visibility with a debugger, then all I know to do is 
modify the default exception handler to print the eip somewhere you 
can see it.

When I look at _defaultExcHandler in cpukit/score/cpu/i386/cpu.c, 
it already is printing eip.  Are you sure it isn't there?  If it 
has scrolled off, move the print with the eip to the end so it 
is visible or switch the console to a com port so you have scroll

> --
> Angelo Fraietta
> PO Box 859
> Hamilton NSW 2303
> Home Page
> http://www.users.bigpond.com/angelo_f/
> There are those who seek knowledge for the sake of knowledge - that is CURIOSITY
> There are those who seek knowledge to be known by others - that is VANITY
> There are those who seek knowledge in order to serve - that is LOVE
>     Bernard of Clairvaux (1090 - 1153)

Joel Sherrill, Ph.D.             Director of Research & Development
joel at OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985

More information about the users mailing list