bug-m4
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: next snapshot in preparation for m4 1.4.12


From: Tom G. Christensen
Subject: Re: next snapshot in preparation for m4 1.4.12
Date: Tue, 2 Sep 2008 17:28:05 +0200
User-agent: Mutt/1.4.2.2i

On Mon, Sep 01, 2008 at 02:48:20PM -0600, Eric Blake wrote:
> Shoot.  I got the logic backwards.  We want the test to exit with non-zero
> status if c_stack_action fails (returns non-zero), or if recurse returns
> (which should be impossible).  The conditional should be written with ||,
> not &&.  At any rate, it confirms that c_stack_action is succeeding.
> 
Oh well. Ofcourse the config.log program crashes with this typo fixed.

> So, with my typo fixed, can you once again try those debugging steps, to
> see if the breakpoint in overflow_handler trips?
> 
It does not.

address@hidden tests]$ gdb test-c-stack
GNU gdb 4.17.gnat.3.11p
Copyright 1998 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 "mips-sgi-irix5.3"...
(gdb) b overflow_handler
Breakpoint 1 at 0x4015e8: file c-stack.c, line 184.
(gdb) run
Starting program: 
/usr/people/tgc/buildpkg/m4/src/m4-1.4.11.42-864d/tests/test-c-stack

Program received signal SIGSEGV, Segmentation fault.
0x400d70 in recurse (p=0x0) at test-c-stack.c:46
46      {
(gdb) step

Program received signal SIGSEGV, Segmentation fault.
0x400d70 in recurse (p=0x0) at test-c-stack.c:46
46      {
(gdb) step

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb)

The sigsegv_handler is never called either or atleast gdb doesn't show
it. I put a breakpoint on segv_handler, but it ends like the above
trace with no stop at the handler.

dbx is no better, trying to step after the SIGSEGV goes nowhere and it
just keeps printing the same line over and over.

-tgc




reply via email to

[Prev in Thread] Current Thread [Next in Thread]