Sections
Timeline
Browse Source
New Ticket
Sub-Sections
Download
Comma-delimited Text
Tab-delimited Text
RSS Feed
Metanav
Preferences
About Trac
Links
Slowchop Studios
Gerald Kaszuba
Advertisement

Ticket #7 (new enhancement)

Opened 15 months ago

Last modified 14 months ago

Subsequent calls to start_trace(reset=False) loses __main__

Reported by: anonymous Owned by: gak
Priority: minor Component: general
Version: 0.3.1 Keywords:
Cc:

Description

It seems calls to start_trace(reset=False) loses edges from main for all but the first start_trace, i.e. the first one after a reset_trace(). It seems maybe there is something that needs "resetting" even when not resetting?

Simple example:

pycallgraph.start_trace(reset=False) #pycallgraph.stop_trace() pycallgraph.start_trace(reset=False) ...test code here... pycallgraph.stop_trace()

That works normally, now uncomment the stop_trace() command, and rerun... main disappears.

Attachments

Change History

Changed 15 months ago by anonymous

Oops. Sorry about the formatting. Obviously it should be this:

pycallgraph.start_trace(reset=False)
#pycallgraph.stop_trace()
pycallgraph.start_trace(reset=False)
...test code here...
pycallgraph.stop_trace()

Changed 15 months ago by anonymous

  • cc hugovdm+pycallgraphbug@… removed

Add/Change #7 (Subsequent calls to start_trace(reset=False) loses __main__)

Author



Change Properties
<Author field>
Action
as new
 
Note: See TracTickets for help on using tickets.