#9 segv in error.c, line 454

closed
nobody
None
5
2001-11-26
2001-11-18
George R. Goffe
No

Mark,

When editing multiple files at the same time I get a
segment violation. I built xxgdb and gdb and did some
debugging. Here's what I got:

XXGDB comes with ABSOLUTELY NO WARRANTY.
GNU gdb 5.0
Copyright 2000 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 "sparc-sun-solaris2.8"...
(xxgdb) iowin
(xxgdb) help run
Start debugged program. You may specify arguments to
give it.
Args may include "*", or "[...]"; they are expanded
using "sh".
Input and output redirection with ">", "<", or ">>" are
also allowed.

With no arguments, uses arguments last specified (with
"run" or "set args").
To cancel previous arguments and run with no arguments,
use "set args" without arguments.
(xxgdb) run /etc/init.d/*
[New LWP 1]
[New LWP 2]
[New LWP 3]
[New LWP 4]

Program received signal SIGSEGV, Segmentation fault.
0x63d0c in open_msgline (base=0 '\000', off=3, rows=23
'\027') at error.c:454

The msgline setting is "msgline on 3 231 OVERLAY"

Anything I can do to help with this?

George...

Discussion

  • Mark Hessling
    Mark Hessling
    2001-11-26

    • status: open --> closed
     
  • Mark Hessling
    Mark Hessling
    2001-11-26

    Logged In: YES
    user_id=86185

    THE 3.1 includes a change in SET MSGLINE to prevent the
    msgline being specified as larger than the screen, and an
    option to allow the msgline to be as big as the screen. See
    doco in SET MSGLINE in THE 3.1 RC1.