Re: ddd bad performance

[Tim Mooney]

In regard to: Re: ddd bad performance, lyman wang said (at 4:06pm on May...:

> Most of the time spend on  "list" operation.
> <- "(gdb) "
> -> "list\n"
> <- "25\t/*======================================================*/\n"
>    "26\tint main(int argc, char* argv[])\n"
>    "27\t{\n"
>    "28\t\n"
>    "29\tT_OASIS_HEADER\t\toasis_header;\n"
>    "30\t\n"
>    "31\t\t/*------------------*/\n"
>    "32\t\t/* SIGSEGV redirect */\n"
>    "33\t\t/*------------------*/\n"
>    "34\t\tsignal(SIGSEGV,end_sigsegv);\n"
> <- "(gdb) "
> -> "info line\n"
> <- "Line 34 of
> \"/vobs/lead_telecom/telecom_simulation/mlight/src/mlight_main.c\" starts
> at address 0x7ca466 <main+6> and ends at 0x7ca478 <main+24>.\n"
>   
> "\032\032/vobs/lead_telecom/telecom_simulation/mlight/src/mlight_main.c:34:695:b
> eg:0x7ca466\n"

First, what happens if you type

        gdb terminal_t
        list

Does it take a long time?

Does it still take a long time if you access it on a non-ClearCase
filesystem?  I'm not familiar enough with CC to know what you need to
do to get mlight_main.c "checked out", but if you get it onto a
traditional UNIX filesystem, does it still take as long?

Tim
--
Tim Mooney                              address@hidden
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164