mimus

I've been using gedit to text-search a readelf file-dump of my
libc-2.3.5.so C runtime library's .dynsym table to get the --start- and
--stop-addresses objdump needs to allow me to look at the assembly code
libc provides for the standard C library functions.

This is bad.

(And what idiot committee decided to put the start-addresses in hex and
the lengths of the snippets in decimal? twisted mofoes.)

For example, here's the libc-2.3.5.so .dynsym line for the standard C
string function strcpy(), which copies a string into a new location:

00066a8c 35 FUNC GLOBAL DEFAULT 11 strcpy@@GLIBC_2.0

here's the resulting objdump command (I was in the /lib directory):

objdump -d --no-show-raw-insn --start-address=0x00066a8c --stop-address=0x00066aaf libc-2.3.5.so

and here's the output of that command:

libc-2.3.5.so: file format elf32-i386

Disassembly of section .plt:
Disassembly of section .text:

00066a8c <strcpy>:
66a8c: push %ebp
66a8d: mov %esp,%ebp
66a8f: push %esi
66a90: mov 0x8(%ebp),%esi
66a93: mov 0xc(%ebp),%edx
66a96: mov %esi,%eax
66a98: sub %edx,%eax
66a9a: lea 0xffffffff(%eax),%ecx
66a9d: movzbl (%edx),%eax
66aa0: add $0x1,%edx
66aa3: test %al,%al
66aa5: mov %al,(%edx,%ecx,1)
66aa8: jne 66a9d <strcpy+0x11>
66aaa: mov %esi,%eax
66aac: pop %esi
66aad: pop %ebp
66aae: ret

My eyes started watering last night and haven't stopped . . . .

--
tinmimus99@hotmail.com

smeeter 11 or maybe 12

mp 10

mhm 29x13

Where am I, Dove?

< _The Einstein Intersection_

mixed nuts

mimus wrote:
> I've been using gedit to text-search a readelf file-dump of my
> libc-2.3.5.so C runtime library's .dynsym table to get the --start- and
> --stop-addresses objdump needs to allow me to look at the assembly code
> libc provides for the standard C library functions.
>
> This is bad.
>
> (And what idiot committee decided to put the start-addresses in hex and
> the lengths of the snippets in decimal? twisted mofoes.)
>
> For example, here's the libc-2.3.5.so .dynsym line for the standard C
> string function strcpy(), which copies a string into a new location:
>
> 00066a8c 35 FUNC GLOBAL DEFAULT 11 strcpy@@GLIBC_2.0
>
> here's the resulting objdump command (I was in the /lib directory):
>
> objdump -d --no-show-raw-insn --start-address=0x00066a8c --stop-address=0x00066aaf libc-2.3.5.so
>
> and here's the output of that command:
>
> libc-2.3.5.so: file format elf32-i386
>
> Disassembly of section .plt:
> Disassembly of section .text:
>
> 00066a8c <strcpy>:
> 66a8c: push %ebp
> 66a8d: mov %esp,%ebp
> 66a8f: push %esi
> 66a90: mov 0x8(%ebp),%esi
> 66a93: mov 0xc(%ebp),%edx
> 66a96: mov %esi,%eax
> 66a98: sub %edx,%eax
> 66a9a: lea 0xffffffff(%eax),%ecx
> 66a9d: movzbl (%edx),%eax
> 66aa0: add $0x1,%edx
> 66aa3: test %al,%al
> 66aa5: mov %al,(%edx,%ecx,1)
> 66aa8: jne 66a9d <strcpy+0x11>
> 66aaa: mov %esi,%eax
> 66aac: pop %esi
> 66aad: pop %ebp
> 66aae: ret
>
> My eyes started watering last night and haven't stopped . . . .
>

As well they should, and shouldn't.

--
nuts

Shirley

