Anyone successful with camera in RobotPy?

[BotnEyedJoe]

With either RobotPy 2011.2 or the latest source from the repository, I am having problems getting off square one with the camera. Just calling the GetInstance() method of AxisCamera silently reboots the cRIO.

Has anyone had success with this? I have the M1011 model camera, and the C++ 2010ImageDemo runs flawlessly. But the PyResult is nasty.

I'm really just looking here to set my expectations, for example, if someone has been successful then how does their setup differ from mine. But it is also helpful for me to know if noone else gets it either.

[BotnEyedJoe]

Well, OK... I'll take that as a "No."

[CastleBravo]

We have the camera running with Python, although Peter had to add more of nivision to RobotPy so our code could run, and do more than simply display output to the driverstation. The only thing is NI Vision Assistant doesn't export code in Python, which makes it a bit trickier.

[BotnEyedJoe]

Great, that's good to hear, that you've gotten that far, too. We had been having trouble just doing GetInstance()!

In fact, about an hour ago, I think we discovered the problem we were having. To work with the M1011 in C++, we had had to make some small modifications to the Vision portion of WPILib. What I did not fully realize until today, was RobotPy has its own copy of the WPILib source, which of course was not patched. Once that was also patched, presto, success!

The feed to the driver station, and to some of the nivision code I had waiting, worked fine. Now on to tuning...

[CastleBravo]

If you need more help with it, I can ask Peter directly. He has been very busy, so I doubt he will be on CD much in the near future.

[Joe Ross]

In fact, about an hour ago, I think we discovered the problem we were having. To work with the M1011 in C++, we had had to make some small modifications to the Vision portion of WPILib. What I did not fully realize until today, was RobotPy has its own copy of the WPILib source, which of course was not patched. Once that was also patched, presto, success!

I'm sure the wpilib maintainers would appreciate your patch http://firstforge.wpi.edu/sf/tracker/do/listArtifacts/projects.wpilib/tracker.wpilib_c_bugs

[BotnEyedJoe]

Yes, agreed; I just need to sift through the actual changes made while investigating the problem, and determine which are significant and which are not...

[BotnEyedJoe]

I'm sure the wpilib maintainers would appreciate your patch http://firstforge.wpi.edu/sf/tracker/do/listArtifacts/projects.wpilib/tracker.wpilib_c_bugs

I have submitted artifact 1330 in the WPILib project in FIRST Forge (follow the link Joe Ross kindly gave to get there). The artifact includes a proposed fix to the relevant parts of WPILib, in the attachment. The proposed fix has been tested with the M1011 model camera in the 2010ImageDemo (the vision demo supplied with the C++ environment) and also in RobotPy (based on the latest code in the repository, but it should also work in 2011.2).

[jhersh]

I have submitted artifact 1330 in the WPILib project in FIRST Forge (follow the link Joe Ross kindly gave to get there). The artifact includes a proposed fix to the relevant parts of WPILib, in the attachment. The proposed fix has been tested with the M1011 model camera in the 2010ImageDemo (the vision demo supplied with the C++ environment) and also in RobotPy (based on the latest code in the repository, but it should also work in 2011.2).

Have you also tested it with the Axis 206 camera that many teams have? We would prefer not to break the other camera to make the new one work. ;)

Thanks,
-Joe

[BotnEyedJoe]

We have not tested with the Axis 206. We don't have one. Hopefully, "someone" out there with one can pick up this change, and try it? Otherwise, I have a [somewhat lower-priority] item on my To-Do list, to try to locate ["borrow"] one for comparison testing... Sorry this answer isn't more helpful.

[newkidd-sagar]

Hey guys, how do you replace the .cpp files in Windriver (the patch that is on FirstForge)?

[BotnEyedJoe]

Hey guys, how do you replace the .cpp files in Windriver (the patch that is on FirstForge)?

Realize, please, that what you ask for is complicated, so please do not attempt this if you are not confident of the steps involved. Ask for help if you need it. <Insert strong disclaimers here>

This is probably all written somewhere semi-officially; I looked for such a reference with no success (surprising!) Anywhere, here goes...

Obtain the source for WPILib: This should be nothing more than un-zipping the WPILib<blahblah>rev2259.zip found in the C:/WindRiver/WPILib folder.

Import the WPILib project into Workbench: In Workbench, File -> Import... -> Existing Projects into Workspace (under General) -> Next -> Select "Select Root Directory" -> Browse... to where you un-zipped the source and click OK. "WPILib" should show up in the Projects box, make sure it is checked. You can also uncheck "Copy projects into workspace" if you want to build WPILib where you un-zipped it, or check this to copy it all into your WindRiver workspace tree. Click Finish.

