Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH/RFC] auxv entries
Date: Tue, 16 Sep 2008 03:28:00 -0000	[thread overview]
Message-ID: <1221535620.12929.3.camel@localhost.localdomain> (raw)
In-Reply-To: <200809152022.m8FKMbbt017028@brahms.sibelius.xs4all.nl>

El lun, 15-09-2008 a las 22:22 +0200, Mark Kettenis escribió:
> Here is the promised diff.  Tested on Linux on amd64 (which doesn't
> say a lot since it is little-endian).

Not sure if you're still interested, but I had already fired the
regression test anyway:

This patch introduces the following regressions in ppc64-linux:

 PASS: gdb.base/auxv.exp: generate native core dump
 PASS: gdb.base/auxv.exp: load core file for info auxv on native core dump
 PASS: gdb.base/auxv.exp: info auxv on native core dump
-PASS: gdb.base/auxv.exp: matching auxv data from live and core
+FAIL: gdb.base/auxv.exp: matching auxv data from live and core
 PASS: gdb.base/auxv.exp: load core file for info auxv on gcore-created dump
 PASS: gdb.base/auxv.exp: info auxv on gcore-created dump
-PASS: gdb.base/auxv.exp: matching auxv data from live and gcore
+FAIL: gdb.base/auxv.exp: matching auxv data from live and gcore

Here's the gdb.log for the failing run:

info auxv^M
0    AT_NULL              End of vector                  0x16^M
(gdb) PASS: gdb.base/auxv.exp: info auxv on native core dump
FAIL: gdb.base/auxv.exp: matching auxv data from live and core

Versus the gdb.log for the successful run:

info auxv^M
22   AT_IGNOREPPC         Entry should be ignored        22^M                                                                  22   AT_IGNOREPPC         Entry should be ignored        22^M
19   AT_DCACHEBSIZE       Data cache block size          128^M
20   AT_ICACHEBSIZE       Instruction cache block size   128^M
21   AT_UCACHEBSIZE       Unified cache block size       0^M
33   AT_SYSINFO_EHDR      System-supplied DSO's ELF header 0x100000^M
16   AT_HWCAP             Machine-dependent CPU capability hints 0xdc080000^M
6    AT_PAGESZ            System page size               4096^M
17   AT_CLKTCK            Frequency of times()           100^M
3    AT_PHDR              Program headers for program    0x10000040^M
4    AT_PHENT             Size of program header entry   56^M                                                                  5    AT_PHNUM             Number of program headers      9^M
7    AT_BASE              Base address of interpreter    0x40000000000^M
8    AT_FLAGS             Flags                          0x0^M
9    AT_ENTRY             Entry point of program         0x10010b98^M
11   AT_UID               Real user ID                   1001^M
12   AT_EUID              Effective user ID              1001^M
13   AT_GID               Real group ID                  100^M
14   AT_EGID              Effective group ID             100^M
23   AT_SECURE            Boolean, was exec setuid-like? 0^M
15   AT_PLATFORM          String identifying platform    0xfffffa62210 "ppc970"^M
0    AT_NULL              End of vector                  0x0^M
(gdb) PASS: gdb.base/auxv.exp: info auxv on native core dump
PASS: gdb.base/auxv.exp: matching auxv data from live and core

 
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


  parent reply	other threads:[~2008-09-16  3:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-14 21:27 Mark Kettenis
2008-09-15  0:28 ` Thiago Jung Bauermann
2008-09-15  0:34 ` Thiago Jung Bauermann
2008-09-15  9:21   ` Mark Kettenis
2008-09-15 20:23     ` Mark Kettenis
2008-09-15 21:14       ` Daniel Jacobowitz
2008-09-16  3:28       ` Thiago Jung Bauermann [this message]
2008-09-15  3:21 ` 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=1221535620.12929.3.camel@localhost.localdomain \
    --to=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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