Bug 3177 - Get proper entry functions for threads in the monitor
Summary: Get proper entry functions for threads in the monitor
Status: ASSIGNED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on: 2936
Blocks: 1632
  Show dependency tree / graph
 
Reported: 2006-09-06 14:50 UTC by Mike Cvet
Modified: 2006-12-19 20:33 UTC (History)
4 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Cvet 2006-09-06 14:50:35 UTC 
Replace deadbeef with the proper entry function for that thread.
Comment 1 Mike Cvet 2006-09-06 14:51:35 UTC 
Requires stacktraces to get the function name.
Comment 2 Wu Zhou 2006-09-28 15:11:12 UTC 
From the view point of the thread, isn't "__clone" the entry point for it?
Comment 3 Mike Cvet 2006-09-28 15:23:47 UTC 
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 ()