public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: Segfault on d5ff39d "tree: Actually delete any deleted nodes"
Date: Tue, 18 Jul 2023 09:29:03 +0100	[thread overview]
Message-ID: <9E5109AB-7D8F-4C01-BD3E-166F50CAB6CC@ipfire.org> (raw)
In-Reply-To: <CA+sCei2ZBEsnoJen0C-7Cy==m-Z92FCdhXrvJ0C16gwkhf-aiw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

Hello Valters,

> On 17 Jul 2023, at 20:15, Valters Jansons <valter.jansons(a)gmail.com> wrote:
> 
> On Mon, Jul 17, 2023 at 10:09 PM Michael Tremer
> <michael.tremer(a)ipfire.org> wrote:
>> Thanks for reviewing my changes. This was indeed a thing that I did observe as well and fixed it right here:
>> 
>>  https://git.ipfire.org/?p=location/libloc.git;a=commitdiff;h=0e894966750e89d1b83c6ad90f37945d4d349118
>> 
>> The root node got deleted and lots of the code just relied on it being there. Especially when the tree was empty.
> 
> I suspected you would already be aware of the expectations that were
> being broken, so wanted to highlight it. Shame on me for not
> double-checking whether you had already resolved it before sending the
> message!

No, I like it when code is double-checked.

I did notice myself but after I pushed my first set of changes. I knew there was some work left to do, but deleting the root node was something I thought I had covered when I did not.

So, please keep the feedback coming. It will help us all to have a better version of libloc.

Best,
-Michael

> Once again: thank you for the changes!
> 
> -Valters


      reply	other threads:[~2023-07-18  8:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 18:35 Valters Jansons
2023-07-17 19:09 ` Michael Tremer
2023-07-17 19:15   ` Valters Jansons
2023-07-18  8:29     ` Michael Tremer [this message]

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=9E5109AB-7D8F-4C01-BD3E-166F50CAB6CC@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --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