Breakpoints and logpoints

Поделиться
HTML-код
  • Опубликовано: 2 авг 2024
  • Discover 5 different ways to debug your code beyond console.log - Discover the breakpoints, debugger statements, logpoints, conditional breakpoints, including pause at exceptions.
    Chapters:
    0:00 Introduction
    0:18 Breakpoints
    0:24 Cleaning up call stack
    0:34 Live edit in the Scope pane
    0:42 Live edit in the Console
    0:52 debugger statement
    1:02 Never pause here
    1:18 Conditional breakpoints
    1:56 Logpoints
    2:25 Pause at exceptions
    Resources:
    Learn more → goo.gle/devtools-breakpoints
    Demo → goo.gle/3mzWTmE
    Questions? Tweet to us:
    Jecelyn Yeen → goo.gle/jecfish
    Chrome DevTools → goo.gle/chromedevtools
    Catch more DevTools Tips → goo.gle/DevToolsTips
    Subscribe to Google Chrome Developers → goo.gle/ChromeDevs
    #DevToolsTips
  • НаукаНаука

Комментарии • 23

  • @ChromeDevs
    @ChromeDevs  Год назад +10

    Subscribe for the latest → goo.gle/ChromeDevs

  • @user-hc4ci1yq1z
    @user-hc4ci1yq1z 8 месяцев назад +7

    the 'for loop' conditional breakpoint is mind blowing! it will save me a lot of time if i had to run a "huge" loop in my JS code next time. I wonder if this is a common feature if other types of programming languages.

  • @bendtherules0
    @bendtherules0 Год назад +3

    "Never pause here" is a very innovative use for conditional breakpoints. I didn't know that breakpoint condition overrides debugger statements (many websites use debugger statements to make it harder to see this code).

  • @RiccardoMares
    @RiccardoMares 11 месяцев назад +3

    My preferred debugging trick is the "overrides" feature :)
    I love it, because - as a SEO - I usually debug on sites where I can't edit the source code.
    It's the best way to suggest modifications to devs who couldn't find them ;)

  • @runthecode_
    @runthecode_ Год назад +5

    Log points and conditional breakpoints are sick 🔥

  • @sle6423
    @sle6423 Год назад +3

    Logpoints are my favorite, especially when debugging focus issues

  • @krasimirk
    @krasimirk Год назад +2

    great explain. especially for the conditional breakpoints !

  • @sagormajomder
    @sagormajomder Год назад

    Great explanation! Thank you

  • @barusuuu
    @barusuuu 11 месяцев назад

    great and easy to following video, thanks!

  • @StephenChapman
    @StephenChapman Год назад +2

    As someone deeply interested in reverse engineering web apps, all these recent changes to the debugger are incredibly useful! Thank you for covering them!

    • @jecjecfish
      @jecjecfish Год назад +1

      Hey Stephen, I am curious to knw which new debugging features are helpful for you!

    • @StephenChapman
      @StephenChapman Год назад +1

      ​@@jecjecfish Hey, Jecelyn! Conditional BPs are really a game-changer for me. That, and the ability to have header local overrides! As for debugging, anything that gets DevTools closer to the core functionality of, say, x64dbg, is a huge boon for me. I spend a lot of time debugging webapps and Electron apps these days (I come from a world of reversing win32 apps), so features like conditional breakpoints are incredibly useful for me!
      If I had ONE single feature request, it would be the ability to have app-wide/side-wide memory scanning functionality for values (perhaps within the Memory tab). I imagine this as perhaps taking a snapshot of the current state of the app first, then scanning all of it for a specified value. For instance, if I know there's a truncated float value of 9999 or a string value of 'jecjecfish', I'd specify that value for my search, then any results would be returned from wherever that value is found -- whether it's in the heap, the comment of a source file, the rendered HTML, a cookie, a query param from a request that happened, local/session storage -- anywhere!
      I understand that's no small feat, and it's probably too edge-case of a feature to ever see, but it would save me so much time that I currently spend searching for certain values -- especially ones that reside in the heap where I seemingly cannot search the results for an exact value (say, 9999) irrespective of where it's instantiated (say, a class name of _0xbeefee).
      Anyway, thank you so much for the videos you do and information you share! I'm a regular lurker, but all these new debugger features have me super-excited. =)

  • @ariosetiawan173
    @ariosetiawan173 Год назад

    This really really useful Thanksssss

  • @abdulkhader567
    @abdulkhader567 8 месяцев назад

    OMG, conditional breakpoints, this is awesome.

  • @MD-zn1jz
    @MD-zn1jz 11 месяцев назад

    How to use a helper function with a console log and see when the helper function was called but not when console log call inside helper?

  • @christopherderrell8470
    @christopherderrell8470 Год назад

    Lol, love the shirt! 😂

  • @user-gu5ts5nx8r
    @user-gu5ts5nx8r Год назад

    very useful

  • @eloka9015
    @eloka9015 Год назад

    I feel like i'm never going to understand this.

  • @veber88
    @veber88 11 месяцев назад

    Im debuuging in the head. You all are wick by using developer tools to debug smth.

  • @lllllllllIIIIIIIIIIl
    @lllllllllIIIIIIIIIIl Год назад +4

    ... What?

  • @user-io4dy9vz5v
    @user-io4dy9vz5v 26 дней назад

    thanks for not explaining anything

  • @user-nd7wv4jy8g
    @user-nd7wv4jy8g 11 месяцев назад

    not helpful

  • @iiiftttcc-by-sa4.o6224-
    @iiiftttcc-by-sa4.o6224- Год назад

    00:36 ขอบคุณวีดีโอของคุณที่นำเสนอ google โครมให้ผู้คนเข้าใจผมได้เข้ามาชมวีดีโอของคุณแล้วคุณทำได้ดีมาก👍✨👈