Weird messages in F12 when using some programs: "used the greatest stack depth ..."

[Joachim Backes]

I'm wondering about weird messages in F12 if some programes are finished:

for example: "du used greatest stack depth: 4772 bytes used"

Who is the issuer of such messages? How can I get rid of them?

Kind regards

[Joachim Backes]

On 09/13/2009 10:12 AM, Joachim Backes wrote:
> I'm wondering about weird messages in F12 if some programes are finished:
>
> for example: "du used greatest stack depth: 4772 bytes used"

Sorry for typo: should be:

"du used greatest stack depth: 4772 bytes left"

Remark: The message does not always appear for such a program (du for 
example).
> Who is the issuer of such messages? How can I get rid of them?
>
> Kind regards

[Michel Alexandre Salim]

On Sun, Sep 13, 2009 at 4:26 AM, Joachim Backes
 wrote:
> On 09/13/2009 10:12 AM, Joachim Backes wrote:
> > I'm wondering about weird messages in F12 if some programes are finished:
> >
> > for example: "du used greatest stack depth: 4772 bytes used"
>
> Sorry for typo: should be:
>
> "du used greatest stack depth: 4772 bytes left"
>
> Remark: The message does not always appear for such a program (du for
> example).
> > Who is the issuer of such messages? How can I get rid of them?

I'm guessing it's some debugging functionality in glibc, and it'd be
turned off for the final release.

Regards,

[Josh Boyer]

On Sun, Sep 13, 2009 at 10:20:17AM -0400, Michel Alexandre Salim wrote:
> On Sun, Sep 13, 2009 at 4:26 AM, Joachim Backes
>  wrote:
> > On 09/13/2009 10:12 AM, Joachim Backes wrote:
> > > I'm wondering about weird messages in F12 if some programes are finished:
> > >
> > > for example: "du used greatest stack depth: 4772 bytes used"
> >
> > Sorry for typo: should be:
> >
> > "du used greatest stack depth: 4772 bytes left"
> >
> > Remark: The message does not always appear for such a program (du for
> > example).
> > > Who is the issuer of such messages? How can I get rid of them?
>
> I'm guessing it's some debugging functionality in glibc, and it'd be
> turned off for the final release.

I'm fairly sure that is coming from the kernel, and it is reporting kernel
stack usage, not application.  It just happens that whatever that application
reported was triggered the greatest stack depth usage on boot I think.

josh

[Dave Jones]

On Mon, Sep 14, 2009 at 08:20:52AM -0400, Josh Boyer wrote:
> > I'm guessing it's some debugging functionality in glibc, and it'd be
> > turned off for the final release.
>
> I'm fairly sure that is coming from the kernel, and it is reporting kernel
> stack usage, not application.  It just happens that whatever that application
> reported was triggered the greatest stack depth usage on boot I think.

correct. it's nothing to be concerned about.
purely an informational thing.  it's useful info if it was followed by
a crash, but in most cases, things are just fine, even if the stack
limits are close to being reached.

Dave