There is an extension called Phoenix Editor that can unpack files so if somebody implements it they could look at how Phoenix unpacks the file. At least it would be a step in the right direction.
On Jan 27, 9:32 pm, Nicolas Hatier <[email protected]> wrote: > Mid-line breakpoints will be very useful. > > However, for minified content, unpacking could also be a must, as code > like this is hard to follow, even with mid-line breakpoints: > > (function(E,B){function ka(a,b,d){if(d === B&&a.nodeType === > 1){d=a.getAttribute("data-"+b);if(typeof d === "string"){try{d=d === > "true"?true [...] > > Unminified code is obviously easier to read: > > (function(E, B){ > function ka(a, b, d){ > if (d === B && a.nodeType === 1){ > d = a.getAttribute("data-" + b); if (typeof d == = "string"){ > try{ > d = d === "true" ? true > : d === "false" ? false > : d === "null" ? null > : !c.isNaN(d) ? parseFloat(d) > : Ja.test(d) ? c.parseJSON(d): d > } > catch (e){} > c.data(a, b, d) > } > else > d = B > } > return d > } > > And code packed with known packers is not debuggable as-is, as it's > usually encoded some way, then eval()ed: > > eval(function(p,a,c,k,e,r)[... unpacking function ...]('(7(E,B){7 > 2u(a,b,d){6(d===B&&a.1d===1){d=a.21("16-"+b);6(13 > d==="1e"){1N{d=d==="12"?12:d==="10"?10:d==="14"?14:!c.2v(d)?22(d):3b.1f(d)?c.3c(d):d}1O(e){}c.16(a,b,d)}V > d=B}P d}7 U(){P 10}7 4i(){P [...] > > If it's possible to detect the packer, unpack, and debug the unpacked > code, now we can get somewhere. > > NH > > On 2011-01-27 13:24, Les wrote: > > > This might be helpful: > > >http://peter.sh/2011/01/css-value-autocompletion-window-onerror-and-i... > > > "Furthermore, a change has been committed which is a first step in > > supporting breakpoints on arbitrary positions on a line, which would > > be convenient for compressed scripts." -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
