Re: debugging a multi-threaded program on linux.
From: Ed L Cashin (ecashin_at_uga.edu)
Date: 05/10/03
- Next message: Paul Pluzhnikov: "Re: Disturbing truss output"
- Previous message: Chris Markle: "Re: debugging a multi-threaded program on linux."
- In reply to: Michael B. Allen: "Re: debugging a multi-threaded program on linux."
- Next in thread: Scott Lacy Smith: "Re: debugging a multi-threaded program on linux."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 09 May 2003 22:49:47 -0400
"Michael B. Allen" <mba2000@ioplex.com> writes:
> On Fri, 09 May 2003 15:58:24 -0400, Jeff wrote:
>
>>> program on ret-hat linux ? another thing that might help me is a
>>> command that i could put in my code and that will print that current
>>> call stuck off my program, this way i could at least know when and from
>>> where am i getting into the code areas i sould not enter.
>
> If you use GNU C I'm certain there is a way to get a sort of stack
> trace. I recall a thread about it. Unfortunately I do not know the
> function/macro necessary to invoke it. Perhaps someone else can put a
> finger on it?
You mean "bt"?
-- --Ed L Cashin PGP public key: http://noserose.net/e/pgp/
- Next message: Paul Pluzhnikov: "Re: Disturbing truss output"
- Previous message: Chris Markle: "Re: debugging a multi-threaded program on linux."
- In reply to: Michael B. Allen: "Re: debugging a multi-threaded program on linux."
- Next in thread: Scott Lacy Smith: "Re: debugging a multi-threaded program on linux."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
