From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: emacs-devel@gnu.org
Subject: Re: Stak dump with tar.[bz2/gz] files (Cygwin)
Date: Sat, 14 Jun 2008 13:41:26 +0300 [thread overview]
Message-ID: <uprqkl2nd.fsf@gnu.org> (raw)
In-Reply-To: <485302BE.5040607@alice.it>
> Date: Sat, 14 Jun 2008 01:29:02 +0200
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> CC: emacs-devel@gnu.org
>
> Eli Zaretskii ha scritto:
>
> > You can put a breakpoint on a function even if its sources are
> > not available.
>
> How?
Like with any other function:
(gdb) break open_stackdumpfile
The argument to the "break" command can be:
. a line number ("break 123")
. an offset ("break +10" or "break "-20")
. a function name ("break func") -- this is your case
. a file name and line number ("break foo.c:123")
. a file name and a function name ("break foo.c:func")
. an address ("break *0x12345678" or "break &expr")
See the node "Specify Location" in the GDB manual for more info.
next prev parent reply other threads:[~2008-06-14 10:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 12:37 Stak dump with tar.[bz2/gz] files (Cygwin) Angelo Graziosi
2008-06-12 16:05 ` Stefan Monnier
2008-06-12 20:00 ` Angelo Graziosi
2008-06-12 21:34 ` Stefan Monnier
2008-06-12 21:56 ` Angelo Graziosi
2008-06-13 1:42 ` Stefan Monnier
2008-06-13 6:46 ` Eli Zaretskii
2008-06-13 15:53 ` Angelo Graziosi
2008-06-13 16:41 ` Eli Zaretskii
2008-06-13 6:36 ` Eli Zaretskii
2008-06-13 15:45 ` Angelo Graziosi
2008-06-13 16:39 ` Eli Zaretskii
2008-06-13 23:29 ` Angelo Graziosi
2008-06-14 10:41 ` Eli Zaretskii [this message]
2008-06-15 1:29 ` Angelo Graziosi
2008-06-15 3:29 ` Eli Zaretskii
2008-06-15 12:50 ` Angelo Graziosi
2008-06-15 18:05 ` Eli Zaretskii
2008-06-15 21:45 ` Angelo Graziosi
2008-06-16 18:12 ` Eli Zaretskii
2008-06-16 20:41 ` Angelo Graziosi
2008-06-17 3:06 ` Eli Zaretskii
2008-06-17 8:23 ` Angelo Graziosi
2008-12-23 19:45 ` Angelo Graziosi
2008-12-23 19:51 ` Angelo Graziosi
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=uprqkl2nd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=angelo.graziosi@alice.it \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.