| To: | linux-mips@linux-mips.org |
|---|---|
| Subject: | Re: explain to me how this works... |
| From: | Jun Sun <jsun@mvista.com> |
| Date: | Thu, 14 Nov 2002 12:07:46 -0800 |
| Cc: | jsun@mvista.com |
| In-reply-to: | <20021114113045.D1494@wumpus.internal.keyresearch.com>; from lindahl@keyresearch.com on Thu, Nov 14, 2002 at 11:30:45AM -0800 |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20021005095335.B4079@lucon.org> <20021113174200.A2874@wumpus.internal.keyresearch.com> <20021114193924.A5610@linux-mips.org> <20021114113045.D1494@wumpus.internal.keyresearch.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.2.5i |
Look like a good case for using kgdb.... Jun On Thu, Nov 14, 2002 at 11:30:45AM -0800, Greg Lindahl wrote: > On Thu, Nov 14, 2002 at 07:39:24PM +0100, Ralf Baechle wrote: > > > Eh? Nothing on MIPS should use socketcall(2); > > OK, so let's say it's using socket(). How do I go about debugging > this? I mean, I can start sprinkling printks all over the place, but is > there a more clever way? > > greg > |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: explain to me how this works..., Greg Lindahl |
|---|---|
| Next by Date: | Re: explain to me how this works..., Ralf Baechle |
| Previous by Thread: | Re: explain to me how this works..., Greg Lindahl |
| Next by Thread: | Re: explain to me how this works..., Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |