slick edit debugging problem

From: Saurabh Aggrawal (games60_at_hotmail.com)
Date: 11/26/04

  • Next message: Saurabh Aggrawal: "slick edit debugging problem" 
    Date: 26 Nov 2004 04:19:39 -0800

    Hi everyone.
    I am trying to debug an old program of device driver which is made
    using c++, SDK and DDK toolkits. The final result of the code is a dll,
    which is the device driver for the printer. The code is divided into
    many directories. Every directory is making a static library. At last
    all the static libraries are producing the dll file which is the device
    driver.

    To compile the code and build the dll, i open the slick edit 6.0 and go
    to the makWin32.mak file and build it using the command "nmake". That
    command just builds the dll at the end of a big compilation.

    For debugging this application i am opening the file rundll32.dll in
    the vc++ 6.0 editor and doing the following steps:
    1. project->settings->General->Output file name->rundll32.exe
    2. project->settings->General->Browse info file name->rundll32.bcs
    3. project->settings->Debug->Exe for debug session->rundll32.exe
    4. project->settings->Debug->program
    arguments->printui.dll,PrintUIEntry /e /n "Name of the Driver"
    5. Now i opened all the .cpp and .h files in the vc++6.0 and added
    breakpoints at the locations i wanted to debug.

    When i run the application, i can easily debug the project.

    The problem is:
    1. For editing, i am bound to use slick-edit
    2. For compiling, i am bound to open shell in slickedit and compile
    using namke.
    3. For debugging, i am bound to use vc++ 6.0

    Can any one suggest me more portable and easy way, so that i can edit,
    compile and debug my project easily.

    ( The make files used in the project are not recognizable to the vc++
    6.0)

    Thanks,
    Saurabh Aggrawal

  • Next message: Saurabh Aggrawal: "slick edit debugging problem"

    Relevant Pages

    • Understanding references...
      ... and two of those projects have a reference to a ... Whenever I compile to test, I "Build Solution", with Active Solution ... Configuration = Debug. ... Why is it looking for a a DLL in Release if everything I'm doing is in Debug ...
      (microsoft.public.dotnet.languages.csharp)
    • Re: How to export a class that inherits from unmanaged exception class
      ... Static linking means your application is self standing and doesn't depend on any non-system DLL. ... Debug or release version. ... In a VC++ project you can't successfully mix debug and release units -- you have to compile all your units with either debugging enabled or disabled uniformly. ...
      (microsoft.public.dotnet.languages.vc)
    • Re: Access Violation using CCriticalSection in DLL
      ... I do not normally mix debug and release components, but I was trying to find ... the source of the problem by using a debugger on at least the DLL ... release compile work on Win XP. ... declared within the logger class. ...
      (microsoft.public.vc.mfc)
    • slick edit debugging problem
      ... I am trying to debug an old program of device driver which is made ... The final result of the code is a dll, ... To compile the code and build the dll, i open the slick edit 6.0 and go ...
      (comp.lang.java.softwaretools)
    • Re: How to connect to children process
      ... Main problem is amount of manual operations required per debug cycle. ... connection to DLL with debugger takes sensible amount of time and manual ... Is the main problem that the debugger keeps symbols file loaded ... AFAIK that's how VS2003 debugger works, but WinDbg should usually ...
      (microsoft.public.vsnet.debugging)