All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: Andrew Burgess <aburgess@redhat.com>, Tom Tromey <tom@tromey.com>,
	Luis Machado via Gdb <gdb@sourceware.org>
Cc: Luis Machado <luis.machado@arm.com>,
	linux-debuggers@vger.kernel.org,
	Omar Sandoval <osandov@osandov.com>,
	Amal Raj T <tjarlama@gmail.com>
Subject: Re: GDB Remote Protocol Extension - Linux VMCOREINFO - Request for Feedback
Date: Wed, 22 Jan 2025 17:11:48 -0800	[thread overview]
Message-ID: <87a5bil4ff.fsf@oracle.com> (raw)
In-Reply-To: <87cygnoxi2.fsf@redhat.com>

Andrew Burgess <aburgess@redhat.com> writes:
> I have included below a very simple example that implements 'info stuff'
> which just displays the 'threads' information from a remote target.
> Place the code into 'cmd.py', then from GDB 'source cmd.py', after which
> you can 'info stuff' and 'help info stuff'.

Hi Andrew (and others)

Thank you for your initial script for the qXfer command. I've started
implementation with QEMU and I used it to great effect to help me debug
and test that. I'll soon be submitting it to the QEMU mailing list (once
I address those 32-bit and other-endian concerns).

I went ahead and updated your script a bit, mostly to my own tastes. The
only major change I made was that the arguments to the qXfer command
need to be in HEX, not decimal.

https://gist.github.com/brenns10/c936c8e7ef8193e668884ed70070ccfb

In any case, at this point, I would like to submit a patch to GDB to
update the manual to include this new qXfer command, since I've at least
got a client & a stub both speaking the same language on it. So I know
it's a feasible design.

I surmise that I need to update the (very large) gdb/doc/gdb.texinfo
file. But when I run commands like "make doc/gdb.dvi" to build the
resulting output, I get errors related to a missing file "gdb-cfg.texi"
(see below). I confirmed this not just on Oracle Linux but also on Arch
Linux. I'm happy to try out another distro via a container too. I have
texinfo, makeinfo, etc. istalled, so it's a bit confusing.

Does anybody have any advice for building the docs?

Thanks,
Stephen

Error below:
$ make doc/gdb.dvi
texi2dvi  doc/gdb.texinfo
This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020) (preloaded format=etex)
 restricted \write18 enabled.
entering extended mode

(./doc/gdb.texinfo (/usr/share/texlive/texmf-dist/tex/texinfo/texinfo.tex
Loading texinfo [version 2019-09-20.22]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.)
./doc/gdb.texinfo:10: I can't find file `gdb-cfg.texi'.
@temp ->@input gdb-cfg.texi 
                            
@includezzz ...and @input #1 }@expandafter }@temp 
                                                  @popthisfilestack 
l.10 @include gdb-cfg.texi
                          
(Press Enter to retry, or Control-D to exit)
Please type another input file name
./doc/gdb.texinfo:10: Emergency stop.
@temp ->@input gdb-cfg.texi 
                            
@includezzz ...and @input #1 }@expandafter }@temp 
                                                  @popthisfilestack 
l.10 @include gdb-cfg.texi
                          
No pages of output.
Transcript written on gdb.log.
/usr/bin/texi2dvi: etex exited with bad status, quitting.
make: *** [<builtin>: doc/gdb.dvi] Error 1


  parent reply	other threads:[~2025-01-23  1:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14  0:22 GDB Remote Protocol Extension - Linux VMCOREINFO - Request for Feedback Stephen Brennan
2025-01-14 15:03 ` Luis Machado
2025-01-14 17:15   ` Tom Tromey
2025-01-14 17:39     ` Stephen Brennan
2025-01-16 10:37       ` Andrew Burgess
2025-01-16 10:49         ` Luis Machado
2025-01-16 16:40           ` Andrew Burgess
2025-01-16 17:15             ` Luis Machado
2025-01-17 22:01             ` Tom Tromey
2025-01-16 17:58         ` Stephen Brennan
2025-01-23  1:11         ` Stephen Brennan [this message]
2025-01-14 15:04 ` Luis Machado
2025-01-26 18:07 ` Thomas Weißschuh
2025-01-27 18:13   ` Omar Sandoval
2025-01-27 18:42     ` Stephen Brennan
2025-01-27 22:40       ` Thomas Weißschuh
2025-01-28  0:19         ` Stephen Brennan
2025-01-29 21:16           ` Thomas Weißschuh

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=87a5bil4ff.fsf@oracle.com \
    --to=stephen.s.brennan@oracle.com \
    --cc=aburgess@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=linux-debuggers@vger.kernel.org \
    --cc=luis.machado@arm.com \
    --cc=osandov@osandov.com \
    --cc=tjarlama@gmail.com \
    --cc=tom@tromey.com \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.