Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

RPC trace_transaction crashes parity with: thread '<unknown>' has overflowed its stack #1686

Closed
johnkozan opened this issue Jul 21, 2016 · 2 comments · Fixed by #1698
Closed
Assignees
Labels
F2-bug 🐞 The client fails to follow expected behavior.
Milestone

Comments

@johnkozan
Copy link

The following RPC call will crash parity every time:

curl -X POST -H "Content-type: application/json" --data '{"jsonrpc":"2.0","method":"trace_transaction","params":["0xddee3249fe1e7cfa9b88bf58b6e1257e8d334b9ec8110cf59701559a53b10e92"],"id":36955}'  localhost:8545

results in:

thread '<unknown>' has overflowed its stack
fatal runtime error: stack overflow
Aborted (core dumped)  

I've reproduced this bug on the following versions:

  • version Parity/v1.3.0-unstable-8ab56ea-20160720/x86_64-linux-gnu/rustc1.12.0-nightly
  • version Parity/v1.2.2-beta/x86_64-linux-gnu/rustc1.10.0

parity was run with the --tracing on flag.
I've also attempted deleting the data and doing a full resync and the problem persists.

@arkpar arkpar added the F2-bug 🐞 The client fails to follow expected behavior. label Jul 21, 2016
@arkpar arkpar added this to the 1.3 Acuity milestone Jul 22, 2016
@mtbitcoin
Copy link

I can confirm this is an issue too "thread '' has overflowed its stack"

gavofyork pushed a commit that referenced this issue Jul 23, 2016
* flat trace serialization

* tracing finds transaction which creates contract

* flatten traces before inserting them to the db
@mtbitcoin
Copy link

mtbitcoin commented Jul 24, 2016

I am not sure if this is related, but calling RPC trace_transaction now causes an exception . https://github.com/ethcore/parity/issues/1704

debris added a commit that referenced this issue Jul 29, 2016
* flat trace serialization

* tracing finds transaction which creates contract

* flatten traces before inserting them to the db
arkpar pushed a commit that referenced this issue Jul 29, 2016
* flat trace serialization

* tracing finds transaction which creates contract

* flatten traces before inserting them to the db
gavofyork pushed a commit that referenced this issue Jul 30, 2016
* Don't try to sync to ancient blocks

* Parallel block body download

* Fixed reading chunked EIP8 handshake (#1712)

* Fixed reading chunked EIP8 handshake

* Added missing break

* Disconnect peers on a fork

* Updated json-ipc-server

* Combine mining queue and enabled into single locked datum (#1749)

* Combine mining queue and enabled into single locked datum

Additional tracing.

* Fix bug uncovered by test.

* Fix typo

* Remove unneeded log initialisation in test.

* fix failing test (#1756)

* Fixed test

* Suicides tracing (#1688)

* tracing suicide

* fixed #1635

* fixed typo

* Stackoverflow #1686 (#1698)

* flat trace serialization

* tracing finds transaction which creates contract

* flatten traces before inserting them to the db

* Trace other types of calls (#1727)

* Trace through DELEGATECALL and CALLCODE

Add them to the JSON output and RLP database store.

* Fix tests.

* Fix all tests.

* Fix one more test.

* filtering transactions toAddress includes contract creation (#1697)

* tracing finds transaction which creates contract

* comma cleanup

Remove when following `}`s, add to final entries.

* Various improvements to tracing & diagnostics. (#1707)

* Various improvements to tracing & diagnostics.

- Manage possibility of `Account` not having code for `PodAccount`
- New RPC: `trace_sendRawTransaction`
- See raw transaction dump when inspecting over RPC

* Fix test

* Remove one of the dupe error messages

* Remove unneeded `&`s

* Reformat and extremely minor optimisation

* Minor optimisation

* Remove unneeded let

* Fix tests.

* Additional fix.

* Minor rename.

* Bowing to the pressure.

* Stackoverflow fix (#1742)

* executive tracer builds flat traces without intermediate struct

* temporarilt commented out tests for traces

* fixed new way of building trace address

* fixed new way of building trace address

* updating state tests with flat tracing in progress

* fixed flat tracing tests

* fixed compiling ethcore-rpc with new flat traces

* removed warnings from ethcore module

* remove unused data structures
gavofyork pushed a commit that referenced this issue Jul 30, 2016
* Suicides tracing (#1688)

* tracing suicide

* fixed #1635

* fixed typo

* Stackoverflow #1686 (#1698)

* flat trace serialization

* tracing finds transaction which creates contract

* flatten traces before inserting them to the db

* Trace other types of calls (#1727)

* Trace through DELEGATECALL and CALLCODE

Add them to the JSON output and RLP database store.

* Fix tests.

* Fix all tests.

* Fix one more test.

* filtering transactions toAddress includes contract creation (#1697)

* tracing finds transaction which creates contract

* comma cleanup

Remove when following `}`s, add to final entries.

* Various improvements to tracing & diagnostics. (#1707)

* Various improvements to tracing & diagnostics.

- Manage possibility of `Account` not having code for `PodAccount`
- New RPC: `trace_sendRawTransaction`
- See raw transaction dump when inspecting over RPC

* Fix test

* Remove one of the dupe error messages

* Remove unneeded `&`s

* Reformat and extremely minor optimisation

* Minor optimisation

* Remove unneeded let

* Fix tests.

* Additional fix.

* Minor rename.

[ci:skip]

* Bowing to the pressure.

* Stackoverflow fix (#1742)

* executive tracer builds flat traces without intermediate struct

* temporarilt commented out tests for traces

* fixed new way of building trace address

* fixed new way of building trace address

* updating state tests with flat tracing in progress

* fixed flat tracing tests

* fixed compiling ethcore-rpc with new flat traces

* removed warnings from ethcore module

* remove unused data structures
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F2-bug 🐞 The client fails to follow expected behavior.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants