| Re: how to debug a IDL DLM routine [message #29339 is a reply to message #29275] |
Wed, 13 February 2002 13:26   |
xje4e
Messages: 18
Registered: February 2002
|
Junior Member |
|
|
Thank you so much for the help.
In my understanding, I think specifying the IDLDE executable is still
the best way as you suggested.
Best,
Julia JIn
Richard Younger <younger@ll.mit.edu> wrote in message news:<3C6A7A29.F90C9E94@ll.mit.edu>...
> Xiaoying Jin wrote:
>
>> How to specifying the IDLDE executable?
>
> Gert's post has the answer, namely project->settings->debug.
>
>> Do you mean you pause IDL for a while? But I think in this case all
>> you can debug and monitor is the variables in IDL not in C program. Am
>> I right? So how can I monitor C variable in this case?
>> How to attatch debugger to the IDLDE process?
>
> Ah. As I said, this method is much dirtier. I wouldn't recommend it
> unless you have an error that you need to debug spontaneously for
> whatever reason. But it's the method I thought of when I first started
> debugging my DLMs. When I found out about the debug executable setting,
> I felt like giving myself a good whack upside the head, since I had been
> debugging the hard way for a couple months.
>
> But if you want to try it, when you have the IDL prompt "press any
> key...", go to your VC++ environment, select Build->start debug->attach
> to process, and then select IDL.
>
> You may have to select break, and then do a little twiddling to figure
> out where you need to go back to IDL and press a key to break out of the
> IDL_GetKbrd() read loop. It'll be a tad confusing as there is no
> debugging info to IDL_GetKbrd(), so you'll be looking at the assembly
> until you can pop up to your own code. Keeping the call stack visible
> helps with this. With a little playing, you can get back to your own
> code inside the VC++ debugger without too much difficulty.
>
> Best of luck,
> Rich
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
