From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9FB963894C11; Thu, 15 Dec 2022 18:43:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9FB963894C11 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1671129829; bh=DaTrlZTg88tCAEXmlX0xYF1Q5nZB1zLWvtFOuZGub3U=; h=From:To:Subject:Date:In-Reply-To:References:From; b=wmxiHS+FOTOBXUHaUQIrredpMaQKEyl9OXm0a95aUk07aOB0YVd0rqKErgPSYl3Z/ SBxEts/8QntOMdtYHwwH0q48jqxXB8j78bVnj6Gb4aIGoH1plHSz9AG4AUhv91T/nv 3sKJN1HDxmrGlaEXgdO4USMUjtU2TA8Y+pWTinCE= From: "seth.pellegrino at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/29395] blockframe.c:79: internal-error: get_frame_block: Assertion `bl != NULL' failed. Date: Thu, 15 Dec 2022 18:43:49 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: 11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: seth.pellegrino at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29395 --- Comment #3 from Seth Pellegrino --- (In reply to Simon Marchi from comment #2) > I get this error when trying to download your link: >=20 > { > "code": "download_cap_exceeded", > "message": "Cannot download file, download bandwidth or transaction (Cl= ass > B) cap exceeded. See the Caps & Alerts page to increase your cap.", > "status": 403 > } >=20 > I suppose it's not easy to make a small reproducer, right? Whoops, I've upped the cap to allow a couple more downloads per day: sorry about that! To your question, I've indeed got very few ideas how to reduce this case. I= t's not every kicad core that presents this way, so I think it's something spec= ific to the memory corruption that happened as a result of a use-after-free bug (that I also don't know how to reproduce). I bet there is a much smaller test case, though. If you've got ideas on how, I'm happy to help shrink it if I can. --=20 You are receiving this mail because: You are on the CC list for the bug.=