From: Joel Brobecker <brobecker@adacore.com>
To: Yuri <yuri@rawbw.com>
Cc: Tom Tromey <tromey@redhat.com>,
gdb@sourceware.org, Steven Kreuzer <skreuzer@FreeBSD.org>
Subject: Re: 7.3 is broken on FreeBSD
Date: Thu, 07 Jul 2011 04:32:00 -0000 [thread overview]
Message-ID: <20110707043156.GA15572@adacore.com> (raw)
In-Reply-To: <4E15165A.10303@rawbw.com>
> gdb-7.3 crashes on this line:
> 563 dr_status_mirror = i386_dr_low.get_status ();
> (gdb) p i386_dr_low
> $1 = {set_control = 0, set_addr = 0, reset_addr = 0, get_status = 0,
> unset_status = 0, debug_register_length = 0}
But i386_dr_low is supposed to be set at GDB startup by
_initialize_i386fbsd_nat:
void
_initialize_i386fbsd_nat (void)
{
struct target_ops *t;
/* Add some extra features to the common *BSD/i386 target. */
t = i386bsd_target ();
#ifdef HAVE_PT_GETDBREGS
i386_use_watchpoints (t);
i386_dr_low.set_control = i386bsd_dr_set_control;
i386_dr_low.set_addr = i386bsd_dr_set_addr;
i386_dr_low.reset_addr = i386bsd_dr_reset_addr;
i386_dr_low.get_status = i386bsd_dr_get_status;
i386_set_debug_register_length (4);
#endif /* HAVE_PT_GETDBREGS */
Is this happening? And if yes, then who is overriding the value?
If not, why is it not happening, since you confirmed that
HAVE_PT_GETDBREGS is defined.
--
Joel
next prev parent reply other threads:[~2011-07-07 4:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 20:41 Yuri
2011-07-06 20:59 ` Tom Tromey
2011-07-06 21:40 ` Yuri
2011-07-06 22:42 ` Joel Brobecker
2011-07-06 22:47 ` Yuri
2011-07-06 22:55 ` Joel Brobecker
2011-07-06 23:12 ` Yuri
2011-07-06 23:24 ` Joel Brobecker
2011-07-06 23:41 ` Yuri
2011-07-07 1:59 ` Joel Brobecker
2011-07-07 2:14 ` Yuri
2011-07-07 4:32 ` Joel Brobecker [this message]
2011-07-07 5:48 ` Yuri
2011-07-07 14:18 ` Tom Tromey
2011-07-06 23:39 ` Yuri
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=20110707043156.GA15572@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=skreuzer@FreeBSD.org \
--cc=tromey@redhat.com \
--cc=yuri@rawbw.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