What an article!

theCPkid

See this [^] Was totally mesmerized by the way he explained all that stuff and could not find any better place to express my gratitude. His CP profile [^]. His article was so inspiring that it helped me solve a very stupid but very hard to find bug. Wow!

Dan Neely

Out of curiosity, is it still messed up in 2k8; the article in question was written in 07.

The latest nation. Procrastination.

theCPkid

Dan Neely wrote:

Out of curiosity, is it still messed up in 2k8; the article in question was written in 07

hahahaha.. it is 2k9 and not 2k8.. update your clock. ;P I am not concerned about his end result but the way he found that bug and the nice examples he gave in between. I can guess you have not read the article.. and regarding your question, I dont know about the bug in _CrtMemCheckPoint and most probably, it should be fixed by now.

Dan Neely

Unless you've stolen a very early (pre?) alpha version from MS you don't have a copy of Visual Studio 2k9 because no such creature ever existed; and even then I doubt they ever planned a new release only one year after the previous as opposed to waiting 2 years and calling it 2k10.

The latest nation. Procrastination.

Rama Krishna Vavilala

:) One of you is talking about Years and another about Visual Studio Versions. All the more reasons not to have product names suffixed year as the version.

Dan Neely

In my original post I used both. It shouldn't've mattered though. The different stylings should've made what was what obvious. :rolleyes:

The latest nation. Procrastination.

theCPkid

Stealing would be fun but a pre-alpha MS product!! No way man. Their RCs are so buggy and we are talking about pre-alpha! did you mean article was written in VS 07? :doh:

PIEBALDconsult

It was obvious, and I haven't even had any coffee yet.

Abu Mami

Rama Krishna Vavilala wrote:

All the more reasons not to have product names suffixed year as the version.

I agree. Looking forward to upcoming versions of Visual Studio such as Visual Studio Galaxy 500 XL, Visual Studio Ram Charger, and so on.

Dan Neely

No, the article was written in 2007, and was talking about Vs6 - VS2k5.

The latest nation. Procrastination.

Paul Conrad

Wow, reading through all your posts with theCPkid, he's not catching the point?

"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham

theCPkid

:^) i am just stoopid maybe. but why I just did not catch the point is because i failed to realize that the bug with _CrtMemCheckPoint is not a bug with _CrtMemCheckPoint but a bug with compiler, VS in this case. I thought I can use _CrtMemCheckPoint inside other compiler like Dev-C++ if I include the right header files. I thought why the very great Newcomer mentioned about VS6-VS2k5 is because he tested with those compilers. And I asked abt VS 07 to make sure that I have not missed something obvious again. :-O enough talk. here's the results with VS 9.0 (VS 2008)

0: Total space allocated (_CrtMemCheckpoint): 47735
0: Total space allocated (_heapwalk): 52998
1: Total space allocated (_CrtMemCheckpoint): 47767
1: Total space allocated (_heapwalk): 52998
2: Total space allocated (_CrtMemCheckpoint): 47799
2: Total space allocated (_heapwalk): 52998
3: Total space allocated (_CrtMemCheckpoint): 47831
3: Total space allocated (_heapwalk): 52998
4: Total space allocated (_CrtMemCheckpoint): 47863
4: Total space allocated (_heapwalk): 52998
5: Total space allocated (_CrtMemCheckpoint): 47895
5: Total space allocated (_heapwalk): 52998
6: Total space allocated (_CrtMemCheckpoint): 47927
6: Total space allocated (_heapwalk): 52998
....
197: Total space allocated (_CrtMemCheckpoint): 54039
197: Total space allocated (_heapwalk): 52998
198: Total space allocated (_CrtMemCheckpoint): 54071
198: Total space allocated (_heapwalk): 52998
199: Total space allocated (_CrtMemCheckpoint): 54103
199: Total space allocated (_heapwalk): 52998
200: Total space allocated (_CrtMemCheckpoint): 54135
200: Total space allocated (_heapwalk): 52998
201: Total space allocated (_CrtMemCheckpoint): 54167
201: Total space allocated (_heapwalk): 52998
...
356: Total space allocated (_CrtMemCheckpoint): 59127
356: Total space allocated (_heapwalk): 52998
357: Total space allocated (_CrtMemCheckpoint): 59159
357: Total space allocated (_heapwalk): 52998
358: Total space allocated (_CrtMemCheckpoint): 59191
358: Total space allocated (_heapwalk): 52998
359: Total space allocated (_CrtMemCheckpoint): 59223
359: Total space allocated (_heapwalk): 52998
360: Total space allocated (_CrtMemCheckpoint): 59255
360: Total space allocated (_heapwalk): 52998
...
667: Total space allocated (_CrtMemCheckpoint): 69079
667: Total space allocated (_heapwalk): 52998
668: Total space allocated (_CrtMemCheckpoint): 69111
668: Total space allocated (_heapwalk): 52998
669: Total

Paul Conrad

I was not directing towards the actual bug that is mentioned in the article, but the versions of Visual Studio.

theCPkid wrote:

VS 07

No such thing :D But, it is understandable since as with many software packages, there's always some new version popping up once once gets settled with the current version.

"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham