From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30435 invoked by alias); 14 Oct 2016 15:21:41 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 30426 invoked by uid 89); 14 Oct 2016 15:21:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=ham version=3.3.2 spammy=H*MI:trinity, HImportance:normal, remotely X-HELO: mout.gmx.net Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.15.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 14 Oct 2016 15:21:39 +0000 Received: from [78.43.42.46] by 3capp-gmx-bs30.server.lan (via HTTP); Fri, 14 Oct 2016 17:21:36 +0200 MIME-Version: 1.0 Message-ID: From: deffo@gmx.de To: gdb@sourceware.org Subject: GDB does not stop at assembly code address Content-Type: text/plain; charset=UTF-8 Date: Fri, 14 Oct 2016 15:21:00 -0000 Sensitivity: Normal X-UI-Out-Filterresults: notjunk:1;V01:K0:YC8UAZj886w=:tcvnPEREbmK7aAKH91+ymA cTHupl68syUKS9mNRqUZWk7g/xfDJ+kVdf0TVPZdaB/5wFYHQLXtUqmi/0fi9U/fBUIkhnqoR ZYBq52ITMD9aSZTftQA/bCrYIkLg3OxnrpcZ8l/rAWo/SY7i+n00cGi2KqL1ZTjFFE80wz1ma B5HLysie24dAeoUk8UtI2rhbPp1/fuhOomgNrr82olHEp1yk1ksq4kLn4hzUIoRcVRgSF318t Hmeqv2ygPG0ppagFuJr14tNtZpbNX0m9eTyKlG7cyG+HmdCUuEJrrH3tvcMfuzbsR4UNqeaUP DhFwboHlL/qBEWVrTEgV4/UfDrMcxKZhis9o4KQfoEJtd6O1xInjY4kQ4WrE0bs1vF1J7itEm 59Y4UOgRreZeBwwuhInCeBPOXx9MTCoW84hUlRPjCyrwCuKvcGrOhpk14xpi7gVJ8lU5W+quA +rIW5dlyWA== X-SW-Source: 2016-10/txt/msg00024.txt.bz2 Hi there, I'm currently debugging the 32 bit Linux Kernel 4.8.1 remotely with GDB and Qemu i386 2.7. My GDB script looks like this: target remote localhost:10000 source . symbol-file vmlinux set width 0 set height 0 set verbose off b rest_init commands continue end b console_init commands continue end b start_kernel commands continue end b startup_32 commands continue end continue Now apparently I'm missing something, since the breakpoints in C land, that is start_kernel, console_init, rest_init are recognized as breakpoints and thus jumped at by GDB just fine. What does not work is the breakpoint on startup_32, which is still in Assembly land. GDB just jumps over it as if it wasn't called, but it is definitely called since it's the 32-bit kernel entrypoint. Is this due to some real-mode/protected-mode fiddlings? Best regards, J.