aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Pages: 1 [2] 3

Author Topic: crashes while searching for resource  (Read 8443 times)

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2505
  • The last shadow you'll ever see
Re: crashes while searching for resource
« Reply #15 on: June 15, 2006, 11:58:05 PM »

I was already ignoring him. That moron has ignore mode set a long time ago. Since I got blind to be exact. :D

If Gerd78 wants to continue helping, it's ok to me. After all, a bug is a bug, it doesn't matter if the original reporter is an asshole.
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5823
Re: crashes while searching for resource
« Reply #16 on: June 16, 2006, 02:17:58 AM »

Yeah, except the original poster can't reply anymore :P
Logged

Gerd78

  • Hero Member
  • *****
  • Karma: 9
  • Offline Offline
  • Posts: 681
Re: crashes while searching for resource
« Reply #17 on: June 16, 2006, 04:39:55 AM »

Quote
Originally posted by phoenix
Any kind of search? Kad, local, global?
You mean the exact circumstances of the crash?

I did a local search for "twierdza" and afterwards a global search for the same term, then it crashed.
Quote
Originally posted by phoenix
Does not segfault here.
It doesn't segfault here either if I do a global search without doing a local search for the same term before.



EDIT: Strange. I did the following tests:

Local search for "bla": OK.

Restart

Global search for "bla": OK.

Restart

Local and then Global search for "bla": Crash

Restart

Global and then local search for "bla": Crash

Restart

Local search for "bla" and then "blubb": Crash

Restart

Global search for "bla" and then "blubb": Crash



At that point I stopped testing, because it looks like every second search crashes.

The backtrace is always the same. And actually I think that it has nothing to do with korner's problem.
« Last Edit: June 16, 2006, 04:50:59 AM by Gerd78 »
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5823
Re: crashes while searching for resource
« Reply #18 on: June 16, 2006, 05:12:50 AM »

Good old "second search crashes"
Logged

Gerd78

  • Hero Member
  • *****
  • Karma: 9
  • Offline Offline
  • Posts: 681
Re: crashes while searching for resource
« Reply #19 on: June 16, 2006, 05:44:52 PM »

Logged

stephen71

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 10
aMule 2.1.3 suse 10.1 64 bit
« Reply #20 on: June 16, 2006, 05:55:06 PM »

I have the same problem. After second search aMule crashes. ;( ;( ;(

Mah.............

aMule 2.1.3 CVS on
Suse 10.1 64 bit
« Last Edit: June 16, 2006, 06:03:08 PM by stephen71 »
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2505
  • The last shadow you'll ever see
Re: crashes while searching for resource
« Reply #21 on: June 17, 2006, 02:02:32 AM »

Gerd78,

I have a theory. Your line numbers do not match mine. So, I believe that your Scanner.cpp has been regenerated in the build process. Maybe it is a problem with Suse's lex.

Please, try to do the following:

1) Untar aMule and save a copy of Scanner.cpp and Scanner.h as they are inside the tar ball.
2) Build aMule.
3) Restore the saved copies and build again, but now just "make" and make sure lex does not regenerate them. You'll probably have to delete the object file too.
4) Test the search.

Kry, if that is the reason, we must find a solution for that lex problem.

Line 757 in your Scanner.cpp is line 772 in mine.
Code: [Select]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1226234192 (LWP 16829)]
0x08379760 in yylex () at Scanner.cpp:757
757                     *yy_cp = (yy_hold_char);
(gdb) bt
#0  0x08379760 in yylex () at Scanner.cpp:757
#1  0x0837a2de in yyparse () at Parser.cpp:1273
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4236
Re: crashes while searching for resource
« Reply #22 on: June 17, 2006, 09:48:49 AM »

hmm works fine on gentoo, all scenarios posted by gerd78 worked here..

$ flex --version
flex 2.5.33
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

Gerd78

  • Hero Member
  • *****
  • Karma: 9
  • Offline Offline
  • Posts: 681
Re: crashes while searching for resource
« Reply #23 on: June 17, 2006, 09:54:30 AM »

Quote
Originally posted by phoenix
I have a theory. Your line numbers do not match mine. So, I believe that your Scanner.cpp has been regenerated in the build process. Maybe it is a problem with Suse's lex.
See my post above (the one from 2006-06-15 17:39 - maybe it was lost between the long backtraces): Yes, the line numbers do not match because Scanner.cpp and Scanner.h were rebuilt, but I did not request that - it happened because the time stamps in the CVS tarball seem to be screwed up.
Code: [Select]
ls -l Scanner.*
-rw-r--r-- 1 user users 53361 2006-03-21 05:52 Scanner.cpp
-rw-r--r-- 1 user users  6439 2006-03-20 11:57 Scanner.h
-rw-r--r-- 1 user users    90 2006-06-13 19:59 Scanner.h.in
-rw-r--r-- 1 user users  4484 2006-03-21 05:52 Scanner.l
This basically means:

Scanner.h.in > Scanner.cpp = Scanner.l > Scanner.h

But IMHO it should be:

Scanner.cpp = Scanner.h > Scanner.h.in > Scanner.l

I just tried the following things:

1) In the CVS tarball, forced Scanner.cpp and Scanner.h to not be rebuilt by "touching" them.

Result: No crash.

2) Exactly the opposite for 2.1.3: Forced Scanner.cpp and Scanner.h to be rebuilt by deleting them.

Result: No crash either.

This makes me wonder if something changed there. In any case, something is wrong with the timestamps because the files are not intended to be rebuilt by users, but it happens anyway.
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5823
Re: crashes while searching for resource
« Reply #24 on: June 17, 2006, 01:28:51 PM »

Yeah. Stupid svn::prop
Logged

Gerd78

  • Hero Member
  • *****
  • Karma: 9
  • Offline Offline
  • Posts: 681
Re: crashes while searching for resource
« Reply #25 on: June 18, 2006, 11:53:38 AM »

Just for information, the results of more tests:

1) flex-2.5.4a compiled from Vanilla sources:

Fails to compile Scanner.cpp, yylex_destroy undeclared.

2) flex-2.5.31 compiled from Vanilla sources:

Crashes on second search as discussed here.

3) flex-2.5.33 compiled from Vanilla sources:

No crash.
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4236
Re: crashes while searching for resource
« Reply #26 on: June 18, 2006, 12:45:21 PM »

^^ good old gentoo being up2date
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

kreegee

  • Full Member
  • ***
  • Karma: 2
  • Offline Offline
  • Posts: 161
    • http://kreegee.cycovery.com
Re: crashes while searching for resource
« Reply #27 on: June 18, 2006, 03:37:26 PM »

btw, compiling with flex-2.5.4a-296 works fine here, but i needed to touch them (the scanner files) so they don't rebuild.

didn't tested the search though, as i only use amuled.

btw, if you use rpm, you might as well just add a "touch src/Scanner.*" after "%setup -q -n amule-cvs" in the spec-file, so you don't have to unpack/touch/pack again for each test...
« Last Edit: June 18, 2006, 03:43:08 PM by kreegee »
Logged

Gerd78

  • Hero Member
  • *****
  • Karma: 9
  • Offline Offline
  • Posts: 681
Re: crashes while searching for resource
« Reply #28 on: June 18, 2006, 03:44:41 PM »

If you touch them, they will not be rebuilt and you don't need any flex at all, neither 2.5.4a nor 2.5.31 or anything else. That's because the one in the tarball was generated with flex-2.5.33.

The above doesn't mean "flex-2.5.4a doesn't compile", but "the Scanner.cpp generated by flex-2.5.4a doesn't compile". Your local flex is not even used if you correct the timestamps by touching the included Scanner.cpp.

Btw. 2.5.31 is also the version used by Debian Sarge, I've just extracted the flex binary from the Sarge package, used that to regenerate Scanner.cpp and it shows exactly the same crash.
« Last Edit: June 18, 2006, 07:48:04 PM by Gerd78 »
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4236
Re: crashes while searching for resource
« Reply #29 on: June 18, 2006, 08:06:48 PM »

kry uses unstable/experimental, he probably has 2.5.33...
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."
Pages: 1 [2] 3