thank you all, device.hints solved it!
On Tue, Oct 7, 2008 at 11:14 AM, Julian Elischer [EMAIL PROTECTED] wrote:
alan yang wrote:
Could people shed some light how to get remote debugging going, must
be something that i overlooked, really appreciate.
Two FreeBSD7 systems, target and
On Wed, Oct 08, 2008 at 09:43:38PM -0700, alan yang wrote:
thank you all, device.hints solved it!
On Tue, Oct 7, 2008 at 11:14 AM, Julian Elischer [EMAIL PROTECTED] wrote:
alan yang wrote:
Could people shed some light how to get remote debugging going, must
be something that i
Could people shed some light how to get remote debugging going, must
be something that i overlooked, really appreciate.
Two FreeBSD7 systems, target and development, connected with null
modem cable on each's COM1.
step 1)
- rebuild kernel with following options:
options
alan yang wrote:
Could people shed some light how to get remote debugging going, must
be something that i overlooked, really appreciate.
Two FreeBSD7 systems, target and development, connected with null
modem cable on each's COM1.
step 1)
- rebuild kernel with following options:
On Tue, Oct 7, 2008 at 10:53 AM, alan yang [EMAIL PROTECTED] wrote:
Could people shed some light how to get remote debugging going, must
be something that i overlooked, really appreciate.
Do you have the right flags for sio or uart in /boot/device.hints? I
have this (for a recent HEAD)::
hi, there,
wonder people can shed some lights on remote debugging. i have
freebsd7 configured with option DDB / KDB / GDB but after entering the
db on the target system the command gdb gives the remote GDB backend
could not be selected.
i browsed through the mailing list, and do find 1 similar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
alan yang wrote:
| hi, there,
|
| wonder people can shed some lights on remote debugging. i have
| freebsd7 configured with option DDB / KDB / GDB but after entering the
| db on the target system the command gdb gives the remote GDB backend
|
