From: Valters Jansons <valter.jansons@gmail.com>
To: location@lists.ipfire.org
Subject: Segfault on d5ff39d "tree: Actually delete any deleted nodes"
Date: Mon, 17 Jul 2023 21:35:29 +0300 [thread overview]
Message-ID: <CA+sCei3047G9U0J2yojOCVM6xyFiQ28g7=znBXRdit+dhLqxiA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
Hi,
I am seeing a segfault during tests (src/test-as, src/test-country and
src/test-signature) for all Ubuntu LTS versions. This only occurs with
the latest commit (d5ff39d) applied. Looking at the change, the node
still seems to be used after dereference, but I am not fully sure of
the way you have planned out the deletion, therefore I am not offering
a patch/resolution.
>From gdb I am seeing:
Program received signal SIGSEGV, Segmentation fault.
loc_network_tree_delete_nodes (tree=0x55555555a370) at src/network.c:1045
1045 tree->root->deleted = 0;
Best regards,
Valters Jansons
next reply other threads:[~2023-07-17 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 18:35 Valters Jansons [this message]
2023-07-17 19:09 ` Michael Tremer
2023-07-17 19:15 ` Valters Jansons
2023-07-18 8:29 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+sCei3047G9U0J2yojOCVM6xyFiQ28g7=znBXRdit+dhLqxiA@mail.gmail.com' \
--to=valter.jansons@gmail.com \
--cc=location@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox