linuxdcpp-team team mailing list archive

[eMTee <791759@xxxxxxxxxxxxxxxxxx>]

I think gdb captures ctrl-c before the application and interrupts the
execution. Maybe a different exit key combination would fit better in
debug mode?

** Changed in: adchpp
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
https://bugs.launchpad.net/bugs/791759

Title:
  Error on closing the console

Status in ADCH++:
  Confirmed

Bug description:
  Error reproduced with rev 500 running in GDB

  OS XPpro SP3 (up to date)

  below the console output and bt result from the moment "ctrl c" is
  used

  [New Thread 2232.0xee0]

  Program received signal SIGINT, Interrupt.
  [Switching to Thread 2232.0xee0]
  0x7c87647d in KERNEL32!GetConsoleCharType ()
     from C:\WINDOWS\system32\kernel32.dll
  (gdb) bt
  #0  0x7c87647d in KERNEL32!GetConsoleCharType ()
     from C:\WINDOWS\system32\kernel32.dll
  warning: (Internal error: pc 0x3 in read in psymtab, but not in symtab.)

  warning: (Internal error: pc 0x3 in read in psymtab, but not in
  symtab.)

  warning: (Internal error: pc 0x3 in read in psymtab, but not in
  symtab.)

  #1  0x00000004 in ?? (warning: (Internal error: pc 0x3 in read in psymtab, but n
  ot in symtab.)

  ) at ./adchpp/Exception.h:32
  warning: (Internal error: pc 0x3 in read in psymtab, but not in symtab.)

  warning: (Internal error: pc 0x0 in read in psymtab, but not in
  symtab.)

  #2  0x7c80b729 in KERNEL32!GetModuleFileNameA ()
     from C:\WINDOWS\system32\kernel32.dll
  #3  0x00000000 in ?? ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/adchpp/+bug/791759/+subscriptions