On Tuesday, 9 November 1999 at 16:04:34 -0500, Zhihui Zhang wrote:
> On Tue, 9 Nov 1999, Greg Lehey wrote:
>> On Tuesday, 9 November 1999 at 13:36:56 -0800, Archie Cobbs wrote:
>>> Zhihui Zhang writes:
>>>> Thanks for your reply. What confuses me is that when I use commands "gdb"
>>>> (enter remote protocol mode) and "step" on the target machine, the
>>>> debugging machine takes control (it executes "target remote /dev/cuaa1").
>>>> In this case, how can I run anything on the target machine to trigger a
>>>> panic?
>>>
>>> I'm not sure if this answers your question, but the command
>>>
>>> sysctl -w debug.cebugger=1
>>>
>>> will cause the kernel to stop and return your gdb prompt.
>>> Then you could call the function panic() directly if you wanted.
>>
>> Take a look at /usr/src/sys/modules/vinum/.gdbinit.kernel. There's
>> some almost undocumented stuff in there, including a macro called
>> ddb. Call it from gdb and it'll switch back to ddb.
>
> Thanks! I will certainly look into them. In the same time, I add a
> sysctl variable and let my program calls Debugger("some string") if that
> sysctl variable is true.
I don't understand what that's useful for.
> It seems working. I hope someone will write a hacker's book.
I'm intending to write something on the subject, but don't count on it
soon.
Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
