From: Lennart Borgman <lennart.borgman@gmail.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 8334@debbugs.gnu.org
Subject: bug#8334: Segmentation fault in mark_object (in my patched version)
Date: Thu, 24 Mar 2011 01:52:24 +0100 [thread overview]
Message-ID: <AANLkTiks+XAMV3EzbqAgUg5U+ndrFouqwmpXw4W2nOUP@mail.gmail.com> (raw)
In-Reply-To: <87ei5xs5q0.fsf@stupidchicken.com>
On Thu, Mar 24, 2011 at 1:49 AM, Chong Yidong <cyd@stupidchicken.com> wrote:
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>
>> I just got a segmentation fault in mark_object. This was with my
>> patched version:
>
> No test case supplied; bug occurs on a tree with unspecified
> modifications. Tagging as unreproducible.
Of course there is no test case for this. I have not idea what caused
it (except from the info in the backtrace). But what is the advantage
and meaning of tagging it as "unreproducible"?
next prev parent reply other threads:[~2011-03-24 0:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 0:07 bug#8334: Segmentation fault in mark_object (in my patched version) Lennart Borgman
2011-03-24 0:49 ` Chong Yidong
2011-03-24 0:52 ` Lennart Borgman [this message]
2011-03-24 1:09 ` Chong Yidong
2011-03-24 1:20 ` Lennart Borgman
2011-03-24 1:46 ` Chong Yidong
2011-03-24 1:52 ` Lennart Borgman
2011-03-24 3:07 ` Juanma Barranquero
2011-03-24 9:24 ` Juanma Barranquero
2011-03-24 14:31 ` Lennart Borgman
2011-03-24 14:33 ` Lennart Borgman
2011-03-24 16:37 ` Chong Yidong
2011-03-24 14:42 ` Stefan Monnier
2011-03-24 14:48 ` Lennart Borgman
2012-03-27 22:42 ` Glenn Morris
[not found] ` <handler.8334.D8334.133289003225313.notifdone@debbugs.gnu.org>
2012-03-27 22:48 ` bug#8334: closed (Re: bug#8334: Segmentation fault in mark_object (in my patched version)) Lennart Borgman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTiks+XAMV3EzbqAgUg5U+ndrFouqwmpXw4W2nOUP@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=8334@debbugs.gnu.org \
--cc=cyd@stupidchicken.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).