From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 99B50385772B; Tue,  9 May 2023 15:59:18 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 99B50385772B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1683647958;
	bh=5pc3KwrWCMUDwCRUyli8oQkaJoKicUJwLacgT75uDw8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=ARHRCxdR5JLGaIyEhyOyJ4ilfkGRYP3rKEnqsQSiXRxjrowP42qxQoNUV2kNckxS3
	 Mi7Mm+0iu9ruh2hSxiUM75yLFxBisYppEPzVT9aTQbq0tfsaksOC5LyMNdjldBuMM6
	 S9bLGehJx0zdfaK4UoF0w2VwWGhFudc5LMDEVES0=
From: "marian.buschsieweke at ovgu dot de"
 <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30431] segfault when inspecting remote variable
Date: Tue, 09 May 2023 15:59:18 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: 13.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marian.buschsieweke at ovgu dot de
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: attachments.created
Message-ID: <bug-30431-4717-PVT2aRu8XI@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30431-4717@http.sourceware.org/bugzilla/>
References: <bug-30431-4717@http.sourceware.org/bugzilla/>
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: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D30431

--- Comment #2 from Marian Buschsieweke <marian.buschsieweke at ovgu dot de=
> ---
Created attachment 14870
  --> https://sourceware.org/bugzilla/attachment.cgi?id=3D14870&action=3Ded=
it
hello-world.elf ; a broken firmware for the MSP430F1611 that I fail to debug

Thanks for the quick reply. I attached the binary in question, a simple
application that flashes on an MSP430F1611 MCU and outputs "Hello world" via
UART using RIOT. (Specifically,
https://github.com/maribu/RIOT/tree/tmp/examples/hello-world is the
corresponding code and can be generated by `make BOARD=3Dolimex-msp430h1611=
`.)

Note that this firmware isn't functional; I'm in the process of figuring out
why the firmware generated with my new toolchain doesn't work, while it does
work with an older toolchain.

Here is the requested info:

(gdb) p *bmsym.minsym
$2 =3D {<general_symbol_info> =3D {m_name =3D 0x7ffff6ebed34 "BCSCTL1", m_v=
alue =3D
{ivalue =3D 87, block =3D 0x57,=20
      bytes =3D 0x57 <error: Cannot access memory at address 0x57>, address=
 =3D 87,
common_block =3D 0x57, chain =3D 0x57},=20
    language_specific =3D {obstack =3D 0x0, demangled_name =3D 0x0}, m_lang=
uage =3D
language_auto, ada_mangled =3D 0, m_section =3D 0},=20
  m_size =3D 0, filename =3D 0x7ffff6bbb500 "irq.c", m_type =3D mst_abs,
created_by_gdb =3D 0, m_target_flag_1 =3D 0,=20
  m_target_flag_2 =3D 0, m_has_size =3D 1, maybe_copied =3D 0, name_set =3D=
 1,
hash_next =3D 0x0, demangled_hash_next =3D 0x0}

--=20
You are receiving this mail because:
You are on the CC list for the bug.=