Open HarryR opened 6 years ago
Seems like the problem is with interface
being used, and abstract classes for that, which cause undefined
entries to be included in the sources
variable in truffle-debugger
.
The solution was found on https://github.com/trufflesuite/truffle/issues/1051 - and hopefully will be included in the next version, but in the meantime the workarounds are listed on that ticket.
Will close this issue when upstream fix is pushed through.
The fix has been pushed through https://github.com/trufflesuite/truffle/pull/1084 - but this is on the @develop branch and I'm not sure if it'll be backported to 4.1.14 or of 5.x is in a workable state at the moment.
In the meantime the patch can be applied manually to the cli.bundled.js
file, at around the 200k line offset, to get it working.
@HarryR develop
targets v4.1.x right now, so that'll go out with v4.1.14 next time we do a release.
It sounds like you've been getting familiar with the debugger. Please keep us informed as you find workarounds and/or fixes. Thanks!
The truffle debugger is buggered,
See:
Using truffle 5.0 ('next') prevents project from deploying (it errors out during migrations)
Truffle v4.1.13 cannot debug my stuff
Truffle v4.1.11 cannot debug my stuff due to other reasons (as per the ticket)
Truffle v4.1.10 can't debug stuff for same reason as 4.1.11
Truffle 4.1.5 cannot deploy contracts:
Have to use truffle 4.1.13 because there's a bug when retrieving transaction receipts that we cannot live without, cannot use earlier versions for some reason.
I think the problem is that some of the new constructs being used by the contracts are broken with Truffle, or the newer solidity compiler is outputting a source map which is incompatible with the debugger. With Truffle 4.1.13 everything works fine, apart from debugging.
Stuff being used:
constructor
This is making it painful to develop at the moment, without the debugger - if something goes wrong it sucks to find out what's gone wrong.