GDB version 6.8 was released just a few days ago. I’m happy to have made my small contribution to it, mostly with development of decimal floating point debugging support. From the NEWS file: “GDB now supports debugging C and C++ programs which use the Decimal Floating Point extension. In addition, the PowerPC target now has [...]
Posts Tagged ‘development’
new GDB release, and decimal floating point
Posted in english, tagged community, decimal floating point, development, gdb, linkedin, linux, open source, planet ltc on Monday, March 31, 2008 | Leave a Comment »
gdb’s backtrace command implemented in python
Posted in english, tagged community, development, gdb, linkedin, linux, open source, planet ltc, python on Monday, March 24, 2008 | 1 Comment »
I’ve been working on Python bindings for exposing GDB’s frame_info, the internal structure it uses to keep track of the frame stack in the debuggee (or inferior, in GDB parlance). I got just enough working to be able to implement an equivalent of GDB’s backtrace command entirely in Python. The difference is that my version [...]
new linker for Linux and others ELF OSes
Posted in english, tagged community, development, linkedin, linux, open source, planet ltc on Saturday, March 22, 2008 | Leave a Comment »
Cool, Ian Taylor (who wrote the current linker used in Linux) just announced that gold, the new linker that he has been writing, was just released. It targets only ELF systems, so I believe its design is much simplified and streamlined by this. I find it interesting that he chose to implement it in C++. [...]
python scripting in gdb!
Posted in english, tagged community, development, gdb, linkedin, linux, open source, planet ltc on Friday, March 14, 2008 | 7 Comments »
It seems the planets are finally aligning to get Python scripting support in GDB! Vladimir published his changes last month, Tromey improved on them, and I joined the bandwagon. The work is being done in a git repo hosted by gitorious. More details here. This looks very promising. Update – 2008/03/15: Sorry, I was a [...]
autoconf tip
Posted in english, tagged autoconf, autotools, development, hint on Thursday, March 13, 2008 | Leave a Comment »
I always dreaded having to do modifications in Makefile.in (e.g., adding a new file to the compilation) because then I’d have to nuke the build directory (you do build your project outside of the source tree, right? ) and run configure again for the Makefile to be generated and then rebuild everything again. Well, of [...]
take care when renaming files in git
Posted in english, tagged development, git, hint, linux, open source, version control on Thursday, January 3, 2008 | 3 Comments »
If you rename and modify a file in the same commit, you will loose its history: http://sourceware.org/ml/frysk/2008-q1/msg00004.html You have to do a commit just with the rename operation (identical file contents), and then modify it. Sheesh, good to know about that! I recall I had a similar problem with Subversion once… I think it was [...]
neat programming note
Posted in english, tagged , development, haha only serious, nerd on Sunday, December 16, 2007 | Leave a Comment »
Cool, I just found out that the POWER ISA (Instruction Set Architecture) specification has a programming note with a big excerpt from the Gulliver’s Travels (it’s in page 52 on v2.05 of the ISA) to explain where the terms “big endian” and “little endian” come from. I knew it came from there, but I had [...]
a couple of git hints
Posted in english, tagged development, git, hint, open source, version control on Friday, November 9, 2007 | 1 Comment »
Today I just discovered a new command in git which should be very useful: git-stash, which is new in git 1.5.3. It’s great for those moments when git complaints about your modified tree, but you don’t want to commit anything yet. Now you can throw your currently uncommited changes into the drawer, work in something [...]
wonderful world of makefiles
Posted in english, tagged build tools, development, haha only serious, hint, nerd on Monday, October 29, 2007 | Leave a Comment »
Did you know… … that “after reading in all makefiles, make will consider each as a goal target and attempt to update it. If a makefile has a rule which says how to update it (found either in that very makefile or in another one) or if an implicit rule applies to it (see Using [...]