Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3E06F2DC.98111738@phekda.freeserve.co.uk>
Date: Mon, 23 Dec 2002 11:26:20 +0000
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: RESEND: gdb 5.2.1 segfaults while debugging fileutils 4.1
References: <3E05A070 DOT 20810EB8 AT phekda DOT freeserve DOT co DOT uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Richard Dawe wrote:
[snip]
> I seem to be having some trouble debugging fileutils 4.1 with gdb 5.2.1.
> Here's the situation:
> 
> * fileutils 4.1 and DJGPP CVS both built with -gstabs+3.
> * gdb 5.2.1 from binaries on Simtel.NET or gdb 5.2.1 built against DJGPP CVS.
[snip]

Neither gdb 5.1.1 nor gdb 5.3 seem much better. They both crash.

Here's a crash from gdb 5.3. It's from DJGPP CVS built without debug and 'ls'
from fileutils 4.1 built with debug. Load ls.exe, type go<TAB>, to
tab-complete for "gobble_file".

There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-msdosdjgpp --target=djgpp"...
(gdb) b goExiting due to signal SIGSEGV
General Protection Fault at eip=001862c6
eax=642f3a67 ebx=642f3a63 ecx=00000002 edx=00000000 esi=00256952 edi=00256952
ebp=00256868 esp=00256860 program=C:\DJGPP.204\BIN\GDB.EXE
cs: sel=00f7  base=846bc000  limit=002effff
ds: sel=00ff  base=846bc000  limit=002effff
es: sel=00ff  base=846bc000  limit=002effff
fs: sel=00cf  base=0001d300  limit=0000ffff
gs: sel=010f  base=00000000  limit=0010ffff
ss: sel=00ff  base=846bc000  limit=002effff
App stack: [00257134..001d7134]  Exceptn stack: [001d6768..001d4828]

Call frame traceback EIPs:
  0x001862c6 _strncmp+22
  0x000415dd _contained_in+93
  0x00041849 _make_symbol_completion_list+345
  0x0003d2d9 _location_completer+649
  0x0003d4ab _complete_line+203
  0x0003d773 _line_completion_function+51
  0x0003cedf _readline_line_completion_function+31
  0x0015258f _completion_matches+47
  0x00151713 _rl_insert_completions+1747
  0x00152344 _rl_complete_internal+148
  0x0014ac7a __rl_dispatch+170
  0x0014aa06 _readline_internal_char+134
  0x00155f34 _rl_callback_read_char+20
  0x00087f0a _delete_timer+442
  0x000884ae _stdin_event_handler+94
  0x0008774c _delete_file_handler+556
  0x00087274 __initialize_infrun+1060
  0x000872c6 _gdb_do_one_event+54
  0x0001418f _do_catch_errors+15
  0x00014090 _throw_exception+464
  0x000141d6 _catch_errors+54
  0x000872e8 _start_event_loop+24
  0x00001794 _main+116
  0x0001418f _do_catch_errors+15
  0x00014090 _throw_exception+464
  0x000141d6 _catch_errors+54
  0x000024bb _main+3483
  0x0001418f _do_catch_errors+15
  0x00014090 _throw_exception+464
  0x000141d6 _catch_errors+54
  0x000025d2 _gdb_main+34
  0x00001748 _main+40
  0x00185117 ___crt1_startup+199
bash-2.04$ symify c:/djgpp.204/bin/gdb.exe
bash-2.04$ c:/djgpp.204/bin/gdb.exe --version
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-msdosdjgpp --target=djgpp".
bash-2.04$ echo $DJDIR
c:/djgpp.204

Has anyone else had this kind of problem?

Bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]