id
name
processing priority
4
site type
0 (generic, awaiting analysis)
review version
11
html import
20 (imported)
first seen date
2024-01-06 20:50:52
expired found date
-
created at
2024-06-07 16:13:12
updated at
2025-12-31 01:51:52
length
10
crc
14586
tld
2644
nm parts
0
nm random digits
0
nm rare letters
0
is subdomain of id
-
previous id
0
replaced with id
0
related id
-
dns primary id
dns alternative id
0
lifecycle status
0 (unclassified, or currently active)
deleted subdomains
0
page imported products
0
page imported random
0
page imported parking
0
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
0
count http 429
0
count http 404
0
count http 403
0
count http 5xx
0
next operation date
-
server bits
—
server ip
-
mp import status
20
mp rejected date
-
mp saved date
-
mp size orig
47618
mp size raw text
12174
mp inner links count
3
mp inner links status
20 (imported)
title
Pedro Alves | thinko's reign
description
musings on whatever
image
site name
Pedro Alves | thinko's reign
author
updated
2025-12-19 04:51:00
raw text
Pedro Alves | thinko's reign : musings on whatever Pedro Alves | thinko's reign musings on whatever Skip to content About Contacts Random stuff Blog List active signal handlers with GDB Listing active signal handlers (or dispositions) with GDB A colleague at Red Hat asked whether it is possible to get GDB to list the currently active signal handlers, aka the signal dispositions. I.e., the actions taken by the inferior process on receipt of each specific signal. You could do it manually, like this, once for each signal. Here done for SIGINT (which is 2): (gdb) set $p = (struct sigaction *) malloc(sizeof (struct sigaction)) (gdb) print sigaction(2, 0, $p) $1 = 0 (gdb) print $p->__sigaction_handler.sa_handler $2 = (__sighandler_t) 0x3ff797bb200 but that’s… rather cumbersome. Read on for something nicer. Knowing what action a signal will take when it is received is important information. For example, it’s a common problem to have a library that “steals” ...
redirect type
0 (-)
block type
0 (no issues)
detected language
1 (English)
category id
index version
2025110801
spam phrases
0
text nonlatin
0
text cyrillic
0
text characters
8733
text words
1877
text unique words
690
text lines
188
text sentences
72
text paragraphs
21
text words per sentence
26
text matched phrases
2
text matched dictionaries
2
links self subdomains
0
links other subdomains
links other domains
links spam adult
0
links spam random
0
links spam expired
0
links ext activities
0
links ext ecommerce
0
links ext finance
0
links ext crypto
0
links ext booking
0
links ext news
0
links ext leaks
0
links ext ugc
12 - secure.gravatar.com, v0.wordpress.com, jetpack.wordpress.com, s0.wp.com, 0.gravatar.com, 1.gravatar.com, 2.gravatar.com, wp.me, flickr.com, wordpress.org
links ext klim
0
links ext generic
0
dol status
0
dol updated
2025-12-19 04:51:00
rss path
rss status
32 (unknown)
rss found date
2024-02-06 11:54:46
rss size orig
3594
rss items
2
rss spam phrases
0
rss detected language
1 (English)
inbefore feed id
-
inbefore status
0 (new)
sitemap path
sitemap status
40 (completed successful import of reports.txt file to table in_pages)
sitemap review version
1
sitemap urls count
2
sitemap urls adult
0
sitemap filtered products
0
sitemap filtered videos
0
sitemap found date
2024-01-23 18:15:04
sitemap process date
2024-07-29 02:45:46
sitemap first import date
-
sitemap last import date
2024-07-31 18:55:50