I'm just playing around with expect and dejagnu for the first time, so
forgive me if i get this wrong. I'm running a mostly-etch system
right now, trying to rebuild GNU mailutils, and make check chokes up
seriously due to attempted SIGSEGV trapping. Applying Matthias
Klose's patch lets me get on with the rest of the the test suite.
Background:
It appears to me that expect version 5.42.1-2 closed bug #157902 by
patching expect to disallow trapping SIGSEGV. [0]
This change makes this bug (#301557: ("Dejagnu asks expect to trap
SEGFAULTS") more urgent than ever because i now get failures referring
to this issue just launching runtest even with no arguments:
[0 [EMAIL PROTECTED] ~]$ runtest
WARNING: No tool specified
Test Run By dkg on Mon Jul 24 21:48:15 2006
Native configuration is i686-pc-linux-gnu
=== tests ===
cannot trap SIGSEGV
while executing
"trap "send_error \"got a \[trap -name\] signal, $str \\n\"; log_and_exit;"
$signal"
("foreach" body line 4)
invoked from within
"foreach sig "{SIGTERM {terminated}} {SIGINT {interrupted by user}} {SIGQUIT
{interrupted by user}} {SIGSEGV {segmentation violation}}" {
set sign..."
invoked from within
"if ![exp_debug] {
foreach sig "{SIGTERM {terminated}} \
{SIGINT {interrupted by user}} \
{SIGQUIT {interrupted by user}..."
(file "/usr/share/dejagnu/runtest.exp" line 1503)
[1 [EMAIL PROTECTED] ~]$ dpkg -l expect dejagnu
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii dejagnu 1.4.4-1 framework for running test suites on softwar
ii expect 5.43.0-6 A program that can automate interactive appl
[0 [EMAIL PROTECTED] ~]$
Given this combination, i'm not sure how packages which rely on these
elements of the toolchain actually get built!
On a relatively clean sarge system, executing runtest with no
arguments at least gets to the point of identifying that no tests are
available (farther into /usr/share/dejagnu/runtest.exp than the etch
versions get, i think).
Note that bug #157903 is essentially the same as #301557 (this bug),
but over 2 years older. Can we get feedback on why these two bugs are
still open (or close them wontfix if some other resolution should be
taken)? Should the bugs at least be merged?
Thanks for maintaining these tools!
Regards,
--dkg
[0] http://packages.qa.debian.org/e/expect/news/20060121T043206Z.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
