From: jamie.couture at gmail.com (Jamie Couture)
Subject: [PATCH 0/1] segfault in cgit
Date: Fri, 9 Sep 2011 00:43:09 -0400 [thread overview]
Message-ID: <1315543390-12451-1-git-send-email-jamie.couture@gmail.com> (raw)
From: Jamie Couture <jamie.couture at gmail.com>
I reproduced the problem reported by Arun Persaud on his version, 9900ac022,
and on 756e3ea6. Based on the suggestions of others, here is a patch to help
avoid segfaults when calculating lcs when printing deferred changed lines.
Jamie Couture (1):
move LCS table away from the stack
cgit.h | 12 ++++++++++++
ui-ssdiff.c | 32 ++++++++++++++++++++++++++++++--
2 files changed, 42 insertions(+), 2 deletions(-)
--
1.7.6
next reply other threads:[~2011-09-09 4:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 4:43 jamie.couture [this message]
2011-09-09 4:43 ` [PATCH 1/1] move LCS table away from the stack jamie.couture
2011-09-11 0:44 ` jamie.couture
2011-09-11 0:44 ` [PATCH] " jamie.couture
2011-09-14 6:38 ` hjemli
2011-09-17 22:25 ` [PATCH 1/1] " jamie.couture
2012-01-03 15:12 ` hjemli
2012-01-04 8:59 ` normalperson
2012-01-04 16:57 ` jamie.couture
2012-01-12 3:38 ` jamie.couture
2012-01-12 3:38 ` [PATCH 1/2] correct length check for LCS table jamie.couture
2012-01-12 3:38 ` [PATCH 2/2] use correct type for sizeof jamie.couture
2012-03-18 9:22 ` hjemli
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=1315543390-12451-1-git-send-email-jamie.couture@gmail.com \
--to=cgit@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).