Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#326 1 comentário 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
15/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
cpp, linux
Domínio
desktop

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
C
Estrelas
10
Forks
8
Merge médio
21min
PRs com merge (30d)
1

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de FriendsofECCE/ECCE

Todas as issues de FriendsofECCE/ECCE

Issues semelhantes

Mais issues de C

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.