The build process automatically calls a Subversion program to embed the software version into the compiled code. If you don't use Subversion, you'll need to modify the build process in one place: Right-click on your new WPILib project in the Project Explorer, and select Properties -> Build Properties -> the Build Tools tab -> select Build Tool: -> C++ Compiler, and in the Command: window, modify the part of the command that reads -D'SVN_REV="$(shell svnversion -n ..)"' so that the part inside the double quotes is a version string you want to see when your robot boots up. Then click Apply and OK to close the Properties dialog.

Build WPILib.a: Right-click on the WPILib project, and select Rebuild Project... -> Go take a break, and when you come back look in the file folder PPC603gnu\WPILib\Debug under your WPILib project. There should be a WPILib.a there. This is the library you want to link your robot code to. The original, official WPILib.a resides in WindRiver\vxworks-6.3\target\lib, and this is where your robot code project expects to find WPILib by default. If you replace the official WPILib.a, you want to do so in a careful, calculated, reasoned, and fully backed up manner.

Notice we have not *changed* WPILib yet, we merely built the official release ourselves. Link your robot code against your library, and prove that it works as well as the official version. Trust me, do not hurry this step.

Once you have established a working baseline WPILib, now proceed to attempt modifications. Get the .zip you mentioned from FIRST Forge, unzip the three files there into their corresponding places in your WPILib source tree. Repeat the "Build WPILib.a" step from above.

Link this new modified library with your robot code, and see if the camera is working better now. Make sure everything else you need works too. Report any problems back here and on the FIRST Forge artifact, thanks.

[newkidd-sagar]

Realize, please, that what you ask for is complicated, so please do not attempt this if you are not confident of the steps involved. Ask for help if you need it. <Insert strong disclaimers here>

This is probably all written somewhere semi-officially; I looked for such a reference with no success (surprising!) Anywhere, here goes...

Obtain the source for WPILib: This should be nothing more than un-zipping the WPILib<blahblah>rev2259.zip found in the C:/WindRiver/WPILib folder.

Import the WPILib project into Workbench: In Workbench, File -> Import... -> Existing Projects into Workspace (under General) -> Next -> Select "Select Root Directory" -> Browse... to where you un-zipped the source and click OK. "WPILib" should show up in the Projects box, make sure it is checked. You can also uncheck "Copy projects into workspace" if you want to build WPILib where you un-zipped it, or check this to copy it all into your WindRiver workspace tree. Click Finish.

The build process automatically calls a Subversion program to embed the software version into the compiled code. If you don't use Subversion, you'll need to modify the build process in one place: Right-click on your new WPILib project in the Project Explorer, and select Properties -> Build Properties -> the Build Tools tab -> select Build Tool: -> C++ Compiler, and in the Command: window, modify the part of the command that reads -D'SVN_REV="$(shell svnversion -n ..)"' so that the part inside the double quotes is a version string you want to see when your robot boots up. Then click Apply and OK to close the Properties dialog.

Build WPILib.a: Right-click on the WPILib project, and select Rebuild Project... -> Go take a break, and when you come back look in the file folder PPC603gnu\WPILib\Debug under your WPILib project. There should be a WPILib.a there. This is the library you want to link your robot code to. The original, official WPILib.a resides in WindRiver\vxworks-6.3\target\lib, and this is where your robot code project expects to find WPILib by default. If you replace the official WPILib.a, you want to do so in a careful, calculated, reasoned, and fully backed up manner.

Notice we have not *changed* WPILib yet, we merely built the official release ourselves. Link your robot code against your library, and prove that it works as well as the official version. Trust me, do not hurry this step.

Once you have established a working baseline WPILib, now proceed to attempt modifications. Get the .zip you mentioned from FIRST Forge, unzip the three files there into their corresponding places in your WPILib source tree. Repeat the "Build WPILib.a" step from above.

Link this new modified library with your robot code, and see if the camera is working better now. Make sure everything else you need works too. Report any problems back here and on the FIRST Forge artifact, thanks.

Thank you for such an in depth reply.

Just one thing I had doubts about was the -D'SVN_REV="$(shell svnversion -n ..)"' part. Could you clarify this a little bit. Where exactly do I put anything and what should I put ? Thank you for your help once again, I really appreciate it.

[BotnEyedJoe]

