Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Blacquiere <blacq@slingshot.co.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Howto single step from beginning
Date: Thu, 02 Feb 2006 03:20:00 -0000	[thread overview]
Message-ID: <20060202162030.wkcswswwo08wsosc@webmail.slingshot.co.nz> (raw)
In-Reply-To: <20060202025704.GA21125@nevyn.them.org>

> First, assuming that this is a dynamically linked application, try
> "set stop-on-solib-events 1".  That'll stop you way back in the dynamic
> linker.  From there you may be able to single-step to _start; it gets
> called from something like _dl_start_user.

pretty sure it is static
gcc -g --static -o test test.c

result as follows:
-------------------------------
(gdb) set stop-on-solib-events 1
(gdb) run
Starting program: /home/blacq/src/bin/test

Program received signal SIGILL, Illegal instruction.
0x00008094 in _start ()
(gdb)
------------------------------

>
> Secondly, does it work outside of GDB?

Yup, sorry forgot to mention earlier.

> If so, I'd suspect that the
> breakpoint GDB has invisibly placed at _start (which it always does)
> is causing SIGILL instead of SIGTRAP.  There was some change in this
> area for ARM/Linux recently.  If your kernel is too old, perhaps
> GDB is using a breakpoint that it doesn't support.  Or maybe it's GDB
> that's too old.  Check with "set debug target 1" before running to see
> what bytes it's inserting, then check your kernel sources (esp.
> arm/kernel/ptrace.c and arm/kernel/traps.c) to see which breakpoints
> it expects.
>

Your description seems very feasible, as I am using Linux kernel 2.6.12.

I will investigate this further.

PaulB.




  reply	other threads:[~2006-02-02  3:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02  1:08 Paul Blacquiere
2006-02-02  1:26 ` Daniel Jacobowitz
2006-02-02  2:52   ` Paul Blacquiere
2006-02-02  2:57     ` Daniel Jacobowitz
2006-02-02  3:20       ` Paul Blacquiere [this message]
2006-02-02  4:45       ` Paul Blacquiere
2006-02-02  5:07         ` Daniel Jacobowitz
2006-02-02  5:29           ` Paul Blacquiere
2006-02-02 13:52             ` Daniel Jacobowitz
2006-02-03  0:09               ` Paul Blacquiere

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060202162030.wkcswswwo08wsosc@webmail.slingshot.co.nz \
    --to=blacq@slingshot.co.nz \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox