468,315 Members | 1,442 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,315 developers. It's quick & easy.

Debug information in the .dll and .exe

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?
--
Ashish Tripathi
Jun 14 '06 #1
5 3449
"Ashish Tripathi" <As************@discussions.microsoft.com> wrote in
message news:12**********************************@microsof t.com...
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?


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

-cd
Jun 14 '06 #2
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.
--
Ashish Tripathi
"Carl Daniel [VC++ MVP]" wrote:
"Ashish Tripathi" <As************@discussions.microsoft.com> wrote in
message news:12**********************************@microsof t.com...
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?


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

-cd

Jun 15 '06 #3
>> > 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?
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.

--

Kind regards,
Bruno van Dooren
br**********************@hotmail.com
Remove only "_nos_pam"
Jun 15 '06 #4
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.
--
Ashish Tripathi
"Bruno van Dooren" wrote:
> 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?

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.

--

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

Jun 16 '06 #5
>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.


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.

--

Kind regards,
Bruno van Dooren
br**********************@hotmail.com
Remove only "_nos_pam"
Jun 16 '06 #6

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

12 posts views Thread by nospam | last post: by
9 posts views Thread by dee | last post: by
10 posts views Thread by Brett | last post: by
6 posts views Thread by pauldepstein | last post: by
10 posts views Thread by Joe Befumo | last post: by
2 posts views Thread by newscorrespondent | last post: by
3 posts views Thread by Arman Sahakyan | last post: by
7 posts views Thread by =?Utf-8?B?SmltIFdhbHNo?= | last post: by
reply views Thread by Teichintx | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.