all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Patrick Mahan <plmahan@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Automatically modifying the gud-gdb command line
Date: Tue, 23 Jun 2020 13:21:41 -0700	[thread overview]
Message-ID: <CAFDHx1+EsPrurne_CTMRrzN51gKAUA5FyxFAGWNBqy7t+v9BEw@mail.gmail.com> (raw)

Before wandering off into the bowels of the GUD lisp code, I was wonder if
anyone has ever done what I want (I could not find anything on the Emacs
Wiki site nor via google-fu).

Basically, when I am starting a debug session, I enter the command 'gud-gdb
<ENTER>' which then prompts me with 'Run gud-gdb (like this): gdb
--fullname <image>'.  Now I have code that breaks apart a core dump into
its core file and the image that dumped and creates a gdb init file.  I
then modify the command line that gud-gdb prompted me with by adding '-x
gdbinit' and 'core.XXXX' to that line and starting the debug session.

I would like to automate this process (can I pre-config the command line
used by gud-gdb?) so I can possibly turn this into a simple turnkey
procedure that I can then give to our tech-support guys to do the
preliminary phase 1 analysis.  I like the way emacs presents the output,
especially since they will have sources to dump and it is easier in emacs
to walk up the backtrace display source.

Any pointers would be appreciated.

Thanks,

Patrick


             reply	other threads:[~2020-06-23 20:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 20:21 Patrick Mahan [this message]
2020-06-23 20:34 ` Automatically modifying the gud-gdb command line Emanuel Berg via Users list for the GNU Emacs text editor
2020-06-23 21:25   ` Patrick Mahan
2020-06-23 21:36     ` tomas
2020-06-24  2:26       ` Patrick Mahan
2020-06-24  4:19         ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-06-23 21:43     ` Emanuel Berg via Users list for the GNU Emacs text editor

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=CAFDHx1+EsPrurne_CTMRrzN51gKAUA5FyxFAGWNBqy7t+v9BEw@mail.gmail.com \
    --to=plmahan@gmail.com \
    --cc=help-gnu-emacs@gnu.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.