From: David Lecomber <david@allinea.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: LD_PRELOAD, SIGTRAP and step/next
Date: Thu, 17 Mar 2005 14:17:00 -0000 [thread overview]
Message-ID: <1111068922.8222.34.camel@delmo.priv.wark.uk.streamline-computing.com> (raw)
In-Reply-To: <20050317141231.GA27192@nevyn.them.org>
On Thu, 2005-03-17 at 09:12 -0500, Daniel Jacobowitz wrote:
> On Thu, Mar 17, 2005 at 12:44:15PM +0000, David Lecomber wrote:
> > Dear all,
> >
> > I am debugging using a memory checking library -- dmalloc -- this does
> > the usual things via an LD_PRELOAD over the malloc. I am getting
> > SIGTRAP when trying to call a function in this library -- but only after
> > a step or a next; after a user-defined breakpoint behaviour is correct!
>
> Kernel version? This sounds like a Linux kernel bug that has since
> been fixed...
2.6.10-1.770_FC3smp
so pretty recent!
d,
--
David Lecomber <david@allinea.com>
next prev parent reply other threads:[~2005-03-17 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 12:45 David Lecomber
2005-03-17 14:12 ` Daniel Jacobowitz
2005-03-17 14:17 ` David Lecomber [this message]
2005-03-17 18:09 ` Daniel Jacobowitz
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=1111068922.8222.34.camel@delmo.priv.wark.uk.streamline-computing.com \
--to=david@allinea.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
/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