Rohan Padhye

@rohan.padhye.org

Computer Science professor at CMU. Doing research on automated software testing and bug finding. https://rohan.padhye.org

⏱️ 9 days until submission deadline (Dec 11, 23:59 AoE). Organized by: @yannicnoller.bsky.social, @rohan.padhye.org, @ruijiemeng.bsky.social, and Laszlo (@lszekeres.bsky.social) Szekeres.

Yannic Noller@yannicnoller.bsky.social · 10mo ago

#FUZZING'26 CALL FOR PAPERS ────── ✨ After 5 years, we will be again co-located with NDSS! 🔗 fuzzing-workshop.github.io 📅 11. Dec (Submission) //cc @mboehme.bsky.social (MPI-SP), @ruijiemeng.bsky.social (CISPA), @rohan.padhye.org (CMU), László Szekeres (Google)

Check out the latest episode of the #BugBash podcast! I had a great time chatting with David Wynn about automated testing in academia vs industry. Thanks @antithesis.com for having me on!

Antithesis@antithesis.com · 8mo ago

If a debate breaks out at your dinner table, take a break and listen to @rohan.padhye.org share how two camps that have long misunderstood each other - industry and academia - can learn from each other instead. This latest ep of the #BugBash podcast is live now, whereever you get your podcasts.

Just Accepted to ACM TOSEM! The "Havoc Paradox" is about the relationship between byte-level fuzzer mutations and their effect on the inputs produced by generators for structured strings (e.g. XML/SQL). Can disruptive mutations be controlled? Should they be? Find out. 📄 dl.acm.org/doi/pdf/10.1...

BildBild

🖊️ Register here: ntnu.eventsair.com/fse2025-isst... (FUZZING is a co-located workshop)

Welcome to FSE 2025 + ISSTA 2025

ntnu.eventsair.com

Rohan Padhye@rohan.padhye.org · last yr.

We're excited to announce two keynote speakers for the #FUZZING'25 workshop (part of @issta_conf at Trondheim, Norway): [*] Will Wilson, CEO and Co-Founder of Antithesis [*] Miryung Kim, Professor and Vice Chair of Graduate Studies at UCLA conf.researchr.org/home/issta-2...

The JQF repo is now both popular enough (700+ stars) and contains enough buggy/vulnerable code as sample fuzz targets that we're getting occasionally spammed with crappy AI-generated patches. I can't imagine what bigger OSS projects are dealing with right now.

And now that we’re all here, some work!🚨 Are Large Language Models Memorizing Bug Benchmarks? 🚨 There’s growing concern that LLMs for SE are prone to data leakage, but no one has quantified it... until now. 🕵️‍♂️ 1/

arxiv.org