From: Daniel Jacobowitz <drow@false.org>
To: daniel he <danielhe99@gmail.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: SIGTRAP, SIGILL/SIGSEGV reported in cross debugging
Date: Wed, 05 Oct 2005 20:22:00 -0000 [thread overview]
Message-ID: <20051005202201.GA14434@nevyn.them.org> (raw)
In-Reply-To: <4ebb21ed0510051310r200db910l734b6f170c3b6925@mail.gmail.com>
Please send bug reports to gdb@, not gdb-patches@, next time.
On Wed, Oct 05, 2005 at 01:10:47PM -0700, daniel he wrote:
> Hi,
>
> While cross-debugging , I found the cross-gdb reported SIGTRAP, SIGILL
> or SIGSEGV if I set the breakpoint at the thread function. I did
> preliminary investiagtion and provided two compact test cases to
> reproduce this bug. I think this bug should be reported here.
Have you tried a CVS version of GDB? If not, please do so; I believe
these should be fixed by a patch that Andreas checked in last week.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-10-05 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 20:10 daniel he
2005-10-05 20:22 ` Daniel Jacobowitz [this message]
2005-10-07 0:13 ` daniel he
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=20051005202201.GA14434@nevyn.them.org \
--to=drow@false.org \
--cc=danielhe99@gmail.com \
--cc=gdb-patches@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