By default, robot projects look to link against WPILib.a in the directory I gave under "Build WPILib.a". If you replace the standard WPILib.a installed there with yours, all your robot projects [the next time you link them] will begin to use your new library. BUT SAVE THE OLD LIBRARY FIRST! And label it, put it somewhere safe, for later when something goes wrong with your robot code and you want to rule out that the problem is in *your* version of the library.

[newkidd-sagar]

Alright I got it working, and the camera works great now. I'm very pleased and thank you for your great instructions on building a custom WPILibrary. That should be documented. Thanks a lot once again!

[BotnEyedJoe]

Glad to hear it helped!

Can I ask, which model of camera are you using: the 206 or M1011?

[BotnEyedJoe]

Have you also tested it with the Axis 206 camera that many teams have? We would prefer not to break the other camera to make the new one work. ;)

Thanks,
-Joe

For anyone interested in the Axis 206, I have run a quick test using the modified WPILib routines mentioned above, with a borrowed 206 model camera, and the live video stream to the FRC Dashboard works, and changing the camera params also works.

Please let me know if you encounter any problems.

[tux]

2 Questions.

1) My team just wants video feed from the camera back to the driver station.

Can I do this without the default RobotPy or do I have to apply all of the fixes discussed in this thread and build from source?


2) I'm not sure which camera we have. I recognize it from the picture in the KoP list, but the description says:

"Camera, Axis M1011
206 color camera..."

So, is it the M1011 or the 206?

[BotnEyedJoe]

2 Questions.

1) My team just wants video feed from the camera back to the driver station.

Can I do this without the default RobotPy or do I have to apply all of the fixes discussed in this thread and build from source?


2) I'm not sure which camera we have. I recognize it from the picture in the KoP list, but the description says:

"Camera, Axis M1011
206 color camera..."

So, is it the M1011 or the 206?

2) The picture in the KOP list is of the M1011.

1) If you just want video back to the driver station, there is a new option this year of plugging the camera directly into the network bridge on the robot (bypassing the cRIO). I understand this requires Dashboard changes, and the camera config is a little different. There are threads here on CD about that, though I can't help more than that, since we are not pursuing that solution.

If you follow the 'traditional' solution, plugging the camera in the cRIO, and doing the vision.AxisCamera.GetInstance() to start the video feed to the Dashboard, I will tell you that we had problems doing even that much with the M1011 in either C++ or any version of RobotPy. Quite a few times the feed would work, many times it would not, and we could never change the camera parameters through the software. But the patch fixed all that.

You can apply the proposed patch mentioned in this thread to either RobotPy 2011.2 or the latest RobotPy from the git repository, and though you will have to 'build it yourself', I believe the result will be a more reliable and configurable video feed.

[team 3311]

If you follow the 'traditional' solution, plugging the camera in the cRIO, and doing the vision.AxisCamera.GetInstance() to start the video feed to the Dashboard, I will tell you that we had problems doing even that much with the M1011 in either C++ or any version of RobotPy. Quite a few times the feed would work, many times it would not, and we could never change the camera parameters through the software. But the patch fixed all that.

You can apply the proposed patch mentioned in this thread to either RobotPy 2011.2 or the latest RobotPy from the git repository, and though you will have to 'build it yourself', I believe the result will be a more reliable and configurable video feed.

Hmmm I read the whole thread and tried a bit with our robot but I can't get it done. I did exactly what you are saying up here.

Can maybe anybody briefly explain the steps that we have to do to get our camera running? Its an Axis 206 camera.

[Robototes2412]

two methods:

one:
import vision
camera_obj = vision.PCVideoServer()

two:
import vision
camera_obj = vision.AxisCamera.GetInstance()

[krudeboy51]

When ever I plug the Camera into the c-rio An error and enable the robot, we would get a live feed from the camera for like 4 seconds and then for some reason the robot would disconnect from the Driverstation and an error would show up on Windriver saying:


Target Exception:

VxWorks6x_10.3.69.2: Exception in Kernal Task FRC_paramTask:0x231b5b0
at pc=0x198F84

Vector 0x300 : Data Access addr=0x6D5FE50E status=0x3E8

The System has been stopped. Do you want to attach the debugger now?

do any one know how to fix this?

[taichichuan]

When ever I plug the Camera into the c-rio An error and enable the robot, we would get a live feed from the camera for like 4 seconds and then for some reason the robot would disconnect from the Driverstation and an error would show up on Windriver saying:


Target Exception:

VxWorks6x_10.3.69.2: Exception in Kernal Task FRC_paramTask:0x231b5b0
at pc=0x198F84