"mimus" <tinmimus99@hotmail.com> wrote in message
news:q56dnXjK9Lmw6O_anZ2dnUVZ_uevnZ2d@giganews.com ...
> I've been using gedit to text-search a readelf file-dump of my
> libc-2.3.5.so C runtime library's .dynsym table to get the --start- and
> --stop-addresses objdump needs to allow me to look at the assembly code
> libc provides for the standard C library functions.
>
> This is bad.
>
> (And what idiot committee decided to put the start-addresses in hex and
> the lengths of the snippets in decimal? twisted mofoes.)
>
> For example, here's the libc-2.3.5.so .dynsym line for the standard C
> string function strcpy(), which copies a string into a new location:
>
> 00066a8c 35 FUNC GLOBAL DEFAULT 11 strcpy@@GLIBC_2.0
>
> here's the resulting objdump command (I was in the /lib directory):
>
> objdump -d --no-show-raw-insn --start-address=0x00066a8c --stop-address=0x00066aaf
> libc-2.3.5.so
>
> and here's the output of that command:
>
> libc-2.3.5.so: file format elf32-i386
>
> Disassembly of section .plt:
> Disassembly of section .text:
>
> 00066a8c <strcpy>:
> 66a8c: push %ebp
> 66a8d: mov %esp,%ebp
> 66a8f: push %esi
> 66a90: mov 0x8(%ebp),%esi
> 66a93: mov 0xc(%ebp),%edx
> 66a96: mov %esi,%eax
> 66a98: sub %edx,%eax
> 66a9a: lea 0xffffffff(%eax),%ecx
> 66a9d: movzbl (%edx),%eax
> 66aa0: add $0x1,%edx
> 66aa3: test %al,%al
> 66aa5: mov %al,(%edx,%ecx,1)
> 66aa8: jne 66a9d <strcpy+0x11>
> 66aaa: mov %esi,%eax
> 66aac: pop %esi
> 66aad: pop %ebp
> 66aae: ret
>
> My eyes started watering last night and haven't stopped . . . .

Speeds up process of finding mimus a girlfriend.

>
> --
> tinmimus99@hotmail.com
>
> smeeter 11 or maybe 12
>
> mp 10
>
> mhm 29x13
>
> Where am I, Dove?
>
> < _The Einstein Intersection_
>

mimus

On Wed, 26 Dec 2007 11:12:56 -0500, mixed nuts wrote:

> mimus wrote:
>
>> I've been using gedit to text-search a readelf file-dump of my
>> libc-2.3.5.so C runtime library's .dynsym table to get the --start- and
>> --stop-addresses objdump needs to allow me to look at the assembly code
>> libc provides for the standard C library functions.
>>
>> This is bad.
>>
>> (And what idiot committee decided to put the start-addresses in hex and
>> the lengths of the snippets in decimal? twisted mofoes.)
>>
>> For example, here's the libc-2.3.5.so .dynsym line for the standard C
>> string function strcpy(), which copies a string into a new location:
>>
>> 00066a8c 35 FUNC GLOBAL DEFAULT 11 strcpy@@GLIBC_2.0
>>
>> here's the resulting objdump command (I was in the /lib directory):
>>
>> objdump -d --no-show-raw-insn --start-address=0x00066a8c --stop-address=0x00066aaf libc-2.3.5.so
>>
>> and here's the output of that command:
>>
>> libc-2.3.5.so: file format elf32-i386
>>
>> Disassembly of section .plt:
>> Disassembly of section .text:
>>
>> 00066a8c <strcpy>:
>> 66a8c: push %ebp
>> 66a8d: mov %esp,%ebp
>> 66a8f: push %esi
>> 66a90: mov 0x8(%ebp),%esi
>> 66a93: mov 0xc(%ebp),%edx
>> 66a96: mov %esi,%eax
>> 66a98: sub %edx,%eax
>> 66a9a: lea 0xffffffff(%eax),%ecx
>> 66a9d: movzbl (%edx),%eax
>> 66aa0: add $0x1,%edx
>> 66aa3: test %al,%al
>> 66aa5: mov %al,(%edx,%ecx,1)
>> 66aa8: jne 66a9d <strcpy+0x11>
>> 66aaa: mov %esi,%eax
>> 66aac: pop %esi
>> 66aad: pop %ebp
>> 66aae: ret
>>
>> My eyes started watering last night and haven't stopped . . . .
>
> As well they should, and shouldn't.

Howdja like that twos-complement masked negative there? (That's what I'm
guessing it is, since I haven't buckled down and made a nice pretty text
IA quick-reference from those three huge .pdfs on the subject I, er,
"borrowed" several years ago-- you could download the things and read 'em,
but Adobe wouldn't let you save them, yet wait, I said to myself, they've
got to be stored _somewhere_ around here, and lo . . . .)

(They do try to call home, the snitches, or at least did under Adobe
and Win98.)

printf() looked all short and sweet, until I realized it was calling
vprintf(), which is about 15K . . . .

(I knew the 6510 AL pretty darn well, enough so to knock up little
utilities in it, write a text-mode video-game (basically flickerin'
"Jumbles"), and modify the C64 BASIC and KERNEL-- both of which I had
printed out and parsed-- for fun . . . .)

