Menu
▾
▴
#5168 Could not send interrupt signal to maxima error
build_info() or bug_report()
WxMaxima version: 26.01.0_MSW
Using wxWidgets version: wxWidgets 3.2.9
Maxima version: 5.49.0
Maxima build date: 2026-01-02 21:27:51
Host type: x86_64-w64-mingw32
System type: Win32 10.0.19041 X86-64
Lisp implementation type: SBCL
Lisp implementation version: 2.6.0
(kill(r1,r2,r12,f,ff,hs,es,es1,es2,f1,f2),depends([f,ff,hs],[r1,r2,r12]),
h12:expand((diff(hs,r1,2)+2/r1diff(hs,r1)+diff(hs,r2,2)+2/r2diff(hs,r2))/2+
diff(hs,r12,2)+2/r12diff(hs,r12)+(r1^2+r12^2-r2^2)diff(hs,r1,1,r12,1)
/2/r1/r12+(r2^2+r12^2-r1^2)diff(hs,r2,1,r12,1)/2/r2/r12),
es:exp(-q(r1+r2)+q12r12/2),
eq:expand(ev(subst(hs=fes,h12),diff,eval)/es+(q/r1+q/r2-q12/r12)f),
d0:expand(eq-c0f ),
kill(r),depends(f,[r[1],r[2],r[3]]), c0:subst([r1=r[1],r2=r[2],r12=r[3]],c0),
d0:subst([r1=r[1],r2=r[2],r12=r[3]],d0),
dn:subst([r1=r[1],r2=r[2],r12=r[3],hs=f],h12),
sum(d[i]:coeff(dn,diff(f,r[i],1,r[3],1))diff(f,r[i],1,r[3],1),i,1,2),
sum(do[i]:coeff(dn,diff(f,r[i]))diff(f,r[i])+coeff(dn,diff(f,r[i],2))diff(f,r[i],2),i,1,3),
coeff(d0,diff(f,r[1]))diff(f,r[1]));
first of all it should not have hung up at all. Second i do ctrl I and all it does is rewrite the expression.
Then i do alt m and choose interrupt and then get error signal
'could not send interrupt signal to maxima'
Now i found the culprit as to why it is hanging up is the
sum(do[i]:coeff(dn,diff(f,r[i]))diff(f,r[i])+coeff(dn,diff(f,r[i],2))diff(f,r[i],2),i,1,3)
expression but it also hangs when do it the long drawn out way as in
(for i thru 3 do do[i]:coeff(dn,diff(f,r[i]))diff(f,r[i])+coeff(dn,diff(f,r[i],2))diff(f,r[i],2))
and also get the 'Could send an interrupt signal to maxima.'
error
that is ofcourse for both of these assuming already did the first expression defining dn
The point is it should not hang up on either of these. Nor when one does ctrl I it should not
just rewrite the expression which is all it does. So anyway have to do alt M choose interrupt and
get the "Could not send an interrupt signal to maxima." error . So finally had to do alt M and
choose restart maxima. Part of it may be wxmaxima error but the hanging up when it should not
is bug in maxima i would think.
by the way it is fault of this interface of not showing multiplication signs . If go to
display2d: false
then that is just too long of output in this case or anyway as in
(display2d:false,disp([for i thru 3 do do[i]:coeff(dn,diff(f,r[i]))diff(f,r[i])+coeff(dn,diff(f,r[i],2))diff(f,r[i],2)]) )
just hangs up again and same errors etc. when choose interrupt
ok i try
suspecting it may have something to do with the key word do so i renamed it
di[i] and
Did work so it should NOT have hung and instead given parsing or syntax error and NOT
'Could not send an interrupt signal to maxima." error when try to interrupt when it should not
have been trying to calculate in the first place.
Please, use proper formatting for your code, the button is right there above the text field, looking like
</>.Otherwise, it's difficult for others to reproduce.
Dan Hayes, you have repeatedly been told how to format code in your reports.
To review, you can either use the
</>command at the top of the text window or you can preface a block of code with~~~and end it with~~~.We have also repeatedly asked you to make an effort to report a minimal example of the problem.
In this case, you seem to have figured out the problem yourself. Yes, in Maxima,
dois a reserved word and cannot be used as a name for a variable, array, function, etc.Closing this report as resolved.
If you can't be bothered to format your problem reports correctly, and can't be bothered to create a minimal example, why should we bother to help you? Next time, I'll just close a bad report.
putting
above and below does not format it properly as multiplication signs are still not shown unless you meant specifically - unless your wrote ~~~~~ or something like that rather than
just -----------------.
As i finally figured only if i check the </> code tab above does it format properly and then only under further
requirements. It is not resolved unless you say '....could not send interrupt...' signal error is ok. I would think not as it should have given parsing,syntax or do not use keywords error instead. Unless u say that is wxmaxima error instead. It is not always clear to the user when/if things are wxmaxima or maxima errors. Further as i have experienced there are instances where one can use keywords and it is still ok. And in fact only do by itself is a keyword NOT do[i], do(i) just like doi is
not a keyword though for example sin[i] ,sin(i) is a different matter. So it should not be classified as resolved even if it is wxmaxima error instead of not just because it is a poor because not minimal example or not properly formatted bug report. NOt in every instance can the general public
figure out what is a minimal example in every case in a reasonably minimal time though this
one may have been considered able to figure out in a reasonable amount of time.
Your messages are extremely difficult to read and understand. They lack structure, punctuation, etc. With today's available tools, there is hardly an excuse for this other than not caring. If you don't care, why should we?