[Top][All Lists]

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

Fwd: segfault with latest gtags

From: Aneesh Kumar
Subject: Fwd: segfault with latest gtags
Date: Wed, 17 Feb 2010 23:08:51 +0530

Missed the list in the previous reply

On Wed, Feb 17, 2010 at 10:21 PM, Hideki IWAMOTO
<address@hidden> wrote:
> Hi.
> On Mon, 15 Feb 2010 23:17:28 +0530, Aneesh Kumar wrote...
>> >> address@hidden /home/opensource/sources/global/gtags/gtags -c -i -f
>> >> gtags.files
>> >> gtags: primary key size == 0.
>> >
>> > Backtrace information when this message is displayed is needed.
>> > Could you execute gtags on GDB like this?
>> > $ gdb /home/opensource/sources/global/gtags/gtags
>> > (gdb) b die
>> > (gdb) r -c -i -f gtags.files
>> > (gdb) bt
>> BTW after creating the G* files you need to checkout an older version
>> and try to recreate using
>> -c -i -f .  I am  attaching below the gdb details
> Your previous E-mail shows the following. Is this right?
> 1. You executed `gtags -c -i -f gtags.files' in the directory where the tag 
> files did not exist.

No it always segfault in the third attempt.
a) create tags files
b) switch to a different branch/version (in other words change some c files )
c) run gtags -c -i -f gtags.file . it will throw an error primary key size = 0
d) run gtags -c -i -f gtags.file it will segfault

> 2. Gtags terminated abnormally with the message "primary key size == 0".
>   At this point, the tag files were corrupted.
> 3. Then, you executed incremental updating with `gtags -c -i -f gtags.files'.
> 4. Segmentation fault occured while executing gtags.
> You seem to have attached backtrace information on 4.
> Backtrace information that I want is on 2.

With the linux kernel source i guess it should be easy to reproduce.


reply via email to

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