I am trying to do remote debugging on HPUX using WDB but am not really getting anywhere.
Any ideas or links to decent tutorials?
HP WDB documentation
Related
we want to write a VSCode debug extension for remote debugging PL/I source code on the mainframe.
We use IBM's z/OS Explorer, but we don't want to start this heavy Eclipse bundle for debugging (everything else is done in this VSCode extension).
We "wiresharked" the communication with IBM's z/OS Explorer, so it would be no problem to send and receive tcp packages according what the debugger (running on the mainframe) needs.
But we don't understand how debugging could work in a VSCode extension.
Now it is working as following:
Write a dataset on the mainframe
Submit a job with the program you want to debug
When the z/OS Explorer is started, debugging is starting.
What is needed to
1.) init vscode debugging functions
2.) send start command via tcp
3.) receive and display the information via tcp
4.) start, stop and breakpoint functionalities
Any examples etc. would be helpful, thank you!
The only way you will be able to do this is with WAZi developer. You MUST have the IBM Debugger installed on the z/OS, and that is a licensable program. Yes, you could write a debugger on your own, but the cost/benefit grossly exceeds the price of IBM's licenses.
Here's the details on debugging with WAZi
https://www.ibm.com/docs/en/developer-for-zos/15.0.0?topic=code-debugging-applications
I'm fresh man in software engineering and I've been working on an MFC Application on Windows 7.
I have a problem with a DLL. When I run this application, this error sometimes occurs:
There was a problem starting C:\Windows\system32\WerConCpl.dll
What is this DLL and what is this DLL used for?
Any answer or clue will be appreciated. Thank you!
A quick Google with that DLL filename leads me to here. The accepted answer states:
werconcpl.dll will access Internet because it is looking for solutions to submitted crash reports.
This file is a Microsoft Windows system file.
I have a project for Xilinx Zynq (Cortex A9). I want to be able to step-by-step debug the application in KDevelop. I know that xilinx has XSCT but I don't understand how can I get KDevelop to work in step-by-step code debugging mode for my processor?
I can advise you to learn how to do this from the terminal first and deal with the work of gdb-server. And also get a suitable make/cmake file.
How can I debug an omnet++ project like as a bmac or Imac.
My omnet++ is Version: 4.6 I want to debug an bmac project. Do I need to change any configuration of my simulator?
I will be thank full to have the solution.
Your question is somewhat broad. If, by debugging a simulation you mean running your simulation in a debugger like gdb, see this other answer.
For general tips on debugging in the sense of finding errors, you might find this article on the OMNeT++ wiki helpful.
i've been trying for a whole day to use Eclipse but i failed every time.
I know that i may be wrong and i do know that there are a lot of people out there who are working hard for an open source project, but if i can't use a program, run and debug an "Hello world" file, there must be something wrong.
I'm using OSX 10.9.5 (yeah, maybe using a mac is my first error, right?).
Every time i try to debug the "Hello World.cpp" program i get the following error.
http://imgur.com/RgXCSyW
Yes, i've searched everywhere on google.
Yes, i've already seen the other replies on a similar topic and i've already tried the solutions they offered. Sadly, it didn't work.
Thanks guys for your patience, i hope to learn how to code and maybe being helpful to others one day.
Luca
p.s. writing the error so other people who are googling it can find it
"
Error in final launch sequence
Failed to execute MI command:
-exec-run
Error message from debugger back end:
Unable to find Mach task port for process-id 33383: (os/kern) failure (0x5).\n (please check gdb is codesigned - see taskgated(8))
Unable to find Mach task port for process-id 33383: (os/kern) failure (0x5).\n (please check gdb is codesigned - see taskgated(8))
"
There is another option to debug you code using LLDB debugger.
You can check this link for install the LLDB debugger integration.
It is super easy and does the work.
Btw The GDB debugger is part of GNU. Xcode does not use GNU tools (gcc, gdb) anymore. Xcode uses LLVM. LLVM's debugger is LLDB.
Some info about it:
apple developers,
The LLDB Debugger
Probably your problem has been solved, but sharing another solution to others cant be bad :)
This is relevant to macOS Sierra also.
This is a relatively well known "issue" on OS X (which btw is a pain-in-the-neck-to-develop-c++ on). You first need to install g++ and GDB debugger (since LLVM clang++ in combination with LLVM debugger are not yet supported by Eclipse on OS X). The easiest way is via macports. First install macports via the native installer, then, from a terminal, install g++ and gdb (debugger)
sudo port install gcc5 # or gcc49
and
sudo port install gdb
After this, you need to codesign it, see this link. The name of the debugger will be ggdb (not gdb), and macoprts will install it in /opt/local/bin/ggdb.