From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 61138 invoked by alias); 18 Oct 2016 16:53:12 -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 58139 invoked by uid 89); 18 Oct 2016 16:53:10 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_ASCII_DIVIDERS,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_WEB,SPF_PASS autolearn=no version=3.3.2 spammy=disp, startup_32, vmlinux, start_kernel X-HELO: mout.gmx.net Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.15.19) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 18 Oct 2016 16:53:09 +0000 Received: from [78.43.42.24] by 3capp-gmx-bs05.server.lan (via HTTP); Tue, 18 Oct 2016 18:53:05 +0200 MIME-Version: 1.0 Message-ID: From: deffo@gmx.de To: qiyaoltc@gmail.com Cc: gdb@sourceware.org Subject: Re: GDB does not stop at assembly code address Content-Type: text/plain; charset=UTF-8 Date: Tue, 18 Oct 2016 16:53:00 -0000 Sensitivity: Normal Content-Transfer-Encoding: quoted-printable X-UI-Out-Filterresults: notjunk:1;V01:K0:kl09u6xws/4=:mJVAB47xDAv9vYRTDxYwTU HDVfxGem3X39AKBdsveluX7Ll2dzn+zMt2HsOHg8jwO6zmSl8jTx9dbb/ZM1+yeYHG3A7hCpl eQ/gUycXE6+KDyefH5lvoLXqjPAtG9NaVoH3jFjsk0qcsfoHkkRC9MPTjnGB9al+ICEI0FigR vH2MZUAFem+zC4DaqJEaKes9hZEpVMXrK1djQXQBEQJ6E67oCotDTWW68FThIIYRUl/2QQhyA zzxTnW63By3Ece+D/4zSsScHpPIFyvdJyVE0CJkVrcxiBWt/AWVbj7P7qn/52S42BxoOwEICg 7HGN3w5XFETDnELF0QfKbz5J0NxOv/j1e03ex81LSNX6CfLLYWHpKog4aFTszZxdlO/tX0ujV 2ZSwgETBHuBew98onLNia3pFl2gc1UaJZ8sYC86ryPFAUTv6S2SsvzNsriz09gE4YqSJaI9jl 3ayZpwBLuw== X-SW-Source: 2016-10/txt/msg00027.txt.bz2 Here's the output: (gdb) b startup_32 Breakpoint 1 at 0xc1000000: file arch/x86/kernel/head_32.S, line 97. (gdb) print startup_32 $1 =3D {} 0xc1000000 (gdb) info breakpoints Num Type Disp Enb Address What 1 breakpoint keep y 0xc1000000 arch/x86/kernel/head_32.S:97 (gdb) b start_kernel Breakpoint 1 at 0xc1be3755: file init/main.c, line 480. (gdb) print start_kernel $1 =3D {void (void)} 0xc1be3755 (gdb) info breakpoints Num Type Disp Enb Address What 1 breakpoint keep y 0xc1be3755 in start_kernel at init/main.c:4= 80 I guess the "no debug info" would be the explanation, but why is that? The = address is listed as a FUNC in readelf -Ws vmlinux, thus it should be corre= ct. What do I have to do? ---------------------------------------------------------------------------= ------------------- What is startup_32 address and where does GDB set breakpoint? You can do "print startup_32" and "info breakpoints" to get the answer of two questions above. --=20 Yao (=E9=BD=90=E5=B0=A7)