Menu

#70 5.02.1570 crashes w access violation importing wxwidgets (C++)

v1.0_(example)
open
nobody
None
1
2014-07-19
2014-07-19
No

I am using the c++ reverse-engineering module. I do not know if the bug is in the module or in staruml, but the crash is in staruml.exe, so I am going to guess it's staruml.
I added every windows file in the wxwidgets-3.0.0 dir tree (msw). I am pretty sure this crash produced a minidump.

Faulting application name: StarUML.exe, version: 5.0.2.1570, time stamp: 0x2a425e19
Faulting module name: StarUML.exe, version: 5.0.2.1570, time stamp: 0x2a425e19
Exception code: 0xc0000005
Fault offset: 0x00006e04
Faulting process id: 0x4f9c
Faulting application start time: 0x01cfa30c37b2d0ec
Faulting application path: f:\prog\StarUML\StarUML.exe
Faulting module path: f:\prog\StarUML\StarUML.exe
Report Id: dbfcd3f1-0f02-11e4-bd68-dc85de2605ca

0xc0000005 is an access violation, which means an array was accessed outside its boundaries usually (I forgot the other situation this happens).

Discussion

  • Jim Michaels

    Jim Michaels - 2014-07-19

    ftp://ftp.wxwidgets.org/pub/
    sorry forgot to provide a link to wxwidgets source code...

     
  • Jim Michaels

    Jim Michaels - 2014-07-19

    was able to successfully import by
    - changing canvas size to 50000x50000
    - changing it to auto-resize the view

    however, after the import (the c++ module put the several hundred class diagrams all in the viewable portion of the canvas only), I did format, layout. this caused another 0xc0000005 crash (access violation).

    if this is a 32-bit program, perhaps it can be compiled as 64-bit using mingw-w64? it's a project in sf.net:

    https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-posix/sjlj/

    https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.0/threads-posix/sjlj/

    you can build for both i686 and x86_64 windows targets. if it's a memory problem I am running into (this would be a HUGE diagram), a 64-bit target would fix the problem, since it can get beyond the 1.6GiB limit you usually get with 32-bit applications (rest is taken up by OS and video RAM).

    Faulting application name: StarUML.exe, version: 5.0.2.1570, time stamp: 0x2a425e19
    Faulting module name: StarUML.exe, version: 5.0.2.1570, time stamp: 0x2a425e19
    Exception code: 0xc0000005
    Fault offset: 0x00006e04
    Faulting process id: 0x4828
    Faulting application start time: 0x01cfa311ee574616
    Faulting application path: F:\prog\StarUML\StarUML.exe
    Faulting module path: F:\prog\StarUML\StarUML.exe
    Report Id: 886f7f77-0f06-11e4-bd68-dc85de2605ca

     

Log in to post a comment.