From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.auc.dk
Subject: Re: Wordcode functions with empty bodies
Date: Wed, 14 Jun 2000 14:23:03 +0000 [thread overview]
Message-ID: <1000614142304.ZM15832@candle.brasslantern.com> (raw)
In-Reply-To: <200006140614.IAA01313@beta.informatik.hu-berlin.de>
On Jun 14, 8:14am, Sven Wischnowsky wrote:
} Subject: Re: Wordcode functions with empty bodies
}
} I had a little debugging session yesterday evening... I could
} reproduce the segv with the `prompt' thing (although I had to invoke
} `prompt bart' a second time with some other command before it to make
} it go kaboom).
}
} I could not, however, see any problems with bld_eprog(). In which way
} do you think it produces garbled eprogs? (I mean, what do those eprogs
} look like?)
They have a `len' of 4 and a `strs' that points to four bytes of garbage.
The crashes appear to happen after dupeprog() copies `strs' -- the new
copy often ends up pointing to a different four bytes of garbage.
In the prompt stuff, as long as I never let the function body be empty --
that is, I replace e.g.
functions[TRAPWINCH]="${functions[TRAPWINCH]//prompt_bart_winch}"
with
functions[TRAPWINCH]="${functions[TRAPWINCH]//prompt_bart_winch/:}"
the crashes never happen. Only if the function body becomes empty do I
have any problem.
} Ok. If you could give me an easy example of how to make bld_eprog()
} give garbled results, I'd be thankful. Just doing `functions[foo]=""'
} at least gives me sensible results.
Try `functions[foo]=" "' so there is a non-empty string there but it
contains no useful tokens.
I'll try to do some more debugging this morning and send some gdb output.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-06-14 14:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-14 6:14 Sven Wischnowsky
2000-06-14 12:20 ` Peter Stephenson
2000-06-14 14:03 ` Peter Stephenson
2000-06-14 14:23 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-15 8:12 Sven Wischnowsky
2000-06-14 14:36 Sven Wischnowsky
2000-06-14 14:28 Sven Wischnowsky
2000-06-14 15:08 ` Peter Stephenson
2000-06-14 15:17 ` Peter Stephenson
2000-06-14 16:17 ` Bart Schaefer
2000-06-14 21:55 ` Peter Stephenson
2000-06-13 16:31 Bart Schaefer
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=1000614142304.ZM15832@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/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.vuxu.org/mirror/zsh/
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).