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 #79015 is a reply to message #79014] Wed, 25 January 2012 14:33 Go to previous messageGo to previous message
b_gom is currently offline  b_gom
Messages: 105
Registered: April 2003
Senior Member
On Jan 25, 1:05 pm, ronn <rlkl...@gmail.com> wrote:
> On Jan 25, 2:19 pm, b_gom <b_...@hotmail.com> wrote:
>
>
>
>
>
>> I'm having trouble with the MS VC++ 2010 Express compiler when trying
>> to debug a DLL called from an IDL DLM. I used to be able to use
>> breakpoints in the C code and the debugger would stop on them as
>> expected when running in debug mode.
>
>> Lately, when I start the debugger in VC++, all the breakpoint markers
>> turn to empty circles with the message: "The breakpoint will not
>> current be hit. No symbols have been loaded for this document."
>
>> I've searched and found dozens of threads on this topic in the general
>> MS visual studio community, but no solutions.
>
>> Anyone have any tips for getting debugging breakpoints to work within
>> a DLM? I did have it working before in VC++ 2008 and 2010, but I don't
>> know what's changed.
>
>> Thanks
>
> Which version of IDL are you running? And  how do you start the debug
> process?  Do you attach to an existing IDL process   or spawn a new
> one?
>
> Ronn Kling
>
>

Hi Ronn,

this is IDL 8.1 on a windows 7 64-bit system, although I'm compiling a
32-bit DLM and calling it with 32-bit IDL. I have the debugger spawn a
new process using this command:
C:\Program Files\ITT\IDL\IDL81\bin\bin.x86\idlde.exe
with command arguments of:
-32
The debugger type is set to 'Auto'.

The only difference I can see from the second printing of your
'Calling C from IDL' book is that I have a post-build step that copies
the DLL to my default DLM path instead of putting it in the IDL bin
directory. The DLM loads and runs fine this way, its just that the
debugger doesn't seem to work.

Report message to a moderator

[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 20:09:08 PDT 2025

Total time taken to generate the page: 0.39973 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.7.
Copyright ©2001-2013 FUDforum Bulletin Board Software