From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Moritz Wilhelmy Newsgroups: gmane.emacs.bugs Subject: bug#31918: 25.3; gud inserts invalid gdb commands Date: Sat, 23 Jun 2018 17:05:41 +0200 Message-ID: <87zhzlbl16.fsf@barfooze.de> References: <871sd1ckvf.fsf@barfooze.de> <831sd0rz9l.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1529766250 26206 195.159.176.226 (23 Jun 2018 15:04:10 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 23 Jun 2018 15:04:10 +0000 (UTC) User-Agent: mu4e 1.0; emacs 25.3.1 To: 31918@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Jun 23 17:04:06 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fWk57-0006j2-9G for geb-bug-gnu-emacs@m.gmane.org; Sat, 23 Jun 2018 17:04:05 +0200 Original-Received: from localhost ([::1]:38820 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fWk7E-0005UJ-A3 for geb-bug-gnu-emacs@m.gmane.org; Sat, 23 Jun 2018 11:06:16 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50874) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fWk74-0005UD-N2 for bug-gnu-emacs@gnu.org; Sat, 23 Jun 2018 11:06:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fWk70-0004VQ-No for bug-gnu-emacs@gnu.org; Sat, 23 Jun 2018 11:06:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:53680) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fWk70-0004VE-KD for bug-gnu-emacs@gnu.org; Sat, 23 Jun 2018 11:06:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fWk70-0007pC-6d for bug-gnu-emacs@gnu.org; Sat, 23 Jun 2018 11:06:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Moritz Wilhelmy Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 23 Jun 2018 15:06:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 31918 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 31918-submit@debbugs.gnu.org id=B31918.152976634530052 (code B ref 31918); Sat, 23 Jun 2018 15:06:02 +0000 Original-Received: (at 31918) by debbugs.gnu.org; 23 Jun 2018 15:05:45 +0000 Original-Received: from localhost ([127.0.0.1]:33344 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fWk6j-0007oe-9z for submit@debbugs.gnu.org; Sat, 23 Jun 2018 11:05:45 -0400 Original-Received: from inferno.barfooze.de ([5.9.157.210]:63536) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fWk6h-0007oV-2Y for 31918@debbugs.gnu.org; Sat, 23 Jun 2018 11:05:43 -0400 Original-Received: from localhost ([10.128.128.11]) by inferno.barfooze.de (8.15.2/8.15.2) with ESMTPS id w5NF5fE9067542 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <31918@debbugs.gnu.org>; Sat, 23 Jun 2018 17:05:41 +0200 (CEST) (envelope-from mw@barfooze.de) Original-Received: by localhost (Postfix, from userid 1000) id 1E71621090; Sat, 23 Jun 2018 17:05:41 +0200 (CEST) In-reply-to: <831sd0rz9l.fsf@gnu.org> X-Scanned-By: MIMEDefang 2.83 on 192.168.42.2 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:147773 Archived-At: Hi Eli, On Thu, Jun 21 2018, Eli Zaretskii wrote: > I tried to reproduce this, but couldn't. Please tell what is your GDB > version. Also, can you provide a complete recipe, including a program > to debug, and all the steps needed to reproduce the issue, preferably > starting from "emacs -Q"? The program I'm debugging is a Linux kernel on an ARM SoC over a serial link. We're using an older version of buildroot to build everything (planning to switch to something newer, which would also bring a newer gdb version), but for now we're stuck with this: $ cat bin/kernelgdb #!/bin/sh BR=~/src/buildroot exec ${BR}/output/host/usr/bin/arm-buildroot-linux-musleabi-gdb ${BR}/output/images/vmlinux -b 115200 -ex "target remote localhost:4441" "$@" With agent-proxy running on localhost 4440^4441. $ exec ${BR}/output/host/usr/bin/arm-buildroot-linux-musleabi-gdb GNU gdb (GDB) 7.10.1 Copyright (C) 2015 Free Software Foundation, Inc. ... This GDB was configured as "--host=x86_64-pc-linux-gnu --target=arm-buildroot-linux-musleabi". ... (gdb) show configuration This GDB was configured as follows: configure --host=x86_64-pc-linux-gnu --target=arm-buildroot-linux-musleabi --with-auto-load-dir=$debugdir:$datadir/auto-load --with-auto-load-safe-path=$debugdir:$datadir/auto-load --with-expat --with-gdb-datadir=/home/mw/src/FAME/miro-service.buildroot/output/host/usr/share/gdb (relocatable) --with-jit-reader-dir=/home/mw/src/FAME/miro-service.buildroot/output/host/usr/lib/gdb (relocatable) --without-libunwind-ia64 --with-lzma --without-guile --with-separate-debug-dir=/home/mw/src/FAME/miro-service.buildroot/output/host/usr/lib/debug (relocatable) --without-babeltrace ("Relocatable" means the directory can be moved with the GDB installation tree, and GDB will still find it.) (gdb) Is there a minimum required gdb version for gdb-mi to work correctly? > (The additional commands are commands injected by gdb-mi.el to allow > Emacs display of various information: call-stack, thread information, > etc. But they shouldn't appear in the commands you specified for your > breakpoints, so this is still some kind of problem. I cannot > reproduce it, though.) For now, I've switched back to gud-gdb without MI, which seems to work better on my setup but I'm somewhat invested in the future of gdb/gud and I think MI is a step in the right direction, so please let me know if you need any more information. Best regards, Moritz