From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2AD613839DF6; Mon, 13 Feb 2023 14:01:02 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2AD613839DF6 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1676296862; bh=gaGTRU6yz2ohnuAu5sATYK//Y79vuL6Xl5sP4qBb0vY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=x+KUL+0LnLgKh3BoEZVUML4IbStCktAq4u8LgQSOH4SR15okiHRbotw2BqFUgkX8x lnd4nTgNMqDvPo0wkFD8VdqBJ5D24joBuyRa6sL/PS44kNrs8KyLm3nRz35jUNFdf4 4+FAmWg8IEUoxc5hKYjmIhD4aVzJF2ZxLLELuyQU= From: "simark at simark dot ca" To: gdb-prs@sourceware.org Subject: [Bug win32/18027] dwarf2 debug info after rebasing DLLs unusable Date: Mon, 13 Feb 2023 14:01:01 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: win32 X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simark at simark dot ca X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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=3D18027 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simark at simark dot ca --- Comment #4 from Simon Marchi --- (In reply to Corinna Vinschen from comment #2) > Still, and just to be sure, if I create the DLL, split off the debuginfo > file and then rebase the DLL sans its debug sections, debuging works > nicely, albeit the debuginfo file continues to maintain the original > addresses. I. e., the load address of the debuginfo file is still > 0x4d9220000. Can you post a session of this working? I don't understand how the debug i= nfo being separate changes this behavior. I'd be interested in seeing the outp= ut of "info breakpoint", to see how GDB placed the same breakpoints as you pla= ced in other sessions. --=20 You are receiving this mail because: You are on the CC list for the bug.=