Main

processing priority

4

site type

3 (personal blog or private political site, e.g. Blogspot, Substack, also small blogs on own domains)

review version

11

html import

20 (imported)

Events

first seen date

2025-02-24 19:45:43

expired found date

-

created at

2025-02-24 19:45:43

updated at

2026-01-20 18:07:53

Domain name statistics

length

26

crc

60047

tld

2211

nm parts

0

nm random digits

0

nm rare letters

0

Connections

is subdomain of id

13642151 (wordpress.com)

previous id

0

replaced with id

0

related id

-

dns primary id

0

dns alternative id

0

lifecycle status

0 (unclassified, or currently active)

Subdomains and pages

deleted subdomains

0

page imported products

0

page imported random

0

page imported parking

0

Error counters

count skipped due to recent timeouts on the same server IP

0

count content received but rejected due to 11-799

0

count dns errors

0

count cert errors

0

count timeouts

1

count http 429

0

count http 404

0

count http 403

0

count http 5xx

0

next operation date

2025-03-30 02:44:37

Server

server bits

server ip

-

Mainpage statistics

mp import status

20

mp rejected date

-

mp saved date

-

mp size orig

93341

mp size raw text

15506

mp inner links count

6

mp inner links status

20 (imported)

Open Graph

title

Macropolygon

description

Simon's graphics musings

image

site name

Macropolygon

author

updated

2026-01-18 20:54:50

raw text

Macropolygon | Simon's graphics musings Macropolygon Simon's graphics musings Skip to content Home About Evaluating Debugged-Process Memory in a Visual Studio Extension Posted on 16/12/2012 by Simon I’ve recently been working on a Visual Studio extension that acts a bit like the Visual Studio memory window, but visualises the memory as a texture. Like the memory window, there’s a box for the user to type in an address expression. The plug-in then needs to evaluate the expression in the context of the debugger’s current thread and stack frame, and then retrieve the contents of the debuggee process’s memory space at that address. This is a relatively common operation for the debugger — it’s done by the memory window, as well as the watch windows, of course. I therefore assumed it would be fairly straightforward. I was very wrong. After much hair-pulling, however, I was finally able to get it to work, so I thought I’d document it here in case anyone else needs to d...

Text analysis

redirect type

0 (-)

block type

0 (no issues)

detected language

1 (English)

category id

224

index version

2025123101

spam phrases

0

Text statistics

text nonlatin

0

text cyrillic

0

text characters

11744

text words

2298

text unique words

707

text lines

278

text sentences

107

text paragraphs

36

text words per sentence

21

text matched phrases

2

text matched dictionaries

3

RSS

rss status

32 (unknown)

rss found date

2025-02-24 19:45:44

rss size orig

22877

rss items

3

rss spam phrases

0

rss detected language

1 (English)

inbefore feed id

-

inbefore status

0 (new)

Sitemap

sitemap status

40 (completed successful import of reports.txt file to table in_pages)

sitemap review version

2

sitemap urls count

5

sitemap urls adult

0

sitemap filtered products

0

sitemap filtered videos

0

sitemap found date

2025-02-24 19:45:43

sitemap process date

2025-04-05 10:13:45

sitemap first import date

-

sitemap last import date

2025-07-05 04:21:26