Debug information in the .dll and .exe

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ashish Tripathi - 14 Jun 2006 23:34 GMT

I am trying to port a program from Visual Studio C++ 6 to Visual Studio 2005.
The program I am trying to port over interacts with another program call UI.
UI opens up the .exe reads in the DOS header, Windows NT header and the
debuging symbols that used to be in the .exe but are now in the .pdb. Is
there a way for me to force the information UI used to read from the .exe in
to a program compiled with Visual Studio 2005?

Signature

Ashish Tripathi

Reply to this Message

Carl Daniel [VC++ MVP] - 14 Jun 2006 23:48 GMT

>I am trying to port a program from Visual Studio C++ 6 to Visual Studio
>2005.
[quoted text clipped - 5 lines]
> in
> to a program compiled with Visual Studio 2005?

No. Embedded debug information hasn't been supported since VC6.

-cd

Reply to this Message

Ashish Tripathi - 15 Jun 2006 15:30 GMT

I realize that the Embedded debug information is no longer supported but I
was wondering if there was a way in which I can force the information back in
because then basicly I will not be able to run my program.

Signature

Ashish Tripathi

> >I am trying to port a program from Visual Studio C++ 6 to Visual Studio
> >2005.
[quoted text clipped - 9 lines]
>
> -cd

Reply to this Message

Bruno van Dooren - 15 Jun 2006 15:54 GMT

>> > The program I am trying to port over interacts with another program
>> > call
[quoted text clipped - 8 lines]
>>
>> No. Embedded debug information hasn't been supported since VC6.

>I realize that the Embedded debug information is no longer supported but I
> was wondering if there was a way in which I can force the information back
> in
> because then basicly I will not be able to run my program.

Maybe you could embed the pdb file as a resource?
Not that you will be able to use it for debugging or anything, but it will
be in the exe.

And in any case, i doubt that you could use it the same way as you did
before and you would have to adapt UI.exe
If you have to do that, you could just as easily adapt it to read in a
separate
pdb file that you redistribute it with your application.

Signature

Kind regards,
Bruno van Dooren
bruno_nos_pam_van_dooren@hotmail.com
Remove only "_nos_pam"

Reply to this Message

Ashish Tripathi - 16 Jun 2006 16:07 GMT

I would very much like to update UI.exe to use the .pdb rather than the .exe
to parse the Code View/debug information it needs to function. Unfourtantaly
I do not have access to the source code of UI.exe. It is distributed by a
different group and interacts with our program. So I was wondering if there
was a way to compile with Microsoft Visual 2005 and retro fit it to the .exe
produced by my older version of Microsoft Visual.

Signature

Ashish Tripathi

> >> > The program I am trying to port over interacts with another program
> >> > call
[quoted text clipped - 23 lines]
> separate
> pdb file that you redistribute it with your application.

Reply to this Message

Bruno van Dooren - 16 Jun 2006 16:21 GMT

>I would very much like to update UI.exe to use the .pdb rather than the
>.exe
[quoted text clipped - 6 lines]
> .exe
> produced by my older version of Microsoft Visual.

No, but if you have the sources to the VC6 application, you could perhaps
write a dll in VC2005,
and call that dll from within the VC6 application.
That way, the VC6 app would act as a wrapper around the functionality in you
VC2005 dll.

I understand that this is a less than ideal solution, but I can think of no
other solution for you.
maybe you could have a meeting with that other group, and explain why it
would be a good idea to adapt UI.exe to use pdb files.
that would probably not be a short term solution, but maybe it would set
things in motion so that you can avoid these problems in the future.

Signature

Kind regards,
Bruno van Dooren
bruno_nos_pam_van_dooren@hotmail.com
Remove only "_nos_pam"

Reply to this Message

Rate this thread:

Debug information in the .dll and .exe

Free Magazines