[ABANDONED] JLinkGDBServer crashes when writing registers with lldb

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [ABANDONED] JLinkGDBServer crashes when writing registers with lldb

    Hi,

    i am using the JLink GDB server with the LLDB client. This works quiet well,
    except writes to registers like

    Source Code

    1. register write pc <addr>
    2. or
    3. j *<addr>

    result in the GDB Server crashing with this error message: "Writing common registers: malloc(): invalid size (unsorted)"



    This is the gdb package that gets send to the gdb server for command "register write pc 0xdeadbeef":

    Source Code

    1. send packet: $G80f760080000000000000000000000008ff760080000000001000000012cbcdd0100000090eeb1db0100000017000000a840bfdd9012b0db0d74baddefbeaddef3010080000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000;thread:dead;#10

    has someone experienced something like that?
    It would be very nice if this works because then one could use VSCode + CodeLLDB + Rust for embedded development :)

    Device: STM32MP15xx_A7
    Interface SWD

    JLink: JLink EDU V11.00 Firmware: 2023 Jun 10:49
    JLink Software: V7.88h (RPM Package)
    OS: Fedora

  • Can you please let us know the exact toolchain version and where to download binaries? (Not interested in building it from source on our own etc)

    Actually, GDB server is (as the name indicates) for GDB. It SHOULD also work for LLDB, as long as it behaves compatible, but there is always the chance that they introduced an incompatibility.
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.