comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: Calling all DLM experts- debugging in MSVC++ 2010
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Calling all DLM experts- debugging in MSVC++ 2010 [message #79012 is a reply to message #79011] Wed, 25 January 2012 15:35 Go to previous messageGo to previous message
Doug Edmundson is currently offline  Doug Edmundson
Messages: 58
Registered: November 2005
Member
On 1/25/12 4:11 PM, b_gom wrote:
> Excellent, thanks for the timely response Doug.
>
> The breakpoint marker still shows up as invalid when the debugger
> starts, but at least the breakpoint does catch when the code is called
> now.
>
> I'm glad this is now working, but my next step is compiling a 64-bit
> DLM of the same routine. Do I understand correctly that for the 64-bit
> project I should set the debugger to launch IDL using C:\Program Files
> \ITT\IDL\IDL81\bin\bin.x86_64\idlde.exe ?
>

Whew, glad it worked. :)

I think the answer to your questions is "yes". Namely, if one wants to
debug 64-bit Windows IDL, one can launch "<IDL
DIR>\bin\bin.x86_64\idlde.exe" directly from Visual Studio. I say
"think" because I actually haven't tried it... I prefer to launch the
workbench normally and then attach moments later. However, the "launch
from Visual Studio" workflow is likely faster and I believe there are
some here at VIS who prefer it too. One might have to worry about how
their PATH and such is set up, but that would just be more project settings.

Just to explain the reason behind running "in" and "out" of process, we
initially wanted the workbench to run in-process because it solves
rendering issues, alleviates _some_ "on top" issues, etc. On all
platforms it works well, except 32-bit Windows. In that case we had to
move IDL out-of-process so that it would have more memory. The
workbench's JVM was fragmenting the process' memory too severely and the
largest chunk IDL could scrounge was only 400 MB or so. Hope this
rounds out the story a bit.

Cheers,
Doug
Exelis VIS
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: al_legend producing an unwanted circle
Next Topic: Re: mapping/interpolation from one irregular grid to another (different) irregular grid.

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu Oct 09 22:27:55 PDT 2025

Total time taken to generate the page: 0.03411 seconds