Hi,
Thank you for your kind report.
>> On Sat, 15 Jul 2006 08:38:03 +0200
>> [EMAIL PROTECTED] (Julien Danjou) said as follows:
>> Automatic build of juman_5.1-1 on avidan by sbuild/i386 0.48
>> Build started at 20060715-0339
>> ******************************************************************************
>...
>> Suffix.dic parsing... done.
>>
>> execution time: 0.000s
>> processor time: 0.030s
>> cat Assert.int AuxV.int ContentW.int Demonstrative.int Noun.hukusi.int
>> Noun.keishiki.int Noun.koyuu.int Noun.suusi.int Postp.int Prefix.int
>> Rengo.int Special.int Suffix.int > jumandic.txt
>> ../makepat/dicsort jumandic.txt > jumandic.dat
>> rm -f jumandic.txt
>> ../makepat/makepat
>> File Name "/build/buildd/juman-5.1/build-tree/juman-5.1/dic/jumandic.dat"
>> .................... 20000
>> .................... 40000
>> .................... 60000
>> .................... 80000
>> .................... 100000
>> ...................make[3]: *** [jumandic.pat] Segmentation fault
>> make[3]: *** Deleting file `jumandic.pat'
>> make[3]: Leaving directory `/build/buildd/juman-5.1/build-tree/juman-5.1/dic'
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory `/build/buildd/juman-5.1/build-tree/juman-5.1'
>> make[1]: *** [all] Error 2
>> make[1]: Leaving directory `/build/buildd/juman-5.1/build-tree/juman-5.1'
>> make: *** [debian/stamp-makefile-build] Error 2
>> ******************************************************************************
>> Build finished at 20060715-0341
>> FAILED [dpkg-buildpackage died]
>> ------------------------------------------------------------------------------
>I agree that this may not be so easy to reproduce. If I can help,
>just ask me.
Yes, I cannot reproduce this problem.
Please tell me what architecture is used when this problem occurs.
And, can you record backtrace of this problem? I imagine that the
following three commands will be required to reproduce the problem.
apt-get source juman
cd juman-5.1
dpkg-buildpackage -us -uc -rfakeroot
After executing these commands, please execute the following four
commands to record backtrace.
cd build-tree/juman-5.1/dic
ulimit -c unlimited
../makepat/makepat
gdb ../makepat/.libs/makepat core
When the prompt "(gdb)" appears, please type "backtrace" and backtrace
which reveals a line causes segmentation fault will be displayed.
Regards,
--
TSUCHIYA Masatoshi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
