X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: mike3 Newsgroups: comp.os.msdos.djgpp Subject: Re: Weird GDB crash with DJGPP Date: Sat, 18 Aug 2007 08:58:47 -0700 Organization: http://groups.google.com Lines: 28 Message-ID: <1187452727.199009.59580@m37g2000prh.googlegroups.com> References: <1187424821 DOT 915011 DOT 306360 AT l22g2000prc DOT googlegroups DOT com> <46C70D66 DOT 5060305 AT iki DOT fi> NNTP-Posting-Host: 74.38.33.242 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: posting.google.com 1187452727 27881 127.0.0.1 (18 Aug 2007 15:58:47 GMT) X-Complaints-To: groups-abuse AT google DOT com NNTP-Posting-Date: Sat, 18 Aug 2007 15:58:47 +0000 (UTC) In-Reply-To: <46C70D66.5060305@iki.fi> User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe) Complaints-To: groups-abuse AT google DOT com Injection-Info: m37g2000prh.googlegroups.com; posting-host=74.38.33.242; posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Aug 18, 9:16 am, Andris Pavenis wrote: > mike3 wrote: > > Hi. > > > When I try to run the GNU Debugger in DJGPP on my program, and list > > the CPU registers with "list all-registers", it crashes with > > > "go32-nat.c:473: internal-error: Invalid register no. 32 in > > fetch_register." > > > when it gets to the XMM registers. And this is really, REALLY bad > > since that's where I need to debug! > > What is going on here? I tried GDBing a different program to see if > > perhaps it was due to a flaw in my program and BAM, same error, so > > nope, that's not it. > > No one has added support of XMM registers for DJGPP. One can see from > gdb/go32-nat.c in gdb-6.6.tar.bz2. > > I remember I had this problem already long time ago when building from > sources and using RHIDE. I workarounded it in some way, but I don't > remeber exactly how (perhaps limiting librhgdb not to try to retrieve > XMM registers at all). Dang. You know, that really sucks quite a bit.