<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pwndbg on IHEXON BLOG</title><link>https://ihexon.github.io/tags/pwndbg/</link><description>Recent content in Pwndbg on IHEXON BLOG</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>zzheasy@gmail.com (IHEXON)</managingEditor><webMaster>zzheasy@gmail.com (IHEXON)</webMaster><copyright>Copy, _right?_ :thinking_face:</copyright><lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ihexon.github.io/tags/pwndbg/index.xml" rel="self" type="application/rss+xml"/><item><title>Installing pwndbg From Source With venv</title><link>https://ihexon.github.io/posts/pwndbg-install-venv/</link><pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate><author>zzheasy@gmail.com (IHEXON)</author><guid>https://ihexon.github.io/posts/pwndbg-install-venv/</guid><description>&lt;p&gt;This is the way I install pwndbg from a local checkout when I want the Python dependencies isolated in a venv.&lt;/p&gt;
&lt;p&gt;I am not using &lt;code&gt;setup.sh&lt;/code&gt; here. The script is convenient, but it also tries to install system packages with &lt;code&gt;sudo&lt;/code&gt;. For a clean user-level install, I prefer doing the Python part explicitly.&lt;/p&gt;</description></item></channel></rss>