From: Daniel Jacobowitz <drow@false.org>
To: Lukas Heiniger <lukas.heiniger@fela.ch>
Cc: gdb@sources.redhat.com
Subject: Re: SIGTRAP or SIG32 when remote debugging threads
Date: Wed, 24 Mar 2004 14:54:00 -0000 [thread overview]
Message-ID: <20040324143913.GA25841@nevyn.them.org> (raw)
In-Reply-To: <200403241411.16660.lukas.heiniger@fela.ch>
On Wed, Mar 24, 2004 at 02:11:16PM +0100, Lukas Heiniger wrote:
> It looks like setting and hitting the shlib event breakpoint works.
Not to me. Is 0x40002570 the shlib event breakpoint, and if so, why
are you stopped there instead of at the first instruction in the
program?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-24 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 17:30 Lukas Heiniger
2004-03-19 18:31 ` Daniel Jacobowitz
2004-03-22 13:21 ` Lukas Heiniger
2004-03-22 17:33 ` Daniel Jacobowitz
2004-03-23 19:25 ` Lukas Heiniger
2004-03-23 20:41 ` Daniel Jacobowitz
2004-03-24 14:44 ` Lukas Heiniger
2004-03-24 14:54 ` Daniel Jacobowitz [this message]
2004-03-24 15:09 ` Lukas Heiniger
2004-03-24 15:44 ` Daniel Jacobowitz
2004-03-25 14:29 ` Lukas Heiniger
2004-03-25 15:37 ` 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=20040324143913.GA25841@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=lukas.heiniger@fela.ch \
/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