Static trace extraction
A trace is a record of the execution of a computer program, showing the sequence of operations executed. Dynamic traces are obtained by executing the program and depend upon the input. Static traces, on the other hand, describe potential sequences of operations extracted statically from the source c...
Gespeichert in:
| Hauptverfasser: | , , |
|---|---|
| Format: | Tagungsbericht |
| Sprache: | eng |
| Schlagworte: | |
| Online-Zugang: | Volltext bestellen |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
| container_end_page | 137 |
|---|---|
| container_issue | |
| container_start_page | 128 |
| container_title | |
| container_volume | |
| creator | Eisenbarth, T. Koschke, R. Vogel, G. |
| description | A trace is a record of the execution of a computer program, showing the sequence of operations executed. Dynamic traces are obtained by executing the program and depend upon the input. Static traces, on the other hand, describe potential sequences of operations extracted statically from the source code. Static traces offer the advantage that they do not depend upon input data. This paper describes a new automatic technique to extract static traces for individual stack and heap objects. The extracted static traces can be used in many ways, such as protocol recovery and validation in particular and program understanding in general. |
| doi_str_mv | 10.1109/WCRE.2002.1173071 |
| format | Conference Proceeding |
| fullrecord | <record><control><sourceid>ieee_6IE</sourceid><recordid>TN_cdi_ieee_primary_1173071</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>1173071</ieee_id><sourcerecordid>1173071</sourcerecordid><originalsourceid>FETCH-LOGICAL-i175t-a2deca5be3b72bb0dfa6c71cabc4d1c10b4c0d2c73cb004c34f2900828d12a583</originalsourceid><addsrcrecordid>eNotj0tLAzEURi8-wLF2LeKmfyDtvbmTyWQpQ6tCoeADlyW5yUDEFzNZ6L93xK4O3-Ic-ACuCJdE6FYv3cN6qRH1NC2jpSOoNFujDDfuGObOtmgbZ8g6Z06gmhyjiA2ewfk4vk4issMKLh-LL1kWZfCSFun7jyV_flzAae_fxjQ_cAbPm_VTd6e2u9v77marMllTlNcxiTchcbA6BIy9b8SS-CB1JCEMtWDUYlkCYi1c99ohtrqNpL1peQbX_92cUtp_DfndDz_7wyf-BU2gPPs</addsrcrecordid><sourcetype>Publisher</sourcetype><iscdi>true</iscdi><recordtype>conference_proceeding</recordtype></control><display><type>conference_proceeding</type><title>Static trace extraction</title><source>IEEE Electronic Library (IEL) Conference Proceedings</source><creator>Eisenbarth, T. ; Koschke, R. ; Vogel, G.</creator><creatorcontrib>Eisenbarth, T. ; Koschke, R. ; Vogel, G.</creatorcontrib><description>A trace is a record of the execution of a computer program, showing the sequence of operations executed. Dynamic traces are obtained by executing the program and depend upon the input. Static traces, on the other hand, describe potential sequences of operations extracted statically from the source code. Static traces offer the advantage that they do not depend upon input data. This paper describes a new automatic technique to extract static traces for individual stack and heap objects. The extracted static traces can be used in many ways, such as protocol recovery and validation in particular and program understanding in general.</description><identifier>ISSN: 1095-1350</identifier><identifier>ISBN: 9780769517995</identifier><identifier>ISBN: 0769517994</identifier><identifier>EISSN: 2375-5369</identifier><identifier>DOI: 10.1109/WCRE.2002.1173071</identifier><language>eng</language><publisher>IEEE</publisher><subject>Computer languages ; Data mining ; Law ; Legal factors ; Program processors ; Protocols ; Reverse engineering ; Software systems</subject><ispartof>Ninth Working Conference on Reverse Engineering, 2002. Proceedings, 2002, p.128-137</ispartof><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/1173071$$EHTML$$P50$$Gieee$$H</linktohtml><link.rule.ids>309,310,780,784,789,790,2057,4049,4050,27924,54919</link.rule.ids><linktorsrc>$$Uhttps://ieeexplore.ieee.org/document/1173071$$EView_record_in_IEEE$$FView_record_in_$$GIEEE</linktorsrc></links><search><creatorcontrib>Eisenbarth, T.</creatorcontrib><creatorcontrib>Koschke, R.</creatorcontrib><creatorcontrib>Vogel, G.</creatorcontrib><title>Static trace extraction</title><title>Ninth Working Conference on Reverse Engineering, 2002. Proceedings</title><addtitle>WCRE</addtitle><description>A trace is a record of the execution of a computer program, showing the sequence of operations executed. Dynamic traces are obtained by executing the program and depend upon the input. Static traces, on the other hand, describe potential sequences of operations extracted statically from the source code. Static traces offer the advantage that they do not depend upon input data. This paper describes a new automatic technique to extract static traces for individual stack and heap objects. The extracted static traces can be used in many ways, such as protocol recovery and validation in particular and program understanding in general.</description><subject>Computer languages</subject><subject>Data mining</subject><subject>Law</subject><subject>Legal factors</subject><subject>Program processors</subject><subject>Protocols</subject><subject>Reverse engineering</subject><subject>Software systems</subject><issn>1095-1350</issn><issn>2375-5369</issn><isbn>9780769517995</isbn><isbn>0769517994</isbn><fulltext>true</fulltext><rsrctype>conference_proceeding</rsrctype><creationdate>2002</creationdate><recordtype>conference_proceeding</recordtype><sourceid>6IE</sourceid><sourceid>RIE</sourceid><recordid>eNotj0tLAzEURi8-wLF2LeKmfyDtvbmTyWQpQ6tCoeADlyW5yUDEFzNZ6L93xK4O3-Ic-ACuCJdE6FYv3cN6qRH1NC2jpSOoNFujDDfuGObOtmgbZ8g6Z06gmhyjiA2ewfk4vk4issMKLh-LL1kWZfCSFun7jyV_flzAae_fxjQ_cAbPm_VTd6e2u9v77marMllTlNcxiTchcbA6BIy9b8SS-CB1JCEMtWDUYlkCYi1c99ohtrqNpL1peQbX_92cUtp_DfndDz_7wyf-BU2gPPs</recordid><startdate>2002</startdate><enddate>2002</enddate><creator>Eisenbarth, T.</creator><creator>Koschke, R.</creator><creator>Vogel, G.</creator><general>IEEE</general><scope>6IE</scope><scope>6IL</scope><scope>CBEJK</scope><scope>RIE</scope><scope>RIL</scope></search><sort><creationdate>2002</creationdate><title>Static trace extraction</title><author>Eisenbarth, T. ; Koschke, R. ; Vogel, G.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-i175t-a2deca5be3b72bb0dfa6c71cabc4d1c10b4c0d2c73cb004c34f2900828d12a583</frbrgroupid><rsrctype>conference_proceedings</rsrctype><prefilter>conference_proceedings</prefilter><language>eng</language><creationdate>2002</creationdate><topic>Computer languages</topic><topic>Data mining</topic><topic>Law</topic><topic>Legal factors</topic><topic>Program processors</topic><topic>Protocols</topic><topic>Reverse engineering</topic><topic>Software systems</topic><toplevel>online_resources</toplevel><creatorcontrib>Eisenbarth, T.</creatorcontrib><creatorcontrib>Koschke, R.</creatorcontrib><creatorcontrib>Vogel, G.</creatorcontrib><collection>IEEE Electronic Library (IEL) Conference Proceedings</collection><collection>IEEE Proceedings Order Plan All Online (POP All Online) 1998-present by volume</collection><collection>IEEE Xplore All Conference Proceedings</collection><collection>IEEE Electronic Library (IEL)</collection><collection>IEEE Proceedings Order Plans (POP All) 1998-Present</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Eisenbarth, T.</au><au>Koschke, R.</au><au>Vogel, G.</au><format>book</format><genre>proceeding</genre><ristype>CONF</ristype><atitle>Static trace extraction</atitle><btitle>Ninth Working Conference on Reverse Engineering, 2002. Proceedings</btitle><stitle>WCRE</stitle><date>2002</date><risdate>2002</risdate><spage>128</spage><epage>137</epage><pages>128-137</pages><issn>1095-1350</issn><eissn>2375-5369</eissn><isbn>9780769517995</isbn><isbn>0769517994</isbn><abstract>A trace is a record of the execution of a computer program, showing the sequence of operations executed. Dynamic traces are obtained by executing the program and depend upon the input. Static traces, on the other hand, describe potential sequences of operations extracted statically from the source code. Static traces offer the advantage that they do not depend upon input data. This paper describes a new automatic technique to extract static traces for individual stack and heap objects. The extracted static traces can be used in many ways, such as protocol recovery and validation in particular and program understanding in general.</abstract><pub>IEEE</pub><doi>10.1109/WCRE.2002.1173071</doi><tpages>10</tpages></addata></record> |
| fulltext | fulltext_linktorsrc |
| identifier | ISSN: 1095-1350 |
| ispartof | Ninth Working Conference on Reverse Engineering, 2002. Proceedings, 2002, p.128-137 |
| issn | 1095-1350 2375-5369 |
| language | eng |
| recordid | cdi_ieee_primary_1173071 |
| source | IEEE Electronic Library (IEL) Conference Proceedings |
| subjects | Computer languages Data mining Law Legal factors Program processors Protocols Reverse engineering Software systems |
| title | Static trace extraction |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-08T08%3A21%3A51IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-ieee_6IE&rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft.genre=proceeding&rft.atitle=Static%20trace%20extraction&rft.btitle=Ninth%20Working%20Conference%20on%20Reverse%20Engineering,%202002.%20Proceedings&rft.au=Eisenbarth,%20T.&rft.date=2002&rft.spage=128&rft.epage=137&rft.pages=128-137&rft.issn=1095-1350&rft.eissn=2375-5369&rft.isbn=9780769517995&rft.isbn_list=0769517994&rft_id=info:doi/10.1109/WCRE.2002.1173071&rft_dat=%3Cieee_6IE%3E1173071%3C/ieee_6IE%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rft_ieee_id=1173071&rfr_iscdi=true |