Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Debug a ProC/C++ file in visual studio VC++ ??

Status
Not open for further replies.

DilipS

Programmer
Sep 3, 2002
5
SG
Hi
I was long working on VC++. But these days working on Proc and proc++ , UNIX env. But for debugging I find it too difficult in Proc/C++ programs to put log messages everytime and see the output.
I want to know some way by which I can compile Proc/C++ files in Visual Studio and can dubug it.
One way I think we can set environment in Visual Studio and can debug it. What are those settings needs to be done ??
Or if there any other better way to debug a proc program.

Regards
Dilip Santlani
 
Do you mean, debugging facilities on Unix are not convenient enough? Did you try, say, KDbg 1.0.2? I don't see any principial differencies between KDbg and Msvc debugger.
 
1) Which flavour of Unix are you using (AIX, Solaris, HPUX, Linux, BSD ...)

2) Presumably PROC translates down to some call into OCI. Why not put a breakpoint on the OCI function and examine the SQL string there?

 
Hi
thnks for both reply.
Actually 'mingis ' I havent tried or noticed any one doing debugging in unix like we do in windows env using F5 key break points and watching the variables value.
'xwb' I am working on HP Unix ver 11 i, proc translates code into OCI , u mean the .cpp file which compiler generates for a .pc file that i can debug ??

Dilip
 
> u mean the .cpp file which compiler generates for a .pc file that i can debug ??
I think so. The last time I used to debug on HPUX (version 5 as I remember) was 1997, it was plain C and debugger xdb. It was not so good, but quite usable, it looked something like xxgdb on RedHat 7.0.
 
ProC will generate a PC file. All you have to do is set up the make system to keep the PC file after it has generated the object code.

dde (the HP debugger) is quite good (but not as good as the Solaris debuggers) if you get the directory settings right. It will do most things that MSVC will do except probably disassemble. The command line syntax is a bit weird as there is a difference whether you specify ' or " or neither. You can always alias them to what you know.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top