Debugging causing exceptions?

Question

I was getting bad data from an application I was writting using C++ in Visual Studio 2k3 so I decided to debug it. Then I found it was throwing an exception but one I can't track down.

Then I placed some try/catch blocks and low and behold, when I don't debug there is no exception. That is, I have code that looks like this:

std::vector<MyClass*> ListOfStuff;
.
.
.
try
{
.
.
.
   const MyClass * localPointer = ListOfStuff[i]; //This is where the exception occurs
.
.
}
 catch (...)
{
   int x = 0;  //place break here
}

So if I step through the code line by line I'll get an exception and shot to the catch. But if I just let it run with a breakpoint inside the catch nothing happens. Using an iterator has the same behavior. And I can successfully check the size of the vector so I know I'm within the bounds.
Can anyone tell me what's going on? If it matters I'm using some standard windows libraries and openGL.

Not an ASSERT, I'm not using conditional breaks and DebugBreak behaves the same way(but I didn't know about that before, that is convenient). — Whaledawg
– Whaledawg, Commented Oct 17, 2008 at 23:25

Michael Burr · Accepted Answer · 2008-10-17 23:04:03Z

2

You can try placing a

DebugBreak();

call in the catch clause. If the app is running in the debugger, it should get control. If it's not running in the debugger you should get an opportunity to attach the "Just in Time" debugger (which is usually Visual Studio if you have that installed).

answered Oct 17, 2008 at 23:04

Michael Burr

342k52 gold badges553 silver badges774 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Henk · Accepted Answer · 2008-10-17 23:32:23Z

1

I'm referring to VS2005 but it should be applicable in your case. If you access the IDE Debug > Exceptions.. menu item you can specify the exception types that the IDE debugger should break on when thrown which should cause you to see the line the exception was raised by when single stepping through the application.

You may need to play around with what types to catch (some 1st chance exceptions are not actually problems) but it will be helpful in identifying the point the exception is raised.

answered Oct 17, 2008 at 23:32

Henk

1,70410 silver badges12 bronze badges

Comments

Doug T. · Accepted Answer · 2008-10-18 02:11:59Z

1

Is the exception an ASSERT? These may get compiled out at compile time or otherwise throw an assertion.

For example, you could have

#ifdef DEBUG
#define ASSERT(cond) if (cond) throw CDebugAssertionObj;
#else
#define ASSERT(cond)
#endif

edited Oct 18, 2008 at 2:11

answered Oct 17, 2008 at 23:00

Doug T.

65.9k28 gold badges142 silver badges206 bronze badges

Comments

billjamesdev · Accepted Answer · 2008-10-17 23:01:56Z

0

If you're using a good IDE that allows conditional breakpoints (such as, "break here if i == 5"), then it's possible the condition itself is causing the exception.

Had that one for while... my head hurt when I found it.

answered Oct 17, 2008 at 23:01

billjamesdev

14.7k6 gold badges58 silver badges79 bronze badges

Comments

Adam Rosenfield · Accepted Answer · 2008-10-18 02:16:52Z

0

Is that code part of a class method, and is ListOfStuff a member of the class? If so, check to make sure that your this pointer is valid.

answered Oct 18, 2008 at 2:16

Adam Rosenfield

402k102 gold badges524 silver badges600 bronze badges

Collectives™ on Stack Overflow

Debugging causing exceptions?

5 Answers 5

Comments

Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related