From: Andrew Cagney <cagney@redhat.com>
To: frysk <frysk@sources.redhat.com>
Subject: Re: meeting 2008-03-19 - version numbers
Date: Wed, 19 Mar 2008 16:00:00 -0000 [thread overview]
Message-ID: <47E13887.3050905@redhat.com> (raw)
In-Reply-To: <47E12D0D.1020309@redhat.com>
Tromey, on irc, was asking what in the below is new:
Andrew Cagney wrote:
> Here's a transcript from using the hpd today (please note kernel
> "issues" mean it may not work on your system):
>
> $ ./frysk/bindir/fhpd ./frysk/pkglibdir/funit-hello
> [0.0] Loaded executable file:
> /home/scratch/frysk/git/native/frysk-core/./frysk/pkglibdir/funit-hello
> (fhpd) run
> Attached to process 7518
> starting/running with this command: ./frysk/pkglibdir/funit-hello
> Running process 7518
> (fhpd) Task 7518 is terminating from signal SIGSEGV(11)
It's here. Previously the behavior was:
(fhpd) Task 9989 is terminating from signal SIGSEGV(11)
focus
Target set pid id path-to-executable
(fhpd)
notice how the thread isn't a member of the focus group as it wasn't
being stopped during termination; it now is. Being able to wait until a
process really is terminating makes things easier; you don't have to
second guess which of many potential signals will be lethal. Instead
just wait for the lethal signal to come along.
> list
> [0.0]
> 34 // exception to your version of the file, but you are not
> obligated to
> 35 // do so. If you do not wish to provide this exception without
> 36 // modification, you must delete this exception statement from
> your
> 37 // version and license this file solely under the GPL without
> 38 // exception.
> 39 40 #include <unistd.h>
> 41 42 void
> 43 print(char *what) {
> -> 44 while (*what != '\0') {
> 45 write(1, what, 1);
> 46 what++;
> 47 }
> 48 }
> 49 50 int
> 51 main(int argc, char** argv) {
> 52 // XXX: This forgets to check ARGC.
> 53 print(argv[1]);
> (fhpd) where
> #0 0x080483da in print(char * what)
> /home/scratch/frysk/git/frysk/frysk-core/frysk/pkglibdir/funit-hello.c#44
> #1 0x08048435 in main(int argc,char ** argv)
> /home/scratch/frysk/git/frysk/frysk-core/frysk/pkglibdir/funit-hello.c#53
> #2 0x00808390 in __libc_start_main () from /lib/libc-2.7.so
> #3 0x08048311 in _start () from
> /home/scratch/frysk/git/native/frysk-core/frysk/pkglibdir/funit-hello
> (fhpd) print what
> (char *) 0x0 " < Memory Error > "
> (fhpd)
>
> which is the most straight forward of debugging sessions; and a major
> milestone. In the meeting, this brought forward two proposals:
prev parent reply other threads:[~2008-03-19 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 15:11 Andrew Cagney
2008-03-19 16:00 ` Phil Muldoon
2008-03-26 11:53 ` Mark Wielaard
2008-04-01 21:13 ` Sami Wagiaalla
2008-03-19 16:00 ` Andrew Cagney [this message]
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=47E13887.3050905@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).