All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Christoph Egger <Christoph.Egger@amd.com>, xen-devel@lists.xensource.com
Cc: John Levon <levon@movementarian.org>
Subject: Re: [PATCH] mkelf32: Correct sh_link
Date: Thu, 04 Jan 2007 09:58:51 +0000	[thread overview]
Message-ID: <C1C2805B.7105%keir@xensource.com> (raw)
In-Reply-To: <200701040930.51259.Christoph.Egger@amd.com>

On 4/1/07 08:30, "Christoph Egger" <Christoph.Egger@amd.com> wrote:

>> Indeed, and that's what we're doing currently. But this is problematic
>> as it's very easy for other files to get lost, not be handed over etc.
>> and working backwards to the right version is very rarely feasible...
>> Thus we'd like to have a single binary (or more importantly dump!) that
>> has everything in place.
> 
> Further, when you boot on a serial console how do you connect gdb
> over a serial console? You can't use a serial console for two things
> concurrently. Then a xen-kernel debugger is useful. And yeah, that needs
> standard symtabs and strtabs.
> And with a kernel debugger, you don't need to worry about what John pointed
> out.

Gdbstub and console can share a serial port. When gdbstub is entered then
the gdbstub steals the serial port. Console messages are then wrapped as gdb
messages. Given that this setup works and requires minimal code in Xen, I
have no interest in accepting an in-kernel debugger into the tree.

 -- Keir

  reply	other threads:[~2007-01-04  9:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-03  9:30 [PATCH] mkelf32: Correct sh_link Christoph Egger
2007-01-03 13:57 ` Keir Fraser
2007-01-03 15:11   ` Christoph Egger
2007-01-03 15:14     ` Christoph Egger
2007-01-03 15:21       ` Keir Fraser
2007-01-03 15:20     ` Keir Fraser
2007-01-03 15:38       ` Christoph Egger
2007-01-03 16:21         ` Keir Fraser
2007-01-03 18:36           ` John Levon
2007-01-03 19:14             ` Keir Fraser
2007-01-03 19:20               ` John Levon
2007-01-03 20:06                 ` Keir Fraser
2007-01-03 20:11                   ` John Levon
2007-01-03 21:21                     ` Keir Fraser
2007-01-03 21:32                       ` John Levon
2007-01-03 21:40                         ` Keir Fraser
2007-01-04 14:34                           ` John Levon
2007-01-04  8:30                 ` Christoph Egger
2007-01-04  9:58                   ` Keir Fraser [this message]
2007-01-04 11:57                     ` Christoph Egger
2007-01-03 14:08 ` grel
2007-01-04  2:58   ` Mark Williamson

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=C1C2805B.7105%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=Christoph.Egger@amd.com \
    --cc=levon@movementarian.org \
    --cc=xen-devel@lists.xensource.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.