Re: Analysing core files
From: clayne (clayne_at_anodized.com)
Date: 11/25/05
- Previous message: Alvin: "Re: Library statistics"
- In reply to: Rich Teer: "Re: Analysing core files"
- Next in thread: Thomas Maier-Komor: "Re: Analysing core files"
- Reply: Thomas Maier-Komor: "Re: Analysing core files"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 24 Nov 2005 16:43:05 -0800
Rich, there is definitely one exception to this rule (Solaris before
Linux):
Valgrind.
I personally would much rather use Solaris for all of my development,
and for the most
part I usually do (Sol8/9) - but for certain profiling or deeper memory
debugging, you cannot beat Valgrind - which is only natively available
on Linux i86 platforms.
On another note I've also found Darwin to be quite the *** about
correct coding (from a runtime perspective) which helps out when you're
trying to double check why something may work on say, Linux, but not on
other platforms. The greater issue here being that Linux is too
programmer-friendly - creating lazy code.
Rich Teer wrote:
> On Thu, 24 Nov 2005, joe@invalid.address wrote:
>
> > The debugging tools available on Solaris work on Linux?
>
> Not necessarily. What I was suggesting to the OP is that maybe
> Solaris would be a better development environment--provided, of
> course, the app is not fraught with Linuxisms.
- Previous message: Alvin: "Re: Library statistics"
- In reply to: Rich Teer: "Re: Analysing core files"
- Next in thread: Thomas Maier-Komor: "Re: Analysing core files"
- Reply: Thomas Maier-Komor: "Re: Analysing core files"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]