From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Sanjoy Das <sanjoy@playingwithpointers.com>
Cc: gdb-patches@sourceware.org, Stan Shebs <stanshebs@earthlink.net>
Subject: Regression for gdb.base/jit.exp and gdb.base/jit-so.exp [Re: JIT Interface Patches Landed]
Date: Sat, 26 Nov 2011 00:23:00 -0000 [thread overview]
Message-ID: <20111126002251.GA5257@host1.jankratochvil.net> (raw)
In-Reply-To: <4EC9CE39.40604@earthlink.net>
On Mon, 21 Nov 2011 05:06:17 +0100, Stan Shebs wrote:
> On 11/20/11 2:13 AM, Sanjoy Das wrote:
> >Hi all,
> >
> >I've checked in the work I did to implement a (hopefully) simpler JIT
> >interface.
> >
>
> Did you recheck running with the testsuite? I just saw four
> regressions in current jit.exp vs a testsuite run I did a week ago,
> but haven't investigated further.
9894c3216f7cf02a51d8c2058cac8cba33dc6e69 is the first bad commit
commit 9894c3216f7cf02a51d8c2058cac8cba33dc6e69
Author: sanjoyd <sanjoyd>
Date: Sun Nov 20 09:14:45 2011 +0000
gdb/
* jit.c: Include block.h, dictionary.h and frame-unwind.h.
(add_objfile_entry, jit_target_read_impl, jit_object_open_impl)
(jit_symtab_open_impl, compare_block, jit_block_open_impl)
(jit_symtab_line_mapping_add_impl, jit_symtab_close_impl)
(finalize_symtab, jit_object_close_impl)
(jit_reader_try_read_symtab, jit_bfd_try_read_symtab)
(free_objfile_data): New functions.
(_initialize_jit): Register jit_objfile_data with a proper cleanup
function.
-PASS: gdb.base/jit.exp: one_jit_test-1: info function jit_function
+FAIL: gdb.base/jit.exp: one_jit_test-1: info function jit_function
-PASS: gdb.base/jit.exp: one_jit_test-2: info function jit_function
+FAIL: gdb.base/jit.exp: one_jit_test-2: info function jit_function
-PASS: gdb.base/jit-so.exp: one_jit_test-1 info function jit_function
+FAIL: gdb.base/jit-so.exp: one_jit_test-1 info function jit_function
-PASS: gdb.base/jit-so.exp: one_jit_test-2 info function jit_function
+FAIL: gdb.base/jit-so.exp: one_jit_test-2 info function jit_function
Unable to find JITed code entry at address: 0x602030
Thanks,
Jan
next prev parent reply other threads:[~2011-11-26 0:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-20 10:09 JIT Interface Patches Landed Sanjoy Das
2011-11-21 4:06 ` Stan Shebs
2011-11-26 0:23 ` Jan Kratochvil [this message]
2011-11-26 13:13 ` Regression for gdb.base/jit.exp and gdb.base/jit-so.exp [Re: JIT Interface Patches Landed] Sanjoy Das
2011-11-27 10:53 ` Jan Kratochvil
2011-11-27 14:27 ` Sanjoy Das
2011-11-27 14:30 ` Jan Kratochvil
2011-11-27 14:38 ` Sanjoy Das
2011-11-27 14:41 ` Sanjoy Das
2011-11-27 18:29 ` Joel Brobecker
2011-11-27 18:56 ` Sanjoy Das
2011-11-27 19:00 ` Jan Kratochvil
2011-11-29 8:33 ` Sanjoy Das
2011-11-29 16:37 ` Jan Kratochvil
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=20111126002251.GA5257@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sanjoy@playingwithpointers.com \
--cc=stanshebs@earthlink.net \
/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