From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: Justin Madru <jdm64@gawab.com>
Cc: "Justin P. Mattock" <justinmattock@gmail.com>,
Jesper Juhl <jj@chaosbits.net>,
lkml <linux-kernel@vger.kernel.org>,
John Stoffel <john@stoffel.org>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [bisected] 2.6.29-rc1 Firefox crashing on page load
Date: Tue, 20 Jan 2009 10:28:38 -0800 [thread overview]
Message-ID: <497617D6.8020707@ct.jp.nec.com> (raw)
In-Reply-To: <49756D07.7080804@gawab.com>
Justin Madru wrote:
> Hiroshi Shimamoto wrote:
>> Justin Madru wrote:
>>> Ok, finally bisected the bug, but the commit isn't related to networking!
>>> I did: git revert 4217458dafaa57d8e26a46f5d05ab8c53cf64191
>>> on current git and that fixed the bug.
>>>
>>> By the way, how do I undo my git revert, so I'm back to a pristine tree?
>>> I want to drop my changes - the revert.
>>> Also how do I find the commit that merged/pulled in this commit?
>>>
>>> commit 4217458dafaa57d8e26a46f5d05ab8c53cf64191
>>> Author: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
>>> Date: Fri Dec 5 17:17:09 2008 -0800
>>>
>>> x86: signal: change type of paramter for sys_rt_sigreturn()
>>>
>>> Impact: cleanup on 32-bit
>>>
>>> Peter pointed this parameter can be changed.
>>>
>>> Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
>>> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>> Hi,
>> thanks for reporting.
>>
>> I'm not sure why this commit affects.
>> Can you check vmlinux? size, objdump, etc.
>> On my environment, the generated code looks same.
>>
>> Thanks,
>> Hiroshi
>>
> I tried to do an objdump but it gave an error. How am I suppose to do an
> objdump?
>
> $ objdump -x /boot/vmlinuz-2.6.29-rc2-git
> objdump: /boot/vmlinuz-2.6.29-rc2-git: File format not recognized
> $ readelf -a /boot/vmlinuz-2.6.29-rc2-git
> readelf: Error: Unable to seek to 0xc031f2eb for section headers
> readelf: Error: Not an ELF file - it has the wrong magic bytes at the start
> $ ls -la /boot/vmlinuz-2.6.29-rc2-git
> -rw-r--r-- 1 root root 2286480 2009-01-19 18:44 /boot/vmlinuz-2.6.29-rc2-git
not vmlinuz, vmlinux.
vmlinuz is a compressed kernel, it is not ELF file.
Usually vmlinux is generated in top of source directory.
I can see disassembled image with objdump -d vmlinux.
Thanks,
Hiroshi
next prev parent reply other threads:[~2009-01-20 18:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 20:56 Justin Madru
2009-01-17 2:28 ` Justin Madru
2009-01-17 3:27 ` John Stoffel
2009-01-17 3:27 ` Justin P. Mattock
2009-01-17 8:48 ` Justin Madru
2009-01-17 9:10 ` Justin P. Mattock
2009-01-17 20:21 ` Jesper Juhl
2009-01-17 21:07 ` Justin Madru
2009-01-17 22:51 ` Justin P. Mattock
2009-01-18 0:05 ` Justin Madru
2009-01-18 0:46 ` Justin P. Mattock
2009-01-18 2:06 ` Justin Madru
2009-01-18 2:49 ` Justin P. Mattock
2009-01-20 0:32 ` [bisected] " Justin Madru
2009-01-20 1:06 ` Justin P. Mattock
2009-01-20 1:25 ` Hiroshi Shimamoto
2009-01-20 6:19 ` Justin Madru
2009-01-20 18:28 ` Hiroshi Shimamoto [this message]
2009-01-20 19:22 ` Justin Madru
2009-01-20 19:48 ` Hiroshi Shimamoto
2009-01-21 2:39 ` Justin Madru
2009-01-21 3:04 ` Hiroshi Shimamoto
2009-01-20 1:39 ` Peter Annema
2009-01-20 7:15 ` Heiko Carstens
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=497617D6.8020707@ct.jp.nec.com \
--to=h-shimamoto@ct.jp.nec.com \
--cc=hpa@zytor.com \
--cc=jdm64@gawab.com \
--cc=jj@chaosbits.net \
--cc=john@stoffel.org \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome