EMX/GCC SYS3175 - OS2

This is a discussion on EMX/GCC SYS3175 - OS2 ; Any ideas on this:- ? 12-31-2004 12:29:04 SYS3175 PID 1c05 TID 0001 Slot 0068 C:\UX2BS\EMX\BIN\CC1.EXE c0000005 000640e1 P1=00000002 P2=00000000 P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000039 ECX=00389350 EDX=00000000 ESI=00000000 EDI=00165db8 DS=0053 DSACC=d0f3 DSLIM=3fffffff ES=0053 ESACC=d0f3 ESLIM=3fffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005b:000640e1 ...

+ Reply to Thread
Results 1 to 7 of 7

Thread: EMX/GCC SYS3175

  1. EMX/GCC SYS3175

    Any ideas on this:- ?



    12-31-2004 12:29:04 SYS3175 PID 1c05 TID 0001 Slot 0068
    C:\UX2BS\EMX\BIN\CC1.EXE
    c0000005
    000640e1
    P1=00000002 P2=00000000 P3=XXXXXXXX P4=XXXXXXXX
    EAX=00000000 EBX=00000039 ECX=00389350 EDX=00000000
    ESI=00000000 EDI=00165db8
    DS=0053 DSACC=d0f3 DSLIM=3fffffff
    ES=0053 ESACC=d0f3 ESLIM=3fffffff
    FS=150b FSACC=00f3 FSLIM=00000030
    GS=0000 GSACC=**** GSLIM=********
    CS:EIP=005b:000640e1 CSACC=d0df CSLIM=3fffffff
    SS:ESP=0053:0295f698 SSACC=d0f3 SSLIM=3fffffff
    EBP=0295f754 FLG=00012217

    CC1.EXE 0001:000540e1

  2. Re: EMX/GCC SYS3175

    On Fri, 31 Dec 2004 13:12:43 UTC, jp wrote:

    > Any ideas on this:- ?


    GCC is very sensitive to hardware problems. I once had a situation,
    where GCC would crash on a certain system. This system worked
    O.K. with all other apps I tried. Just GCC crashed. By accident, I found
    out, that the memory timing in the BIOS was set up pretty aggressive.
    Setting this a bit more relaxed made GCC work as well. The behaviour
    was 100% reproducable on this system.


    --
    Ruediger "Rudi" Ihle [S&T Systemtechnik GmbH, Germany]
    http://www.s-t.de
    Please remove all characters left of the "R" in my email address


  3. Re: EMX/GCC SYS3175

    On Fri, 31 Dec 2004 13:12:43 +0000, jp wrote:

    > Any ideas on this:- ?
    >
    > 12-31-2004 12:29:04 SYS3175 PID 1c05 TID 0001 Slot 0068
    > C:\UX2BS\EMX\BIN\CC1.EXE
    > c0000005
    > 000640e1
    > P1=00000002 P2=00000000 P3=XXXXXXXX P4=XXXXXXXX
    > EAX=00000000 EBX=00000039 ECX=00389350 EDX=00000000
    > ESI=00000000 EDI=00165db8
    > DS=0053 DSACC=d0f3 DSLIM=3fffffff
    > ES=0053 ESACC=d0f3 ESLIM=3fffffff
    > FS=150b FSACC=00f3 FSLIM=00000030
    > GS=0000 GSACC=**** GSLIM=********
    > CS:EIP=005b:000640e1 CSACC=d0df CSLIM=3fffffff
    > SS:ESP=0053:0295f698 SSACC=d0f3 SSLIM=3fffffff
    > EBP=0295f754 FLG=00012217
    >
    > CC1.EXE 0001:000540e1


    It's a bug.

  4. Re: EMX/GCC SYS3175

    Paul Ratcliffe wrote:

    >On Fri, 31 Dec 2004 13:12:43 +0000, jp wrote:
    >
    >
    >
    >>Any ideas on this:- ?
    >>
    >>12-31-2004 12:29:04 SYS3175 PID 1c05 TID 0001 Slot 0068
    >>C:\UX2BS\EMX\BIN\CC1.EXE
    >>c0000005
    >>000640e1
    >>P1=00000002 P2=00000000 P3=XXXXXXXX P4=XXXXXXXX
    >>EAX=00000000 EBX=00000039 ECX=00389350 EDX=00000000
    >>ESI=00000000 EDI=00165db8
    >>DS=0053 DSACC=d0f3 DSLIM=3fffffff
    >>ES=0053 ESACC=d0f3 ESLIM=3fffffff
    >>FS=150b FSACC=00f3 FSLIM=00000030
    >>GS=0000 GSACC=**** GSLIM=********
    >>CS:EIP=005b:000640e1 CSACC=d0df CSLIM=3fffffff
    >>SS:ESP=0053:0295f698 SSACC=d0f3 SSLIM=3fffffff
    >>EBP=0295f754 FLG=00012217
    >>
    >>CC1.EXE 0001:000540e1
    >>
    >>

    >
    >It's a bug.
    >
    >

    Nothing gets past you does it, Paul? ;-)....

  5. Re: EMX/GCC SYS3175

    Ruediger Ihle wrote:

    >On Fri, 31 Dec 2004 13:12:43 UTC, jp wrote:
    >
    >
    >
    >>Any ideas on this:- ?
    >>
    >>

    >
    >GCC is very sensitive to hardware problems.
    >

    I've suspected there is a hardware problem but can't track anything down.


    >I once had a situation,
    >where GCC would crash on a certain system. This system worked
    >O.K. with all other apps I tried. Just GCC crashed. By accident, I found
    >out, that the memory timing in the BIOS was set up pretty aggressive.
    >Setting this a bit more relaxed made GCC work as well.
    >
    >

    I've never heard of aggressive memory timing and certainly haven't seen
    anything in the BIOS for configuring memory. Could it be called
    something else?

    Could overclocking cause the symptoms you mention?


  6. Re: EMX/GCC SYS3175

    On Fri, 31 Dec 2004 16:43:26 UTC, jp wrote:

    > I've never heard of aggressive memory timing and certainly haven't seen
    > anything in the BIOS for configuring memory. Could it be called
    > something else?


    Look for something like "RAS pre-charge" or "Burst rate".


    > Could overclocking cause the symptoms you mention?


    Yes.


    --
    Ruediger "Rudi" Ihle [S&T Systemtechnik GmbH, Germany]
    http://www.s-t.de
    Please remove all characters left of the "R" in my email address


  7. Re: EMX/GCC SYS3175

    Ruediger Ihle wrote:

    > GCC is very sensitive to hardware problems. I once had a situation,
    > where GCC would crash on a certain system. This system worked
    > O.K. with all other apps I tried. Just GCC crashed.
    >

    I saw the same thing with VAC++. It would randomly but reliably
    crash on a machine which otherwise worked OK. It was bad memory.


    Michal


+ Reply to Thread