--
tinmimus99@hotmail.com

smeeter 11 or maybe 12

mp 10

mhm 29x13

Let's get the hell out of here while we can still pass
our Rorschasch tests.

< _The Last Happy Hour_

mimus

On Wed, 26 Dec 2007 11:18:56 -0500, Shirley wrote:

> "mimus" <tinmimus99@hotmail.com> wrote in message
> news:q56dnXjK9Lmw6O_anZ2dnUVZ_uevnZ2d@giganews.com ...
>
>> I've been using gedit to text-search a readelf file-dump of my
>> libc-2.3.5.so C runtime library's .dynsym table to get the --start- and
>> --stop-addresses objdump needs to allow me to look at the assembly code
>> libc provides for the standard C library functions.
>>
>> This is bad.
>>
>> (And what idiot committee decided to put the start-addresses in hex and
>> the lengths of the snippets in decimal? twisted mofoes.)
>>
>> For example, here's the libc-2.3.5.so .dynsym line for the standard C
>> string function strcpy(), which copies a string into a new location:
>>
>> 00066a8c 35 FUNC GLOBAL DEFAULT 11 strcpy@@GLIBC_2.0
>>
>> here's the resulting objdump command (I was in the /lib directory):
>>
>> objdump -d --no-show-raw-insn --start-address=0x00066a8c --stop-address=0x00066aaf
>> libc-2.3.5.so
>>
>> and here's the output of that command:
>>
>> libc-2.3.5.so: file format elf32-i386
>>
>> Disassembly of section .plt:
>> Disassembly of section .text:
>>
>> 00066a8c <strcpy>:
>> 66a8c: push %ebp
>> 66a8d: mov %esp,%ebp
>> 66a8f: push %esi
>> 66a90: mov 0x8(%ebp),%esi
>> 66a93: mov 0xc(%ebp),%edx
>> 66a96: mov %esi,%eax
>> 66a98: sub %edx,%eax
>> 66a9a: lea 0xffffffff(%eax),%ecx
>> 66a9d: movzbl (%edx),%eax
>> 66aa0: add $0x1,%edx
>> 66aa3: test %al,%al
>> 66aa5: mov %al,(%edx,%ecx,1)
>> 66aa8: jne 66a9d <strcpy+0x11>
>> 66aaa: mov %esi,%eax
>> 66aac: pop %esi
>> 66aad: pop %ebp
>> 66aae: ret
>>
>> My eyes started watering last night and haven't stopped . . . .
>
> Speeds up process of finding mimus a girlfriend.

Don't try to tamper with my budding relationship with Libby C. here, woman.

--
tinmimus99@hotmail.com

smeeter 11 or maybe 12

mp 10

mhm 29x13

You want a job and a lizard to ride?

< _The Einstein Intersection_

dave hillstrom

On Wed, 26 Dec 2007 10:37:31 -0500, mimus <tinmimus99@hotmail.com>
wrote:

>I've been using gedit to text-search a readelf file-dump of my
>libc-2.3.5.so C runtime library's .dynsym table to get the --start- and
>--stop-addresses objdump needs to allow me to look at the assembly code
>libc provides for the standard C library functions.
>
>This is bad.
>
>(And what idiot committee decided to put the start-addresses in hex and
>the lengths of the snippets in decimal? twisted mofoes.)
>
>For example, here's the libc-2.3.5.so .dynsym line for the standard C
>string function strcpy(), which copies a string into a new location:
>
>00066a8c 35 FUNC GLOBAL DEFAULT 11 strcpy@@GLIBC_2.0
>
>here's the resulting objdump command (I was in the /lib directory):
>
>objdump -d --no-show-raw-insn --start-address=0x00066a8c --stop-address=0x00066aaf libc-2.3.5.so
>
>and here's the output of that command:
>
>libc-2.3.5.so: file format elf32-i386
>
>Disassembly of section .plt:
>Disassembly of section .text:
>
>00066a8c <strcpy>:
> 66a8c: push %ebp
> 66a8d: mov %esp,%ebp
> 66a8f: push %esi
> 66a90: mov 0x8(%ebp),%esi
> 66a93: mov 0xc(%ebp),%edx
> 66a96: mov %esi,%eax
> 66a98: sub %edx,%eax
> 66a9a: lea 0xffffffff(%eax),%ecx
> 66a9d: movzbl (%edx),%eax
> 66aa0: add $0x1,%edx
> 66aa3: test %al,%al
> 66aa5: mov %al,(%edx,%ecx,1)
> 66aa8: jne 66a9d <strcpy+0x11>
> 66aaa: mov %esi,%eax
> 66aac: pop %esi
> 66aad: pop %ebp
> 66aae: ret
>
>My eyes started watering last night and haven't stopped . . . .

youd never make it as a microcontroller guy, you know.

--
dave hillstrom mhm15x4 zrbj

<This space for rent.>

mimus

On Wed, 26 Dec 2007 12:42:39 -0500, dave hillstrom wrote:

> On Wed, 26 Dec 2007 10:37:31 -0500, mimus <tinmimus99@hotmail.com>
> wrote:
>
>>I've been using gedit to text-search a readelf file-dump of my
>>libc-2.3.5.so C runtime library's .dynsym table to get the --start- and
>>--stop-addresses objdump needs to allow me to look at the assembly code
>>libc provides for the standard C library functions.
>>
>>This is bad.
>>
>>(And what idiot committee decided to put the start-addresses in hex and
>>the lengths of the snippets in decimal? twisted mofoes.)
>>
>>For example, here's the libc-2.3.5.so .dynsym line for the standard C
>>string function strcpy(), which copies a string into a new location:
>>
>>00066a8c 35 FUNC GLOBAL DEFAULT 11 strcpy@@GLIBC_2.0
>>
>>here's the resulting objdump command (I was in the /lib directory):
>>
>>objdump -d --no-show-raw-insn --start-address=0x00066a8c --stop-address=0x00066aaf libc-2.3.5.so
>>
>>and here's the output of that command:
>>
>>libc-2.3.5.so: file format elf32-i386
>>
>>Disassembly of section .plt:
>>Disassembly of section .text:
>>
>>00066a8c <strcpy>:
>> 66a8c: push %ebp
>> 66a8d: mov %esp,%ebp
>> 66a8f: push %esi
>> 66a90: mov 0x8(%ebp),%esi
>> 66a93: mov 0xc(%ebp),%edx
>> 66a96: mov %esi,%eax
>> 66a98: sub %edx,%eax
>> 66a9a: lea 0xffffffff(%eax),%ecx
>> 66a9d: movzbl (%edx),%eax
>> 66aa0: add $0x1,%edx
>> 66aa3: test %al,%al
>> 66aa5: mov %al,(%edx,%ecx,1)
>> 66aa8: jne 66a9d <strcpy+0x11>
>> 66aaa: mov %esi,%eax
>> 66aac: pop %esi
>> 66aad: pop %ebp
>> 66aae: ret
>>
>>My eyes started watering last night and haven't stopped . . . .
>
> youd never make it as a microcontroller guy, you know.

I'm kind of irritated by this "run-time library" business, but I can see
the reasoning, and it _is_ all whippin' back and forth in RAM.

--
tinmimus99@hotmail.com

smeeter 11 or maybe 12

mp 10

mhm 29x13

+++ Divide By Cucumber Error. Please Reinstall Universe And Reboot. +++

< Hex

Shirley

"mimus" <tinmimus99@hotmail.com> wrote in message
news:__Cdnekrbuc_Fe_anZ2dnUVZ_jydnZ2d@giganews.com ...
> On Wed, 26 Dec 2007 11:18:56 -0500, Shirley wrote:
>
>> "mimus" <tinmimus99@hotmail.com> wrote in message
>> news:q56dnXjK9Lmw6O_anZ2dnUVZ_uevnZ2d@giganews.com ...
>>
>>> I've been using gedit to text-search a readelf file-dump of my
>>> libc-2.3.5.so C runtime library's .dynsym table to get the --start- and
>>> --stop-addresses objdump needs to allow me to look at the assembly code
>>> libc provides for the standard C library functions.
>>>
>>> This is bad.
>>>
>>> (And what idiot committee decided to put the start-addresses in hex and
>>> the lengths of the snippets in decimal? twisted mofoes.)
>>>
>>> For example, here's the libc-2.3.5.so .dynsym line for the standard C
>>> string function strcpy(), which copies a string into a new location:
>>>
>>> 00066a8c 35 FUNC GLOBAL DEFAULT 11 strcpy@@GLIBC_2.0
>>>
>>> here's the resulting objdump command (I was in the /lib directory):
>>>
>>> objdump -d --no-show-raw-insn --start-address=0x00066a8c --stop-address=0x00066aaf
>>> libc-2.3.5.so
>>>
>>> and here's the output of that command:
>>>
>>> libc-2.3.5.so: file format elf32-i386
>>>
>>> Disassembly of section .plt:
>>> Disassembly of section .text:
>>>
>>> 00066a8c <strcpy>:
>>> 66a8c: push %ebp
>>> 66a8d: mov %esp,%ebp
>>> 66a8f: push %esi
>>> 66a90: mov 0x8(%ebp),%esi
>>> 66a93: mov 0xc(%ebp),%edx
>>> 66a96: mov %esi,%eax
>>> 66a98: sub %edx,%eax
>>> 66a9a: lea 0xffffffff(%eax),%ecx
>>> 66a9d: movzbl (%edx),%eax
>>> 66aa0: add $0x1,%edx
>>> 66aa3: test %al,%al
>>> 66aa5: mov %al,(%edx,%ecx,1)
>>> 66aa8: jne 66a9d <strcpy+0x11>
>>> 66aaa: mov %esi,%eax
>>> 66aac: pop %esi
>>> 66aad: pop %ebp
>>> 66aae: ret
>>>
>>> My eyes started watering last night and haven't stopped . . . .
>>
>> Speeds up process of finding mimus a girlfriend.
>
> Don't try to tamper with my budding relationship with Libby C. here,
> woman.

Who is Libby C.?

Did someone send a memo out and I somehow missplaced mine?

<strains to hear soft music playing>

<hear mimus spouting poetry>

>
> --
> tinmimus99@hotmail.com
>
> smeeter 11 or maybe 12
>
> mp 10
>
> mhm 29x13
>
> You want a job and a lizard to ride?
>
> < _The Einstein Intersection_
>

mimus

On Wed, 26 Dec 2007 14:06:09 -0500, Shirley wrote:

> "mimus" <tinmimus99@hotmail.com> wrote in message
> news:__Cdnekrbuc_Fe_anZ2dnUVZ_jydnZ2d@giganews.com ...
>
>> On Wed, 26 Dec 2007 11:18:56 -0500, Shirley wrote:
>>
>>> "mimus" <tinmimus99@hotmail.com> wrote in message
>>> news:q56dnXjK9Lmw6O_anZ2dnUVZ_uevnZ2d@giganews.com ...
>>>
>>>> I've been using gedit to text-search a readelf file-dump of my
>>>> libc-2.3.5.so C runtime library's .dynsym table to get the --start- and
>>>> --stop-addresses objdump needs to allow me to look at the assembly code
>>>> libc provides for the standard C library functions.
>>>>
>>>> This is bad.
>>>>
>>>> (And what idiot committee decided to put the start-addresses in hex and
>>>> the lengths of the snippets in decimal? twisted mofoes.)
>>>>
>>>> For example, here's the libc-2.3.5.so .dynsym line for the standard C
>>>> string function strcpy(), which copies a string into a new location:
>>>>
>>>> 00066a8c 35 FUNC GLOBAL DEFAULT 11 strcpy@@GLIBC_2.0
>>>>
>>>> here's the resulting objdump command (I was in the /lib directory):
>>>>
>>>> objdump -d --no-show-raw-insn --start-address=0x00066a8c --stop-address=0x00066aaf
>>>> libc-2.3.5.so
>>>>
>>>> and here's the output of that command:
>>>>
>>>> libc-2.3.5.so: file format elf32-i386
>>>>
>>>> Disassembly of section .plt:
>>>> Disassembly of section .text:
>>>>
>>>> 00066a8c <strcpy>:
>>>> 66a8c: push %ebp
>>>> 66a8d: mov %esp,%ebp
>>>> 66a8f: push %esi
>>>> 66a90: mov 0x8(%ebp),%esi
>>>> 66a93: mov 0xc(%ebp),%edx
>>>> 66a96: mov %esi,%eax
>>>> 66a98: sub %edx,%eax
>>>> 66a9a: lea 0xffffffff(%eax),%ecx
>>>> 66a9d: movzbl (%edx),%eax
>>>> 66aa0: add $0x1,%edx
>>>> 66aa3: test %al,%al
>>>> 66aa5: mov %al,(%edx,%ecx,1)
>>>> 66aa8: jne 66a9d <strcpy+0x11>
>>>> 66aaa: mov %esi,%eax
>>>> 66aac: pop %esi
>>>> 66aad: pop %ebp
>>>> 66aae: ret
>>>>
>>>> My eyes started watering last night and haven't stopped . . . .
>>>
>>> Speeds up process of finding mimus a girlfriend.
>>
>> Don't try to tamper with my budding relationship with Libby C. here,
>> woman.
>
> Who is Libby C.?

