Re: [Kgdb-bugreport] [PATCH][1/3] Update CVS KGDB's serial driver

From: Tom Rini (trini_at_kernel.crashing.org)
Date: 02/26/04

  • Next message: Hansjoerg Lipp: "Re: [PATCH] Linux 2.6: shebang handling in fs/binfmt_script.c" 
    Date:	Wed, 25 Feb 2004 16:18:28 -0700
To: George Anzinger <george@mvista.com>

    On Wed, Feb 25, 2004 at 03:10:03PM -0800, George Anzinger wrote:

    > Convention has been that control C does the break. If I read this
    > correctly you are saying that any character does it.

    There are two cases. One is that kgdb is not connected (so it's not
    active) and since we're the int handler, someone wants to connect. This
    lets us do very nice things like break in any old time (gdb doesn't need
    to be modified to send a ^C before it's first packet, etc). The second
    case is that we have connected, we've issued a few commands, continued,
    and we want to break in now, so we ^C in gdb (which sends a ^C to the
    target) and we do what we've got to do.

    So perhaps, and I haven't read all of the code again to verify this,
    kgdb_connected could be eliminated in favor of debugger_active.

    > If that is the intent
    > and it works, then the whole buffer interrupt characters thing can be
    > removed. In fact, an interrupt implies we are not in kgdb (it holds all
    > interrutps off) so that test, too, can go. The interrupt thing then
    > reduces to a breakpoint.

    I'll give that a shot tomorrow and see what happens. 

    -- 
Tom Rini
http://gate.crashing.org/~trini/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: Hansjoerg Lipp: "Re: [PATCH] Linux 2.6: shebang handling in fs/binfmt_script.c"

    Relevant Pages

    • Re: User mode drivers: part 1, interrupt handling (patch for 2.6.11)
      ... > Xen just posted patches for using kgdb between two instances but I ... > don't see how they get out of the interrupt acknowledge problem ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Animosity on the part of Mr Richard Heathfield
      ... And it is you, not me, who have tarnished your character. ... to interrupt a technical discussion to call a person racist. ... no control (e.g. ethnicity, gender), but on the way that they behave. ... an apology for what I said, and I'd send them a present in good will. ...
      (comp.lang.c)
    • Re: writing ISR for UART
      ... so if the interrupt handler adds a character to the queue while ... and a little care to avoid buffer overflows) is safe on ... detect whether a character is available. ...
      (comp.arch.embedded)
    • Re: TN3270 - Why it still synchronous ?
      ... >> interface each byte sent from the terminal generated an interrupt. ... > result is far fewer resources being used for each character ((especially since ... block mode terminals would ... armful of cpu whenever anyone hit the tx tit, ...
      (comp.os.vms)
    • Re: reading on serial port slow...
      ... FIFO has some characters waiting but no new ones have arrived ... IIRC "a while" is a few character times. ... the port to signal an interrupt after each character. ...
      (comp.os.linux.development.system)