From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 944C83858C74; Thu, 21 Sep 2023 15:22:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 944C83858C74 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1695309774; bh=dWESPtm+75jvSyZI+KDk8FXCH3pE+VpgFhAPur+jniE=; h=From:To:Subject:Date:From; b=VOMHHOQk07P8afsTcC3UbFPhf+PUymaMRjSWHgau8+zJn/gREjBXKCr8CKgbHmXs4 DxdRa/U9DjcCYz2CIUpVlEHA1XExzMFS3ykCroSN2KgktawiUiv4LdyQLINJNIseQU OemtumwUF+V9w8wejk2pV6dM4l1DBL3J19rbJnxE= From: "juangburgos at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/30876] New: Frames not displayed correctly for target tfile Date: Thu, 21 Sep 2023 15:22:54 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: juangburgos at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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=3D30876 Bug ID: 30876 Summary: Frames not displayed correctly for target tfile Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: juangburgos at gmail dot com Target Milestone: --- When I load a trace file using the target tfile command, I get messages of = the type: Tracepoint 1 at 0x1157: file ... Created tracepoint 1 for target's tracepoi= nt 1 at 0x555555555157. Then when I try to look at a frame using tfind start, I get: Found trace frame 0, tracepoint 1 #0 0x0000555555555157 in ?? () If I add the symbol file with the difference displayed by the message 0x555555555157 - 0x1157 =3D 0x555555554000: add-symbol-file ./trace_test -o 0x555555554000 Then the frame works: (gdb) tfind start Found trace frame 0, tracepoint 3 #0 foo (a=3D33, b=3D4) at /home/juangburgos/Documents/REPOS/trace_test/mai= n.cpp:3 3 return a + b + b; But I would expect GDB to correct this offset by itself, as I believe the u= ser should not be expected to compute the offset manually and reload the symbols every time. See this stackoverflow question for more details: https://stackoverflow.com/questions/77148274/gdb-tracing-loaded-trace-file-= does-not-display-frame-correctly Thanks, --=20 You are receiving this mail because: You are on the CC list for the bug.=