vc++ 5.0 debugger problems, any solutions yet?
Quote:
> > The Visual Studio service pack has just been released (see
> > http://www.*-*-*.com/ ). You don't mention
> which
> > de{*filter*} problem was worrying you, so I couldn't say whether it's been
> > fixed. However, the web site does include a full fix list, so you
should
> be
> > able to determine if it has.
> > --
> > Martyn Lovell
> > Visual Studio Development
> Thanks for the information, and indeed, the service pack was released
just
> after
> I posted that question, typical huh? :)
> The problem I was mainly concerned with was the painfully slow remote
> debugging.
> After installed the patch, I have noticed that remote debugging is
somewhat
> quicker, and more reliable when trying to stop debugging when the remote
> app
> has crashed. However, I won't say its perfect by a long shot, since
> sometimes
> the remote application can take 10-15 seconds to start up, and single
> stepping
> speed is still somewhat below that of vc4.2, at least on my machine.
> However, since I cannot tell what the general network load is at any
time,
> I cannot
> say exactly how slow vc5 is at remote debugging. All I can conclude is
that
> its
> better after installing this service pack, and now just about useable,
but
> still
> falls short of what I had hoped for.
> All in all though, sp1 was a timely release, full of good fixes. Keep up
> the good
> work.
Appologies for following up my post with another post. My above response
was
based on just half a day of using vc5, after which I thought remote
debugging
was definitely improved. However, after a very late programming session
trying
to do extensive remoting debugging or a game I'm writing, I have to
unfortunately
conclude that remote debugging is seriously broken compared to vc4.2
So until this is resolved, I have to go back to 4.2 :/
And I was beginning to love those vc5 macro's too.
Just to give some details on my problems, heres a few things I have
noticed:
1. It can take 10-20 seconds for remote debugging to start and get to
my first line of code.
2. Single stepping over code is stil extremely slow at times.
3. Numerous crashes. Sometimes the remote app locks up before it even
starts properly, taking both machines with it (vc5 stops responding
and has to be shut down forceably after a few minutes, even though
I've reset the target machine... vc4.2 used to detect this and say
it had lost connection).
4. Numerous vc5 de{*filter*} crashes, sometimes as I single step out of
functions.
Shame.
Martin Kift
Millennium Interactive Ltd.
