Can anybody tell me what exactly the following segmentation fault means?
Unhandled dwarf expression opcode 0x93
Its on solaris 10 i386.
Any advice appreciated.
This sort of error message ("unhandled dwarf expression") can occur if your version of GDB is too old (older than the compiler that generated the code). Try installing the latest version of gdb and running that.
This may not immediately help, but "dwarf" probably refers to the DWARF Debugging Standard.
The wikipedia entry for DWARF indicates that the file format contains "byte-coded instructions for simple, special-purpose finite state machines". This may mean that you have a corrupted debug info file of some kind, but without more information I wouldn't be able to guess further.
Related
I've crosscompiled qt using qtcreator. Debug works good, but when I try to step in (F11) a function defined in an external shared library (of mine), I see gdb hanging and finally fail with the following error:
115^error,msg="Reply contains invalid hex digit 116" COOKIE FOR TOKEN 115 ALREADY EATEN (InferiorStopOk). TWO RESPONSES FOR ONE COMMAND? Executable failed: Reply contains invalid hex digit 116
Any Ideas?
It could be:
A general gdb bug unrelated to the communications protocol,
A gdb bug in its gdb communications protocol implementation,
A Qt Creator bug in the gdb communications protocol implementation.
Since it is a bug in any case, you're after good information to put into the bug report. Examine Qt Creator's debugger log to see exactly when it happens. You can then try to reproduce the same command stream manually, from gdb's command line. If you succeed, then #1 is unlikely. You could use another IDE (say Eclipse) to differentiate between #2 and #3, but remember that the other IDE is unlikely to issue the same commands that Qt Creator would issue.
The only sure way of debugging it is interposing a small program between Qt Creator and gdb, dumping the commands that Qt creator has sent, then replaying them without Qt Creator. You then need to parse the responses and ascertain whether they are valid. If they are, then neither #1 nor #2 holds and it's very likely a Qt Creator bug, #3.
The 'error,msg=' is generated by GDB in response to a GDBserver message. Qt Creator's communication with GDB is not involved. So this is a mis-communication between GDB and GDBserver.
Is that a proper GDBserver, and a GDB for that target architecture?
Btw, one does not need a program to intercept what Qt Creator send to GDB, it's all listed in the left pane of the debugger log.
I've found that the problem is related to the use of "step-in" (F11) function.
Inexplicably, you can avoid this message toggling a breakpoint in the library and simply using play function (F5), in order to debug your library.
Thanks anyway for your response. I've done a lot of tests before focusing the real problem.
It has been answered before, but i don't know the way to find the exact solution. I took whole day to find the solution but i entirely stuck with this.
I was worked with my project nicely on day before yesterday. I designed many modules for doing my project further. AS usual i opened and started doing (I didn't get any errors) my project today in visual studio. To execute my old project(coding) once again, i checked in browser, as soon as i did, my face gone too bad :( because of this strange error. Error is,
Compilation Error
Description : An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
*Compiler Error Message:*CS0009: Metadata file 'c:\Windows\Microsoft.NET\assembly\GAC_32\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll' could not be opened -- 'Error importing module 'System.EnterpriseServices.Wrapper.dll' of assembly 'c:\Windows\Microsoft.NET\assembly\GAC_32\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll' -- An attempt was made to load a program with an incorrect format. '
Source Error:
[No relevant source lines]
I did deleting temporary files in this area : C:\Users\username\AppData\Local\Temp\Temporary ASP.NET Files. But again I'm getting the root folder when am running the project
Any help, would be more and more helpful to me. Thanks in advance.
The error message
An attempt was made to load a program with an incorrect format
means that there is an incompatibility in processor architecture. I think you installed either the 32- or 64-bit version of .NET and try to run your website in the opposite architecture.
You should install both the .NET framework versions, or change your application pool to use the right processor architecture.
The linker for an iOS simulator target I have is reporting the following warning:
ld: warning: too many personality routines for compact unwind to encode
No line number is given, nor anything else that is actionable. Googling turned up some Apple open source code, but I'm not groking it.
What does it mean and what can I do to address it?
I found some information in the C++ ABI for Itanium docs that sheds some light on what this means.
The personality routine is the function in the C++ (or other language) runtime library which serves as an interface between the system unwind library and language-specific exception handling semantics.
Extrapolating, this warning indicates that you've got too many kinds of exception handling in the same binary, and at least one of them may fail. Indeed this is exactly what is observed in this question.
Sadly, there's no clear way to fix this, only workarounds. You can suppress the warning, remove code, rewrite code in a different language, disable a language's exception handing and possibly others.
If you have a crash on exception with this warning, i.e. ::terminate() call on every throw, the workaround is to use old dwarf exception-handling tables. Add following flags to Build Settings/Linking/Other Linker Flags:
-Wl,-keep_dwarf_unwind -Wl,-no_compact_unwind
You can try silencing the warning with -Wl,-no_compact_unwind for the Other Linker Flags setting. I think it's harmless.
I bumped into this issue as well when trying to run on the iOS simulator while my code was running correctly on the device. In my case, it was not a warning but a linker error.
Luckily, i remembered that I added two flags for luajit to run correctly following the instructions of this page under the section Embedding LuaJIT:
-pagezero_size 10000 -image_base 100000000
My guess is that the image_base address is simply out of bounds on the host CPU.
Anyway, removing these settings made it work in my configuration.
So go to your project's settings and look for any hard wired values of this kind if not the same.
Hope this helps,
M
I'm writing plugin for the MITK framework using Qt-Creator with gdb on Linux-Mint 15.
Resuming after halting at any breakpoint doesn't work, or seems to take upwards of 30 minutes (every time). My project is not very big however, so there's no way I've got the debugger set up correctly.
I've got the Qt 4.8 and 5.01 packages installed. MITK requires Qt4 and I believe to have it specified everywhere in the makefiles.
I do get the following output when starting to debug:
&"warning: GDB: Failed to set controlling terminal: Unpassender IOCTL (I/O-Control) f\303\274r das Ger\303\244t\n"
no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff7ffa000
From other answers on this site I get that the first line can be ignored...
Can anyone say if the second line is related to my problem and possibly how?
I wonder if this could have to do with there being two versions of Qt installed on my pc - I dont know how to get Qt5 completely off the system with all its packages though...
One user mentioned this: https://stackoverflow.com/a/17256365/2561709
Its all I could really find but I dont understand it, any clues?
I'd appreciate any hint at a possible cause of the problem. Please tell me what other relevant information I could provide, thanks!
I'm trying to simulate my VHDL code using Xilinx ISim.
When I try to generate the testbench for the simulation, the simulator throws up the following error:
FATAL_ERROR:Simulator:Fuse.cpp:500:1.133 - Failed to compile generated C file isim/
I tried to simulate it on an 32-bit Ubuntu 12.04 using ISE 14.3, a 32-bit Windows XP SP3 also ISE 14.3 and a 64-bit Windows 7 SP1 same ISE version as before.
The Xilinx support provided a reinstall as solution, but that didn't solve the problem.
Maybe the community on Stack Overflow has an idea?
That is a tool crash and it's going to be hard to get an answer here on stackoverflow, at least without providing some code and the steps that cause the problem. I would get back with Xilinx support and open a case -- this is something they need to fix in the tool. Can you provide your code as a testcase to them? Potentially cutting it down so it's as simple as possible while still causing the problem.
I can never provide production code to EDA vendors as a testcase due to confidentiality. Quite often I find that while creating a smaller testcase that I can send that I'm able to also find a workaround to the original problem. Try a binary search procedure -- remove or black box half of your design and see if the crash still happens.
And -- can you find the particular C file that fails to compile? Looking at it may give a clue as to what in your design may be causing the problem.