From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gdb-patches@sourceware.org
Subject: [commit] Fix inf-ttrace.c
Date: Sat, 29 Oct 2005 21:31:00 -0000 [thread overview]
Message-ID: <200510292122.j9TLMi5J001048@elgar.sibelius.xs4all.nl> (raw)
I'm not sure what happened here, but while checking out some other
HP-UX related changes, I discovered that gdb didn't work properly on
HP-UX anymore. Turns out GDB doesn't really like
TARGET_WAITKIND_EXECD events. Either this broke somewhere along the
line, or I accidentally comitted a inf-ttrace.c that didn't work.
Since the exec following stuff needs some major surgery anyway, I'll
commit this now, such that we have at least working HP-UX support in
the next release.
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* inf-ttrace.c (inf_ttrace_wait): Comment out TARGET_WAITKIND_EXEC
code; return TARGET_WAITKIND_STOPPED instead.
Index: inf-ttrace.c
===================================================================
RCS file: /cvs/src/src/gdb/inf-ttrace.c,v
retrieving revision 1.15
diff -u -p -r1.15 inf-ttrace.c
--- inf-ttrace.c 28 Oct 2005 18:20:35 -0000 1.15
+++ inf-ttrace.c 29 Oct 2005 21:18:31 -0000
@@ -894,6 +894,10 @@ inf_ttrace_wait (ptid_t ptid, struct tar
#endif
case TTEVT_EXEC:
+ /* FIXME: kettenis/20051029: GDB doesn't really know how to deal
+ with TARGET_WAITKIND_EXECD events yet. So we make it look
+ like a SIGTRAP instead. */
+#if 0
ourstatus->kind = TARGET_WAITKIND_EXECD;
ourstatus->value.execd_pathname =
xmalloc (tts.tts_u.tts_exec.tts_pathlen + 1);
@@ -902,6 +906,10 @@ inf_ttrace_wait (ptid_t ptid, struct tar
tts.tts_u.tts_exec.tts_pathlen, 0) == -1)
perror_with_name (("ttrace"));
ourstatus->value.execd_pathname[tts.tts_u.tts_exec.tts_pathlen] = 0;
+#else
+ ourstatus->kind = TARGET_WAITKIND_STOPPED;
+ ourstatus->value.sig = TARGET_SIGNAL_TRAP;
+#endif
break;
case TTEVT_EXIT:
next reply other threads:[~2005-10-29 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 21:31 Mark Kettenis [this message]
2005-10-30 23:28 ` Daniel Jacobowitz
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=200510292122.j9TLMi5J001048@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
/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