×

Discussion Board

Results 1 to 5 of 5
  1. #1
    Super Contributor
    Join Date
    Dec 2004
    Posts
    643

    Carbide.c++ 1.2 - issues, workarounds and wishes

    I succeeded in importing the whole Python for S60 source into Carbide, compiling it and debugging some parts of it on device.

    My overall experience so far has been much better than with any previous tool for ODD I've tried. Thank you, Carbide team!

    I've found the following two small bugs:

    - The default time given for SIS file installation through TRK is too short. It seems like Carbide sends the SIS file to the phone, issues the install command and waits for 15 seconds. If the installation doesn't complete within that time, Carbide sends the install command again, and again after another 15 seconds. If the third time fails, an error is displayed. The program installation still apparently continues in the background and after waiting for a while you can run the application and debug it normally. The application install timeout should be configurable separately.

    Workaround: Increase the global TRK "Message retry delay" in Run->Debug...->Debugger from the default 2000 ms. 10000 ms was sufficient for the PyS60 package.

    - The error message given if you forget to enter an executable to debug is very obscure -- It's a NullPointerException buried under a nested exception hierarchy. This error condition should be checked and a better error message given. See http://discussion.forum.nokia.com/fo...d.php?t=106689
    Last edited by jplauril; 2007-05-09 at 15:22.

  2. #2
    Super Contributor
    Join Date
    Dec 2004
    Posts
    643

    Re: Carbide.c++ 1.2 - small on-device debugging issues and workarounds

    And more: In "Run->Debug...->Main->Remote process to launch" the drive letter is case sensitive. If you give a lowercase drive letter there, you will get the error [Installation] The installation drive does not match the drive of the process to be launched.

    This setting should be case insensitive, obviously.

  3. #3
    Super Contributor
    Join Date
    Dec 2004
    Posts
    643

    Re: Carbide.c++ 1.2 - small on-device debugging issues and workarounds

    When trying to set a breakpoint to a file that hasn't been recognized as loaded by TRK (such as a static DLL loaded by another static DLL) the error message is highly obscure: "Unresolved breakpoint". This error message should give some possible reasons why the breakpoint is unresolved, and of course ideally TRK should just work in this situation as well.

  4. #4
    Super Contributor
    Join Date
    Dec 2004
    Posts
    643

    Re: Carbide.c++ 1.2 - small on-device debugging issues and workarounds

    Sometimes the process "DE.EXE" gets stuck holding the DLL to be debugged even after terminating the debug session. This causes build to fail with the error message "The process cannot access the file because it is being used by another process.".

    Workaround: Restart Carbide.

  5. #5
    Super Contributor
    Join Date
    Dec 2004
    Posts
    643

    Re: Carbide.c++ 1.2 - small on-device debugging issues and workarounds

    The parser for GCCE errors and warnings should be improved. The current version often fails to find the full message when GCCE splits them to several lines.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×