Greg 'groggy' Lehey wrote:
You're a bit sketchy on the details that I've omitted here. What
happens between these two lines?
(kgdb) target remote /dev/cuad0
(kgdb) add-symbol-file /path/to/local/copy/of/file
I've solved my problem.
I run on the second machine:
# kgdb -r /dev/cuad0 /path/to/c
Greg 'groggy' Lehey wrote:
You're a bit sketchy on the details that I've omitted here. What
happens between these two lines?
(kgdb) target remote /dev/cuad0
Remote debugging using /dev/cuad0
0x in ?? ()
(kgdb) add-symbol-file /path/to/local/copy/of/file
You should have some communi
On Monday, 3 September 2007 at 10:58:54 +0400, Andrey V. Elsukov wrote:
> Hi,
>
> I want to debug my kernel with modules through serial console.
> I have two machines with 7.0-CURRENT.
> What i do:
> ...
>
> What i've missed?
You're a bit sketchy on the details that I've omitted here. What
happe
Well, I'll look into that in GDB somewhen, when I have time if nobody
else has any idea...
I tried four functions from three different areas of the kernel, and
all crashed, so I didn't bother to try more... But I'll try more
somewhen and see if I find functions which don't cause a panic...
Than
The filers here are all debugged through terminal servers using
gdb on the client and a gdb stub on the server. So if it doesn't
work it is likely due to your setup or a bug in FreeBSD's gdb stub.
-Kip
On Wed, 11 Jun 2003, Brooks Davis wrote:
> Does anyone kno
On 09 Mar 2002 15:31:55 +1130
"Daniel O'Connor" <[EMAIL PROTECTED]> wrote:
> On Fri, 2002-03-08 at 21:26, Willem van Engen wrote:
> > > Anyone have any handy tips?
> > Did you read the developers' handbook, chapter 16?
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/x5013
On Fri, 2002-03-08 at 21:26, Willem van Engen wrote:
> > Anyone have any handy tips?
> Did you read the developers' handbook, chapter 16?
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/x5013.html
Yeah I read that.
I can't get an annotates back trace though :(
ie I want gdb
On 08 Mar 2002 19:30:34 +1130
"Daniel O'Connor" <[EMAIL PROTECTED]> wrote:
> I'm trying to debug a KLD in -stable and I can't get gdb to show me a
> stack trace with the extra info (variable names, line numbers etc..)
>
> I've built a debugging kernel and copied it to the debug machine and I
> c
Duh, nevermind, thanks Julian.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Christopher
Harrer
Sent: Friday, November 17, 2000 4:48 PM
To: Julian Elischer
Cc: Freebsd-Hackers
Subject: RE: Remote GDB
Yes, that's what I mean.
I've already
he gdb terminal. It doesn't work in this environment.
Any ideas?
Thanks.
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Julian Elischer
Sent: Friday, November 17, 2000 4:48 PM
To: Christopher Harrer
Cc: Freebsd-Hackers
Subject: Re: Remote GDB
Christopher Harrer wrote:
>
> Hello All,
>
> Is there a way to "break" into a gdb (using remote GDB) while a FreeBSD
> system under test is running? I've tried ^C with no success (meaning I
> never stop execution). Also, I've tried "interrupt" from the button menu in
do you mean kernel debu
/dev/cuaa1 turned out to be the culprit. I tested this
by `echo "hello" > /dev/cuaa1` on the debugger and
`cat /dev/cuaa1` on the debuggee. The hello makes it across.
Now I'm having some "packet error" problems with kgdb.
On the debuggee I ctrl-alt-esc into ddb and do:
db> gdb
db> step
>Fro
On Monday, 28 August 2000 at 22:28:29 -0400, Christopher Stein wrote:
>
> Hello,
>
> I have been trying to connect to a remote gdb debug session via a serial
> port (null modem cable) and can't seem to get the device right. I've tried
> the devices:
>
> /dev/ttyd*
> /dev/cuaa0 (as suggested by the
sometimes the low tech answer of using ^T can help
On Thu, 30 Mar 2000, Samuel Tardieu wrote:
> On 30/03, Samuel Tardieu wrote:
>
> | I can enter remote gdb just fine using the keyboard interrupt, but the
> | call stack is pretty useless to me:
>
> Nevermind, setting breakpoints when not know
On 30/03, Samuel Tardieu wrote:
| I can enter remote gdb just fine using the keyboard interrupt, but the
| call stack is pretty useless to me:
Nevermind, setting breakpoints when not knowing at all where it blocks
is a pain but the dichotomy method should work.
To Unsubscribe: send mail to [E
15 matches
Mail list logo
