[jamming] Segfault w/ GCC 4.2

[Ryan Hill]

Ingo Weinhold wrote:

> The code there (ll. 585-587) reads:
> 
> 	    for( l = rule->params, i = 0; l; l = l->next, i++ )
> 		s = addsettings( s, 0, l->string, 
> 		    list_copy( L0, lol_get( args, i ) ) );
> 
> Apparently a string pointer in the rule's parameter list is invalid. The list 
> is built in compile_setcomp() (which looks OK to me) and AFAIK is never 
> changed afterwards.
> 
> Given that gcc 4.2 is not yet released yet, I wouldn't rule out that a gcc 
> regression is responsible.

It should be released today, though you're right.

BTW, i found a Debian bug report as well, maybe it can provide more
information: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=372470

> PS: Out of curiosity, how do you auto-attach a gdb to a crashed program?

I didn't.  I just cut the lines where i launched gdb for brevity. ;)

-- 
                                where to now? if i had to guess
dirtyepic gentoo org        i'm afraid to say antarctica's next
9B81 6C9F E791 83BB 3AB3  5B2D E625 A073 8379 37E8 (0x837937E8)