Jump to content

ntavendale

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

6 Neutral

Technical Information

  • Delphi-Version
    Delphi 10.3 Rio
  1. ntavendale

    Sydney, debugger not working on Ubuntu LTS 20.04

    The PA Server might be expecting certain versions of the debug libraries. My suggestion would be to try Ubuntu 18.04 and see if that works.
  2. Trying to get Linux Development running using Ubuntu And WSL on Windows 10. Followed instructions found here: https://community.idera.com/developer-tools/b/blog/posts/targeting-windows-10-s-windows-subsystem-for-linux-with-delphi-for-linux I can run run the Hellow World example without the debugger - it prints "Hello World" in PA server just fine. But when trying to run it with the debugger I get the following in the Delphi IDE Event Log using both 10.3 & 10.4: GNU gdb (GDB) 7.3.1-gg2 (Embarcadero:gdb-28919) (Wed Jul 19 10:41:36 UTC 2017) Process delphi_demo (86) Copyright (C) 2011 Free Software Foundation, Inc. Process delphi_demo (86) with modifications copyright 2017 Embarcadero Technologies, Inc. Process delphi_demo (86) linked with iconv (GNU libiconv 1.14) written by Bruno Haible, copyright (C) 2000-2011 Free Software Foundation, Inc. Process delphi_demo (86) License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. Process delphi_demo (86) This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: Process delphi_demo (86) <http://www.gnu.org/software/gdb/bugs/>. Process delphi_demo (86) Module Load: delphi_demo. Has Debug Info. Base Address: $0000000000412B70. Process delphi_demo (86) Module Load: ld-linux-x86-64.so.2. Has Debug Info. Base Address: $00007FFFFF400F10. Process delphi_demo (86) Module Load: linux-vdso.so.1. No Debug Info. Base Address: $0000000000000000. Process delphi_demo (86) [Thread debugging using libthread_db enabled] Process delphi_demo (86) Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Process delphi_demo (86) Module Load: libpthread.so.0. Has Debug Info. Base Address: $00007FFFFF1E5BB0. Process delphi_demo (86) Module Load: libgcc_s.so.1. Has Debug Info. Base Address: $00007FFFFEFC2AC0. Process delphi_demo (86) Module Load: libc.so.6. Has Debug Info. Base Address: $00007FFFFEBE12D0. Process delphi_demo (86) Module Load: libdl.so.2. Has Debug Info. Base Address: $00007FFFFE9B0E50. Process delphi_demo (86) Module Load: libm.so.6. Has Debug Info. Base Address: $00007FFFFE61BA80. Process delphi_demo (86) Cannot find user-level thread for LWP 86: generic error Process delphi_demo (86) I know I'm probably doing something wrong, I just cant figure out what.
  3. I have a collection of Syslog and Windows Event Log Utilities. All 100% developed in Delphi. http://www.allthingssyslog.com/ They are intended for use in testing. Unfortunately I can't put links to the actual tool pages as the site is a single page React Web Application at the moment. Will convert to ASP .Net when I get hosting sorted out. There is a menu in the top right corner of the page which is easy enough to navigate. Go to the Downloads to access the following: 1) The Simulator. This allows you to send test messages to your Syslog server, Log Management system or whatever. Messages can be edited, sent on demand, sent in repeating batches etc. 2) The Windows Event Log Converter. This utility will read entries in a Windows Event Log and forward them to a Syslog Server. There is also a YouTube channel with tutorials on using these utilities here: https://www.youtube.com/channel/UCg97aUZMTKlqMNA_Qxc8wWA Most recently I updated the UIs to make them multi lingual. I just hope google translate didn't give me the German/French/Italian/Dutch equivalent of Engrish. Go to the Utilities page for some extra stuff 1) A basic test Syslog Receiver. It takes messages on UDP and dumps them to a file. Noting special, not even good performance, but useful for demoing basic principles in videos. 2) A Windows Event Log Writer. Works pretty much the same as the simulator, but instead of sending messages to a Syslog receiver, It dumps them in a local Event Log. Using batches it can write up to 12k logs/sec into a Windows Even Log. I originally started writing this stuff to do dev testing on a log management system, but the company was never interested in building out a serious testing architecture. After I left I kept working on them. I still find them useful on occasion, maybe others will too.
×