Menu

#355 Memory access violation for build 1.136 and up

closed
nobody
None
5
2012-09-26
2004-07-01
No

Hello,

Build 1.136 and up will crash with an access violation if
files devcpp.cfg and devcpp.ini do not exist on the
default location, or the location indicated with the -c
option. Even if the files exist, build 1.136 and up will
only run if devcpp.cfg and devcpp.ini were created with
a previous build, say for example 1.135.

Jesus

Discussion

  • Marek Januszewski

    Logged In: YES
    user_id=609236

    I can't reproduce it. What is the exact message with access
    violation?

     
  • Jesus Calvino-Fraga

    Logged In: YES
    user_id=603650

    The first message is:

    Exception EAccessViolation in module devcpp.exe at 00145006
    Access violation at address 00545006 in module 'devcpp.exe'.
    Read of address 00000350

    The second message is:

    Runtime error 216 at 00441Cf5

    This happens with every computer I tried on: Windows 2000,
    XP home, and XP pro.

    My shortcut call Dev-c++ as:

    C:\Dev-Cpp\devcpp.exe -c c:\Dev-Cpp

    Also think, bug report 984881 is exactly the same thing.

    Jesus

     
  • Krzysztof Rusocki

    Logged In: YES
    user_id=1082525

    I am seeing something VERY similar as well with 4.9.8.10 and
    r1.138 of dev-cpp.exe (windows 98).

    After initial configuration (style, class browser...)
    dev-cpp crashes with ,,Program performed illegal operation''
    (,,invalid page fault'', no backtrace, all registers == 0)
    followed by message boxes:

    Application Error
    Exception EAccessViolation in module DEVCPP.EXE at 00145006.
    Access violation at address 00545006 in module 'DEVCPP.EXE'.
    Read of address FFFFFFFF.

    and:
    Runtime error 216 at 00464A73

    I'll verify whether it's the matter of configuration files that
    Jesus mentioned.

     
  • Krzysztof Rusocki

    Logged In: YES
    user_id=1082525

    Ok, now I'm pretty sure it's the same bug. 1.136+ crash,
    and that seems to be related to codepath, that handles First=1
    in DEVCPP.ini,

    although it crashed - devcpp.cfg and DEVCPP.ini were both
    created and devcpp kept crashing until I set First to 0 in
    DEVCPP.ini - then it started properly.

     
  • Nobody/Anonymous

    Logged In: NO

    Yup, this seems to work well, no crash (verified on XPSP1)
    occured.

    Many Thanks!

     
  • Krzysztof Rusocki

    Logged In: YES
    user_id=1082525

    Urgh, that was me, forgot to log in (sorry for the noise).

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.