On 1/27/11, Nicolas Hatier <[email protected]> wrote: > Mid-line breakpoints will be very useful. >
Yeah. I was thinking of that as feature "break on statement". > However, for minified content, unpacking could also be a must, as code > like this is hard to follow, even with mid-line breakpoints: > Exactly. As you've shown with your example, code can be interpreted and reformatted. And JJB says its possible to do it in Firebug, so its just a matter of refining and then implementing it. Easier said than done! [snip example] > And code packed with known packers is not debuggable as-is, as it's > usually encoded some way, then eval()ed: > There are a lot of sites that use minified code but don't use packer. Most cases of minified code can be covered without support for packer and such. Maybe that can be added later. > If it's possible to detect the packer, unpack, and debug the unpacked > code, now we can get somewhere. > Jsbeautifier at http://jsbeautifier.org/ can handle packer and a couple others so it is possible. The first version of "debug obfuscated script" could hold off on Packed scripts. I think it could go in the script tab menu: [Script v] | [*] Enabled | Deobfuscate (New!) | Decompile for eval() source | Show chrome sources | Track throw/catch -- Garrett -- 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.
