Re: Crashing bug

[Bruno Haible]

Hello Cem,

> > Can you come up with a stack trace (either by running gperf under gdb,
> > or from the log file in $HOME/Library/Logs/CrashReporter/)?
> 
> I tried getting a stack trace, and I tried attaching it to the message I
> sent you, but unfortunately the attachment got refused! :(

Hmm, you can try gzip or bzip it; maybe that works?

> gperf --version returns 3.0.1... maybe there were some bug fixes???

There were no bug fixes that could be related to this crash.

> I'm not sure how long it ran; I let it run over the weekend, it seems it
> crashed after 3 days or so, but I'm not 100% sure; I just see where the
> terminal crashed, not where gperf crashed.  Mainly, it never completes; it
> just goes until it crashes.

Nevertheless it should crash with a reasonable error message. On MacOS X 10.3,
when a C++ program allocates too much memory, this is what happens:

  *** malloc: vm_allocate(size=3000000512) failed (error code=3)
  *** malloc[11283]: error: Can't allocate region
  Abort trap

If gperf crashes without such a message, there's something wrong. I have
my copy running for 18 hours now, and it is still running...

> BTW, are there any options for compiling gperf with STABS or DWARF?  That
> way, I can run everything under gdb and step through the code, or at least
> see a little more of why it crashed...

"g++ -g" or "g++ -g3" should enable sufficient debugging information. Whether
it's STABS or DWARF, does not make much difference.

> There are many comments I'd like to make, all of them funny, but our funny
> bones are legally removed when we become employees of the government! :P

Sorry, I wouldn't have joked if had known that you are defenseless. I didn't
know that jokes are an area where military and governmental personnal is
without defense.

Regards,

Bruno