Rongxin Wu

最新

• SQLess: Dialect-Agnostic SQL Query Simplification
• LibAlchemy: A Two-Layer Persistent Summary Design for Taming Third-Party Libraries in Static Bug-Finding Systems
• Pinolo: Detecting Logical Bugs in Database Management Systems with Approximate Query Synthesis
• Detecting JVM JIT Compiler Bugs via Exploring Two-Dimensional Input Spaces
• Improving Java Deserialization Gadget Chain Mining via Overriding-Guided Object Generation
• Accelerating Build Dependency Error Detection via Virtual Build
• smartPip: A Smart Approach to Resolving Python Dependency Conflict Issues
• Will Dependency Conflicts Affect My Program's Semantics?
• MVD: memory-related vulnerability detection based on flow-sensitive graph neural networks
• BEACON: Directed Grey-Box Fuzzing with Provable Path Pruning
• Targeting Requirements Violations of Autonomous Driving Systems by Dynamic Evolutionary Search
• Transcode: Detecting Status Code Mapping Errors in Large-Scale Systems
• Historical Spectrum based Fault Localization
• Skeletal Approximation Enumeration for SMT Solver Testing
• Fuzzing SMT Solvers via Two-Dimensional Input Space Exploration
• Path-Sensitive Sparse Analysis without Path Conditions
• Automatic Detection and Update Suggestion for Outdated API Names in Documentation
• Escaping Dependency Hell: Finding Build Dependency Errors with the Unified Dependency Graph
• Conquering the Extensional Scalability Problem for Value-Flow Analysis Frameworks
• Pangolin: Incremental Hybrid Fuzzing with Polyhedral Path Abstraction
• Exploring and Exploiting the Correlations between Bug-Inducing and Bug-Fixing Commits
• Could I Have a Stack Trace to Examine the Dependency Conflict Issue?
• Exposing Library API Misuses Via Mutation Analysis
• SMOKE: Scalable Path-Sensitive Memory Leak Detection for Millions of Lines of Code
• Do the Dependency Conflicts in My Project Matter?
• How Well Do Change Sequences Predict Defects? Sequence Learning from Software Changes
• Pinpoint: Fast and Precise Sparse Value Flow Analysis for Million Lines of Code
• ChangeLocator: Locate Crash-Inducing Changes Based on Crash Reports
• Context-Aware Patch Generation for Better Automated Program Repair
• Locus: locating bugs from software changes
• Casper: an efficient approach to call trace collection
• Diagnose Crashing Faults on Production Software
• CrashLocator: locating crashing faults based on crash stacks
• ReBucket: A method for clustering duplicate crash reports based on call stack similarity
• Sample-based software defect prediction with active and semi-supervised learning
• ReLink: recovering links between bugs and changes
• Dealing with noise in defect prediction