From: Simon Marchi <simark@simark.ca>
To: Nan Xiao <xiaonan830818@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: The newest gdb 8.3 crash on OpenBSD
Date: Mon, 03 Feb 2020 17:00:00 -0000 [thread overview]
Message-ID: <aa755de4-0ef9-908c-4d5f-be44424bbb02@simark.ca> (raw)
In-Reply-To: <CA+MhoaO7b3=OZ5y-sMOfNhV6UJ5MD_Oa6UOMzd=Kcz+X0sPzUQ@mail.gmail.com>
On 2020-02-01 5:47 a.m., Nan Xiao wrote:
> Hi Simon,
>
> Thanks very much for your reply!
>
> Yes, you are correct! After checking gdb/config.h, I found all ptrace
> related macros are undefined:
>
> /* Define if sys/ptrace.h defines the PTRACE_GETFPXREGS request. */
> /* #undef HAVE_PTRACE_GETFPXREGS */
>
> /* Define if sys/ptrace.h defines the PTRACE_GETREGS request. */
> /* #undef HAVE_PTRACE_GETREGS */
>
> /* Define to 1 if you have the <ptrace.h> header file. */
> /* #undef HAVE_PTRACE_H */
>
> /* Define if sys/ptrace.h defines the PT_GETDBREGS request. */
> /* #undef HAVE_PT_GETDBREGS */
>
> /* Define if sys/ptrace.h defines the PT_GETXMMREGS request. */
> /* #undef HAVE_PT_GETXMMREGS */
>
> I checked the header files, there is no /usr/include/ptrace.h. There
> is /usr/include/sys/ptrace.h, but the real definitions (such as
> PT_GETREGS, PT_SETREGS, etc) are in system related header files. E.g.,
> in my OS, it is in /usr/include/amd64/ptrace.h. I checked OpenBSD's
> gdb port (gdb 7.12.1, http://openports.se/devel/gdb), it seems I need
> more tweak to make gdb work on OpenBSD, not as simple as just
> "configure" and "make".
>
> Anyway, thanks very much again for your time and help!
>
> Best Regards
>
> Nan Xiao
Ok, it would be nice if GDB worked, instead of crashed, with a simple ./configure && make on
OpenBSD. If you manage to make it work, please consider sending a patch so that other users
don't bump into this problem!
Simon
next prev parent reply other threads:[~2020-02-03 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 5:44 Nan Xiao
2020-01-30 4:21 ` Simon Marchi
2020-02-01 10:47 ` Nan Xiao
2020-02-03 17:00 ` Simon Marchi [this message]
2020-02-04 9:20 ` Nan Xiao
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=aa755de4-0ef9-908c-4d5f-be44424bbb02@simark.ca \
--to=simark@simark.ca \
--cc=gdb@sourceware.org \
--cc=xiaonan830818@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