Re: [AD] Breakpointing an app in the MSVC 6 debugger can get a key to be

Re: [AD] Breakpointing an app in the MSVC 6 debugger can get a key to be stuck in Windows 2000

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]

To: alleg-developers@xxxxxxxxxx
Subject: Re: [AD] Breakpointing an app in the MSVC 6 debugger can get a key to be stuck in Windows 2000
From: Andrei Ellman <ae-a-alleg@xxxxxxxxxx>
Date: Mon, 16 Jan 2006 14:16:51 +0100
Organization: Wacko Software

aj wrote:

I strongly suggest you upgrade from msvc6 it is considered quite brokenand old.
I also suggest you try using WindowsXP instead of Windows 2000,
and the latest version of DirectX 9.0c i think that is at the moment.

Can this problem be reproduced on newer versions of MSVC? I only haveaccess to MSVC 6, so I do not know if this is specific to version 6 or not.

AE.

Follow-Ups:
- Re: [AD] Breakpointing an app in the MSVC 6 debugger can get a key to be stuck in Windows 2000
  - From: aj

Messages sorted by: [ date | thread ]
Prev by Date: Re: Allegro assembly code (was: Re: [AD] proposing a new official .lib name for VC static CRT version)
Next by Date: Re: [AD] Breakpointing an app in the MSVC 6 debugger can get a key to be stuck in Windows 2000
Previous by thread: Re: [AD] Breakpointing an app in the MSVC 6 debugger can get a key to be stuck in Windows 2000
Next by thread: Re: [AD] Breakpointing an app in the MSVC 6 debugger can get a key to be stuck in Windows 2000

Mail converted by MHonArc 2.6.19+

http://listengine.tuxfamily.org/