From: "Amit S. Kale" <akale@veritas.com>
To: "Michael S. Miles" <mmiles@alacritech.com>
Cc: gdb@sources.redhat.com
Subject: Re: remote gdb: reboot system(Linux)
Date: Tue, 24 Jul 2001 02:12:00 -0000 [thread overview]
Message-ID: <3B5D3985.9550C07B@veritas.com> (raw)
In-Reply-To: <KIEKJCGPOOADIOGPDJJLOEPHEFAA.mmiles@alacritech.com>
You can set pc to machine_restart function and continue.
That will immediately reboot the machine.
kgdb ( http://kgdb.sourceforge.net/ ) doesn't yet support
gdb remote protocol packets kill, attach and detach.
I'll add it whenever I get some time.
"Michael S. Miles" wrote:
>
> I do a lot of Linux remote kernel debugging over serial lines. I will now
> be doing even more of this only the debugger and target system will be at a
> remote site.
>
> In a previous life I did a lot of NT kernel debugging with windbg and it had
> a command called ".reboot" which if made in windbg would actually cause a
> reboot of the target system. I really need this same capability in gdb when
> debugging Linux. I know that a lot of this functionality was probably
> provided in the kernel, but I thought someone might know if this presently
> exists or what would be involved with providing it.
>
> thanks for any help or info,
> michael
--
Amit Kale
Veritas Software ( http://www.veritas.com )
next prev parent reply other threads:[~2001-07-24 2:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200107211225.f6LCPA730345@maat.cygnus.com>
2001-07-21 9:07 ` 1 GCC regressions, 1 new, with your patch on 2001-07-21T09:30:01Z Geoff Keating
2001-07-21 9:34 ` remote gdb: reboot system(Linux) Michael S. Miles
2001-07-24 2:12 ` Amit S. Kale [this message]
2001-07-24 17:22 ` Andrew Cagney
2001-07-25 5:33 ` Amit S. Kale
2001-07-21 12:55 ` 1 GCC regressions, 1 new, with your patch on 2001-07-21T09:30:01Z Nathan Sidwell
2001-07-23 14:49 ` Andrew Cagney
2001-07-23 22:11 ` Geoff Keating
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=3B5D3985.9550C07B@veritas.com \
--to=akale@veritas.com \
--cc=gdb@sources.redhat.com \
--cc=mmiles@alacritech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox