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: Information on 2.2.0, and 2.1.3 patch  (Read 376340 times)

xushi

  • Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 45
    • http://xushi.co.uk
Re: Information on 2.2.0, and 2.1.3 patch
« Reply #30 on: November 13, 2007, 04:08:45 PM »

Quote
amulecmd also doesn't seem to connect properly.
I heard other reports.

Quote
amuleweb shows KAD as one state, while amulecmd shows it as another state, while amule shows it as a third state.. which is it? connected? disconnected? firewalled?
Not on my machine. Can you please be more specific? When this happen? What is correct state? What is reported where?

Quote
I still can't search.. Searching through amuleweb gives no results
Works fine for me.

Quote
amuleweb is really weird when it comes to connecting to Servers
I don't know what are you talking about.

Quote
I still get amuleweb segfaults on amd64 using it.
Not very informative. I can not test such thing since I don't have amd64, so please provide more info if you want see this fixed.


Sure thing. Yea i'll get you more information as soon as I have the time in the weekend. Maybe submit a bug report for each of the list above.

But there's one thing i'm having trouble with, and that's gathering debug info from gdb when amuleweb segfaults. If i run gdb on amuleweb itself, it does not get binded with amuled. If i run gdb on amuled, it does not detect or report anything when amuleweb crashes.

If you can give me a hand on this, i'll really appreciate it, and can offer a lot in terms of detailed bug reports.


Edit: lfroen, how about postponing this for a day or two, and I'll meet you on IRC where we can solve it more quickly ?
« Last Edit: November 13, 2007, 04:13:09 PM by xushi »
Logged
--
Avtomat KaXushnikova
\/ushi - xushi.co.uk
/\          - socialprotest.com

I am nerdier than 94% of all people. Are you nerdier? Click here to find out!

lfroen

  • Guest
Re: Information on 2.2.0, and 2.1.3 patch
« Reply #31 on: November 13, 2007, 05:18:22 PM »

Quote
But there's one thing i'm having trouble with, and that's gathering debug info from gdb when amuleweb segfaults.
Enable core dumps, and create backtrace postmortem, i.e. by loading executable (amuleweb) and core dump into gdb and executing "bt"

Quote
lfroen, how about postponing this for a day or two, and I'll meet you on IRC where we can solve it more quickly ?
Postpone what? Unfortunately I can't get to IRC, but you can reach me by mail/PM/forum.
Logged

xushi

  • Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 45
    • http://xushi.co.uk
Re: Information on 2.2.0, and 2.1.3 patch
« Reply #32 on: November 13, 2007, 08:12:48 PM »

Postpone what? Unfortunately I can't get to IRC, but you can reach me by mail/PM/forum.

Postpone getting into the errors above.. And nevermind. I'll just start a new thread or PM you later :)

Thanks for the help.
Logged
--
Avtomat KaXushnikova
\/ushi - xushi.co.uk
/\          - socialprotest.com

I am nerdier than 94% of all people. Are you nerdier? Click here to find out!

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: Information on 2.2.0, and 2.1.3 patch
« Reply #33 on: November 14, 2007, 04:52:56 AM »

Well, if you make detailed bug reports with enough information to reproduce these bugs, maybe we can help.

Cheers!
Logged

vvoody

  • Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 1
Re: Information on 2.2.0, and 2.1.3 patch
« Reply #34 on: November 24, 2007, 04:22:53 PM »

wxGTK2.8.6 can still use this patch ?
Logged

ciakah

  • Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 1
Re: Information on 2.2.0, and 2.1.3 patch
« Reply #35 on: March 20, 2008, 01:21:20 PM »

