Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Builder: crash (SIGSEGV) when closing the window, after Log/Delete/metal-bond attempts

Abierto
  • ¿Algo no está bien?
#326 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
15/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
cpp, linux
Área
desktop

Línea de trabajo

Start by building the same commit with debug symbols so frames 1-5 of the SIGSEGV backtrace resolve to names, then read the close-window handler at builder+0x32ceb3 in the event table. Check whether the Log pane (the active wxLog target) or objects left by the failed Delete and metal-bond commands are used after they are destroyed. Done means exact reproduction steps are written down and the dangling pointer is identified and fixed, with the crash no longer occurring on close.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Seen: 2026-10-14 15:14, Debian 13, GNOME on Wayland, a test build of main + #322 (9.1.0 version string). The Builder crashed with SIGSEGV while its window was being closed; the ecce session in the terminal ended with "Segmentation fault (core dumped)". Earlier in that Builder session: selecting a line in the Log panel, Edit → Select Molecule, Delete attempts (#324), then closing the Log panel; metal–π bond attempts that failed (#325).

Core (systemd-coredump, PID 78624): the faulting instruction address is inside the Builder's own mapping but not executable code (kernel: segfault at 560212142b38 ip 560212142b38 ... error 15), i.e. a call through a corrupt or dangling pointer. Stack, with the package binary (stripped, so the Builder frames have no names):

#0  builder+0xf09b38          <- jump target, not code
#1  builder+0xae87a3
#2  builder+0x32aef0
#3  builder+0x32c50e
#4  builder+0x32ccf4
#5  builder+0x32ceb3          <- Builder's close-window handler (event table)
#6  wxEvtHandler::ProcessEventIfMatchesId
...
#12 wxWindowBase::Close(bool)
#13..  GTK delete-event (window manager close)

Next: exact steps to reproduce; then resolve frames 1–5 with a build of the same commit that keeps symbols. Candidates to check: something the close path touches after a pane was closed (the Log pane is also the active wxLog target), and objects left behind by the failed bond commands.

Lenguaje dominante
C
Estrellas
10
Forks
8
Merge medio
21 min
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de FriendsofECCE/ECCE

Todos los issues de FriendsofECCE/ECCE

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.