Home
Search results “Gcc most used options” for the 2009
C Programming, Disassembly, Debugging, Linux, GDB
 
09:56
A brief introduction to GDB and Assembly Language on Intel processors using the venerable C language and GCC compiler toolchain. This is probably more fun than it is informative (and not even all that fun), but maybe it will give somebody ideas... Documentation: man wprintf man gdb man objdump man hexdump Use pinfo -m instead of man for a nice, colorful interface that can be navigated by clicking or using the arrow keys. The IDE used in this video is actually the SciTE text editor. http://www.youtube.com/watch?v=OWYdVmULKW0&feature=related Making simple programs and analysing them with a debugger such as GDB is a great way to learn a little bit about assembly language and machine code. Why delve into machine code during an introductory video? Do we realy need to know that the stack grows downward in memory or that the arguments to a function are pushed onto the stack in reverse order, so they can pop back off in the right order? What's with the wide characters? Why complicate things by adding a function? First of all, functions and assembly are not that hard to grasp. It's just a push and call. We push an address to something onto the stack and call a function. What's so difficult about that? I'm sick of people trying to insulate us from the details. Besides, knowing a little bit about what goes on under the hood makes better hackers and better programmers. That's what we do while learning. We build things and we take them apart to see how they work. I know there is no compelling reason to use wide characters (C90 spec), but I just want to be prepared to understand them when I see them. Yes, it is probably better to use utf-8 and char now that most platforms support it. You can find simple "hello world" programs anywhere that use printf. I wanted my video to be different. And I wanted to let everyone know I'm OK. I haven't died. I've just been busy learning a little C. Oh, and I'll show you why I used a function in a little bit. There is a reason. We have used up nearly the full 10 minutes and it is still just a brief tour. We were only able to cover a small handful of the tools I wanted to demonstrate. Oh well, Linux is so full of toys that it even has a tool to help find them. Type "man apropos" or "pinfo -m apropos" in a terminal for details. Yes, GDB sucks at printing wide character strings, as this video shamelessly points out. It can do it if you include debugging symbols in your program, though, by compiling with gcc -g -o hi hi.c and by downloading a special script for GDB (http://www.linux.com/feature/51836) and putting it in your .gdbrc file. Great. Wide characters of type wchar_t are not necessarily unicode, but, depending on the implementation, do often represent unicode strings. See: http://en.wikipedia.org/wiki/Wide_character http://www.cl.cam.ac.uk/~mgk25/unicode.html#utf-8 Resources: http://cs.baylor.edu/~donahoo/tools/gdb/tutorial.html http://www.iso-9899.info/wiki/Main_Page http://www.cs.princeton.edu/~benjasik/gdb/gdbtut.html http://en.wikibooks.org/wiki/Category:X86_Disassembly http://en.wikipedia.org/wiki/X86_calling_conventions#cdecl http://www.linux.com/feature/51836 This video contains parts or visuals of a free software program. You may use it freely according to its particular license: This work is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This work is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
Views: 106256 Executive Quest
Debugging in Code::Blocks
 
00:46
This video explains how to use Code::Blocks debugger to inspect variables defined in the scope of any specified breakpoint (which is usually the most useful thing to do using a debugger). I used GCC for Win32 (and GDB as the debugger).
Views: 64791 Roman Zeyde
Working with FlexiSIGN Pro 8.1
 
03:26
Creating multi-color outlines using FlexiSIGN Pro 8.1 This is a video response but I will create more of these if I have any requests. Just let me know what you are having problems with.
Views: 71851 101Osprey101
Google I/O 2009 - How Do I Code Thee? Let Me Count the Ways
 
59:27
Google I/O 2009 - How Do I Code Thee? Let Me Count the Ways Dan Morrill The primary way to develop apps for Android is using managed code that runs in the Dalvik virtual machine. Yet, Android also includes a super-modern Browser that includes Gears. It's even possible to build parts of your apps in native code (that is, C.) Choice is good, but it does mean one more decision for the developer to make -- and in this case, a big decision. Should you write your app in managed code, to integrate cleanly and seamlessly with the system? Should you write your app in the Browser as "Ajax plus", so that it can run on multiple phone platforms? Or should you go for raw speed, and write part of it in ARM-processor native code? There's no universal answer to these questions, but in this session Dan Morrill will teach you to pick the technique that works best for your app. In this session, you'll get a demonstration of each technique, and learn how to apply them to your own apps. For presentation slides and all I/O sessions, please go to: code.google.com/events/io/sessions.html
Views: 148778 Google Developers
Toyota Landcruiser Prado 4WD Test Drive
 
02:35
Toyota introduced its new Prado Landcruiser mid-size 4WD as a "best of both worlds" solution for both the highway and the rough stuff. Gizmag had a chance to test the vehicle on all types of terrain - including, open roads, tight forest trails and a formidable purpose built 4x4 track - and it didn't fail to impress. Full story and image gallery at http://www.gizmag.com/prado-test-drive/13534/
Views: 3164181 gizmag
Lec 2 | MIT 6.189 Multicore Programming Primer, IAP 2007
 
01:17:07
Lecture 2: Introduction to Cell processor (Courtesy of Michael Perrone. Used with permission.) License: Creative Commons BY-NC-SA More information at http://ocw.mit.edu/terms More courses at http://ocw.mit.edu Subtitles are provided through the generous assistance of Rohan Pai.
Views: 36494 MIT OpenCourseWare