From: Emmanuel Fleury <fleury@cs.auc.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: Random Segmentation fault... in my code
Date: Mon, 06 Oct 2003 19:58:28 +0200 [thread overview]
Message-ID: <1065463108.13027.171.camel@rade7.s.cs.auc.dk> (raw)
In-Reply-To: <1065456083.13024.144.camel@rade7.s.cs.auc.dk>
Never mind.... I found the bug. A very stupid one... :-/
Regards
--
Emmanuel (very ashamed)
'I don't like to ask them questions.'
'Why not?'
'They might give me answers. And then what would I do?'
-- Terry Pratchett (Lords and Ladies)
prev parent reply other threads:[~2003-10-06 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 16:01 Emmanuel Fleury
2003-10-06 17:58 ` Emmanuel Fleury [this message]
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=1065463108.13027.171.camel@rade7.s.cs.auc.dk \
--to=fleury@cs.auc.dk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®