Vector 0x300 : Data Access addr=0x6D5FE50E status=0x3E8

The System has been stopped. Do you want to attach the debugger now?

do any one know how to fix this?

The error you're seeing is a bus error on the cRIO. The 0x6D... is the address that's being accessed caused the buss error. The problem happened in the FRC_paramtask application. So, this is a pointer related problem. Recheck your camera configuration in the cRIO code and make suer that you've updated to the latest WPILib release. There are a couple of threads that talk about a problem with WPILib that was fixed.

[krudeboy51]

The error you're seeing is a bus error on the cRIO. The 0x6D... is the address that's being accessed caused the buss error. The problem happened in the FRC_paramtask application. So, this is a pointer related problem. Recheck your camera configuration in the cRIO code and make suer that you've updated to the latest WPILib release. There are a couple of threads that talk about a problem with WPILib that was fixed.

I have updated to the latest WPIlib. over three times now, and still the same problem. and also in the description in the lateset update, it doesnt state anyhing on fixing this error
this is the code that I have for it right now:


Class
AxisCamera *camera;

Operator control(void)
HSLImage image; //Creates an image
AxisCamera &camera = AxisCamera::GetInstance();
camera.WriteResolution(AxisCamera::kResolution_640 x480);
camera.WriteCompression(20);
camera.WriteBrightness(0);


would I have to add something in Public in order to fix it other than ds = driverstation::GetInstance();?

[jhersh]

Have you attached the WindRiver Workbench debugger when running your code so that you can trap the exception and potentially get a call stack to give us a better idea where to look?

[krudeboy51]

Have you attached the WindRiver Workbench debugger when running your code so that you can trap the exception and potentially get a call stack to give us a better idea where to look?

Yes I have over three times now but it wont connect back to the driverstation at all only when I restart and when I restart the same error pop up and I attach the debugger over and over but still the same problem

[jhersh]

Yes I have over three times now but it wont connect back to the driverstation at all only when I restart and when I restart the same error pop up and I attach the debugger over and over but still the same problem

Great!

Please post the call stack here.

[krudeboy51]

Great!

Please post the call stack here.

wats that? when I click the attach debbugger it shows a loading page then closes out when complete

[jhersh]

wats that? when I click the attach debbugger it shows a loading page then closes out when complete

So you don't ever get the debugger to stop when the exception occurs? It sounds like you are attaching the debugger in response to a crash. Try attaching the debugger to the running python interpreter before you do whatever instigates the crash or start the python interpreter using the debugger. When the exception occurs, you should be able to open the stack view. That would be the first helpful piece of information in tracking down the issue.

[krudeboy51]

So you don't ever get the debugger to stop when the exception occurs? It sounds like you are attaching the debugger in response to a crash. Try attaching the debugger to the running python interpreter before you do whatever instigates the crash or start the python interpreter using the debugger. When the exception occurs, you should be able to open the stack view. That would be the first helpful piece of information in tracking down the issue.

this is the stack view I got:


java.io.FileNotFoundException
at org.eclipse.help.internal.context.ContextFileProvi der.loadContexts(ContextFileProvider.java:235)
at org.eclipse.help.internal.context.ContextFileProvi der.getContexts(ContextFileProvider.java:181)
at org.eclipse.help.internal.context.ContextFileProvi der.getPluginContexts(ContextFileProvider.java:158 )
at org.eclipse.help.internal.context.ContextFileProvi der.getContext(ContextFileProvider.java:83)
at org.eclipse.help.internal.context.ContextManager.g etContext(ContextManager.java:79)
at org.eclipse.help.HelpSystem.getContext(HelpSystem. java:49)
at com.windriver.ide.internal.apidoc.WRAPIHelpProvide r.getFunctionInfo(WRAPIHelpProvider.java:110)
at org.eclipse.cdt.internal.ui.text.CHelpSettings.get FunctionInfo(CHelpSettings.java:121)
at org.eclipse.cdt.internal.ui.CHelpProviderManager.g etFunctionInfo(CHelpProviderManager.java:163)
at org.eclipse.cdt.internal.ui.text.c.hover.CDocHover .getHoverInfo(CDocHover.java:73)
at org.eclipse.cdt.internal.ui.text.c.hover.BestMatch Hover.getHoverInfo(BestMatchHover.java:100)
at org.eclipse.cdt.internal.ui.text.c.hover.CEditorTe xtHoverProxy.getHoverInfo(CEditorTextHoverProxy.ja va:64)
at org.eclipse.jface.text.TextViewerHoverManager$4.ru n(TextViewerHoverManager.java:165)


