Is there a command line interface to the scw32.exe debugger? I'm trying to track down a bug in a DLL I've created that's loaded by java; there's an access violation in a method that starts with _ti (typeinfo function?). I'm trying to generate a decent stack traceback.

Are there any decent debuggers that would allow me to do this, besides Cygwin/MinGW gdb?

My basic requirements are:
a) I need to work from a specific directory
b) Set breakpoints in the DLL
c) Specify the command line to the program
d) Work within a self-funded graduate student's budget


-scooter

Never mind... sometimes it helps to experiment a bit with the tools.

Answering my own questions and other helpful debugging hints:

- scw32 can be used as a standalone debugger. It's a pretty decent
  debugging environment even without a project file active.

- Use the Debug>Settings options to set the current directory

- Use Project>Arguments to set the executable's arguments.

- Set the Debug>Settings>Debug application startup box so that you can
  initially set your program's breakpoints, you can't set breakpoints
  w/o a Win32 process active. However, breakpoints will reinstated each
  time you execute the program.

- Be careful with '-gf' when you have lots of source files (like I do)
  because you can easily exceed the OPTLINK 64K debugging entry limit.


-scooter

Scott Michel <scottm@cs.ucla.edu> wrote:
> Is there a command line interface to the scw32.exe debugger? I'm trying to track down a bug in a DLL I've created that's loaded by java; there's an access violation in a method that starts with _ti (typeinfo function?). I'm trying to generate a decent stack traceback.
> 
> Are there any decent debuggers that would allow me to do this, besides Cygwin/MinGW gdb?
> 
> My basic requirements are:
> a) I need to work from a specific directory
> b) Set breakpoints in the DLL
> c) Specify the command line to the program
> d) Work within a self-funded graduate student's budget
> 
> 
> -scooter