public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "3480283348 at qq dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26804] gdbserver crash at <init_cacheinfo+22> when program has canary and is 32 bit.
Date: Thu, 12 Nov 2020 06:59:30 +0000	[thread overview]
Message-ID: <bug-26804-4717-n9B8DW0sLs@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26804-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26804

--- Comment #2 from Allen_Hong <3480283348 at qq dot com> ---
Well, I find it is caused by changing of linux kernel.  Kernel which is before
linux-5.9 version does not have this bug. However, I can not find the position
causing this bug because of my poor ability...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-11-12  6:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29  3:25 [Bug gdb/26804] New: " 3480283348 at qq dot com
2020-10-29 13:44 ` [Bug gdb/26804] " simark at simark dot ca
2020-11-06  7:11 ` 3480283348 at qq dot com
2020-11-12  6:59 ` 3480283348 at qq dot com [this message]
2020-12-02 16:46 ` vries at gcc dot gnu.org
2021-01-11 18:17 ` bp at alien8 dot de
2021-01-12 17:06 ` markus.t.metzger at intel dot com
2021-01-18 16:40 ` vries at gcc dot gnu.org
2021-01-19  7:12 ` vries at gcc dot gnu.org
2021-01-19  7:13 ` [Bug server/26804] " vries at gcc dot gnu.org
2021-01-19  7:37 ` markus.t.metzger at intel dot com
2021-01-19 12:40 ` markus.t.metzger at intel dot com
2021-01-19 12:50 ` vries at gcc dot gnu.org
2021-01-20 13:00 ` vries at gcc dot gnu.org
2021-01-20 15:35 ` vries at gcc dot gnu.org
2021-01-20 15:36 ` vries at gcc dot gnu.org

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=bug-26804-4717-n9B8DW0sLs@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).