and the error messege was:

Error reading context-sensitive help file /"com.windriver.ide.doc.wr_vx_simulator_6.3/wr_workbench_diagnostics_programmers_guide_1.1/html/contexts.xml" (skipping file)

[jhersh]

Please refer to the getting started guide for how to setup the debugger. http://firstforge.wpi.edu/sf/go/doc1197?nav=1

[taichichuan]

this is the stack view I got:



and the error messege was:

Error reading context-sensitive help file /"com.windriver.ide.doc.wr_vx_simulator_6.3/wr_workbench_diagnostics_programmers_guide_1.1/html/contexts.xml" (skipping file)


Is this by any chance on a 64-bit machine? I've seen these errors (context-sensitive help file that is) on machines where the WRS workbench didn't install properly. You might try to reinstall Workbench to see if it solves the missing file problem.

As for the camera problem, try a lower resolution like 320x240 and loose the camera compression options. These might be stressing the stack space for the thread and causing the failure. 640x480 is really too big to be shipping across the net anyway at run time.


HTH,

Mike

[krudeboy51]

Is this by any chance on a 64-bit machine? I've seen these errors (context-sensitive help file that is) on machines where the WRS workbench didn't install properly. You might try to reinstall Workbench to see if it solves the missing file problem.

As for the camera problem, try a lower resolution like 320x240 and loose the camera compression options. These might be stressing the stack space for the thread and causing the failure. 640x480 is really too big to be shipping across the net anyway at run time.


HTH,

Mike

ok, I reinstalled windriver and changed the camera feed size to 320x240, but I got the same problem, but this time when I pressed attach debugger another page popped up in windriver called FRC_paramtask with a list of deadbxx: in which xx varies whether a number or letter and after each deadbaxx: it said "Read access not allowed"

[taichichuan]

ok, I reinstalled windriver and changed the camera feed size to 320x240, but I got the same problem, but this time when I pressed attach debugger another page popped up in windriver called FRC_paramtask with a list of deadbxx: in which xx varies whether a number or letter and after each deadbaxx: it said "Read access not allowed"

OK, the deadbxx is a memory poisoning technique to help diagnose problems. The "Read access not allowed" indicates that there is a bad pointer address being accessed by the FRC_paramtask. Now that the debugger is seemingly working, you can now run the debugger (that is launch the robot code as a "debug" run). Make sure that you select to attach to spawned tasks in the debugger set up so you can debug your complete code. It should break on entry to the main code. Set a breakpoint in your robot initialization code where the camera is instantiated and step through the code to see what parameters are being passed. Also, could you post your camera initialization sequence?

HTH,

Mike

[krudeboy51]

OK, the deadbxx is a memory poisoning technique to help diagnose problems. The "Read access not allowed" indicates that there is a bad pointer address being accessed by the FRC_paramtask. Now that the debugger is seemingly working, you can now run the debugger (that is launch the robot code as a "debug" run). Make sure that you select to attach to spawned tasks in the debugger set up so you can debug your complete code. It should break on entry to the main code. Set a breakpoint in your robot initialization code where the camera is instantiated and step through the code to see what parameters are being passed. Also, could you post your camera initialization sequence?

HTH,

Mike

One question, how do you run robot code as a "debug run?"

CAMERA INITIALIZATION:

HSLImage image; //Creates an image
AxisCamera &camera = AxisCamera::GetInstance();
camera.WriteResolution(AxisCamera::kResolution_320 x240);
//camera.WriteCompression(20);
//camera.WriteBrightness(0);

[taichichuan]

One question, how do you run robot code as a "debug run?"

CAMERA INITIALIZATION:

HSLImage image; //Creates an image
AxisCamera &camera = AxisCamera::GetInstance();
camera.WriteResolution(AxisCamera::kResolution_320 x240);
//camera.WriteCompression(20);
//camera.WriteBrightness(0);


To run a debug session, you right-click the project and select "Debug as" -> Open Debug Dialog instead of "Run as Kernel task". This brings up a dialog screen that will allow you to launch the application under the debugger. Before you launch, make sure you select the "Debug Options" tab and select "Automatically attach to spawned Kernel Tasks" or you won't be able to debug.

Once launched, you'll be asked to switch to the debug perspective. Say "yes". You should see your code in the main view in the center of the screen and a "Debug" view on the upper right hand of the Workbench. Just below that is a "Breakpoints" view. If you right click a line of code in the editor, it should pop up a dialog where you can toggle a breakpoint. This breakpoint will show up in the right-hand breakpoint view.

