Board index » cppbuilder » Trouble debugging exceptions

Trouble debugging exceptions


2003-09-03 01:55:31 PM
cppbuilder0
In BCB6, I have trouble getting the de{*word*81} to show me the codelines
where exceptions occur. It normally stops if the problem occurs in my
own .cpp files, but if the exception thrown in stl or boost the de{*word*81}
doesn't react. Can this be fixed by adding all the folders with headers
to the debug source path? Or is the problem connected to templates?
Morten Espeland
 
 

Re:Trouble debugging exceptions

"Morten Espeland" < XXXX@XXXXX.COM >writes:
Quote
In BCB6, I have trouble getting the de{*word*81} to show me the
codelines where exceptions occur. It normally stops if the problem
occurs in my own .cpp files, but if the exception thrown in stl or
boost the de{*word*81} doesn't react.
When you say it doesn't react, do you mean that it doesn't break at
all on the exception? Have you disabled any of the de{*word*81}
break-on-exception options (under tools/de{*word*81}?)
Quote
Can this be fixed by adding all the folders with headers to the
debug source path?
It wouldn't hurt to be sure the IDE and de{*word*81} can find all the code
you're using. If it does stop, then it'll be able to display the code
that threw.
Quote
Or is the problem connected to templates?
I haven't had troubles with templates throwing exceptions.
Do you have a small example application that can demonstrate the
problem?
--
Chris (TeamB);
 

Re:Trouble debugging exceptions

Well, I see that the default options for all OS exceptions
is "Handled by User program". I guess that would be it!
Morten
"Chris Uzdavinis (TeamB)" < XXXX@XXXXX.COM >wrote in message
Quote
"Morten Espeland" < XXXX@XXXXX.COM >writes:

>In BCB6, I have trouble getting the de{*word*81} to show me the
>codelines where exceptions occur. It normally stops if the problem
>occurs in my own .cpp files, but if the exception thrown in stl or
>boost the de{*word*81} doesn't react.

When you say it doesn't react, do you mean that it doesn't break at
all on the exception? Have you disabled any of the de{*word*81}
break-on-exception options (under tools/de{*word*81}?)

>Can this be fixed by adding all the folders with headers to the
>debug source path?

It wouldn't hurt to be sure the IDE and de{*word*81} can find all the code
you're using. If it does stop, then it'll be able to display the code
that threw.

>Or is the problem connected to templates?

I haven't had troubles with templates throwing exceptions.

Do you have a small example application that can demonstrate the
problem?

--
Chris (TeamB);
 

{smallsort}