On Mon, Nov 13, 2006 at 12:58:58PM -0700, Paul E Condon wrote:
> On Mon, Nov 13, 2006 at 02:05:20PM -0500, [EMAIL PROTECTED] wrote:
> > On Mon, Nov 13, 2006 at 10:41:52AM -0700, Paul E Condon wrote:
> > >
> > > I'm not a professional programmer, so my standards of reasonableness
> > > are not temp
On Mon, Nov 13, 2006 at 02:05:20PM -0500, [EMAIL PROTECTED] wrote:
> On Mon, Nov 13, 2006 at 10:41:52AM -0700, Paul E Condon wrote:
> >
> > I'm not a professional programmer, so my standards of reasonableness
> > are not tempered by 'real world' experience. I use C++ to write
> > simulation code f
On Mon, Nov 13, 2006 at 10:41:52AM -0700, Paul E Condon wrote:
>
> I'm not a professional programmer, so my standards of reasonableness
> are not tempered by 'real world' experience. I use C++ to write
> simulation code for my research in biodiversity. It seems to me, from
> reading the doc.s, tha
On Mon, Nov 13, 2006 at 12:22:27AM -0500, [EMAIL PROTECTED] wrote:
> On Sun, Nov 12, 2006 at 08:31:42PM -0700, Paul E Condon wrote:
> > On Sun, Nov 12, 2006 at 09:55:52AM -0800, John L Fjellstad wrote:
> > > Paul E Condon <[EMAIL PROTECTED]> writes:
> > >
> > > > Thanks for stack profiling info. I
Paul E Condon <[EMAIL PROTECTED]> writes:
> This is really interesting. man malloc calls the default behavior
> of the kernel a really bad bug, with which I agree. kernel-docs
> sysctl/vm.txt justifies the default by claiming it is helpful to
> programmers who 'malloc() huge amounts of memory "jus
On Sun, Nov 12, 2006 at 08:31:42PM -0700, Paul E Condon wrote:
> On Sun, Nov 12, 2006 at 09:55:52AM -0800, John L Fjellstad wrote:
> > Paul E Condon <[EMAIL PROTECTED]> writes:
> >
> > > Thanks for stack profiling info. I wonder if this _is_ a reportable
> > > bug. After all, there is a lot of inf
On Sun, Nov 12, 2006 at 09:55:52AM -0800, John L Fjellstad wrote:
> Paul E Condon <[EMAIL PROTECTED]> writes:
>
> > Thanks for stack profiling info. I wonder if this _is_ a reportable
> > bug. After all, there is a lot of information on the 'bad_alloc'
> > exception in various sources. If GNU C++
Paul E Condon <[EMAIL PROTECTED]> writes:
> Thanks for stack profiling info. I wonder if this _is_ a reportable
> bug. After all, there is a lot of information on the 'bad_alloc'
> exception in various sources. If GNU C++ library doesn't try to throw
> this exception until it is too late for the t
On 11/6/06, Paul E Condon <[EMAIL PROTECTED]> wrote:
Thanks for stack profiling info. I wonder if this _is_ a reportable
bug. After all, there is a lot of information on the 'bad_alloc'
exception in various sources. If GNU C++ library doesn't try to throw
this exception until it is too late for t
On Mon, Nov 06, 2006 at 10:04:15AM -0500, Michael Marsh wrote:
> On 11/5/06, Paul E Condon <[EMAIL PROTECTED]> wrote:
> >I've written a program in C++ using STL for some fairly
> >tricky simulation work. The program works, but fails
> >during initialization for some choices of input parameters.
> >
On 11/5/06, Paul E Condon <[EMAIL PROTECTED]> wrote:
I've written a program in C++ using STL for some fairly
tricky simulation work. The program works, but fails
during initialization for some choices of input parameters.
I think the problem is not enough RAM, but I'd like to
confirm that, so I t
On Mon, Nov 06, 2006 at 01:42:06AM -0500, Allan Wind wrote:
> On 2006-11-05T21:02:33-0700, Paul E Condon wrote:
> > My code does not have the string 'Killed' in it anywhere, so I suppose
> > this comes from some place in the C/C++ libraries. The string "caught
> > ...!!!" never appears in the outp
On 2006-11-05T21:02:33-0700, Paul E Condon wrote:
> My code does not have the string 'Killed' in it anywhere, so I suppose
> this comes from some place in the C/C++ libraries. The string "caught
> ...!!!" never appears in the output, nor does the string " After
> catch.".
You program (probably) r
I've written a program in C++ using STL for some fairly
tricky simulation work. The program works, but fails
during initialization for some choices of input parameters.
I think the problem is not enough RAM, but I'd like to
confirm that, so I tried enclosing the relevant parts
of int main(...) in a
14 matches
Mail list logo