s88 wrote:
> On 10/11/06, Tim Van Holder <[EMAIL PROTECTED]> wrote:
>>
>> s88 wrote:
>> > Hi all:
>> > I'm confused with the bison and malloc right now...
>> > I'm using the Bison 2.0 on Ubuntu(Linux) 6.06, and everytime when I use
>&
On 10/11/06, Tim Van Holder <[EMAIL PROTECTED]> wrote:
s88 wrote:
> Hi all:
> I'm confused with the bison and malloc right now...
> I'm using the Bison 2.0 on Ubuntu(Linux) 6.06, and everytime when I use
> the malloc(actually is strdup) in the produc
s88 wrote:
> Hi all:
> I'm confused with the bison and malloc right now...
> I'm using the Bison 2.0 on Ubuntu(Linux) 6.06, and everytime when I use
> the malloc(actually is strdup) in the production rules. It will cause an
> unpredictable
> segmentation fault. The st
On Wed, Oct 11, 2006 at 08:38:32PM +0800, s88 wrote:
> Hi all:
> I'm confused with the bison and malloc right now...
> I'm using the Bison 2.0 on Ubuntu(Linux) 6.06, and everytime when I use
> the malloc(actually is strdup) in the production rules. It will cause an
> unp
Hi all:
I'm confused with the bison and malloc right now...
I'm using the Bison 2.0 on Ubuntu(Linux) 6.06, and everytime when I use
the malloc(actually is strdup) in the production rules. It will cause an
unpredictable
segmentation fault. The stack size on my system is set unlimited.