|
From: Nicholas N. <n.n...@gm...> - 2009-02-18 20:15:23
|
On Thu, Feb 19, 2009 at 6:36 AM, Josef Weidendorfer <Jos...@gm...> wrote: > > . . > memcpy(0x8062c0d, 0xbefda9d4, ...) [libc-2.9.so / 0x75c40] > . . > memcpy(0x8062c13, 0xbefda9db, ...) [libc-2.9.so / 0x75c40] > . . > fgets_unlocked(0xbefda9d4, 0x190, ...) [libc-2.9.so / 0x67380] > . . > 0x0001653f(0x8062518, 0xbefda9d4, ...) [libc-2.9.so / 0x1653f] > . . > _IO_getline(0x8062518, 0xbefda9d4, ...) [libc-2.9.so / 0x5deb0] > . . .> 0x0001653f(0x8062518, 0xbefda9d4, ...) [libc-2.9.so / 0x1653f] > . . .> _IO_getline_info(0x8062518, 0xbefda9d4, ...) [libc-2.9.so / 0x5df00] > . . . > 0x0001653f(0xbefda9d4, 0x4024793, ...) [libc-2.9.so / 0x1653f] > . . . > memchr(0x40247a6, 0xa, ...) [libc-2.9.so / 0x752f0] > . . . > memcpy(0xbefda9d4, 0x40247a6, ...) [libc-2.9.so / 0x75c40] > . . > index(0xbefda9d4, 0xa, ...) [libc-2.9.so / 0x73460] > ... > > If somebody can derive enough information from debug info to allow for output similar > to "strace" or "ltrace", this for sure is welcome, and probably would rectify its own > tool "vtrace". I just tried this on the simple program 'date' and got lots of lines like this: . . > strcmp(0x0, 0xfefffce6, ...) [libc-2.8.90.so / 0x82210] . . > strcmp(0x0, 0xfefffce6, ...) [libc-2.8.90.so / 0x82210] . . .> strcmp(0x0, 0xfefffce6, ...) [libc-2.8.90.so / 0x82210] . . . > strcmp(0x0, 0xfefffce6, ...) [libc-2.8.90.so / 0x82210] . . . > strcmp(0x0, 0xfefffce6, ...) [libc-2.8.90.so / 0x82210] . . . > strcmp(0x0, 0xfefffce6, ...) [libc-2.8.90.so / 0x82210] . . . .> strcmp(0x0, 0xfefffce6, ...) [libc-2.8.90.so / 0x82210] . . . . > strcmp(0x0, 0xfefffce6, ...) [libc-2.8.90.so / 0x82210] . . . . > strcmp(0x0, 0xfefffce6, ...) [libc-2.8.90.so / 0x82210] . . . . > strcmp(0x0, 0xfefffce6, ...) [libc-2.8.90.so / 0x82210] [and 1000s more lines like it] What's happening there? And what does the "..." mean? (I looked in the manual but didn't see anything about this.) N |