#23 Division by Zero at eip=0000b2d1

open
None
6
2005-01-29
2004-05-29
No

Rhide (1.5,binary from rhide.com) seems to crash not
only when opening a file. This crash is reproduceable
(but not controllable). Rhide crashes also when using
its built in help and when compiling/running (djgpp).
There is always -- as it seems -- an errorlevel
(%ERRORLEVEL%) of 255. Without a crash it returns 0.
This bug also occured in its previous version.
Some data:

(env-vars:)
NUMBER_OF_PROCESSORS=1
OS=Windows_NT
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 6 Model 4 Stepping 2,
AuthenticAMD
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0402

(machine:)
RAM 256M, WIN2k SP4

traceback attached

Discussion

  • Mario Duhanic

    Mario Duhanic - 2004-05-29

    2x traceback/debugging

     
  • Mario Duhanic

    Mario Duhanic - 2004-05-29
    • priority: 5 --> 6
     
  • Mario Duhanic

    Mario Duhanic - 2005-01-29
    • assigned_to: nobody --> rhoehne
     
  • Blue Chip

    Blue Chip - 2005-12-26

    Logged In: YES
    user_id=799410

    This one had me foxed for AGES... But I finally spotted it!

    If you attempt to open a file when the file is listed as
    "Closed" in the WindowList, then opening the file will cause
    RHIDE 1.5b to crash as described.

    It doesn't matter how you open the file, you can click in
    the ProjectWindow, select "Open" from the "File" menu, or
    even press return on the "Closed" entry in the WindowList .
    ..the program will crash the same way under all conditions.

    As stated, this is MOST annoying when using the InfoViewer
    ...the workaround is simple, but irritating. Before you
    attempt to open a file or use the InfoViewer, goto the
    WindowList (ALT-0) and delete any "Closed" entry for that
    file ...all is well :)

    A patch to fix this would be appreciated *A LOT* :)

     
  • Andreas E

    Andreas E - 2007-01-09

    Logged In: YES
    user_id=100533
    Originator: NO

    OK, here is another victim :)

    First of all, thanks Mario for your findings.
    I saved up a full dump of the problem on my system...

    It happened when I tried to compile a project, and the compiler found a bug in an *auxiliary* file. Yes, this auxiliary file was not opened, only the main file was (to keep a decent overview).

    Exiting due to signal SIGABRT
    Division by Zero at eip=0000b2d1, x87 status=0000
    eax=000000c8 ebx=003915d4 ecx=00000000 edx=0000000a esi=003915b8 edi=00391630
    ebp=00391550 esp=00391528 program=E:\DEVEL\DJGPP\BIN\RHIDE.EXE
    cs: sel=01a7 base=01e30000 limit=003fffff
    ds: sel=01af base=01e30000 limit=003fffff
    es: sel=01af base=01e30000 limit=003fffff
    fs: sel=01bf base=00000000 limit=0010ffff
    gs: sel=01bf base=00000000 limit=0010ffff
    ss: sel=01af base=01e30000 limit=003fffff
    App stack: [00391db0..00311db0] Exceptn stack: [003114e0..0030f5a0]

    Call frame traceback EIPs:
    0x0000b2d1
    0x0023d6e7
    0x0023d085
    0x0004c179
    0x0002aa49
    0x000227d5
    0x00007602
    0x00007f05
    0x00231076
    0x0004f701
    0x0023ab76
    0x00050334
    0x0004f471
    0x0022710b
    0x002271c8
    0x0022f9f0
    0x002311a0
    0x0022710b
    0x002271c8
    0x002406e8
    0x0022710b
    0x002271c8
    0x00225fba
    0x00007ff1
    0x00226d94
    0x002264e0
    0x0000ba5e
    0x00289d58

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks