From: Jun Sun <jsun@mvista.com>
To: linux-mips@linux-mips.org
Cc: jsun@mvista.com
Subject: Re: explain to me how this works...
Date: Thu, 14 Nov 2002 12:07:46 -0800 [thread overview]
Message-ID: <20021114120746.E28717@mvista.com> (raw)
In-Reply-To: <20021114113045.D1494@wumpus.internal.keyresearch.com>; from lindahl@keyresearch.com on Thu, Nov 14, 2002 at 11:30:45AM -0800
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
>
next prev parent reply other threads:[~2002-11-14 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 16:53 gcc 3.2 is available for RedHat 7.3/mips/mipsel H. J. Lu
2002-11-14 1:42 ` explain to me how this works Greg Lindahl
2002-11-14 4:15 ` ilya
2002-11-14 16:10 ` Greg Lindahl
2002-11-14 18:39 ` Ralf Baechle
2002-11-14 19:30 ` Greg Lindahl
2002-11-14 20:07 ` Jun Sun [this message]
2002-11-14 20:12 ` Ralf Baechle
2002-11-14 21:12 ` Greg Lindahl
2002-11-14 21:50 ` Greg Lindahl
2002-11-14 22:27 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021114120746.E28717@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox