Skip to content

Add SIGABRT monitoring support to segfault_analyzer#51

Merged
saimizi merged 1 commit intomainfrom
feature/support_abort_detect
Nov 29, 2025
Merged

Add SIGABRT monitoring support to segfault_analyzer#51
saimizi merged 1 commit intomainfrom
feature/support_abort_detect

Conversation

@saimizi
Copy link
Owner

@saimizi saimizi commented Nov 29, 2025

What's changed

  • Extended segfault_analyzer to monitor both SIGSEGV and SIGABRT signals
  • Added support for detecting abort signals including stack smashing errors
  • Updated data structures to include signal_number and event_type fields
  • Modified BPF program to capture SIGABRT events with stack traces
  • Enhanced output to display abort events with diagnostic information
  • Stack traces for SIGABRT marked as potentially unreliable due to corruption
  • Added test_stack_smashing.c test program compiled with -fstack-protector-strong
  • Updated Makefile to build stack smashing test program
  • Updated requirements.md and design.md to reflect simplified abort handling
  • Users can identify stack smashing by examining stack trace for __stack_chk_fail

Key features:

  • Captures complete stack traces for SIGABRT events
  • Provides instruction pointer, registers, and VMA information
  • Marks abort stack traces as potentially unreliable
  • Simplified approach: all SIGABRT treated as 'ABORT' events
  • Stack trace reveals abort cause (e.g., __stack_chk_fail for stack smashing)

- Extended segfault_analyzer to monitor both SIGSEGV and SIGABRT signals
- Added support for detecting abort signals including stack smashing errors
- Updated data structures to include signal_number and event_type fields
- Modified BPF program to capture SIGABRT events with stack traces
- Enhanced output to display abort events with diagnostic information
- Stack traces for SIGABRT marked as potentially unreliable due to corruption
- Added test_stack_smashing.c test program compiled with -fstack-protector-strong
- Updated Makefile to build stack smashing test program
- Updated requirements.md and design.md to reflect simplified abort handling
- Users can identify stack smashing by examining stack trace for __stack_chk_fail

Key features:
- Captures complete stack traces for SIGABRT events
- Provides instruction pointer, registers, and VMA information
- Marks abort stack traces as potentially unreliable
- Simplified approach: all SIGABRT treated as 'ABORT' events
- Stack trace reveals abort cause (e.g., __stack_chk_fail for stack smashing)
@saimizi saimizi merged commit 74672b1 into main Nov 29, 2025
3 checks passed
@saimizi saimizi deleted the feature/support_abort_detect branch November 29, 2025 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant