Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #12655

S

Software Verify

Company blog · softwareverify.com/blogprogrammingsystems

Software Verify is the company blog at softwareverify.com, writing about programming and systems. Since 2009, 6 different Hacker News readers have linked it 6 times. It is still writing: the last post was on 2026-06-20, and you can follow it by feed.

Visit the blog
6mentions?
6HN people?
2009–2026first – last linked?
Links on Hacker News per year · peak 2 in 2020

Software tools for code coverage, memory leak detection, performance profiling, deadlock detection, execution tracing. C++, C, C#, VB6, Delphi

What Hacker News says?

  1. Anyone have any tips for memory profiling tools, other than the one mentioned in the article comments? ( http://www.softwareverify.com/javascript/memory/feature.html , Windows-only, Firefox-only, non-free)

    Comment linking /javascript/memory/feature.html

    on “Deep Tracing of Internet Explorer”
  2. Submitted Unusual Memory Bit Patterns as a story · 2 points

    HN discussion
  3. I went to MicroCong last year. Long way to go from the UK. If you can't afford Business of Software, go to MicroConf. It's much better than the European ESWC. I wrote a blog article about each talk and a few other bits. Most speakers let me post the MP3 of their talk as well. http://www.softwareverify.com/blog/?tag=microconf

    Comment linking /blog/?tag=microconf

    on “MicroConf 2012: The Conference for Self Funded Startups”
  4. Submitted 59 seconds with Eric Ries as a story · 2 points

    HN discussion
  5. For windows I use 2 C++ profilers (memory and speed) from https://www.softwareverify.com/index.php I like to memory profile on a regular basis. It a is lot easier to catch and fix a memory leak if you discover it soon after you’ve introduced it.

    Comment linking /index.php

    on “Ask HN: What do you recommend for optimization and profiling?”
  6. Can you clarify? As far as I'm aware, dwAllocationGranularity returned via GetSystemInfo determines the MEM_RESERVE alignment and size. Yes, in practice this is always 64KiB but may not always be true in the future. Additionally, dwPageSize returned via GetSystemInfo determines the alignment and size for MEM_COMMIT which in practice is 4KiB or 16KiB. Put differently, while an application might be stuck with allocati…

    Comment linking /blog/leaking-memory-with-virtualalloc/

    on “How to Allocate Memory”

Search all of HN for softwareverify.com