Re: Library Function Tracer

From: George (
Date: 02/25/99

On Thu, 25 Feb 1999, Mark A. Heilpern wrote:

>I used this attaching to my mud while it was running several times...
>(ltrace -p mud-pid), and discovered an overwhelming number of
>calls to random and strncmp... so I tried to filter out the random
>calls (ltrace -e !random ...) (actually, ltrace -e \!random ...) and got

Probably due to combat.  If all else fails, do:

ltrace bin/circle 2>&1 | grep -v 'random('

>(ltrace -e random ...) and noticed that even after I kill -9'd the ltrace,
>my mud had ceased responding. I suspect that this is caused by
>ltrace attaching to the process and not being able to properly
>detach upon a kill -9, but I'm only guessing. User beware.

Probably, I'd suggest 'kill' alone.

>Other than that little problem, I can envision several good uses for this.
>George, thank you for telling us about it.

No problem.  I heard about it on the Linux kernel list.  Much handier for
pin-pointing what was called prior to a crash than strace.

George Greer

     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
     |  |

This archive was generated by hypermail 2b30 : 12/15/00 PST