HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
YahooArchive
rtrace
Ruby2015–2015
YahooArchive / rtrace · Archived

rtrace

Rtrace is an x86/x86_64 native code debugger written in Ruby with zero dependencies

2Distinct people
2Mentions
0Explicit recommenders
138GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Rtrace is an x86/x86_64 native code debugger written in Ruby with zero dependencies

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2015-07-14 16:03:12 UTC to 2015-07-15 00:58:50 UTC.

012015-07-14 16:00:00 UTC to 2015-07-14 17:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJul 14, 16:002015-07-14 17:00:00 UTC to 2015-07-14 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-14 18:00:00 UTC to 2015-07-14 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-14 19:00:00 UTC to 2015-07-14 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-14 20:00:00 UTC to 2015-07-14 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 14, 20:002015-07-14 21:00:00 UTC to 2015-07-14 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-14 22:00:00 UTC to 2015-07-14 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-14 23:00:00 UTC to 2015-07-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-15 00:00:00 UTC to 2015-07-15 01:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 15, 00:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 14, 16:002015-07-14 16:00:00 UTC2015-07-14 17:00:00 UTC110
Jul 14, 17:002015-07-14 17:00:00 UTC2015-07-14 18:00:00 UTC000
Jul 14, 18:002015-07-14 18:00:00 UTC2015-07-14 19:00:00 UTC000
Jul 14, 19:002015-07-14 19:00:00 UTC2015-07-14 20:00:00 UTC000
Jul 14, 20:002015-07-14 20:00:00 UTC2015-07-14 21:00:00 UTC000
Jul 14, 21:002015-07-14 21:00:00 UTC2015-07-14 22:00:00 UTC000
Jul 14, 22:002015-07-14 22:00:00 UTC2015-07-14 23:00:00 UTC000
Jul 14, 23:002015-07-14 23:00:00 UTC2015-07-15 00:00:00 UTC000
Jul 15, 00:002015-07-15 00:00:00 UTC2015-07-15 01:00:00 UTC101

What Hacker News says

2 sources
I am the author of this code. If you're interested in getting started with it right away then check out Eucalyptus: https://github.com/yahoo/rtrace/tree/master/Eucalyptus I wrote Eucalyptus as the primary unit test for rtrace but its a fully functional native code debugger. Here is an example of how you can configure it using Ruby to trace calls to malloc() and print out some information: https://github.com/yahoo/rtrace/blob/master/Eucalyptus/examp... If you're interested in contributing, the signal handler in Rtrace could use some cleanup. Helper methods for interacting with procfs and the process memory are always useful too.
In Rtrace is an x86/x86_64 native code debugger written in Ruby

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.