From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 88794 invoked by alias); 31 Oct 2019 18:58:32 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 88786 invoked by uid 89); 31 Oct 2019 18:58:31 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:996, H*c:alternative X-HELO: mail-ot1-f50.google.com Received: from mail-ot1-f50.google.com (HELO mail-ot1-f50.google.com) (209.85.210.50) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 31 Oct 2019 18:58:30 +0000 Received: by mail-ot1-f50.google.com with SMTP id z6so6349380otb.2 for ; Thu, 31 Oct 2019 11:58:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=e7T5KZC5u90tJy5NwcnuPddjQGh+Cbek7FJIHiohqhg=; b=qLltTljAhxVsl2CudfJnFQkYLbOXIDGsUhgzuy8gbXLRwe3SibfDp3yRqJozR/weOU Vwkn+V6v1rRT+FAB/wTLPnXbikeP8xUa2mLF2h3ueYlBjQ4tGWH1v3+x4ddn4CkLoFIR wa+NegzOiSYY+kJ2S/X0nsosAfhMSNF9aEumoDFGB4Jegha02oExeKL0dvVMlWVWAVT9 3Ulz0bTs1WLieujm+OdY+gjvbGkO3jjTl68RSGRPCjFC/T7v+twGfwZ9cYit+GEhMsas jy8VWi1GliJP2n0vf5oSm7KTq1TJpYQKMzsNiN1QDi1shDjev6Ygro1m+lo6RDuf931f 6rNg== MIME-Version: 1.0 From: Reinoud Koornstra Date: Thu, 31 Oct 2019 18:58:00 -0000 Message-ID: Subject: gdb 8.3.1 truncated register in remote g packet To: gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2019-10/txt/msg00053.txt.bz2 Hello Everyone, I downloaded an compiled gdb 8.3.1 with --target=arm-linux-gnueabihf on my x86_64 pc. Compiled and installed fine. I started the gdb with the vmlinux file and tried to connect to the remote arm32 machine: target remote /dev/ttyUSB0 Then I get: Truncated register 19 in remote 'g' packet. What is going wrong here? I saw earlier archives about similar issues, but i thought those would have been patched. Any help would be appreciated. Thanks, Reinoud.