Re: [ Memory ] Re: Thought

2002-10-03 Thread Rafael Garcia-Suarez
[EMAIL PROTECTED] wrote: > For a more fine-grained view, you > need hooks into Perl internals (such as the Perl malloc). This sounds like Devel::Peek::mstat(). But I never looked at this before.

Re: [ Memory ] Re: Thought

2002-10-03 Thread Andrew . Savige
En op 4 oktober 2002 sprak Michael G Schwern: > The problem is when you put those two next to each other, one > promising a friendly interface, one a bare-metal interface, > it confuses the intent of the module. Is it for Joe End User > or is it for Joe Core Hacker? A module to report memory usag

Re: Smoke db (was perl-current doesn't compil on MinGw-2.0.0-3)

2002-10-03 Thread Alain BARBET
> I can put it up, but there is limited time to update the cgi-scripts (you > need to mail them to me and I need to put them up). So if the code is > stable, I can donate the page and the bandwidth (up to a limit, though). Many thanks for your offer but I don't think if you can support this: Data

RE: Smoke db (was perl-current doesn't compil on MinGw-2.0.0-3)

2002-10-03 Thread Tels
-BEGIN PGP SIGNED MESSAGE- Moin, On 03-Oct-02 alian carved into stone: > http://www.alianwebserver.com/cgi-bin/smoke_db updated. > > Reports from 17500 => 17967. > My db server on alianwebserver allow me to only fetch 60k per cgi > request, so I've limit to 17500 smoke reports. > (don'

Smoke db (was perl-current doesn't compil on MinGw-2.0.0-3)

2002-10-03 Thread alian
http://www.alianwebserver.com/cgi-bin/smoke_db updated. Reports from 17500 => 17967. My db server on alianwebserver allow me to only fetch 60k per cgi request, so I've limit to 17500 smoke reports. (don't try "All" with all browse list, it's same problem, it's stop before display). If we can f

Re: [ Memory ] Re: Thought

2002-10-03 Thread Benjamin Goldberg
Michael G Schwern wrote: > > On Wed, Oct 02, 2002 at 01:50:56PM +0200, H.Merijn Brand wrote: > > SYNOPSIS > > use Devel::Internals; > > A little broad. Perhaps Devel::Memory? > > > my $end = sbrk (); > > > > my @array = (1..1); > > print "The creation of th

Re: [ Memory ] Re: Thought

2002-10-03 Thread Michael G Schwern
On Thu, Oct 03, 2002 at 10:43:43AM +0100, Nicholas Clark wrote: > The reason I'm saying it might not be much use to people unfamiliar with > the internals of unix is precisely because it does return a precisely defined > but not directly useful value - the highest address on the heap. > If you rea

Re: [ Memory ] Re: Thought

2002-10-03 Thread Michael G Schwern
On Thu, Oct 03, 2002 at 11:39:42AM -0400, Green, Paul wrote: > H.Merijn Brand [mailto:[EMAIL PROTECTED]] writes: > > So far, all I got was criticism. I asked for it. But no-one said it was > useful. > > (Or I didn't read between the lines enough). > > In my experience, the phrase "I really liked

RE: [ Memory ] Re: Thought

2002-10-03 Thread Green, Paul
H.Merijn Brand [mailto:[EMAIL PROTECTED]] writes: > So far, all I got was criticism. I asked for it. But no-one said it was useful. > (Or I didn't read between the lines enough). In my experience, the phrase "I really liked your idea and I hope you won't mind if I share a few ideas for improving

Re: [ Memory ] Re: Thought

2002-10-03 Thread Elizabeth Mattijsen
At 01:01 PM 10/3/02 +0200, H.Merijn Brand wrote: >So far, all I got was criticism. I asked for it. But no-one said it was >useful. >(Or I didn't read between the lines enough). Well, since I probably have been the person that set this off, I think I should say something here. Ideally, I think

Re: [ Memory ] Re: Thought

2002-10-03 Thread H.Merijn Brand
On Thu 03 Oct 2002 15:19, "Green, Paul" <[EMAIL PROTECTED]> wrote: > sbrk is very Unixish. I know. I'm not targetting Win32 (memory shortage is not an option, but a feature) or OS/2. I was targetting my own problem/curiousity and probing the usefulness of making it public. My initial sbrk probe

RE: [ Memory ] Re: Thought

2002-10-03 Thread Green, Paul
sbrk is very Unixish. It isn't in POSIX at all. Our system is highly POSIX compliant but doesn't have a function that directly maps to sbrk. We do have a way of determining heap max size and heap current usage, but it is a functional (subroutine) interface. If you had a function that just calcul

Re: [ Memory ] Re: Thought

2002-10-03 Thread Andreas J. Koenig
> On Thu, 03 Oct 2002 13:01:52 +0200, "H.Merijn Brand" <[EMAIL PROTECTED]> said: >> If it only returns the value from sbrk(), damn well call it sbrk. > Ahh, someone on /my/ side. Mee too. > So far, all I got was criticism. I asked for it. But no-one said it was useful. > (Or I didn'

Re: [ Memory ] Re: Thought

2002-10-03 Thread H.Merijn Brand
On Thu 03 Oct 2002 11:43, Nicholas Clark <[EMAIL PROTECTED]> wrote: > On Wed, Oct 02, 2002 at 05:07:20PM -0400, Michael G Schwern wrote: > > On Wed, Oct 02, 2002 at 10:26:32PM +0200, H.Merijn Brand wrote: > > > > > I realize that sbrk() is a familiar concept to deep C programmers on > > > > BSD-s

Re: [ Memory ] Re: Thought

2002-10-03 Thread Nicholas Clark
On Wed, Oct 02, 2002 at 05:07:20PM -0400, Michael G Schwern wrote: > On Wed, Oct 02, 2002 at 10:26:32PM +0200, H.Merijn Brand wrote: > > > I realize that sbrk() is a familiar concept to deep C programmers on > > > BSD-style systems, but in order for this to be useful to Perl programmers, > > > or