GS

Protezione da Buffer Overrun con Visual Studio 2010

Security & Architecture — Thu, 04 Jun 2009 14:21:59 GMT

Segnalo il nuovo posto del team di C++ sulla nuova versione di /gs, gs++ in Visual Studio 2010 . Dal

Channel 9 Video: Louis Lafreniere: Next Generation Buffer Overrun Protection - gs++

Visual C++ Team Blog — Wed, 03 Jun 2009 19:03:50 GMT

Thanks to a recent VC Blog post by Hongwei Qi , you already know that we have worked on our /GS switch

Debugging and Profiling API enhancements in CLR 4.0

Notes from a dark corner — Wed, 27 May 2009 19:10:47 GMT

There’s a very interesting interview been published on Channel 9 about the new and changed profiling

re: GS

Frank Bristow — Sat, 16 May 2009 16:34:23 GMT

Please help me with getting my default back.

The dialog box

Jim — Wed, 13 May 2009 20:28:06 GMT

Is it possible (or will it be possible) to disable the dialog box that shows when a buffer overrun is detected? Since _set_security_error_handler is no longer supported, there's no way to just quietly exit, rather than showing a dialog box. This is evil for a server product that will display a dialog box that users will never see and can never dismiss. The server product has logic to handle crashed sub-processes, so just exiting would be preferable to a dialog.

re: GS

vcblog — Tue, 07 Apr 2009 19:33:01 GMT

Hello,

To follow up on the profiler/bounds checker issues please refer to one of these blogs at http://blogs.msdn.com/profiler/, or the profiler forums at http://social.msdn.microsoft.com/forums/en-US/vstsprofiler/threads/. We are currently preparing for our first beta but we will be responding to other issues on this posting in the upcoming weeks.

Thank you,

Visual C++ Team

re: GS

Joe — Fri, 27 Mar 2009 07:06:57 GMT

to_be_defined: Using your argument we could start chucking features right and left. Why have any features at all?

The point is that Microsoft does make a profiler and it's absolutely horrible. They are also pumping this /GS feature which is next to useless. They also have a memory leak detector which is also next to useless. Given how many other things Visual Studio does well, the extremely poor implementation of these features are very glaring.

The other point is that Microsoft spends a tremendous amount of time and effort on extremely fringe features. They have ignored C++ for years and now claim to be returning to it. Yet many of the things they are concentrating on are still fringe instead of things that should have been a natural evolution of the VC++ 6.0 product.

What is the difference between VS Standard and VS Pro? Pro offers Windows Mobile support and remote debugging. Big deal and big ripoff. Now if Pro offered a non-crappy profiler and memory checker, I'd upgrade.

re: GS

longtime c++/Mfc dev — Thu, 26 Mar 2009 20:27:42 GMT

Is there some way to improve GS, while accommodating the needs of somebody like Tony, yet benefiting all our end users? Some sort of win-win-win compromise?

One of the fantastic things about this blog is the amazing (dare I say "unrivaled") transparency.

- Kudos yet again

re: GS

Tony — Thu, 26 Mar 2009 00:31:58 GMT

My name is Tony and i'm a hacker from Russia. Please turn off GS feature (and if possible SafeSEH etc) in next release of MSVC. It is very difficult to gain money, my family need more food.

At least it is up to user - if she will not switch it ON - that is only her problem. Right?

Both Microsoft and I will be fine.

p.s. And by the way. Please contact guys from Windows dev.team - is it possible to turn off DEP and ASLR by default?

profiler

Greg — Tue, 24 Mar 2009 18:03:30 GMT

The statement level profiler was included in VS6.0 as a standard built in (no extra cost) feature. Please add it to VS10 or at least VS10 professional as a standard buit in (no extra cost) feature.