On Sun, Sep 08, 2002 at 09:54:47PM -0700, Tim Gilman wrote:
Sorry about this, Christian; your patches are buried in my
bottomless inbox. It appears real-life has swept me off my
feet. I fully don't expect to come down for a month or so
(getting married in 2 weeks, honeymoon, etc), so please
On Saturday, 7 September 2002 at 10:28:27 +0200, Christian Zander wrote:
On Sat, Sep 07, 2002 at 12:56:12AM -0700, Julian Elischer wrote:
What I found to work well is remote GDB debugging with the UDP
wrapper (ip-gdb), it responds to CTRL-C as expected.
huh? do we have that?
(rushes of to
On Sun, Sep 08, 2002 at 05:54:56PM +0930, Greg 'groggy' Lehey wrote:
Just by coincidence, I heard of this today from Richard Sharpe of
Panasas. It seems that Tim has moved on, which is possibly why you
haven't heard back from him.
I was aware of that, I had been in touch with Tim over
Christian Zander at 9/8/02 (maybe):
On Sun, Sep 08, 2002 at 05:54:56PM +0930, Greg 'groggy' Lehey wrote:
Just by coincidence, I heard of this today from Richard
Sharpe of Panasas. It seems that Tim has moved on,
which is possibly why you haven't heard back from him.
I was aware of that, I had
On Sat, 7 Sep 2002, Christian Zander wrote:
On Fri, Sep 06, 2002 at 05:17:07PM -0700, Nate Lawson wrote:
But I want to be able to pass control to the debugger when
the target kernel `hangs', that is when no `ctl-alt-f1',
`ctl-alt-del' has any effect.
If the hang is not a
On Sat, Sep 07, 2002 at 12:56:12AM -0700, Julian Elischer wrote:
What I found to work well is remote GDB debugging with the UDP
wrapper (ip-gdb), it responds to CTRL-C as expected.
huh? do we have that?
(rushes of to see it it's in ports)
comes back sadly..
(where do you get it
On Sep 07 at 09:47, Christian Zander spoke:
What I found to work well is remote GDB debugging with the UDP
wrapper (ip-gdb), it responds to CTRL-C as expected.
Is there a description available about how to configure/setup the
target kernel?
Where is ip-gdb available?
-Hanspeter
To
On Sep 06 at 17:17, Nate Lawson spoke:
You can do this by connecting a second serial cable for a console between
your host and target or by using the remotechat option and a single cable.
Once you have the serial console, option ALT_BREAK_TO_DEBUGGER allows you
to initiate a break using
Hello,
I have BREAK_TO_DEBUGGER, DDB and no DDB_UNATTENDED on the target
kernel and remotebreak = 1 on the remote gdb. So I'm expecting
pressing ctl-C in the remote gdb should interrupt the remote kernel
as if it had encountered a breakpoint. Is my expectation right?
Nothing happens when
hit CTL_ALT_ESC on it's keyboard...
or do:
sysctl debug.enter_debugger=gdb
On Fri, 6 Sep 2002, Hanspeter Roth wrote:
Hello,
I have BREAK_TO_DEBUGGER, DDB and no DDB_UNATTENDED on the target
kernel and remotebreak = 1 on the remote gdb. So I'm expecting
pressing ctl-C in the remote gdb
On Sep 06 at 12:11, Julian Elischer spoke:
hit CTL_ALT_ESC on it's keyboard...
Doing this on the remote host (running gdb) tells me `No debugger in
kernel'.
Doing this on the target host passes control to the remote gdb.
But I want to pass control to the remote debugger by issuing
the
On Fri, 6 Sep 2002, Hanspeter Roth wrote:
On Sep 06 at 12:11, Julian Elischer spoke:
hit CTL_ALT_ESC on it's keyboard...
Doing this on the remote host (running gdb) tells me `No debugger in
kernel'.
Doing this on the target host passes control to the remote gdb.
Like it should.
12 matches
Mail list logo
