public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Julien Laganier <Julien.Laganier@Sun.COM>
To: Linux Mailing List <linux-kernel@vger.kernel.org>
Subject: Shared library interceptor/SIGSEGV
Date: Mon, 09 Jul 2001 16:11:45 +0200	[thread overview]
Message-ID: <3B49BBA1.4CAD3187@Sun.COM> (raw)

Hi folks,

I have written a library for intercepting outgoing network connections,
and redirecting them through a proxy server.
The user had to set LD_PRELOAD to load my library, and my library
redefine the connect() function for INET sockets. It also uses
dlsym(RTLD_NEXT, "connect") to get the location of the 'real' libc
connect.

The problem is : when I run some programs (like cat, which doesn't use
connect), it causes a SIGSEGV, and strace doesn't help me more! It seems
that the segmentation fault occurs after a 'certain' number of syscalls,
but I can't figure why.

Does anybody know where could be the bug ?

Tnx.
--

    Julien Laganier
     Student Intern
Sun Microsystem Laboratories

                 reply	other threads:[~2001-07-09 14:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3B49BBA1.4CAD3187@Sun.COM \
    --to=julien.laganier@sun.com \
    --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