|
From: | Michael D Godfrey |
Subject: | Current tip hang on bad syntax |
Date: | Thu, 25 Mar 2010 23:39:08 -0700 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3 |
I accidentally did: octave chirpm1 =============== where the file chirpm1.m contained: % chirp defn: x(t) = sin(2\pi \int_0^t f(t')dt') = sin(2\pi(f_0 + (k/2)t)t) ============================ The result was: octave:1> chirp1 parse error near line 3 of file /home/godfrey/mdg/reps/noise_and_info/chirp1.m syntax error >>> x(t) = sin(2\pi \int_0^t f(t')dt') = sin(2\pi(f_0 + (k/2)t)t) ^ parse error near line 3 of file /home/godfrey/mdg/reps/noise_and_info/chirp1.m syntax error >>> x(t) = sin(2\pi \int_0^t f(t')dt') = sin(2\pi(f_0 + (k/2)t)t) ^ ^C^CPress Control-C again to abort. ^Cpanic: Interrupt -- stopping myself... ^C^C^C ^C^C^C^C^C^C^C ============================ The only way to kill octave was with kill -9 from another window. Running under gdb shows a loop (after seg fault) like: (after SIGSEGV message) bt command dumps trace, which drops into loop: #1040 0x00007ffff75901f0 in feval (name="unimplemented", args=..., nargout=0) at oct-parse.yy:4038 #1041 0x00007ffff766738d in maybe_missing_function_hook (name=Traceback (most recent call last): File "/usr/lib64/../share/gdb/python/libstdcxx/v6/printers.py", line 467, in to_string header = ptr.cast(reptype) - 1 RuntimeError: Cannot access memory at address 0x1000 ) at variables.cc:2397 #1042 0x00007ffff75901f0 in feval (name="unimplemented", args=..., nargout=0) at oct-parse.yy:4038 ============================ But, under gdb it did not print anything before SIGSEGV message. I do not know where to start to diagnose this. The text which octave read is really TeX, but this should not lead to a dead hang. Michael |
[Prev in Thread] | Current Thread | [Next in Thread] |