gdb itself should have a log file too, maybe this helps: http://wiki.netbeans.org/GdbLog or not, but somewhere when you do those steps you should get a gdb log, that could help too. Once you find where it is generated, I'd advise to start from scratch, i.e, close the IDE, remove the userdir, reproduce the problem, and generate the gdb log.
And at this point you have enough info for filing an issue, though it appears to be similar or exactly this: https://netbeans.org/bugzilla/show_bug.cgi?id=169842 Aside from that, I'd advise switching to clang debugger to see if that will meet your needs. Gj On Fri, Jul 5, 2019 at 10:54 AM Ulf Zibis <ulf.zi...@cosoco.de> wrote: > Hi, > > here is the log from fresh userdir with on run of debugger. I don't see > any error, but warnings. > > -Ulf > Am 05.07.19 um 06:57 schrieb Geertjan Wielenga: > > Well, the solution is like always — start again with a fresh userdir and > recreate the problem, then you'll have log files that we can look at to see > the errors generated when the problem occurs. Also consider using a > different version of gdb to see if that makes a difference or switch from > gdb to clang debugger. In addition look on-line for issues about C/C++ > debugger breakpoints not being hit in NetBeans, I’ve seen a few issues > about that, which appears to be the problem here. > > Gj > > > On Fri, 5 Jul 2019 at 01:27, Ulf Zibis <ulf.zi...@cosoco.de> wrote: > >> Hi, >> >> now I installed NB 11.1 beta-3 from here: >> >> https://github.com/rtaneja1/netbeans/blob/installer-bin-11-1/nbbuild/installer/binaries/Apache-NetBeans-11.1-bin-linux-x64.sh >> >> With this I have the same bad results when running the debugger. :-( >> >> Aside: I said the installer to install into >> /opt/netbeans/11.1/ >> but it installed into >> /opt/netbeans/11.1/netbeans/ >> Additionally it had deleted "/usr/share/applications/netbeans >> 10.0.desktop" >> and created "/usr/share/applications/NetBeans-11.1.desktop" >> I think, this is not correct. >> >> -Ulf >> Am 04.07.19 um 23:42 schrieb Ulf Zibis: >> >> Hi Geertjan, >> >> please note, that I use NetBeans 10 (not 11.1) and I have installed it >> into "/opt/netbeans/10.0/" as root. Then I started it as root and added the >> C/C++ plugin besides few others with "Force install into shared >> directories". Hope that doesn't hurt. >> >> The starter is in "/usr/share/applications/netbeans 10.0.desktop" with: >> [Desktop Entry] >> Name=NetBeans IDE 10.0 >> Comment=Apache NetBeans IDE 10.0 >> Exec=/opt/netbeans/10.0/bin/netbeans %f >> Path=/opt/netbeans/10.0 >> Terminal=false >> Icon=/opt/netbeans/10.0/nb/netbeans.icns >> Type=Application >> Categories=Java;Development;IDE; >> MimeType=application/x-jar;application/x-java; >> >> Then I copied the project files into "~/Projects/ffmpeg/test". >> Then I started NB as normal user and created a new "C/++ Project with >> existing sources" in "~/Projects/ffmpeg/test". >> It automatically started to build and failed with: >> cd '/home/ich/Projects/ffmpeg/test' >> /bin/sh ./configure CC=/usr/bin/gcc CXX=/usr/bin/g++ CFLAGS="-g3 >> -gdwarf-2" CXXFLAGS="-g3 -gdwarf-2" >> Unknown option "CC=/usr/bin/gcc". >> See ./configure --help for available options. >> >> RUN FAILED (exit value 1, total time: 293ms) >> >> So I had to configure: >> Pre-Build -> Command Line: ./configure >> Make -> Build Command: make >> Make -> Clean Command: make clean >> Run -> Command Line: ./ffmpeg -version >> Debug -> Debug command: ./ffmpeg_g -version >> >> Then: test -> More Build Commands -> Pre-Build: >> cd '/home/ich/Projects/ffmpeg/test' >> ./configure >> install prefix /usr/local >> source path . >> C compiler gcc >> C library glibc >> ARCH x86 (generic) >> big-endian no >> runtime cpu detection yes >> standalone assembly yes >> x86 assembler nasm >> [.....] >> PRE-BUILD SUCCESSFUL (total time: 21s) >> >> Then: test -> Build: >> cd '/home/ich/Projects/ffmpeg/test' >> make >> GEN libavutil/libavutil.version >> GEN libswscale/libswscale.version >> GEN libswresample/libswresample.version >> GEN libavcodec/libavcodec.version >> GEN libavformat/libavformat.version >> GEN libavfilter/libavfilter.version >> GEN libavdevice/libavdevice.version >> CC libavdevice/alldevices.o >> [.....] >> LD ffprobe_g >> STRIP ffprobe >> >> BUILD SUCCESSFUL (total time: 24m 28s) >> >> Then: test -> Run: >> ffmpeg version N-93535-gca448f0b47 Copyright (c) 2000-2019 the FFmpeg >> developers >> built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04.1) >> configuration: >> libavutil 56. 26.100 / 56. 26.100 >> libavcodec 58. 48.100 / 58. 48.100 >> libavformat 58. 26.101 / 58. 26.101 >> libavdevice 58. 7.100 / 58. 7.100 >> libavfilter 7. 48.100 / 7. 48.100 >> libswscale 5. 4.100 / 5. 4.100 >> libswresample 3. 4.100 / 3. 4.100 >> >> RUN FINISHED; exit value 0; real time: 190ms; user: 0ms; system: 0ms >> >> Then in "fftools/ffmpeg.c" in line 4848 "register_exit(ffmpeg_cleanup);" >> I set a breakpoint. >> >> Then: test -> Debug: >> ffmpeg version N-93535-gca448f0b47 Copyright (c) 2000-2019 the FFmpeg >> developers >> built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04.1) >> configuration: >> libavutil 56. 26.100 / 56. 26.100 >> libavcodec 58. 48.100 / 58. 48.100 >> libavformat 58. 26.101 / 58. 26.101 >> libavdevice 58. 7.100 / 58. 7.100 >> libavfilter 7. 48.100 / 7. 48.100 >> libswscale 5. 4.100 / 5. 4.100 >> libswresample 3. 4.100 / 3. 4.100 >> >> The program didn't stop at the breakpoint :-( >> Shortly in the status bar I saw "Program completed, exit value 0", but as >> you can see above there is missing somthing like: >> DEBUG FINISHED; exit value 0; real time: 990ms; user: 0ms; system: 0ms >> >> So bad, that it doesn't work at me. Hopefully we finde the cause. I'll >> try to install NB 11.1 for that. >> >> -Ulf >> Am 04.07.19 um 20:30 schrieb Geertjan Wielenga: >> >> https://youtu.be/xPvasdbFJAw >> >> There it is. Tell me what to do differently as specifically as possible, >> if needed, and I'll do it to reproduce your requirements. >> >> Gj >> >> On Thu, Jul 4, 2019 at 8:08 PM Ulf Zibis <ulf.zi...@cosoco.de> wrote: >> >>> Sorry, I think I don't understand your question. >>> >>> If you were able to run the bebugger with "./ffmpeg --version" then with >>> "./ffmpeg_g -i sample.jpg result.jpg" it should be the same ... if you have >>> prepared a "sample.jpg" in start dir. >>> >>> -Ulf >>> Am 04.07.19 um 19:59 schrieb Geertjan Wielenga: >>> >>> But how to run the debugger on that? >>> >>> Gj >>> >>> On Thu, Jul 4, 2019 at 7:54 PM Ulf Zibis <ulf.zi...@cosoco.de> wrote: >>> >>>> The simplest command line for real world is: >>>> ./ffmpeg_g -i sample.jpg result.jpg >>>> >>>> -Ulf >>>> Am 04.07.19 um 19:29 schrieb Ulf Zibis: >>>> >>>> The main() function is in fftools/ffmpeg.c >>>> I think you can set a breakpoint there for a first test. Maybe set it >>>> at line 4869 where show_banner(argc, argv, options); is called, so you can >>>> test what happens when jumping in. >>>> For first try just run ./ffmpeg_g (stands for gdb and includes symbols) >>>> without arguments or try ./ffmpeg_g --version. >>>> >>>> Curious if that works. >>>> >>>> -Ulf >>>> >>>> > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org > For additional commands, e-mail: users-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
