Re: How can I trace a segfault on program start?

To: "Oliver Elphick" <olly@lfix.co.uk>
Cc: "Eric G. Miller" <egm2@jps.net>, debian-user@lists.debian.org, debian-devel@lists.debian.org
Subject: Re: How can I trace a segfault on program start?
From: Philip Blundell <philb@gnu.org>
Date: Tue, 17 Jul 2001 17:39:12 +0100
Message-id: <[🔎] E15MXsO-0001ew-00@kings-cross.london.uk.eu.org>
In-reply-to: Message from "Oliver Elphick" <olly@lfix.co.uk> of "Tue, 17 Jul 2001 17:02:52 BST." <[🔎] 200107171602.f6HG2qig019616@linda.lfix.co.uk>
References: <[🔎] 200107171602.f6HG2qig019616@linda.lfix.co.uk>

>Obviously!  But what is causing it?  This happens while the program is
>loading, before any of my own code is executed.

Some buggy constructor in a shared library?

What do you get if you set LD_DEBUG=files before running your program?

p.

Attachment: pgpmIohiQaF0d.pgp
Description: PGP signature

Reply to:

References:
- Re: How can I trace a segfault on program start?
  - From: "Oliver Elphick" <olly@lfix.co.uk>

Prev by Date: Re: "All packages use debconf"
Next by Date: Re: sponsor rules
Previous by thread: Re: How can I trace a segfault on program start?
Next by thread: Better development announcements
Index(es):
- Date
- Thread