| To: | linux-mips@linux-mips.org |
|---|---|
| Subject: | Re: explain to me how this works... |
| From: | Greg Lindahl <lindahl@keyresearch.com> |
| Date: | Thu, 14 Nov 2002 11:30:45 -0800 |
| In-reply-to: | <20021114193924.A5610@linux-mips.org>; from ralf@linux-mips.org on Thu, Nov 14, 2002 at 07:39:24PM +0100 |
| Mail-followup-to: | linux-mips@linux-mips.org |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20021005095335.B4079@lucon.org> <20021113174200.A2874@wumpus.internal.keyresearch.com> <20021114193924.A5610@linux-mips.org> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.2.5.1i |
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: rsync suggestion, Ralf Baechle |
|---|---|
| Next by Date: | Re: explain to me how this works..., Jun Sun |
| Previous by Thread: | Re: explain to me how this works..., Ralf Baechle |
| Next by Thread: | Re: explain to me how this works..., Jun Sun |
| Indexes: | [Date] [Thread] [Top] [All Lists] |