Error log for Octave "panic: Illegal instruction -- stopping myself" - octave

Is there an error log where I can figure out the error message and line of code in my file which makes the Octave interpreter post the following messages in Emacs?
panic: Illegal instruction -- stopping myself...
panic: attempted clean up apparently failed -- aborting...
Process Inferior Octave aborted (core dumped)

You must use the Octave debugger (take a look at the Debugging section of the Octave manual).
If this was an error message, you could activate debug_on_error. Since it is not, it's a proper crash, you must start on debug mode (enter the keyboard command) and step line by line (enter the command dbstep) until you find which one causes the issue.

Related

Can't terminate TCL script using exit command as it is not being identified

Here is the error message:
May 10, 2021 4:01:35 PM com.altera.debug.core
SEVERE: java.lang.Exception: invalid command name "exit"
while executing
"exit
"
invoked from within
"if {$use_specified_base_addresses == 1} {
puts "using predefined peripheral base addresses"
# Peripheral address offset from taken from ..."
It is strange that the keyword "exit" is not being identified by the interpreter I am using. I just need to stop running the script when "catch" actually catches error raised by a procedure call. I am getting this problem in Quartus Prime Standard System Console.
The exit command is a standard Tcl command, but it looks like it has been removed from the interpreter, presumably because it is being run in an environment which wants to keep on running. (Tcl definitely supports defining interpreters with restricted command sets.) You'll have to check the application documentation on what to use instead.
Poking around in what Google digs up, the qexit command (if defined) might work instead. It's apparently called like this:
qexit -error
I've no idea why they don't follow the standard exit protocol.

An unexpected error happened during phase Publishing of job

I am trying to use the ForgeApp with Revit. For the same I am trying to execute the workitem from Postman. During the execution I am getting below error.
An unexpected error happened during phase Publishing of job.
The parts of the actual report (after removing some of the sensitive info) is as follows:
[10/15/2020 05:45:24] Finished running. Process will return: Success
[10/15/2020 05:45:24] ====== Revit finished running: revitcoreconsole ======
[10/15/2020 05:45:25] End Revit Core Engine standard output dump.
[10/15/2020 05:45:25] End script phase.
[10/15/2020 05:45:25] Start upload phase.
[10/15/2020 05:45:25] Error: Non-optional output [result.json] is missing.
[10/15/2020 05:45:25] Error: An unexpected error happened during phase Publishing of job.
[10/15/2020 05:45:25] Job finished with result FailedMissingOutput
[10/15/2020 05:45:25] Job Status:
From the error it is clear that the Plugin has failed in processing but it gives give much idea as to why it has failed . After receiving this error, I tried to debug locally by following https://forge.autodesk.com/blog/design-automation-debug-revit-plugin-locally
But during debugging it is failing with below error while Executing the Plugin itself. It executes the Onstartup without any issues but after that it is not going in HandleDesignAutomationReadyEvent.
Managed Debugging Assistant 'FatalExecutionEngineError' : 'The runtime has encountered a fatal error. The address of the error was at 0xdb9b8a8d, on thread 0x3784*
So I am not sure what to ahead to resolve this. If I can get this working somehow in the Local with Debugger or through Postman then it would help.
Further update - I have now found the root cause. Even though it was complaining about the missing output file leading me to believe the code was not running properly, the actual root cause was that it was not finding the model from the inputFile parameter. This became clear once I tried putting Console.Write in the Plugin code and then debugging became easy. I wasn't sure Console would be printed in the output at first and hence turned the debug logs off at first . But as I didn't have any other means to have the verbose logging , I put in lots of Console write and now got to know the root cause. Thanks

popen2("unix") not working in octave

I'm trying to get octave to execute a 2-way sub-process, in order to communicate with the shell 'online', while processing data acquired from the shell.
the normal popen is not good for me because it waits for the sub-process to return before i'm able to process the data.
So I tried all kinds of ways, and I've read the octave example for using popen2("sort"), but it didn't help me to get popen2("unix") working.
The error I get is:
error: popen2: popen2 (child): unable to start process -- No such file or directory*
I get this error for other popen2 commands such as popen2("help"). Maybe I'm missing something out.
The error message
error: popen2: popen2 (child): unable to start process -- No such file or directory*
tries to tell you, that there is no command or program "unix". Which OS are you using and why are you expecting that there is a command "unix" available? Btw, have you had a look at system?
If you really want a two way communication with a shell try
[in, out, pid] = popen2 ("bash");

Error while printing in octave

When i am trying to print variables or even for 'help < topic >' commands, I am getting this error in octave.
octave-3.6.4.exe:66> help minimize
0 [main] us 0 init_cheap: VirtualAlloc pointer is null, Win32 error 487
AllocationBase 0x0, BaseAddress 0x60E90000, RegionSize 0x170000, State 0x10000
C:\Software\Octave-3.6.4\bin\less.exe: *** Couldn't reserve space for cygwin's heap, Win32 error 0
I am not sure what is causing this error. I removed cygwin from my windows registry. Is that the reason? In any case, how to get rid of this error?
I had the exact same problem. Just uninstall Octave, then reboot, then reinstall it. This did the trick for me.

MySQL restart causes double free or corruption using MySQL C API

I have a c program that maintains a persistent MySQL connection, version 5.1.46. If I restart mysql while the program is running I get a double free or corruption error as such:
# /etc/init.d/mysql restart
Shutting down MySQL........ [ OK ]
Starting MySQL.*** glibc detected *** /home/user/a.out: double free or corruption (!prev): 0x000000000b64dd00 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3739471634]
I am expecting the connection to automatically reconnect since I have set the MYSQL_OPT_RECONNECT option and have not explicitly closed this connection yet. In addition, the query I am executing is not a char* that I have accidentally set to NULL or deallocated, it is a constant, double quoted string.
Here are a few lines from the resulting core file in gdb
#11 0x000000000044ed71 in mysql_send_query (mysql=0x41966aa0, query=0x41966100 "SELECT count (*) from TableA", length=27) at client.c:2894
#12 0x000000000044edd9 in mysql_real_query (mysql=0x602a, query=0x602d <Address 0x602d out of bounds>, length=6) at client.c:2905
#13 0x000000000042b42f in do_query (conn=0x41966aa0, msg=0x41966100 "SELECT count(*) from TableA") at dosql.cpp:20
Any ideas why this might be occurring?
Any ideas why this might be occurring?
Because of a bug in MySQL.
You can try to update to later package, and see if the problem disappears.
Alternatively, run your client program under Valgrind, and it will report the bug in a way that is usable for fixing it. In particular, it will report
stack trace where the memory was allocated
stack trace where it has been freed
stack trace where double-free is happening (should be same as your GDB stack trace)
Given that info, you could report the bug to MySQL developers, and hope it will eventually be fixed.