tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Kristaps Dzonsons <kristaps@bsd.lv>
Cc: tech@mdocml.bsd.lv
Subject: Re: More Valgrind Errors
Date: Mon, 18 Aug 2014 18:39:34 +0200	[thread overview]
Message-ID: <20140818163934.GF24456@iris.usta.de> (raw)
In-Reply-To: <53F1D3A0.7010400@bsd.lv>

Hi Kristaps,

Kristaps Dzonsons wrote on Mon, Aug 18, 2014 at 12:21:20PM +0200:

> Another mystery, still on HEAD.  (And in the many Mac OSX manuals,
> this is the end of what I found.)  Consider the following manual
> (reduced from groff.7 around line 404, where the leak was originally
> found):
> 
> .TH GROFF 7 "16 February 2005" "Groff Version 1.19.2"
> .SH NAME
> groff \- a short reference for the GNU roff language
> .SH DESCRIPTION
> .RS
> .P
> .RE
> hello, world
> 
> valgrind notes that the RS body is never freed ("indirectly lost",
> in its parlance).  In looking closely, the -Ttree output just isn't
> quite right (clipped for the screen):
> 
> root (root) 0:1
> 	SH (block) *2:2
> 		SH (block-head) 2:2
> 			NAME (text) 2:5
> 		SH (block-body) 2:2
> 			groff \- ... (text) *3:1
> 	SH (block) *4:2
> 		SH (block-head) 4:2
> 			DESCRIPTION (text) 4:5
> 		SH (block-body) 4:2
> 			RS (block) *5:2
> 				hello, world (text) *8:1
> 
> I'm afraid I don't have the time to dive into this right now--any
> ideas on this behaviour?

Fixed, in all branches, thanks!

> Meanwhile, I'm running through the manuals again and will then do
> the same with the 1.12 branch.

Good, i'm looking forward to the results

Yours,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

      reply	other threads:[~2014-08-18 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18  0:13 Valgrind Error Kristaps Dzonsons
2014-08-18  5:49 ` Ingo Schwarze
2014-08-18 10:21   ` More Valgrind Errors Kristaps Dzonsons
2014-08-18 16:39     ` Ingo Schwarze [this message]

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=20140818163934.GF24456@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=kristaps@bsd.lv \
    --cc=tech@mdocml.bsd.lv \
    /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).