debugging

问题 My program(assembly tasm 16bit) supposed to print a bar graph represtion for an array.Right now its only supports specificarray but I will add support for general cases in the future.The code works fine in debugger and prints the bars as expcted.But in run the code gets stuck and dosent print anything. All the functions apart from PrintArr were working separately as expcted. I cant find my problam in debugging beacouse the problame dosent seem to exist in the debugger. ; IDEAL MODEL small

问题 Consider the following simple program: var dblMax = Double.MaxValue; var result = (dblMax * 1000) / 1800; Console.WriteLine(result); When I build this in Debug mode and run (Ctrl+F5) or debug (F5) it, it prints 9.987140856842E+307 . When I switch to Release mode and run (Ctrl+F5) it, it prints 8 for infinity. I understand that this difference is due to some compiler optimization which is done in Release mode. However, if I debug (F5) the same build in Release mode, it prints 9.987140856842E

问题 Reposting with full code, as suggested from others. Just updated the main function with hard coded arguments that causes segmentation fault. Changing the width and height to something else lets the program run fine, for example 500 and 433 respectively. Main file: #include <cstdint> #include <iostream> #include <sstream> #include <vector> #include <cmath> #include "sierpinski.h" Triangle::Triangle() { this->pixels = nullptr; this->top = Coordinate(); this->left = Coordinate(); this->right =

问题 I have a process that handles exceptions great. It calls: _set_se_translator(exception_trans_func); SetUnhandledExceptionFilter(UnhandledExceptionFilterHandler); _set_purecall_handler(purecallHandler); set_terminate(terminateHandler); set_unexpected(unexpectedHandler); _set_invalid_parameter_handler(InvalidParameterHandler); atexit(exitHandler); //ignored during an expected exit _onexit(onexitHandler); //ignored during an expected exit Anytime an exception happens, one of the handlers is

问题 I want to fetch debug information of an ldap connection in a PHP script (Windows Environment). To activate the debug output you have to use ldap_set_option calling ldap_connect: ldap_set_option(NULL, LDAP_OPT_DEBUG_LEVEL, 7); And it is necessary to run the from command line. Otherwise you wont get the debug output. In a reqeust this debug output is not shown. <?php // Set the ldap server $ldapurl = "foo.bar"; // Set debugging ldap_set_option(NULL, LDAP_OPT_DEBUG_LEVEL, 7); // connect to ldap

问题 I have this C++ project I am trying to debug in Visual Studio (Community) 2015. The build is always successful, but after that debugging never starts. All that shows up is the Windows loading icon, which just never goes away. Any ideas about what might be wrong? 回答1: The problem was that Avast was interfering with my Visual Studio Projects. I used the instructions at https://forum.avast.com/index.php?topic=139935.0 to get it to work. Basically you need to exclude your VS projects from Avast's

问题 I've just finished debugging an issue where an iOS Google Map ( GMSMapView ) showed on some devices and in some iOS version simulators, but not others. It was odd that it broke on a 32-bit iOS 7 device and 64-bit iOS 7 simulator, but not other combinations, indicating it wasn't an iOS version specific or 64-bit specific, but something else. Anyway, the fact that it was a GMSMapView and had strange variation in behaviour across devices/simulators may be an aside, but perhaps it's related to

问题 I'm sorry if i eventually do something wrong. Ok my problem is the following: I just coded something very easy, but when you take a look at the Valgrind error output it just confuses me. Code: #include <stdio.h> #include <stdlib.h> int main(int argc, char *argv[]) { int num1 = 100; double num2 = 1.2; printf("Number 1 one is: %d.\n Number two is: %f.\n", num1, num2); return 0; } Valgrind error report: $ valgrind --leak-check=full ./yaq ==50642== Memcheck, a memory error detector ==50642==

问题 Quick question on LINQ to SQL generated queries output. I am in a ASP.NET MVC project, Visual Studio 2008, and I am trying what's suggested in MSDN documentation: MyDataContext _dc = new MyDataContext(); _dc.Log = Console.Out; But nothing is being shown on "Output" window (CTRL+Alt+O). Is there is something else I need to configure in order to make LINQ to SQL dumping debug info to Output window in Visual Studio 2008? I don't know if it makes any difference, but my entities (and MyDataContext

问题 For testing purposes I'm planning to put together a little app that will listen for a particular event coming from an application and interact with it at that point. Given that we're at a point in the testing process where changing the application code is out of the question, the ideal from my point of view would be to listen to the debugging trace from the application, a little like debugview does, and respond to that. Can anyone offer guidance on how best to go about this? 回答1: The way I