public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
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 [thread overview] Message-ID: <bug-30431-4717-PVT2aRu8XI@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30431-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30431 --- Comment #2 from Marian Buschsieweke <marian.buschsieweke at ovgu dot de> --- Created attachment 14870 --> https://sourceware.org/bugzilla/attachment.cgi?id=14870&action=edit 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=olimex-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 = {<general_symbol_info> = {m_name = 0x7ffff6ebed34 "BCSCTL1", m_value = {ivalue = 87, block = 0x57, bytes = 0x57 <error: Cannot access memory at address 0x57>, address = 87, common_block = 0x57, chain = 0x57}, language_specific = {obstack = 0x0, demangled_name = 0x0}, m_language = language_auto, ada_mangled = 0, m_section = 0}, m_size = 0, filename = 0x7ffff6bbb500 "irq.c", m_type = mst_abs, created_by_gdb = 0, m_target_flag_1 = 0, m_target_flag_2 = 0, m_has_size = 1, maybe_copied = 0, name_set = 1, hash_next = 0x0, demangled_hash_next = 0x0} -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-05-09 15:59 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-08 21:05 [Bug gdb/30431] New: " marian.buschsieweke at ovgu dot de 2023-05-09 15:01 ` [Bug gdb/30431] " tromey at sourceware dot org 2023-05-09 15:59 ` marian.buschsieweke at ovgu dot de [this message] 2023-05-09 16:53 ` marian.buschsieweke at ovgu dot de 2023-06-02 7:19 ` marian.buschsieweke at posteo dot net 2023-06-02 15:06 ` tromey at sourceware dot org 2023-06-03 18:28 ` marian.buschsieweke at posteo dot net 2023-06-03 18:29 ` marian.buschsieweke at posteo dot net 2023-06-03 20:31 ` tromey at sourceware dot org 2023-06-03 21:33 ` marian.buschsieweke at posteo dot net 2023-06-03 21:35 ` marian.buschsieweke at posteo dot net 2023-06-04 17:25 ` tromey at sourceware dot org 2023-06-04 20:19 ` marian.buschsieweke at posteo dot net 2023-06-20 21:20 ` tromey at sourceware dot org 2023-06-20 21:21 ` tromey at sourceware dot org 2023-07-10 17:19 ` cvs-commit at gcc dot gnu.org 2023-07-10 17:19 ` tromey at sourceware dot org
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=bug-30431-4717-PVT2aRu8XI@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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).