This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH/i386newframe] amd64newframe


Elena Zannoni writes:
 > Mark Kettenis writes:
 >  > 
 >  > Yes, that would be great.  As soon as it performs better than the old
 >  > stuff, I'd like to move things over to mainline.
 >  > 
 >  > Mark
 > 
 > 
 > For me, I get:
 > 
 > 63 failures in gdb.base
 > 25 in gdb.c++
 > 50 in gdb.threads
 > 24 in gdb.mi
 > 6 in gdb.asm
 > 
 > and
 > 
 > 40 ERROR's
 > 
 > 		=== gdb Summary ===
 > 
 > # of expected passes		8523
 > # of unexpected failures	177
 > # of unexpected successes	3
 > # of expected failures		46
 > # of known failures		19
 > # of unresolved testcases	38
 > # of unsupported tests		2
 > 
 > 
 > not perfect, but, I say, pretty close.
 > 
 > Hmm, I should run the testsuite for mainline too, doh.
 > 

hmm, gdb in mainline dies at startup:

(gdb) dir /home/ezannoni/gdb-sources/src/gdb/testsuite/gdb.asm
Source directories searched: /home/ezannoni/gdb-sources/src/gdb/testsuite/gdb.asm:$cdir:$cwd
(gdb) file /home/ezannoni/gdb-sources/torrent/gdb/testsuite/gdb.asm/asm-source
/home/ezannoni/gdb-sources/src/gdb/regcache.c:172: internal-error: init_regcache_descr: Assertion `!REGISTER_VIRTUAL_TYPE_P ()' failed.
A problem internal to GDB has been detected.  Further
debugging may prove unreliable.
Quit this debugging session? (y or n) ERROR: couldn't load /home/ezannoni/gdb-sources/torrent/gdb/testsuite/gdb.asm/asm-source into /home/ezannoni/gdb-sources/torrent/gdb/testsuite/../../gdb/gdb (timed out).


I think we can merge, if Michal can verify this.

elena



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]