low-level

This question already has an answer here: Building an assembler 4 answers How Do You Make An Assembler? [closed] 4 answers I've recently been trying to immerse myself in the world of assembly programming with the eventual goal of creating my own programming language. I want my first real project to be a simple assembler written in C that will be able to assemble a very small portion of the x86 machine language and create a Windows executable. No macros, no linkers. Just assembly. On paper, it seems simple enough. Assembly code comes in, machine code comes out. But as soon as I thinking about

This might be a duplicate question. I wish to know how the memory map of a windows process look like? I am looking for details. Kindly provide links to blogs, articles and other relevant literature. I always like to actually be able to see things, rather than just read theory. It turns out, according to this blog post , that if you open a program using windbg even when it isn't running it still gets mapped to an address space as if it were. Thus, your disassembly window figuratively (not guaranteed to load your code at these exact addresses) shows you what is at those addresses in terms of

Is there a way to manually set low-level still-camera settings like shutter speed, aperture, or ISO in iOS4 on the iPhone 4? I don't think it exists in the official SDK but perhaps someone has found some private APIs to allow this? I find my iPhone 4 camera to be unusable because even in fairly decent lighting, it always insists on shooting at the slowest 1/15th a second shutter speed causing motion blur if the subject is moving at all. Thanks! Not directly. Please file a bug report. Yes, there may be private APIs available, but that's of limited use. anshika Try this, I could be useful for

So this morning I posted a confused question about assembly and I received some great genuine help, which I really appreciate. And now I'm starting to get into assembly and am beginning to understand how it works. Things I feel I understand alright include the stack, interrupts, binary/hex, and in general what most of the basic operations do (jmp, push, mov, etc). Concepts that I'm struggling to understand and would like help with are below - it would be a huge help if you could address any of the following: What exactly is happening in the .data section? Are those variables we're declaring?

I'm not exactly sure how to tag this question or how to write the title, so if anyone has a better idea, please edit it Here's the deal: Some time ago I had written a little but cruicial part of a computing olympiad management system . The system's job is to get submissions from participants (code files), compile them, run them against predefined test cases, and return results. Plus all the rest of the stuff you can imagine it should do. The part I had written was called Limiter . It was a little program whose job was to take another program and run it in a controlled environment. Controlled

I want to get a file name from a user via stdin, open the file with open() and assign it to a file descriptor, then print the contents of that file to stdout. This is my code, and it's not working properly. Problems: the printf("enter filename"); statement is never showing up it never opens the file; instead whatever the user inputs is printed to the screen and then the "no such file or directory" error message is printed and the program exits after the program exists i see "enter filename" printed before the prompt in terminal CODE: { printf("Enter the filename: "); read(STDIN_FILENO,

How can I find the text segment (AKA code segment) range in iOS? Meaning, what is the start address and the end address of the text segment? I found this interesting post but it works for me on Android but not on iOS. After some digging and expert help (thanks Moshe Kravchik) I got to the desired solution - getting the text segment range by parsing the mach header and retrieving the load commands, segments and sections. #include <mach-o/dyld.h> #include <stdio.h> #include <stdlib.h> #include <string.h> #include <dlfcn.h> #import <Foundation/Foundation.h> #define PRINT_STR "Found __text Section