public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "swagiaal at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/5730] stack trace does not show location information
Date: Wed, 06 Feb 2008 20:20:00 -0000	[thread overview]
Message-ID: <20080206201931.1958.qmail@sourceware.org> (raw)
In-Reply-To: <20080205201316.5730.tromey@redhat.com>


------- Additional Comments From swagiaal at redhat dot com  2008-02-06 20:19 -------
okay that patch is the fixer not the breaker stack traces before that patch had
incorrect addresses:

PSTACK:

[swagiaal@toner frysk.patches]$ pstack $$
#0  0x00000030f549a835 in waitpid () from /lib64/libc.so.6
#1  0x0000000000435a11 in ?? ()
#2  0x000000000043782e in wait_for ()
#3  0x000000000042b0a1 in execute_command_internal ()
#4  0x000000000042ba9f in execute_command ()
#5  0x000000000041b7b6 in reader_loop ()
#6  0x000000000041b309 in main ()

FRYSK BEFORE:

[swagiaal@toner frysk.patches]$ ./frysk-core/frysk/bindir/fstack $$
Task #4299
#0 0x00000030f549a835 in __GI___waitpid () from /lib64/libc-2.7.so
#1 0x00000000004359d1 in waitchld () from /bin/bash
#2 0x00000000004377ee in wait_for () from /bin/bash
#3 0x000000000042b071 in execute_command_internal () from /bin/bash
#4 0x000000000042ba5f in time_command () from /bin/bash
#5 0x000000000041b786 in reader_loop () from /bin/bash
#6 0x000000000041b2d9 in main () from /bin/bash
#7 0x00000030f541e074 in __libc_start_main () from /lib64/libc-2.7.so
#8 0x0000000000419179 in [unknown] from /bin/bash

FRYSK AFTER:

(fhpd) where
[0.0]
#0 0x00000030f549a835 in __GI___waitpid () from /lib64/libc-2.7.so
#1 0x0000000000435a11 in waitchld () from /bin/bash
#2 0x000000000043782e in wait_for () from /bin/bash
#3 0x000000000042b0a1 in execute_command_internal () from /bin/bash
#4 0x000000000042ba9f in execute_command () from /bin/bash
#5 0x000000000042c87f in execute_connection () from /bin/bash
#6 0x000000000042a8b3 in execute_command_internal () from /bin/bash
#7 0x000000000042ba9f in execute_command () from /bin/bash
#8 0x000000000041b7b6 in reader_loop () from /bin/bash
#9 0x000000000041b309 in main () from /bin/bash
#10 0x00000030f541e074 in __libc_start_main () from /lib64/libc-2.7.so
#11 0x0000000000419179 in [unknown] from /bin/bash
(fhpd) quit
Quitting...


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|frysk-bugzilla at sourceware|swagiaal at redhat dot com
                   |dot org                     |


http://sourceware.org/bugzilla/show_bug.cgi?id=5730

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


  parent reply	other threads:[~2008-02-06 20:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 20:13 [Bug general/5730] New: " tromey at redhat dot com
2008-02-05 20:50 ` [Bug general/5730] " swagiaal at redhat dot com
2008-02-05 20:51 ` swagiaal at redhat dot com
2008-02-06 18:29 ` swagiaal at redhat dot com
2008-02-06 18:59 ` mark at klomp dot org
2008-02-06 20:20 ` swagiaal at redhat dot com [this message]
2008-03-05  3:04 ` scox at redhat dot com

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=20080206201931.1958.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).