From: Chris January <chris.january@allinea.com>
To: Daniel Jacobowitz <dan@codesourcery.com>
Cc: Hui Zhu <teawater@gmail.com>, gdb@sourceware.org
Subject: Re: [RFC] make gdb handle weak function better
Date: Wed, 18 Aug 2010 08:17:00 -0000 [thread overview]
Message-ID: <1282119424.1953.1.camel@gumtree> (raw)
In-Reply-To: <20100811203057.GA25122@caradoc.them.org>
On Wed, 2010-08-11 at 16:31 -0400, Daniel Jacobowitz wrote:
> That makes sense, although it may be system-specific. Even better
> would be to revisit our support for multiple-location breakpoints.
> "break calloc" ought to stop on every instance of calloc.
Aside from breakpoints you still need to know which 'calloc' the dynamic
linker has bound in order to evaluate function calls, i.e.
print calloc(100)
ought to call the same 'calloc' as the inferior.
Regards,
Chris
This e-mail message may contain confidential and/or privileged information. If you are not an addressee or otherwise authorized to receive this message, you should not use, copy, disclose or take any action based on this e-mail or any information contained in the message.
If you have received this material in error, please advise the sender immediately by reply e-mail and delete this message. Thank you.
Allinea Software Limited: Registered in England and Wales No: 6871298
Registered Address: The Innovation Centre, Warwick Technology Park, Gallows Hill, Warwick, CV34 6UW, United Kingdom
next prev parent reply other threads:[~2010-08-18 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 9:04 Hui Zhu
2010-08-11 3:21 ` Hui Zhu
2010-08-11 8:05 ` Chris January
2010-08-11 20:31 ` Daniel Jacobowitz
2010-08-12 3:17 ` Hui Zhu
2010-08-18 8:17 ` Chris January [this message]
2011-08-09 9:11 ` Hui Zhu
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=1282119424.1953.1.camel@gumtree \
--to=chris.january@allinea.com \
--cc=dan@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=teawater@gmail.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