Summary: | Get proper entry functions for threads in the monitor | ||
---|---|---|---|
Product: | frysk | Reporter: | Mike Cvet <mcvet> |
Component: | general | Assignee: | Unassigned <frysk-bugzilla> |
Status: | ASSIGNED --- | ||
Severity: | normal | CC: | pmuldoon, qiyaoltc, woodzltc, zhengyo |
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: | ||
Bug Depends on: | 2936 | ||
Bug Blocks: | 1632 |
Description
Mike Cvet
2006-09-06 14:50:35 UTC
Requires stacktraces to get the function name. From the view point of the thread, isn't "__clone" the entry point for it? We're looking for the inital function that the new thread executes, so in the example: Task #20365 #0 0x8048512 in do_it () from /home/yyz/mcvet/tester2.c #1 0xa89433 in start_thread () #2 0xb93a1e in __clone () We'd be interested in the function do_it () |