ok, applied the patch but while "make" i still get this error:
Quote
++  -DUSE_EMBEDDED_CRYPTO -W -Wall -Wshadow -Wundef -g -ggdb -fno-inline -D__DEBUG__ -fmessage-length=0 -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC    -lpthread -o amule  amule-AICHSyncThread.o amule-AddFileThread.o amule-amule.o amule-BaseClient.o amule-ClientList.o amule-ClientCreditsList.o amule-ClientTCPSocket.o amule-ClientUDPSocket.o amule-DownloadClient.o amule-DownloadQueue.o amule-EMSocket.o amule-ECSpecialCoreTags.o amule-ExternalConn.o amule-Friend.o amule-FriendList.o amule-HTTPDownload.o amule-IPFilter.o amule-KnownFileList.o amule-ListenSocket.o amule-MuleUDPSocket.o amule-SearchList.o amule-ServerConnect.o amule-ServerList.o amule-ServerSocket.o amule-ServerUDPSocket.o amule-SharedFileList.o amule-UploadBandwidthThrottler.o amule-UploadClient.o amule-UploadQueue.o amule-Kademlia.o amule-Search.o amule-Indexed.o amule-KademliaUDPListener.o amule-Prefs.o amule-RoutingZone.o amule-Contact.o amule-amule-gui.o amule-amuleDlg.o amule-AddFriend.o amule-ChatSelector.o amule-ClientDetailDialog.o amule-FileDetailDialog.o amule-KadDlg.o amule-OScopeCtrl.o amule-PartFileConvert.o amule-PrefsUnifiedDlg.o amule-SearchDlg.o amule-ServerWnd.o amule-SharedFilesWnd.o amule-StatisticsDlg.o amule-SearchListCtrl.o amule-DownloadListCtrl.o amule-ClientListCtrl.o amule-FriendListCtrl.o amule-ServerListCtrl.o amule-SharedFilesCtrl.o amule-MuleTrayIcon.o amule-TransferWnd.o amule-ClientCredits.o amule-ECSpecialMuleTags.o amule-KnownFile.o amule-GetTickCount.o amule-Logger.o amule-PartFile.o amule-Preferences.o amule-Proxy.o amule-Server.o amule-Statistics.o amule-StatTree.o amule-SHAHashSet.o amule-OtherFunctions.o -L. -lmuleappcommon -Llibs/common -Llibs/ec -lmulecommon -lec -lz  -lbfd -liberty  -L. -lmuleappcore -L. -lmuleappgui  -pthread   -L/usr/X11R6/lib   -lwx_gtk2u_adv-2.8 -lwx_gtk2u_core-2.8 -lwx_baseu_net-2.8 -lwx_baseu-2.8
/usr/local/lib/librt.so.1: undefined reference to `__fortify_fail@GLIBC_PRIVATE'
collect2: ld returned 1 exit status
make[3]: *** [amule] Error 1
make[3]: Leaving directory `/home/kit/src/aMule-2.1.3/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/kit/src/aMule-2.1.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/kit/src/aMule-2.1.3'
make: *** [all] Error 2

I'm using slack 12.0
« Last Edit: March 20, 2008, 01:24:15 PM by ciakah »
Logged

3OPAH

  • Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 8
Re: Information on 2.2.0, and 2.1.3 patch
« Reply #36 on: March 28, 2008, 08:54:23 PM »

Use the utiliy 'patch'.

example usage:  patch  < diff.file
You might have to add the -p argument followed by a number, if you run the patch of a different directory. e.g. patch -p2 < diff.file

What I did was:
1. opened http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/aMule-wx.patch?rev=1.2
2. saved it as aMule-wx.patch into the directory where I unpacked aMule-2.1.3.tar.bz2 i.e. ...something/aMule-2.1.3
3. went to that directory and typed:
> patch -Np1 -i ./aMule-wx.patch
4. continued as usual, from that directory: > ./configure; make; su -c "make install"

and here's the result - latest released package (2.1.3) for openSUSE-10.3 :

 http://rapidshare.com/files/103098841/aMule-2.1.3-1.zj.openSUSE10.3.i586.rpm

Logged
Pages: 1 2 [3]