Hello.

Jason Wessel wrote:

>>    In fact, you've brought up an interesting point -- when I tried 
>> using KGDBoE as a module, I failed at that.  How did you manage to 
>> make it work?

>> WBR, Sergei

> It used to be the case that you could build a built-in rs232 driver as 
> well kgdboe and load that as a module as well.  It should also work to 
> use kgdboe directly as a built in.

    I've also tried that and failed.

> What kind of error did you see?  What was your modprobe line like?  Are 
> the target and host on the same subnet?

   IIRC, I couldn't connect to modularized KGDBoE (although it loaded OK)...

> I generally build the kgdb I/O modules and not as a built in, so I can 
> use what ever I have available at the time.  Assuming my host ip address 
> is 10.0.2.2, for kgdboe I would use:
> modprobe kgdboe kgdboe=@/,@10.0.2.2/

> For the rs232 using the "simple configuration" on the system's second 
> serial port, I would use:
> modprobe 8250_kgdb kgdb8250=1,115200

    This is not the case for other KGDBoE serial drivers, I'm afraid.

> Long ago I merged in the feature to allow you to change the I/O module 
> out at runtime.  If it doesn't work, please describe the scenario you 
> had and before you run any commands run "echo 8 > 
> /proc/sys/kernel/printk" so the output of any messages can be seen for 
> the modprobe right on the console.

    I need to try once more (but not right now)...

> Jason.

WBR, Sergei

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport

Reply via email to