Chris Quenelle's Weblog
Thoughts on developer tools.

Monday October 11, 2004

Sun developers can't use the latest Solaris This is an issue that's been near and dear to my heart for a long time because it seems like a solvable problem. If you develop software that has to run on Solaris 8, you essentially have to develop it on Solaris 8. If you develop it on Solaris 10, you'll fight a constant battle with changing runtime linker dependencies and possibly even changing compiler defaults. Greg Nakhimovsky has a good writeup on this: http://developers.sun.com/solaris/articles/developing_new_solaris.html Posted by Chris Quenelle ( Oct 11 2004, 10:23:20 AM PDT ) - Permalink - Comments [3] - Software Philosophy

Older blog entries:

• Blog relocation
• C++ and OpenMP runtime libraries in Solaris
• command-not-found for OpenSolaris?
• Goodbye Solaris 9 (for Sun Studio)
• git user's guide?
• New Sun Studio FAQ site
• Dbx versus gdb
• Django (actually MySQL-python) and RPATH
• SXDE 5/07 -- Solaris Express Developers Edition
• Debugging tips for threaded programs on Solaris
• New dbx blog!
• libumem dbx module update (works on Solaris 9 now)
• Using dbx and libumem to find memory problems
• Latest Sun dwarf extensions
• dbx .ldynsym support - stack traces for stripped programs
• Using LDAP inside Sun
• gnome kstats
• Calling Sun Studio users...
• Compiler options by category and platform
• What do you call 64-bits?
• Sun Studio resources on genunix.org
• mod_auth_ldap
• Find Data Races and Deadlocks
• Goodbye -xarch=amd64, hello -m64
• Intel and Sun
• Sun Studio Express 3 lives again!
• Sun Studio Express 3 -- bad tarballs
• Sun Studio Wiki
• Introduction to Functional Programming Concepts
• OpenID starting to take off (finally)
• Dwarf and XML
• Sun Studio Express 3 (new GUI!)
• The latest Nevada/dbx bug
• Patch Check Advanced
• Dbx help docs in HTML
• Performancing at work.
• Performancing
• I keep forgetting how closures work...
• malloc interposition can't possibly work reliabily
• Dbx can crash with g++ symbols
• Sun Studio and patchadd -G
• Linux dbx patch available!! (for Sun Studio 11)
• Enterprise versus The Developer
• Data Race in my last example
• Graphical display of thread synchronization
• Attempting to tame StarOffice HTML
• My single greatest accomplishment
• Empty hallways ...
• Red Hat versus Ubuntu
• Markets without Marketing
• Instruction set selection in Sun Studio and gcc (Grudge match: -xarch versus -fast)
• Linux compilers update
• Community and Terminology
• Data Race Detection Tool and Sun Studio Express
• Fast threads
• /bin considered harmful
• AMD64 Nevada b37-b40 doesn't like dbx
• Solaris 10: Ack! Where did my archive libraries go?
• Anti-help
• Taking the plunge!
• Why can't dbx find my function?
• Solaris Day at the University of Washington
• Getting started with dtrace
• parallel features of dmake and gmake
• Linux headers are gcc-specific
• 32 versus 64-bit programs
• Sun Studio and Solaris integration
• Conform
• How to use libumem to find a bad free call
• Reporting bugs
• New blog theme
• Blogging client
• Page-o-links (good Sun Studio links!)
• Installing dual boot
• Blogger RTE editor
• Optimizing synchronization
• Keysigning...
• Sun email servers
• FREE SUPPORT for Sun Studio compilers and tools
• Using separate .dbg files with dbx
• Beyond Java
• CMT and MT
• Johnny L's layup
• misligned ELF section headers
• Sun Studio IDE -- turning off locals
• Two bad Solaris bugs that affect dbx users
• Supporting threads is harder than it seems
• Non-java developers unite!
• Sun Studio 11, less expensive than ever!
• Importing debug information into dbx
• The story of lazy stabs
• java google toolbar
• MAP_NORESERVE and dbx
• debug info in XML, and DSD 2.0
• shadows.com
• Concurrency utils for C/C++
• simple umem integration with dbx
• The Good Old Motif Workshop IDE
• Give it away for free, and make it up in volume!
• Technorati