gdb konsole system crash

From: Android (android_at_oberon.pfi.lt)
Date: 11/23/05

  • Next message: Sergey N. Voronkov: "sym(4) broken on amd64 (Time to port new driver?)" 
    To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org
Date: Wed, 23 Nov 2005 08:26:42 +0200

    Hello all!

    Discovering troubles with kde-apps startup I've faced with interesting
    effect - starting of gdb konsole (as nonprivileged user) causes system
    crash.

    Here is an example:

          gdb konsole
          run

       In my case this method 100% rebooting system in 80 seconds (mysterious
    network wait).

       On konsole appears this message:
          --------------------
          android@callisto:~> gdb konsole
          GNU gdb 6.1.1 [FreeBSD]
          Copyright 2004 Free Software Foundation, Inc.
          GDB is free software, covered by the GNU General Public License, and
    you are
          welcome to change it and/or distribute copies of it under certain
    conditions.
          Type "show copying" to see the conditions.
          There is absolutely no warranty for GDB. Type "show warranty" for
    details.
          This GDB was configured as "amd64-marcel-freebsd"...(no debugging
    symbols found)...
          (gdb) run
          Starting program: /usr/local/bin/konsole
          (no debugging symbols found)...(no debugging symbols found)...(no
          debugging symbols found)...(no debugging symbols found)...(no
    debugging
          symbols found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...(no debugging symbols
          found)...warning: Unable to get location for thread creation
    breakpoint:
          generic error
          [New LWP 100082]
          (no debugging symbols found)...(no debugging symbols found)...(no
          debugging symbols found)...(no debugging symbols found)...(no
    debugging
          symbols found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...(no debugging symbols
          found)...(no debugging symbols found)...[New Thread 0x50c000 (LWP
    100082)]
          (no debugging symbols found)...(no debugging symbols
    found)...kbuildsycoca running...
          --------------------

          Then after 80 seconds:

          [New Thread 0x50c400 (LWP 100128)]

       and system reboots.

    Maybe someone has faced with such problem on amd64 platform? Could you try
    to repeat this situation on other systems, or it's only my computer
    problem?

    My system:

       android@callisto:~> uname -a
       FreeBSD callisto 6.0-STABLE FreeBSD 6.0-STABLE #0: Sat Nov 19 14:31:34
    EET 2005 root@callisto:/usr/obj/usr/src/sys/callisto amd64

    I'm keeping up my system actual, ports are updating regullary. 

    -- 
WBR Android Andrew [:]
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
  • Next message: Sergey N. Voronkov: "sym(4) broken on amd64 (Time to port new driver?)"

    Relevant Pages

    • gdb konsole system crash
      ... effect - starting of gdb konsole (as nonprivileged user) causes system ... crash. ... network wait). ...
      (freebsd-stable)
    • Unhandled exception on domain network only
      ... stored on a network drive. ... just-in-time debugging instead of this dialog box. ... Win32 Version: 1.1.4322.2032 ... CodeBase: ...
      (microsoft.public.dotnet.general)
    • Re: Memory corruption and Dump Stack trace
      ... create a dump file. ... you can use JIT debugging to invoke the debugger ... crashes very randomly and thus hard to reproduce the crash. ...
      (microsoft.public.vc.mfc)
    • Re: System Freezes When MBufClust Usages Rises
      ... When it freezes, the number of Kbytes allocated to network is roughly 160,000. ... Are there any other parameters that would help us to allocate more memory to the kernel networking? ... Remember that if you run out of clusters, you may experience network deadlocks that prevent SSH sessions from operating, so direct console access may be required to effectively monitor the system when in an extreme state of low memory in the network stack. ... My advice would be to use a serial console anyway, if possible, when debugging, as it means you can use a second machine to copy and paste DDB output into a file to e-mail out later. ...
      (freebsd-net)
    • Re: BSOD during log in
      ... Microsoft Debugging Tools are at: ... >The sudden-nature of your issue makes me suspect that it's some sort of>attack, or you're running some custom code in lsass/winlogon with a bug>related to network access. ... I guess attack is possible, but I'm behind a hardware firewall and have not loaded anything non-standard, opened any attachments, etc. ...
      (microsoft.public.win2000.cmdprompt.admin)