The Debug view then has a series of small icons along the top that allow you to single step or continue the code. Once you hit a breakpoint, the variables should then show up on the bottom right view "Variables" tab. step through the code and pay particular attention to variables like pointers getting modified. Variables that get modified should be color-coded red.

HTH,

Mike

[krudeboy51]

To run a debug session, you right-click the project and select "Debug as" -> Open Debug Dialog instead of "Run as Kernel task". This brings up a dialog screen that will allow you to launch the application under the debugger. Before you launch, make sure you select the "Debug Options" tab and select "Automatically attach to spawned Kernel Tasks" or you won't be able to debug.

Once launched, you'll be asked to switch to the debug perspective. Say "yes". You should see your code in the main view in the center of the screen and a "Debug" view on the upper right hand of the Workbench. Just below that is a "Breakpoints" view. If you right click a line of code in the editor, it should pop up a dialog where you can toggle a breakpoint. This breakpoint will show up in the right-hand breakpoint view.

The Debug view then has a series of small icons along the top that allow you to single step or continue the code. Once you hit a breakpoint, the variables should then show up on the bottom right view "Variables" tab. step through the code and pay particular attention to variables like pointers getting modified. Variables that get modified should be color-coded red.

HTH,

Mike

I'll try that right now but just one question, we are not doing image processing so when connecting the camera through the bridge, is there anything I have to add to the code or driverstation to get a live feed more than changing the IP?

[taichichuan]

I'll try that right now but just one question, we are not doing image processing so when connecting the camera through the bridge, is there anything I have to add to the code or driverstation to get a live feed more than changing the IP?

Not that I'm aware of. If you put the camera on the 10.x.y.0 network, you should be able to see the camera output if you connect directly to the camera's IP.

HTH,

Mike

[krudeboy51]

Not that I'm aware of. If you put the camera on the 10.x.y.0 network, you should be able to see the camera output if you connect directly to the camera's IP.

HTH,

Mike

Yea, Im not getting a live feed that way, I followed the instructions in the manual to set it to 10.xx.yy.zz but no feed

[taichichuan]

Yea, Im not getting a live feed that way, I followed the instructions in the manual to set it to 10.xx.yy.zz but no feed

Hmm... Check to make sure that the subnet is set properly (255.0.0.0). You should be able to ping the camera (open a cmd box and do "ping 10.xx.yy.zz"). Also, you should be able to open the camera's web interface via a browser and any device on the same subnet. If you can't ping the camera, then you've got a cable or other connectivity issue.

HTH,

Mike

[krudeboy51]

To run a debug session, you right-click the project and select "Debug as" -> Open Debug Dialog instead of "Run as Kernel task". This brings up a dialog screen that will allow you to launch the application under the debugger. Before you launch, make sure you select the "Debug Options" tab and select "Automatically attach to spawned Kernel Tasks" or you won't be able to debug.

Once launched, you'll be asked to switch to the debug perspective. Say "yes". You should see your code in the main view in the center of the screen and a "Debug" view on the upper right hand of the Workbench. Just below that is a "Breakpoints" view. If you right click a line of code in the editor, it should pop up a dialog where you can toggle a breakpoint. This breakpoint will show up in the right-hand breakpoint view.

The Debug view then has a series of small icons along the top that allow you to single step or continue the code. Once you hit a breakpoint, the variables should then show up on the bottom right view "Variables" tab. step through the code and pay particular attention to variables like pointers getting modified. Variables that get modified should be color-coded red.

HTH,

Mike

Ok I opened up the debug dialog but there are only three tabs: "main" "source" and "common" there was no debug option tab

[taichichuan]

Ok I opened up the debug dialog but there are only three tabs: "main" "source" and "common" there was no debug option tab

Look at my presentation on C++:

http://www.chiefdelphi.com/forums/showthread.php?t=87598

Towards the middle, you'll see the steps for setting up debugging complete with pictures of what you should see.

HTH,

Mike

[krudeboy51]

Look at my presentation on C++:

http://www.chiefdelphi.com/forums/showthread.php?t=87598

Towards the middle, you'll see the steps for setting up debugging complete with pictures of what you should see.

HTH,

Mike

nevermind, i give up trying to fix this thing, i will try to see if I can get it working through the bridge if not then too bad! we are not using it. Thanks for your help though! but one thing, would the stream profile cause this error or not??