public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "1in.lang at seznam dot cz" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/27006] Segmentation fault when using gdb command 'call'
Date: Fri, 04 Dec 2020 15:55:28 +0000 [thread overview]
Message-ID: <bug-27006-4717-iSiQuuyCeN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27006-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27006
--- Comment #2 from Stanislav Lang <1in.lang at seznam dot cz> ---
I'll try to prepare a minimal reproduction next week,...
---------- Původní e-mail ----------
Od: simark at simark dot ca <sourceware-bugzilla@sourceware.org>
Komu: 1in.lang@seznam.cz
Datum: 3. 12. 2020 14:35:13
Předmět: [Bug c++/27006] Segmentation fault when using gdb command 'call'
"https://sourceware.org/bugzilla/show_bug.cgi?id=27006
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simark at simark dot ca
--- Comment #1 from Simon Marchi <simark at simark dot ca> ---
Can you add a sample program, so that others can try to reproduce?
--
You are receiving this mail because:
You reported the bug."
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-12-04 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 11:29 [Bug c++/27006] New: " 1in.lang at seznam dot cz
2020-12-03 13:35 ` [Bug c++/27006] " simark at simark dot ca
2020-12-03 16:34 ` ssbssa at sourceware dot org
2020-12-04 15:55 ` 1in.lang at seznam dot cz [this message]
2020-12-07 13:51 ` 1in.lang at seznam dot cz
2020-12-07 13:52 ` 1in.lang at seznam dot cz
2020-12-07 14:17 ` simark at simark dot ca
2020-12-07 14:43 ` 1in.lang at seznam dot cz
2020-12-07 14:48 ` simark at simark dot ca
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-27006-4717-iSiQuuyCeN@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).