She's just some chick.

> Did someone send a memo out and I somehow missplaced mine?

That happens to me all the time.

The best was the time I was driving _through_ Ohio and _over the Great
River to_ West Virginia, and, like, the bridge was gone . . . .

--
tinmimus99@hotmail.com

smeeter 11 or maybe 12

mp 10

mhm 29x13

The roads crawled in all directions like
crayfish poured out of a bag.

< Gogol

Shirley

"mimus" <tinmimus99@hotmail.com> wrote in message
news:4I-dnQl41K67Mu_anZ2dnUVZ_jydnZ2d@giganews.com...
> On Wed, 26 Dec 2007 14:06:09 -0500, Shirley wrote:
>
>> "mimus" <tinmimus99@hotmail.com> wrote in message
>> news:__Cdnekrbuc_Fe_anZ2dnUVZ_jydnZ2d@giganews.com ...
>>
>>> On Wed, 26 Dec 2007 11:18:56 -0500, Shirley wrote:
>>>
>>>> "mimus" <tinmimus99@hotmail.com> wrote in message
>>>> news:q56dnXjK9Lmw6O_anZ2dnUVZ_uevnZ2d@giganews.com ...
>>>>
>>>>> I've been using gedit to text-search a readelf file-dump of my
>>>>> libc-2.3.5.so C runtime library's .dynsym table to get the --start-
>>>>> and
>>>>> --stop-addresses objdump needs to allow me to look at the assembly
>>>>> code
>>>>> libc provides for the standard C library functions.
>>>>>
>>>>> This is bad.
>>>>>
>>>>> (And what idiot committee decided to put the start-addresses in hex
>>>>> and
>>>>> the lengths of the snippets in decimal? twisted mofoes.)
>>>>>
>>>>> For example, here's the libc-2.3.5.so .dynsym line for the standard C
>>>>> string function strcpy(), which copies a string into a new location:
>>>>>
>>>>> 00066a8c 35 FUNC GLOBAL DEFAULT 11 strcpy@@GLIBC_2.0
>>>>>
>>>>> here's the resulting objdump command (I was in the /lib directory):
>>>>>
>>>>> objdump -d --no-show-raw-insn --start-address=0x00066a8c --stop-address=0x00066aaf
>>>>> libc-2.3.5.so
>>>>>
>>>>> and here's the output of that command:
>>>>>
>>>>> libc-2.3.5.so: file format elf32-i386
>>>>>
>>>>> Disassembly of section .plt:
>>>>> Disassembly of section .text:
>>>>>
>>>>> 00066a8c <strcpy>:
>>>>> 66a8c: push %ebp
>>>>> 66a8d: mov %esp,%ebp
>>>>> 66a8f: push %esi
>>>>> 66a90: mov 0x8(%ebp),%esi
>>>>> 66a93: mov 0xc(%ebp),%edx
>>>>> 66a96: mov %esi,%eax
>>>>> 66a98: sub %edx,%eax
>>>>> 66a9a: lea 0xffffffff(%eax),%ecx
>>>>> 66a9d: movzbl (%edx),%eax
>>>>> 66aa0: add $0x1,%edx
>>>>> 66aa3: test %al,%al
>>>>> 66aa5: mov %al,(%edx,%ecx,1)
>>>>> 66aa8: jne 66a9d <strcpy+0x11>
>>>>> 66aaa: mov %esi,%eax
>>>>> 66aac: pop %esi
>>>>> 66aad: pop %ebp
>>>>> 66aae: ret
>>>>>
>>>>> My eyes started watering last night and haven't stopped . . . .
>>>>
>>>> Speeds up process of finding mimus a girlfriend.
>>>
>>> Don't try to tamper with my budding relationship with Libby C. here,
>>> woman.
>>
>> Who is Libby C.?
>
> She's just some chick.

When the wedding bells ring...do I get an invitation?

>
>> Did someone send a memo out and I somehow missplaced mine?
>
> That happens to me all the time.
>
> The best was the time I was driving _through_ Ohio and _over the Great
> River to_ West Virginia, and, like, the bridge was gone . . . .

What did you do?

>
> --
> tinmimus99@hotmail.com
>
> smeeter 11 or maybe 12
>
> mp 10
>
> mhm 29x13
>
> The roads crawled in all directions like
> crayfish poured out of a bag.
>
> < Gogol
>