Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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: Wed, 06 Jul 2011 22:55:00 -0000	[thread overview]
Message-ID: <20110706225535.GW15572@adacore.com> (raw)
In-Reply-To: <4E14E5D2.1080009@rawbw.com>

> >Program received signal SIGSEGV, Segmentation fault.
> >[Switching to Thread 8018041c0 (LWP 101940)]
> >Can you look at gdb/config.in in the build directory, and tell
> >me if the following macro is defined?
> >
> >         HAVE_PT_GETDBREGS
> 
> I have #undef HAVE_PT_GETDBREGS

That explains it why you get the SEGV...

> >I don't have FreeBSD 8.2 lying around, can you see if
> >PT_GETDBREGS is defined in /usr/include/sys/ptrace.h?
> 
> 
> #define PT_GETDBREGS    37      /* get debugging registers */

But that doesn't explain why it's undef'ed in your case. For that,
you're going to have to look inside the gdb/config.log file,
and search for PT_GETDBREGS.  It should tell you that the compilation
failed, what source file was used, and why it failed.

-- 
Joel


  reply	other threads:[~2011-07-06 22:55 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 [this message]
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
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=20110706225535.GW15572@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