Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Jan 2003 16:17:39 -0500 (EST)
From:      Robert Watson <rwatson@FreeBSD.org>
To:        current@FreeBSD.org, davidxu@FreeBSD.org
Cc:        Craig Dooley <cd5697@albany.edu>
Subject:   Profiling kills -current?
Message-ID:  <Pine.NEB.3.96L.1030130161622.26712H-100000@fledge.watson.org>

next in thread | raw e-mail | index | archive | help

Looks like recent commits may have broken profiling of user applications; 
or rather, it's also causing the kernel to crash.  I suspect (but have not
confirmed) it was the recent KSE commit.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Network Associates Laboratories

---------- Forwarded message ----------
Date: Thu, 30 Jan 2003 16:19:32 -0500
From: Craig Dooley <cd5697@albany.edu>
To: Robert Watson <rwatson@freebsd.org>
Subject: Re: Recent current dies hard with simple program

That did it.  When I took -pg out of CFLAGS the program will now run
fine.  I must have been playing around with it and added that within the
last two days.  I'll check back through the archives to see what the
profiling bugs are.  Sorry for not looking deeper before posting to the
lists. 

-Craig


On Thu, Jan 30, 2003 at 02:32:04PM -0500, Robert Watson wrote:
> On Thu, 30 Jan 2003, Craig Dooley wrote:
> 
> > It worked here on the 28th.  When I wrote it it worked fine and showed
> > that my program worked fine.  I dont think it's my read_file function
> > since thats ripped out of the actual program, and that still works fine. 
> > Could it possibly be something with not freeing the buffer before I
> > exit?  It doesnt make much sense.  Im going to check through all cvs
> > patches between the 28th and 29th since it was dying on a kernel from
> > yesterday.  I do have a serial console, and will try to break through it
> > next time I make it happen.  All input it hosed and it's caught in a
> > tight loop repeating the sample in the sound card and doing nothing.  I
> > will try look into it more closely, heres some more info
> 
> I'm having trouble figuring out what it could be, other than it's clearly
> a kernel bug :-).  I'll try updating a system to more recent source.  Any
> chance you're using profiling support?
> 
> Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
> robert@fledge.watson.org      Network Associates Laboratories
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1030130161622.26712H-100000>