From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin@cygwin.com
Subject: Re: setup 2.920 release candidate - please test
Date: Mon, 15 Aug 2022 10:18:39 +0200 [thread overview]
Message-ID: <385b14df-889a-8225-21b0-b34858180596@t-online.de> (raw)
In-Reply-To: <874jyeydok.fsf@Rainer.invalid>
Achim Gratz wrote:
> Christian Franke writes:
>> This version aborts if "Sync" setting is reverted to "Best".
> If the abort goes away when building setup with the previous version of
> libsolv then you might have found an easier reproducer for a bug I'm
> chasing… Running it in gdb should get you a SIGSEGV in
> solver_addduprules in this case.
Indeed:
Thread 1 received signal SIGSEGV, Segmentation fault.
0x00007ff60bb42a19 in solver_addduprules (solv=<optimized out>,
addedmap=<optimized out>) at
/usr/src/debug/mingw64-x86_64-libsolv-0.7.22-1/src/rules.c:2125
...
next prev parent reply other threads:[~2022-08-15 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 14:37 Jon Turney
2022-08-14 12:38 ` Christian Franke
2022-08-14 16:47 ` Achim Gratz
2022-08-14 19:00 ` Jon Turney
2022-08-15 8:18 ` Christian Franke [this message]
2022-08-14 18:56 ` Jon Turney
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=385b14df-889a-8225-21b0-b34858180596@t-online.de \
--to=christian.franke@t-online.de \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).