Julian Elischer wrote: > Kris Kennaway wrote: >> On Mon, Dec 11, 2006 at 03:09:16PM -0800, Julian Elischer wrote: >>> I often have the following: >>> >>> >>> code x() does some bad thing 'A'.. it's a known thing and you can tell >>> where it was done from (x()) but x() tell at the time that it is bad. >>> >>> at some later time, you discover 'A' is bad but now you don't know who >>> was teh bad caller of x() >>> >>> >>> The solution I'm looking for: >>> >>> when x() is called it calls kdb_backtrace, but has teh backtrace >>> written to a static 16K buffer instead of being put out the normal way. >>> >>> when A is found to be wrong, we can see who the last caller of x() was >>> and how it was called. >>> >>> >>> I am looking at it now.. but if anyone has any thoughts let me know... >> >> See <sys/stack.h> > > interesting... is there any documentation on how to use this and what > its limitations are? > > man -k stack doesn't provide anything.. grrrrr. cute.. after reading code.. interesting but it doesn't save any arguments.. but definitly interesting.. thanks for pointing it out. I missed that being added.. > > >> >> Kris > > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"Received on Tue Dec 12 2006 - 00:04:28 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:03 UTC