From: Jim Blandy <jimb@redhat.com>
To: ankit thukral <ankit_plug@yahoo.com>
Cc: gdb@sources.redhat.com
Subject: Re: Internal breakpoints
Date: Wed, 01 Oct 2003 06:45:00 -0000 [thread overview]
Message-ID: <vt2wubplato.fsf@zenia.home> (raw)
In-Reply-To: <20031001061818.32778.qmail@web60102.mail.yahoo.com>
ankit thukral <ankit_plug@yahoo.com> writes:
> -2 shlib events keep y 0x4000c9c0
> <_dl_debug_state_internal>
> breakpoint already hit 3 times
The dynamic linker in the program being debugged calls this function
each time it loads or unloads a shared library. GDB sets this
breakpoint so it can keep its copy of the shared library table up to
date.
> -7 longjmp keep n 0x4000f870 <longjmp>
> -8 longjmp keep n 0x42027240 <siglongjmp>
> -9 longjmp keep n 0x42027240 <siglongjmp>
> -10 longjmp resume keep n 0x00000000
GDB needs to be able to recognize calls to longjmp, to avoid losing
control of the program, to make sure watchpoints on local variables in
frames popped by the longjmp are disabled, and so on.
You'll need to look at breakpoint.c for more detail.
next prev parent reply other threads:[~2003-10-01 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 6:18 ankit thukral
2003-10-01 6:45 ` Jim Blandy [this message]
2003-10-01 20:15 ` Eli Zaretskii
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=vt2wubplato.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=ankit_plug@yahoo.com \
--cc=gdb@sources.redhat.com \
/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