From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] Put a NT_PSTATUS note on solaris cores.
Date: Tue, 11 Dec 2012 15:12:00 -0000 [thread overview]
Message-ID: <20121211151136.GQ31477@adacore.com> (raw)
In-Reply-To: <50C72573.5060305@redhat.com>
> You're doing the right test. The issue is that core_pid_to_str
> calls into the gdbarch_core_pid_to_str, and that isn't expecting
> to be passed a "process pid" instead of an "LWP pid".
>
> Could you try this one when you have a chance? This is rebased on
> top of current mainline, so it restores the elfcore_write_pstatus
> call that the Unixware-excise patch removed. I made sure it builds with
> --enable-targets=all.
Nice detective work :)
(gdb) core core.26444
[New LWP 1]
Core was generated by `/[...]/simple_main'.
Program terminated with signal 5, Trace/breakpoint trap.
#0 simple_main () at simple_main.adb:4
4 simple.test_simple;
(gdb) info inferiors
Num Description Executable
* 1 process 26444 /[...]/simple_main
And with an older core file, since your patch handles it too:
(gdb) info inferiors
Num Description Executable
* 1 <core> /[...]/simple_main
I tested the patch against our testsuite again, no regression either.
So it looks all good to go!
Cheers,
--
Joel
next prev parent reply other threads:[~2012-12-11 15:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 17:37 [PATCH] solib-svr4.c: Remove old SCO-related code Pedro Alves
2012-12-10 16:44 ` Pedro Alves
2012-12-10 18:02 ` [PATCH 1/2] Put a NT_PSTATUS note on solaris cores Pedro Alves
2012-12-11 3:04 ` Joel Brobecker
2012-12-11 12:22 ` Pedro Alves
2012-12-11 15:12 ` Joel Brobecker [this message]
2012-12-11 15:16 ` Mark Kettenis
2012-12-11 16:45 ` Pedro Alves
2012-12-10 18:04 ` [PATCH 2/2] Remove all traces of Unixware Pedro Alves
2012-12-10 19:24 ` Tom Tromey
2012-12-11 2:57 ` Joel Brobecker
2012-12-11 11:37 ` Pedro Alves
2012-12-11 12:46 ` Eli Zaretskii
2012-12-11 4:20 ` Yao Qi
2012-12-11 10:59 ` Pedro Alves
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=20121211151136.GQ31477@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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