RE: [GD-Windows] annoying First-chance exception message

[Andy G. <an...@mi...>]

Short answer - No, this message cannot be disabled in VC 6.

This bugged me too - I had a little program that dumped memory on
crashes, I would check each byte with IsBadReadPtr before reading it and
sometimes this would generate hundreds of 1st chance exceptions.
IsBadReadPtr just reads the byte surrounded by an exception handler -
which is pretty silly, you could just have done that yourself. I moved
to writing my own IsBadReadPtr routine - 1. Check the address is not bad
(<64K etc..) 2. Check the page protections for the address permit
reading 3. Read the byte in an exception block.  This got rid of 99.9%
of my first chance exception messages and seems much more sensible.

I don't know why you are getting a lot of exceptions - this is NOT the
best way of coding something, exceptions are slow and should be used
for, well.... Exceptional things....

Andy Glaister

-----Original Message-----
From: Jacob Turner (Core Design Ltd) [mailto:Ja...@Co...]=20
Sent: Wednesday, January 16, 2002 4:13 AM
To: 'Gam...@li...'
Subject: RE: [GD-Windows] annoying First-chance exception message


I don't know if this is what you want, but have you tried the
"Exceptions" menu option in the "Debug" menu.  Then select all the
options using Shift and mouse and select "Stop if not handled".  Then if
you have a try, catch your try, catch should get the exception before
MSVC does.  We used this to disable MSVC exception has occured dialog
box.

Jake

> -----Original Message-----
> From: Ivan-Assen Ivanov [mailto:as...@ha...]
> Sent: 16 January 2002 11:39
> To: GDWindows
> Subject: [GD-Windows] annoying First-chance exception message
>=20
>=20
> Do you know a way to suspend the annoying "First chance
> exception" message which
> appears in the output window of MSVC 6.0 any time anything=20
> throws any kind of exception in
> your program? We are trying to move to an exception-based=20
> error handling system and
> these messages make the output window nearly unusable. In=20
> "real" applications, of course,
> exceptions would not appear too often (they're not an=20
> replacement for return values), but still,
> these messages clutter my debug output too much.
>=20
>=20
> _______________________________________________
> Gamedevlists-windows mailing list=20
> Gam...@li...
> https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows
>=20

_______________________________________________
Gamedevlists-windows mailing list
Gam...@li...
https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows